Cannot connect to ESP32 via JTAG

tim687
Posts: 5
Joined: Thu Oct 26, 2023 4:51 pm

Cannot connect to ESP32 via JTAG

Postby tim687 » Thu Oct 26, 2023 6:09 pm

Hi,

I'm trying to connect my development board over JTAG, but it only connects some of the times.

I'm starting openocd with:
openocd -s "C:\esp-idf-5.0.1\tools\openocd-esp32\v0.11.0-esp32-20221026\openocd-esp32\share\openocd\scripts" -f interface/ftdi/esp32_devkitj_v1.cfg -f board/esp-wroom-32.cfg -c "init; halt; esp32 appimage_offset 0x20000"
And this is the output:
Open On-Chip Debugger v0.11.0-esp32-20221026 (2022-10-26-14:48)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
adapter speed: 20000 kHz

WARNING: boards/esp-wroom-32.cfg is deprecated, and may be removed in a future release.
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi tdo_sample_edge falling"
Info : clock speed 20000 kHz
Info : JTAG tap: esp32.cpu0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.cpu1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Error: [esp32.cpu1] Unexpected OCD_ID = 00000000
Warn : target esp32.cpu1 examination failed
Info : starting gdb server for esp32.cpu0 on 3333
Info : Listening on port 3333 for gdb connections
Info : [esp32.cpu0] Target halted, PC=0x4009274A, debug_reason=00000000
Info : [esp32.cpu0] Reset cause (3) - (Software core reset)
Error: [esp32.cpu1] Unexpected OCD_ID = 00000000
Error: Target not examined yet
I've tried to lower the adapter speed, without any success.

The app is still running on the ESP32, I can connect to bluetooth, whilst the JTAG couldn't connect.

Who is online

Users browsing this forum: Baidu [Spider], rsimpsonbusa and 66 guests