ESP32 Forum

My coredump is set to save as an ELF image to a flash partition (ESP32-C3, IDF v5.1).
I can create a panic and successfully get the coredump info from the device using the following command: The above command connects to the device in boot mode, fetches the ELF from the partition, saves it to disk (-s option), then examines it and prints the info.

In the field, I want to upload the image myself and process it offline. The "coredump-info" command has a "--core" option that is supposed to take the downloaded file and use that INSTEAD of going to the device and getting the coredump contents.

However, when I issue the following command it ALWAYS tries to go to the device (COM port) and will NEVER use the file supplied (which IT saved previously). There is also NO debug/prints to tell you what/why it's not using it:
Can someone enlighten me as to why this is happening?
According to this help page https://docs.espressif.com/projects/esp ... _dump.html, I should be able to do just this (albeit from a Serial port dump); I've even tried b64 encoding it to no avail (though I did check the Python and it will recognize ELF format).

I think this should work if you use 'raw' type, pass the core dump (as obtained from Flash partition) to the --core argument, and also include the application ELF file as the last positional argument.

Something like this:

espcoredump.py info_corefile --core coredump-from-flash.bin -t raw project.elf

I have the following SDKCONFIG options set for coredump:
As you can see, the format is set to ELF. I have confirmed, byte for byte, that the ELF file created with the "--save-core TEXT" option is identically the one that is in flash.
Also, please note that I'm using IDF v5.1 and the espcoredump.py has been replaced by "idf.py coredump-info".

So, you are correct.... I did a file find in the IDF v5.1 tree and found "espcoredump.py". After using the same downloaded ELF file that refused to work with the "idf.py coredump-info" command, it DOES work with "espcoredump.py".