Trouble Connecting JTAG to ESP32-Solo-1
Posted: Wed Jun 25, 2025 11:42 pm
I'm having trouble getting JTAG to connect to an ESP32-Solo-1. I had this working a couple of years ago (around 2–3 years back), but I can't seem to find the correct settings to get it working again.
From the output console, it looks like it's still trying to connect to a second core, even though my settings.json file specifies the target as "target/esp32-solo-1.cfg". The application runs fine when uploaded over UART, so I believe the menu configuration is correct (unicore is enabled).
Here’s my current setup:
OS: Windows 11
IDE: VS Code
ESP-IDF Version: v5.4.1
Debugger: ESP-Prog
Has anyone run into this issue recently or have suggestions on what might be misconfigured?
Thanks in advance!
My settings.jason file:
And the Output from trying to start OpenOCD
From the output console, it looks like it's still trying to connect to a second core, even though my settings.json file specifies the target as "target/esp32-solo-1.cfg". The application runs fine when uploaded over UART, so I believe the menu configuration is correct (unicore is enabled).
Here’s my current setup:
OS: Windows 11
IDE: VS Code
ESP-IDF Version: v5.4.1
Debugger: ESP-Prog
Has anyone run into this issue recently or have suggestions on what might be misconfigured?
Thanks in advance!
My settings.jason file:
Code: Select all
{
"C_Cpp.intelliSenseEngine": "default",
"idf.espIdfPathWin": "c:\\Espressif\\esp\\v5.4.1\\esp-idf",
"idf.pythonInstallPath": "c:\\Espressif\\.espressif\\tools\\idf-python\\3.11.2\\python.exe",
"idf.openOcdConfigs": [
"interface/ftdi/esp32_devkitj_v1.cfg",
"target/esp32-solo-1.cfg"
],
"idf.toolsPathWin": "c:\\Espressif\\.espressif",
"idf.customExtraVars": {
"IDF_TARGET": "esp32"
},
"idf.flashType": "UART",
"idf.portWin": "COM6"
}
Code: Select all
Open On-Chip Debugger v0.12.0-esp32-20241016 (2024-10-16-14:17)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
adapter speed: 20000 kHz
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : ftdi: if you experience problems at higher adapter clocks, try the command "ft
di tdo_sample_edge falling"
Info : clock speed 20000 kHz
Info : JTAG tap: esp32.tap0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32.tap1 tap
❌ /device found: 0xffffffff (mfg: 0x7ff (<invalid>), part: 0xffff, ver: 0xf)
Warn : JTAG tap: esp32.tap1 UNEXPECTED: 0xffffffff (mfg: 0x7ff (<invalid>), part: 0xffff, ver: 0xf)
Error: JTAG tap: esp32.tap1 expected 1 of 1: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Error: Trying to use configured s
❌ can chain anyway...
Error: esp32.tap1: IR capture error; saw 0x1f not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : [esp32] Unexpected OCD_ID = 00000000
Error: [esp32] Examination failed
Warn : target esp32 examination failed
Info : [esp32] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections