You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I've encountered an image (BIOS.zip) in which UEFITool can't parse DXE volume.
For example here I search for (D6A2CB7F-6A18-4E2F-B43B-9920A733700A = DxeCore) and as it can be seen this GUID is only found in the unparsed padding area:
At the same time MMTool successfully finds the DxeCore EFI module:
Not sure if this is relevant, but UEFITool outputs some debug information at the image load:
Can I get some hints about what is wrong and how can I get DXE FV and parse it with the UEFITool?
The text was updated successfully, but these errors were encountered:
The problem with this particular image is that a volume of 0x407000 bytes is inserted into an OBB region of 0x37A000 bytes, and Intel FIT (the software that created all those structures) has no diagnostics to detect that, but UEFITool has some.
It is a problem with the image itself, and it will stop being harmless and start breaking the image once the actual non-FF file content of that volume will become larger than 0x37A000.
I don't have any ideas yet on how to fix it in UEFITool other than creating "bruteforce" parsing mode that would ignore any non-UEFI structures.
Recently I've encountered an image (BIOS.zip) in which UEFITool can't parse DXE volume.
For example here I search for (
D6A2CB7F-6A18-4E2F-B43B-9920A733700A
=DxeCore
) and as it can be seen this GUID is only found in the unparsed padding area:At the same time MMTool successfully finds the
DxeCore
EFI module:Not sure if this is relevant, but UEFITool outputs some debug information at the image load:
Can I get some hints about what is wrong and how can I get DXE FV and parse it with the UEFITool?
The text was updated successfully, but these errors were encountered: