Hi, can you please provide some more details? Which platform are you using (in the case of Windows also if it is command line or Powershell)? What are the versions of ESP-IDF and esp-idf-monitor (should be at the start of the output) that you are using? It would be also nice to see the output from t...

Hello, as Roland mentioned, please make sure that you have installed and exported the ESP-IDF environment correctly — run `./install.sh` and `. ./export.sh`; see https://docs.espressif.com/projects/esp-idf/en/stable/esp32/get-started/index.html . *-addr2line tools should be available in your PATH, n...

There are a couple of reasons why you may see that message: 1. Ensure that after you added esp-gdb into the path you restarted the command line (PowerShell) so the changes will get applied 2. Ensure that you have the correct toolchain architecture based on the chip you are using. You either need RIS...

Hello, if you are trying to use just a coredump I would suggest following this installation guide: https://github.com/espressif/esp-coredump?tab=readme-ov-file#installation There is also an option for standalone installation without ESP-IDF if you don't need it for anything else. You are seeing the ...

Hi, I am sorry for the inconvenience, this is a known issue that has been already resolved and should be part of the next bugfix for v5.1. You can try using the release/v5.1 branch of ESP-IDF to get the fix. Alternatively, you can use a workaround by adding a port argument like this: idf.py --port C...

Hi, the fix was released and should be now available in esp-idf-monitor 1.3.4. You can install it easily by running the install script (./install.sh) for ESP-IDF.

I am sorry for the issues. I was able to reproduce the same problem. We will fix it ASAP and I will let you know once the fix is available.

A possible workaround is to install older version of esp-idf-monitor, to install it you can run `pip install esp-idf-monitor==1.1.2` in ESP-IDF environment.

Hi Felix,

I am happy to inform you that the fix for the non-default partition table offset was backported to 4.4 in commit `4ef81211` and should be available in the next bugfix release - 4.4.7 and also soon in 5.1.

That sort of information, if not the fix, should be back ported to the 4.4 branch as that is what is shipped with ADF. Thanks for your suggestion, I will see what can be done regarding the backporting, but we will try to add some warning at least. I had moved the part table up. I shifted it back to...

Hi, the error from `espcoredump.py` usually means that the coredump partition was not found. This can be caused by e.g. having the non-default offset of the partition table (!=0x8000) or by some misconfiguration of the partition table. The bug for non-default partition offset was fixed in the master...