ESP32-C3-DevKitM-1 default software

[eperie]

@ESP_Minatel: And no, I don't mean the console output, I mean a Jlink debug probe connected to the proper pins of the esp32-c3, using openocd-esp32, as described https://docs.espressif.com/projects/esp ... index.html, with the following configuration file:

Code: Select all

# Example OpenOCD configuration file for ESP32-C3 connected via ESP-Prog.
# 
# For example, OpenOCD can be started for ESP32-C3 debugging on
#
#   openocd -f board/esprv_ftdi.cfg
#

# Source the JTAG interface configuration file
source [find interface/jlink.cfg]
# Source the ESP32-C3 configuration file
source [find target/esp32c3.cfg]
adapter_khz 4000

And this command:

Code: Select all

sudo bin/openocd -f esp32-c3.cfg -c "init; halt"

Please note that I was able to debug the ESP32-C3-DevKitM-1 default software using my setup and GDB.

Code: Select all

Info : VTarget = 3.300 V
Info : clock speed 4000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Info : datacount=2 progbufsize=16
Info : Examined RISC-V core; found 1 harts
Info :  hart 0: XLEN=32, misa=0x40101104
Error: Debugger is not authenticated to target Debug Module. (dmstatus=0x80018642). Use `riscv authdata_read` and `riscv authdata_write` commands to authenticate.
Info : Listening on port 3333 for gdb connections
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: Debugger is not authenticated to target Debug Module. (dmstatus=0x80000000). Use `riscv authdata_read` and `riscv authdata_write` commands to authenticate.
Error: Debugger is not authenticated to target Debug Module. (dmstatus=0x80000000). Use `riscv authdata_read` and `riscv authdata_write` commands to authenticate.
Error: Debugger is not authenticated to target Debug Module. (dmstatus=0x80000000). Use `riscv authdata_read` and `riscv authdata_write` commands to authenticate.

And I cannot connect when the ESP32-C3-DevKitM-1 is executing the blink example:

Code: Select all

Info : VTarget = 3.300 V
Info : clock speed 4000 kHz
Info : JTAG tap: esp32c3.cpu tap/device found: 0xf0000301 (mfg: 0x180 (<invalid>), part: 0x0000, ver: 0xf)
Warn : JTAG tap: esp32c3.cpu       UNEXPECTED: 0xf0000301 (mfg: 0x180 (<invalid>), part: 0x0000, ver: 0xf)
Error: JTAG tap: esp32c3.cpu  expected 1 of 1: 0x00005c25 (mfg: 0x612 (Espressif Systems), part: 0x0005, ver: 0x0)
Error: Trying to use configured scan chain anyway...
Warn : Bypassing JTAG setup events due to errors
Error: dtmcontrol is 0. Check JTAG connectivity/board power.
Info : Listening on port 3333 for gdb connections
Error: Target not examined yet

This is why I would need the information on how to enable JTAG interface in a brand new project.

[ESP_Minatel]

Hi,

Check the GPIO10. The strapping pins are described in the table below.

Screenshot from 2021-04-30 19-40-54.png (161.3 KiB) Viewed 4895 times

ESP32-C3 datasheet: https://www.espressif.com/sites/default ... eet_en.pdf

[chegewara]

In esp32 C3 revision 2 JTAG is not working. Probably from revision 3 it will be available.

[eperie]

@ESP_Minatel: I am not changing any GPIO strapping, on the board. The JTAG interface is working when the board is running the firmware it came installed with, and is not when I am running the blink example.

Any clue why the blink example is not working on my ESP32-C3-DevKitM-1 revision2 from the sdkconfig file I submitted ? thanks.

[eperie]

@chegewara: Thank you. You may refer to the usb-jtag interface, because the external (using GPIO pins) interface is working on my revision 2 ESP32-C3-DevKitM-1 (not with the blink SDK example though).

[eperie]

@chegewara: I checked the rainmaker example you pointed me to, and the firmware my ESP32-C3-DevKitM-1 came installed width seems to behave the same way (user button toggling the LED on/on) - thank you very much for this lead.I can now look at the rainmaker SDK in order to understand why I can use the GPIO JTAG interface with the firmware my ESP32-C3-DevKitM-1 came installed width, but not with the 'blink' example.

[ESP_Sprite]

Just because I don't think anyone asked yet: you didn't happen to change the LED GPIO in the blink example to one of the GPIOs that is used by JTAG?

Edit: Never mind, saw you attached the sdkconfig, it's attached to GPIO8. Grasping at straws, but perhaps there's a short between that GPIO and one of the JTAG pins?