Problem while using ESP32-S2 as a JTAG usb-bridge and ESP32 as a target in Windows (EUB-87)

[Hanning-Liu]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Successfully flash project and debug with ESP32-S2 as a JTAG usb-bridge and ESP32 as a target in Windows.

Actual behavior (suspected bug)

The response when I am using ESP32-S2 as a JTAG usb-bridge with a ESP32-WROOM-32E as a terget:

(base) PS C:\Users\HANI\Desktop\New_folder\IDF\blink> openocd -f board/esp32-bridge.cfg   
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
Info : only one transport option; autoselecting 'jtag'
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1002
Info : esp_usb_jtag: capabilities descriptor set to 0x30a
Info : esp_usb_jtag: target chip id set to 1
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Error: libusb_open() failed with LIBUSB_ERROR_NOT_FOUND
Error: esp_usb_jtag: could not find or open device!
c:\Espressif\frameworks\esp-idf-v5.4.1\tools\tools\openocd-esp32\v0.12.0-esp32-20241016\openocd-esp32\share\openocd\scripts/target/esp_common.cfg:9: Error:
at file "c:\Espressif\frameworks\esp-idf-v5.4.1\tools\tools\openocd-esp32\v0.12.0-esp32-20241016\openocd-esp32\share\openocd\scripts/target/esp_common.cfg", line 9

But it works well after I resolve the driver issue of ESP32-S3 builtin. See: This Github issue.
And powershell log:

(base) PS C:\Users\HANI\Desktop\New_folder\IDF\blink> openocd -f board/esp32s3-builtin.cfg
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
Info : only one transport option; autoselecting 'jtag'
Info : esp_usb_jtag: VID set to 0x303a and PID to 0x1001
Info : esp_usb_jtag: capabilities descriptor set to 0x2000
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : esp_usb_jtag: serial (30:ED:A0:AC:66:20)
Info : esp_usb_jtag: Device found. Base speed 40000KHz, div range 1 to 255
Info : clock speed 40000 kHz
Info : JTAG tap: esp32s3.tap0 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : JTAG tap: esp32s3.tap1 tap/device found: 0x120034e5 (mfg: 0x272 (Tensilica), part: 0x2003, ver: 0x1)
Info : [esp32s3.cpu0] Examination succeed
Info : [esp32s3.cpu1] Examination succeed
Info : [esp32s3.cpu0] starting gdb server on 3333
Info : Listening on port 3333 for gdb connections
Info : [esp32s3.cpu0] Debug controller was reset.
Info : [esp32s3.cpu0] Core was reset.
Info : [esp32s3.cpu1] Debug controller was reset.
Info : [esp32s3.cpu1] Core was reset.
Info : [esp32s3.cpu0] Target halted, PC=0x4037B7F2, debug_reason=00000000
Info : [esp32s3.cpu0] Reset cause (1) - (Power on reset)
Info : [esp32s3.cpu1] Target halted, PC=0x4037B7F2, debug_reason=00000000
Info : [esp32s3.cpu1] Reset cause (1) - (Power on reset)
shutdown command invoked

Error logs or terminal output

Steps to reproduce the behavior

1. use ESP32-S2 as a JTAG usb-bridge with a ESP32-WROOM-32E as a terget.
2. type in openocd -f board/esp32s3-builtin.cfg in the powershell in the project folder with correct env variable.

Project release version

latest

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

Windows11

Shell

PowerShell

Additional context

No response

[Dzarda7]

Hello @Hanning-Liu, thanks for the great report, already working on fix.