https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284042
--- Comment #8 from Pero Oršolić <[email protected]> --- Still an issue on 15.0-ALPHA1, clean (uftdi.c not changed), latest OpenOCD from Espressif. HW: ESPprog with FT2232HL and ESP32-P4 board. schematic: https://dl.espressif.com/dl/schematics/SCH_ESP32-PROG_V2.1_20190709.pdf This works multiple times in a row: % openocd-esp32 -f board/esp32p4-ftdi.cfg -c "init; reset; exit" Open On-Chip Debugger v0.12.0-esp32-20250707-211-gb981c3be (2025-09-22-23:51) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html 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: esp32p4.tap0 tap/device found: 0x00012c25 (mfg: 0x612 (Espressif Systems), part: 0x0012, ver: 0x0) Info : JTAG tap: esp32p4.tap1 tap/device found: 0x00012c25 (mfg: 0x612 (Espressif Systems), part: 0x0012, ver: 0x0) Info : [esp32p4.hp.cpu0] datacount=1 progbufsize=2 Info : [esp32p4.hp.cpu0] Core 0 made part of halt group 1. Info : [esp32p4.hp.cpu0] Examined RISC-V core; found 2 harts Info : [esp32p4.hp.cpu0] XLEN=32, misa=0x40901125 Info : [esp32p4.hp.cpu0] Examination succeed Info : [esp32p4.hp.cpu1] datacount=1 progbufsize=2 Info : [esp32p4.hp.cpu1] Core 1 made part of halt group 1. Info : [esp32p4.hp.cpu1] Examined RISC-V core; found 2 harts Info : [esp32p4.hp.cpu1] XLEN=32, misa=0x40901125 Info : [esp32p4.hp.cpu1] Examination succeed Info : [esp32p4.hp.cpu0] starting gdb server on 3333 Info : Listening on port 3333 for gdb connections Info : JTAG tap: esp32p4.tap0 tap/device found: 0x00012c25 (mfg: 0x612 (Espressif Systems), part: 0x0012, ver: 0x0) Info : JTAG tap: esp32p4.tap1 tap/device found: 0x00012c25 (mfg: 0x612 (Espressif Systems), part: 0x0012, ver: 0x0) Info : [esp32p4.hp.cpu0] Reset cause (24) - (JTAG CPU reset) Info : [esp32p4.hp.cpu1] Reset cause (24) - (JTAG CPU reset) Stops working if something is using FTDI's UART: % cu -s 115200 -l /dev/cuaU1 % openocd-esp32 -f board/esp32p4-ftdi.cfg -c "init; reset; exit" Open On-Chip Debugger v0.12.0-esp32-20250707-211-gb981c3be (2025-09-22-23:51) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi tdo_sample_edge falling" Info : clock speed 20000 kHz Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. embedded:startup.tcl:126: Error: Traceback (most recent call last): File "src/jtag/core.c", line 1697 jtag_init File "embedded:startup.tcl", line 109, in jtag_init init_reset startup File "embedded:startup.tcl", line 126, in init_reset {jtag arp_init-reset} Error: [esp32p4.hp.cpu0] Unsupported DTM version: -1 Error: [esp32p4.hp.cpu0] Could not identify target type. Error: [esp32p4.hp.cpu1] Unsupported DTM version: -1 Error: [esp32p4.hp.cpu1] Could not identify target type. Tried it on Linux 6.12.47 (Debian 13 arm64) and the results is same as on FreeBSD % cu -s 115200 -l /dev/ttyUSB1 % openocd-esp32 -f board/esp32p4-ftdi.cfg -c "init; reset; exit" Open On-Chip Debugger v0.12.0-esp32-20250707-211-gb981c3be (2025-09-22-20:21) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : ftdi: if you experience problems at higher adapter clocks, try the command "ftdi tdo_sample_edge falling" Info : clock speed 20000 kHz Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. Error: JTAG scan chain interrogation failed: all ones Error: Check JTAG interface, timings, target power, etc. embedded:startup.tcl:126: Error: Traceback (most recent call last): File "src/jtag/core.c", line 1697 jtag_init File "embedded:startup.tcl", line 109, in jtag_init init_reset startup File "embedded:startup.tcl", line 126, in init_reset {jtag arp_init-reset} Error: [esp32p4.hp.cpu0] Unsupported DTM version: -1 Error: [esp32p4.hp.cpu0] Could not identify target type. Error: [esp32p4.hp.cpu1] Unsupported DTM version: -1 Error: [esp32p4.hp.cpu1] Could not identify target type. My custom PCB with FT2232HL (which connects JTAG and UART pins directly to the pin header) and (same) ESP32-P4 board works - it is possible to run OpenOCD while cu is running on 2nd port. Not sure if this is SW bug or not. It will work as expected with HW changes, but it would be nice to able to use it with COTS ESPprog JTAG and UART. -- You are receiving this mail because: You are the assignee for the bug.
