This would be my fault. If the size of ME region is between 0x17D000 and 0x1FFFFF, I assumed it is ME 1.5 and cut it at 0x17D000, without checking if the rest is actually padding. This worked for the firmwares I had until now, so I was lazy to do a proper check. But now I added a check of the padding, to at least avoid cutting useful bytes and extract the full region if the padding is not empty. I should work on a proper size checking and extraction, but I remember that some ME firmwares have a different base for calculating the offset of modules, so that is why I ignored it for some time. Other ME firmwares are unaffected, because I extracted the entire region as is.

What is strange is that we have Skylake before a proper release of Broadwell. Have they screwed that bad or just not enough reasons (competition included) to release it in time? At least he have a chance to support Skylake from alpha stages.

The modules have sub-modules with a similar header as the main ME header?

I see you are using your mind reading ability again. Shame on you!

Now to being serious. It seems that way: name + offset + size + function + something else.

Edit: but they do. The base is the module start. Check again how the sub-modules are formed.

Here is an example:



No, ME Analyzer needs its special place. You worked hard on it. There is not point for me in doing the same thing (and doing it worse, for that matter). My only need is version, date is size.

It seems to be name [0xC] + offset1 [4] + size1 [4] + reserved [4] + next [0xC] + offset2 [4] + size2 [4] + reserved [4] ?

Replace offset with pointer to be more accurate.

By looking backwards, the second pointer is not needed.

After MN2 seems to be similar? Name [0xC or 0xE] + [FFFF or 0000FFFF] + size [4] + SHA256.



The size is the same as the one from the main module header.

Taking touch_fw.met as example:

- begins at start + 21BE, size = 10E.
- select block 1091BE - 1092CB.

You don't need to go backwards literally. Of course they are parsed in order, but that was to point that each sub-module header takes 0x18 or 0x30 if they need the .met part.

Maybe plat_n_sku and bup_sku?