VSCODE platformIO says No debug on ESP32-C3 but JTAG seen in Device Manager.

For Adafruit customers who seek help with microcontrollers

Moderators: adafruit_support_bill, adafruit

Please be positive and constructive with your questions and comments.
Locked
User avatar
RufusVS2020
 
Posts: 62
Joined: Thu Nov 19, 2020 6:31 pm

VSCODE platformIO says No debug on ESP32-C3 but JTAG seen in Device Manager.

Post by RufusVS2020 »

When I plug in my QT Py ESP32-C3 into my Windows 10 system, device manager reports both a serial port, as well as a USB JTAG serial interface. Yet the platformIO extension in VSCODE reports no debugger, and the documentation for Adafruit QT Py ESP32-C3 claims there's no debugger. I have to think PlatformIO is incorrect, otherwise, what would the JTAG device showing up be for? Has anyone else worked through this issue?

User avatar
mikeysklar
 
Posts: 13824
Joined: Mon Aug 01, 2016 8:10 pm

Re: VSCODE platformIO says No debug on ESP32-C3 but JTAG seen in Device Manager.

Post by mikeysklar »

The espressif documentation mentions that you esp-idf tools installer needs to be v2.8 or higher.

https://docs.espressif.com/projects/esp ... -jtag.html
JTAG communication should work on all supported platforms. Windows users might get LIBUSB_ERROR_NOT_FOUND errors. Please use version 2.8 (or newer) of the ESP-IDF Tools Installer and select the driver “Espressif - WinUSB support for JTAG (ESP32-C3/S3)” in order to resolve this issue
They also have two good summaries to get you going with OpenOCD. The last link is VSCode specific walk through (scroll down the github page).

https://docs.espressif.com/projects/esp ... index.html
https://github.com/espressif/vscode-esp ... bugging.md

User avatar
RufusVS2020
 
Posts: 62
Joined: Thu Nov 19, 2020 6:31 pm

Re: VSCODE platformIO says No debug on ESP32-C3 but JTAG seen in Device Manager.

Post by RufusVS2020 »

Yes, I finally found that tidbit (along with the fact Rev 1 and 2 of the chip didn't have the JTAG on USB so it required Rev. 3, which the QT Py is, fortunately). After I installed the proper driver, I navigated to the JTAG device in device manager, updated the driver, and from then on the debugger worked!

This is what the device properties now look like:
JTAG Device Properties.jpg
JTAG Device Properties.jpg (45.03 KiB) Viewed 97 times

Locked
Please be positive and constructive with your questions and comments.

Return to “Microcontrollers”