Debugging ESP32S3 in Eclipse IDE (IEP-1299)

[jrdecesare]

Hi!
For quite some time I was able to compile and debug my ESP32S3 project. I went back to the project a few weeks later and I am now getting this error message when I debug:

Usage: idf.py Marine\BMS\Software\BMS_Test_App\build [OPTIONS]
Try 'idf.py Marine\BMS\Software\BMS_Test_App\build --help' for help.

Error: No such option: -p

It seems as if the -p is no longer an option?? I have my USB connected to my workstation as COM9. This used to work so I don't know if a windows update had something to do with this.

I also:

• downloaded the latest tools ESP-IDF-V5.3
• can compile the code succesfully
• deleted the Debug Configuration and recreated one. Problem still exists.
• Rebooted my workstation twice.

Thanks!!
John

[sigmaaa]

Hi @jrdecesare,

I could not reproduce this issue with the ESP32-S3 devkit and ESP-IDF 5.3 (I've tested the uart flashing, the serial monitor, and the openocd debugging). It's weird, that you're encountering this problem when trying to debug, as the -p argument is used for UART flashing. If you use the debug configuration (ESP-IDF GDB OpenOCD Debugging), you don't need the UART port, as flashing is done via JTAG.

If you are using the ESP32-S3 devkit, please follow these steps for debugging:

1. Create the ESP-IDF GDB OpenOCD Debugging configuration if you don't already have one.

2. Edit the Configuration and navigate to the Debugger tab -> Select the esp32s3 target and ESP32-S3 chip (via built-in USB-JTAG) board.

3. Specify Flash Size on Windows: Sometimes it's necessary to specify flash size on Windows. To do it: Open sdkconfig in your project (double-click the file). Search for Serial flasher config and set the Flash size to 4MB.

4. Connect the Device: The ESP32-S3 devkit has two micro USB ports (USB and UART). Connect to the USB port.

5. Start the Debug Session: Select the debug configuration in debug mode and click "Debug". The flash process will be done automatically via JTAG, and then the debug session should start.

[jrdecesare]

Hi Denys, Thanks for the quick reply! I actually downloaded the latest Eclipse (2024 06) and via their website, dragged over the ESP-IDF Eclipse Plugin which is here: https://marketplace.eclipse.org/content/esp-idf-eclipse-plugin I can build my application fine with no errors. ***@***.*** I created a debug configuration as such: ***@***.*** ***@***.*** When I debug, I get this error: ***@***.*** Any help would be appreciated as I’ve spent about 5 hours trying to get this to work. Thanks! John From: Denys Almazov ***@***.***> Sent: Wednesday, July 31, 2024 6:12 AM To: espressif/idf-eclipse-plugin ***@***.***> Cc: John Decesare ***@***.***>; Mention ***@***.***> Subject: Re: [espressif/idf-eclipse-plugin] Debugging ESP32S3 in Eclipse IDE (IEP-1299) (Issue #1026) Hi @jrdecesare<https://github.com/jrdecesare>, I could not reproduce this issue with the ESP32-S3 devkit and ESP-IDF 5.3 (I've tested the uart flashing, the serial monitor, and the openocd debugging). It's weird, that you're encountering this problem when trying to debug, as the -p argument is used for UART flashing. If you use the debug configuration (ESP-IDF GDB OpenOCD Debugging), you don't need the UART port, as flashing is done via JTAG. If you are using the ESP32-S3 devkit, please follow these steps for debugging: 1. Create the ESP-IDF GDB OpenOCD Debugging configuration if you don't already have one. 2. Edit the Configuration and navigate to the Debugger tab -> Select the esp32s3 target and ESP32-S3 chip (via built-in USB-JTAG) board. 3. Specify Flash Size on Windows: Sometimes it's necessary to specify flash size on Windows. To do it: Open sdkconfig in your project (double-click the file). Search for Serial flasher config and set the Flash size to 4MB. 4. Connect the Device: The ESP32-S3 has two micro USB ports (USB and UART). Connect to the USB port. 5. Start the Debug Session: Select the debug configuration in debug mode and click "Debug". The flash process will be done automatically via JTAG, and then the debug session should start. — Reply to this email directly, view it on GitHub<#1026 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKGSD7KWU2553XHXWAGYWKLZPCZ6TAVCNFSM6AAAAABLWLDA5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGE2TSMRSGA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[sigmaaa]

I can build my application fine with no errors.

@.***

I created a debug configuration as such:

@.***

@.***

When I debug, I get this error:

@.***

Hi @jrdecesare,

we can't see the screenshots. Could you please upload it again? Thank you

[jrdecesare]

Hi Denys, I have attached them in a word document. Sorry about that!! Thanks! John From: Denys Almazov ***@***.***> Sent: Wednesday, July 31, 2024 7:29 AM To: espressif/idf-eclipse-plugin ***@***.***> Cc: John Decesare ***@***.***>; Mention ***@***.***> Subject: Re: [espressif/idf-eclipse-plugin] Debugging ESP32S3 in Eclipse IDE (IEP-1299) (Issue #1026) I can build my application fine with no errors. @.*** I created a debug configuration as such: @.*** @.*** When I debug, I get this error: @.*** Hi @jrdecesare<https://github.com/jrdecesare>, we can't see the screenshots. Could you please upload it again? Thank you — Reply to this email directly, view it on GitHub<#1026 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKGSD7OJEOFW54VZIF2FZGDZPDC6ZAVCNFSM6AAAAABLWLDA5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRQGI4TSMJSGI>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[sigmaaa]

Hi @jrdecesare

we can't see the word document either. Looks like github blocking the files uploaded from the email

[jrdecesare]

Then how should I get you the files? Do you have another non github address? Thanks! John From: Denys Almazov ***@***.***> Sent: Thursday, August 1, 2024 4:03 AM To: espressif/idf-eclipse-plugin ***@***.***> Cc: John Decesare ***@***.***>; Mention ***@***.***> Subject: Re: [espressif/idf-eclipse-plugin] Debugging ESP32S3 in Eclipse IDE (IEP-1299) (Issue #1026) Hi @jrdecesare<https://github.com/jrdecesare> we can't see the word document either. Looks like github blocking the files uploaded from the email — Reply to this email directly, view it on GitHub<#1026 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKGSD7J63IOS3GT2EFVFCDTZPHTSXAVCNFSM6AAAAABLWLDA5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRSGMYDKMZUGY>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[sigmaaa]

Hi @jrdecesare,

you can send them via a browser on the GitHub page or to me at this address - [email protected]. Thanks

[sigmaaa]

Hi @jrdecesare,

the configuration that you are showing on the screenshot (ESP-IDF Application) is for flashing. For openOCD debugging, you must use the "ESP-IDF GDB OpenOCD Debugging" configuration. I've deleted the default one and recorded a small demo of how the debug should work. Please, take a look:

debug.esp32s3.demo.mp4

PS I'm using the latest master, so the icon for the configuration is different

[sigmaaa]

Hi @jrdecesare,

one more thing. It's not clear why you are having this issue:

Could you please provide an error log after you face it again by following these steps? https://github.com/espressif/idf-eclipse-plugin?tab=readme-ov-file#error-log

[sigmaaa]

Hi @jrdecesare,

Is there any update on this? Were you able to debug?

[jrdecesare]

Hey Denys, I have not yet. I am actually on vacation until next week. Thank you very much for keeping in touch. I will get back on this when I return late next week. Again, thanks!!! Most appreciated. John From: Denys Almazov ***@***.***> Sent: Wednesday, August 7, 2024 11:25 AM To: espressif/idf-eclipse-plugin ***@***.***> Cc: John Decesare ***@***.***>; Mention ***@***.***> Subject: Re: [espressif/idf-eclipse-plugin] Debugging ESP32S3 in Eclipse IDE (IEP-1299) (Issue #1026) Hi @jrdecesare<https://github.com/jrdecesare>, Is there any update on this? Were you able to debug? — Reply to this email directly, view it on GitHub<#1026 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BKGSD7PFYQNS2S4EBCXB4ATZQI35BAVCNFSM6AAAAABLWLDA5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENZTG4ZTMNZXHA>. You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>

[sigmaaa]

Hi @jrdecesare,

Is there any update on this?