This topic continues from https://github.com/espressif/openocd-esp32/issues/326

In the meantime, I have tested together IDF v4.4 + esp-coredump 0.4.0 with the binary and elf formatted coredump data. Both are ok for me. I didn't need to trim the header using the 'raw' type espcoredump.py info_corefile -t raw -c core.elf build/blink.elf espcoredump.py info_corefile -t raw -c core...

Is it possible to send your decoded coredump file? You can create an issue here and attach the file. https://github.com/espressif/esp-coredump Or, if you can create an app to reproduce the issue, it would be perfect. Looks like something is broken in the crashed task TCB/stack and can not be parsed ...

And what happens when you try to run the below command without trimming the header part?

At the beginning of the coredump elf file, there is a header part which is 20 Bytes in IDF-4.4. You have to trim that part before passing it to the espcoredump.py On linux, something like; dd bs=20 skip=1 if=core.elf of=trimmed.elf Then; espcoredump.py --chip esp32 info_corefile -c trimmed.elf -t el...

I gave a try with Jlink-EDU which has v10 firmware and seems no issue for me. I have used hello-world example. Adapter speed is 5000khz. 100khz is pretty slow and that is the reason you are getting some timeout warnings. Debugger config options; -s ${openocd_path}/share/openocd/scripts -c 'adapter s...

Attached in to the https://github.com/espressif/openocd-esp32/issues/218

Looks like the same issue. https://github.com/espressif/openocd-esp32/issues/218