You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using GPIO 18 and GPIO 19 on the devkitM and a usb cable to connect to Openocd.
The problem is that the Serial/JTAG debug device is only detected by the PC or Mac when the ESP32-C3 is in download mode(powered on while GPIO9 is LOW)
USB JTAG/serial debug unit:
Product ID: 0x1001
Vendor ID: 0x303a
Version: 1.01
Serial Number: 7C:DF:A1:66:DD:1C
Speed: Up to 12 Mb/s
Manufacturer: Espressif
Location ID: 0x14310000 / 24
Current Available (mA): 500
Current Required (mA): 500
Extra Operating Current (mA): 0
I can successfully upload firmware from both the Serial and JTAG ports but nothing else. Its impossible to debug the firmware simply because the JTAG port is not presented to the PC or Mac when the ESP32-C3 is in normal boot mode.
Is that some limitation of I am missing something? I double checked the documentation and this weird behaviour is not mentioned anywhere.
The text was updated successfully, but these errors were encountered:
miroslavpetrov
changed the title
ESP32-C3 built-in JTAG port only showing when in download mode
ESP32-C3 built-in JTAG port only detected when in download mode
Nov 8, 2021
github-actionsbot
changed the title
ESP32-C3 built-in JTAG port only detected when in download mode
ESP32-C3 built-in JTAG port only detected when in download mode (OCD-436)
Nov 8, 2021
Environment
Problem Description
I am using GPIO 18 and GPIO 19 on the devkitM and a usb cable to connect to Openocd.
The problem is that the Serial/JTAG debug device is only detected by the PC or Mac when the ESP32-C3 is in download mode(powered on while GPIO9 is LOW)
I can successfully upload firmware from both the Serial and JTAG ports but nothing else. Its impossible to debug the firmware simply because the JTAG port is not presented to the PC or Mac when the ESP32-C3 is in normal boot mode.
Is that some limitation of I am missing something? I double checked the documentation and this weird behaviour is not mentioned anywhere.
The text was updated successfully, but these errors were encountered: