Show $FPT partitions and their details, like in a normal Engine region. The current implementation is exactly what I meant. I don't have any FPT parsing yet (was interested in code much more than in data) Implement workaround for last volume in IFWI 2.0 region to not cross the region boundary.I'd really like to disagree here, but I haven't ever seen an image that's not broken this way, so it's probably the only suitable approach. The last FFS volume size crossing over DevExp1 should be fixed automatically by UEFITool in my opinion If UEFITool can automatically adjust it and fix it upon rebuilding (when that's implemented) then great.ĭevExp1 region is populated with CSTXE $FPT Data could you please attach such an initialized dump I guess it is similar in nature to the stupid OEM practice a few years back when they left the BIOS limit to 0x0 at the Flash Descriptor. The classic (at this point) APL/GLK bug with the last FFS volume size crossing over DevExp1 should be fixed automatically by UEFITool in my opinion. If an $FPT is found, parse it like it's a regular Engine region. Currently DevExp1 is not parsed by UEFITool but it should be very simple. It's basically the extension of the IFWI for Engine data, after first boot. At BPDT v2 (IFWI 1.7) it is 4 bytes (CRC-32) and covers BPDT (Header + Entries) without Signature.Īt dumped/initialized APL/GLK images, the DevExp1 region is populated with CSTXE $FPT Data modules (the same Data/Non-Code modules as found at the IFWI 1.6 CSME structure - which is actually called CSE Layout Table). At BPDT v1 (IFWI 1.6 & 2.0) it is 2 bytes (CRC-16 ?) and covers data from BPDT up to and including S-BPDT. It's not used at APL/GLK but it is used at other platforms so it might be useful to add that if its value is not 0. The BPDT Checksum does not seem to be checked or displayed. It's probably always 0x200 (min) for now as not a lot of entries are needed. The minimum size for BPDT header is 0x200 and the maximum is 0x1000 so such an adjustment can remove the padding after it. I'm going to ignore CSE firmware related IFWI module bugs for this issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |