kongo wrote:The new dump (http://df.lth.se/~kongo/esp8266.bin/iram0.bin, 7b52074c61442ee4c45f59d026313fa3), should hopefully be correct.
I have made an symbol-annotated disassembly for reference (http://df.lth.se/~kongo/esp8266.bin/iram0.txt), and it looks much more sane.
Thanks for the update.
Not perfect, I know, but I'm getting tired of xt-objdump.
I feel your pain. Actually, without symbols (i.e. disassembling raw binary), it's usually much worse, with function prolog being fused with preceding padding. And I'm actually curious how you could inject symbols while disassembling a bin file?
But yeah, it's not perfect - see for example ets_run: it has "call0 dfc", but at dfc it's actually mis-disassembles it.
Btw, compiler used for that code has a funny habbit of putting big constant *before* the function which uses them, not after.
I'm planning to clean up esptool, probably integrating the image creation stuff, or perhaps make it read ELF and split it up automagically. Any and all feedback is welcome.
As long as it retains ability to works with just byte stream both internally (i.e. via separate funcs) and externally (via cmdline args), why not?