Open
Description
There's a second ROM header format that includes the .irom0.text at the beginning of flash. The tool will currently complain about a magic number mismatch (0xe9 != 0xea) and fail to parse. A painful workaround is to massage the flash dump into the old format, but it would be nice if the tool supported this case.
Metadata
Assignees
Labels
No labels
Activity
detect new ROM headers and raise a more informative exception #3
Made EspRomHeader class smarter - it can now identify both header typ…
moved logic for reading irom0.text in non-OTA case to esp_rom - this …
made EspRomSection smarter - we can specify an address and size for a…
Pull irom0.text from the appropriate location depending on the header…
stayliv3 commentedon Jul 14, 2017
i meet the condition. how to massage the flash dump into the old format? thanks
zayfod commentedon Dec 5, 2019
Added support for 0xea headers here: https://github.com/zayfod/esp-bin2elf