I am not entirely sure. Could be that the 48K is used by the ROM. ok, i actually miscalculated and it's 32K. but still, it is a big chunk of heap unaccounted for, would be nice to have it back or at least know that it's intentional. can you clarify it? you could possibly use this by just pointing a...

is this really all there is?
for example, have all crypto functions been removed from ROM?
i suspect not. can you please publish the list of exports and (important!) C decls / prototypes for them?
full documentation would be nice too, but headers or even just addresses would be a good start.

ok, figured it out. it's the same "first flash" bug, but the difference is that i was triggering it all the time because of my wiring. described in detail, the bug is as follows: first flash_begin after reset (toggling CHIP_PU / EN pin) will most likely fail. if it succeeds (rarely but happens), it ...

i think EN can be used to reset the device.
that said, i'm not having much success flashing the device, so take it for what it's worth...

i am also very interested in dram vs iram configuration. thanks for the explanation of the memory map Jeroen, it makes sense, except for this: in your reply you mention that the region at 0x3FFD8000 is the shared 192K segment. but there's only 144K between 0x3FFD8000 and 0x40000000 which is where RO...

Thanks! i'm getting errors though. instead of failing occasionally, for me, it will occasionally work, but fail most of time. i added some debug output and usually get this: Connecting... connected on attempt 0 Erasing flash... Erase size 1400 num_blocks 5 offset 0 (1431642119, '\x00\xa9') Traceback...

Sprite_tm wrote:esptool.py variant which can flash the ESP31

where can i get it? can you share, please?