Coredump-info keeps asking for port when trying to decode text file

ua100k
Posts: 1
Joined: Mon Feb 05, 2024 1:36 pm

Coredump-info keeps asking for port when trying to decode text file

Postby ua100k » Mon Feb 05, 2024 1:42 pm

version 5.1 esp-edf, using powershell

running idf.py coredump-info -C <project directory> -c <dump file name>

I get the error "serial port COM4 COM4 failed to open.


according to the online help pages, there is no direction there for this other then -c option.

According to the --help of coredump-info, -C is the directory of the project and -c is the dump file and if the port is not specified, it is read from the file.

However this is not working and I cannot find any help on using the coredump utilities other then the online help page which appears to be outdated or wrong.

What is the correct syntex to read the text dump file taken from the UART output and stored in a file on windows 10.

Thanks.

ESP_pdragun
Posts: 12
Joined: Fri Dec 02, 2022 2:18 pm

Re: Coredump-info keeps asking for port when trying to decode text file

Postby ESP_pdragun » Tue Feb 06, 2024 8:11 am

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 COM4 coredump-info -C <project directory> -c <dump file name>

The port number should not matter in this case and it is NOT going to be used (AFAIK can be even port that does not exist). There was a bug when you did not set the port the ESP-IDF would try to autodetect the port - which is not needed anywhere because you are passing the core file. By setting any port you bypass this port detection.

Please let me know if that helps or if you need anything else.

Who is online

Users browsing this forum: Bing [Bot] and 203 guests