Hello,

I've been reading through some of the posts regarding this issue but it doesn't seem something encountered before.

I'm able to upload a sketch through either the UART or the USB interface without a problem but when I try to setup a hardware debug session I get an error (I use the options "Debug: hardware" with "ESP32S3-USB" and "No Optimization" selected). The build log can be found in the dedicated email (see  the bottom of the post for the details. You can also see below the output of the *.log file:

Quote:


If I inspect the folder, I can see that the "esp32s3-builtin.cfg" file it complains about is actually missing.

I then retrieved the openocd folder from the installation of the ESP-IDF Tools folder (here: c:\esp\tools\.espressif\tools\openocd-esp32), replaced across the whole content, tried to debug again and I got the error included in the file "Test2.ino_DebugOpenOCD - 2.log"

This was clearly a bodged solution but was worth trying it. :p

I'm not sure what the problem is. I followed the recommendations from this page (with and without the board.txt file): https://www.visualmicro.com/page/ESP32S3-USB-Debugging.aspx

I've also configured the driver of the "USB JTAG/serial debug unit (Interface 0)" with Zadig as "USB Serial (CDC)".

I'm not sure what the problem is. Probably it is something very silly.


For info, I'm running with the following specs:
- Visual Studio Community 2022 (64-bit) - Current Version 17.5.3
- VisualMicro 2024.102.2203

All the files are attached to the email I sent you privately:
    vMicro Support Request | AndreaC | Cannot start debugging ESP32-S3-DevKitC-1 using integrated JTAG over USB

Containing the following files:

     
• Test2.ino_DebugOpenOCD - 1.log (first attempt, with openocd files as are)
       
• Test2.ino_DebugOpenOCD - 2.log (with bodged openocd files)
       
• Build - 1.log (log file of the first build)
       
• Build - 2.log (log file of the second build)

Thanks in advance to anyone who tries to help.

Thanks for the reply.

I created the board.txt file as you suggested and installed the driver on the Interface 2 with Zadig but now when I try to debug I get the error shown in the screenshot attached ErrorDialog.png.

Could it be because there are spaces and special characters in the path (in the obfuscated part)?

Thanks Simon, I sent an email with the details.

Good news!

After changing the two paths as suggested it finally works!

I had to re-install all the boards (which took an unusual amount of time) but then it was fine.

I even set up the two folders in a different drive than "C:\" and it still works fine (this shouldn't be taken for granted).

Thank you Simon for the assistance, you've been blazing fast and really helpful in solving the issue.