The specified debug interface was not found (ftdi)

[srinivasa]

sai@sai:/usr/local/share/openocd/scripts$ sudo openocd -d3 -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f board/rpi4b.cfg
Open On-Chip Debugger 0.12.0+dev-gebec9504d (2024-09-21-23:55)
Licensed under GNU GPL v2
For bug reports, read
    http://openocd.org/doc/doxygen/bugs.html
User : 3 3 options.c:52 configuration_output_handler(): debug_level: 3User : 4 3 options.c:52 configuration_output_handler():
Debug: 5 3 options.c:233 add_default_dirs(): bindir=/usr/local/bin
Debug: 6 3 options.c:234 add_default_dirs(): pkgdatadir=/usr/local/share/openocd
Debug: 7 3 options.c:235 add_default_dirs(): exepath=/usr/local/bin
Debug: 8 3 options.c:236 add_default_dirs(): bin2data=../share/openocd
Debug: 9 3 configuration.c:33 add_script_search_dir(): adding /home/sai/.config/openocd
Debug: 10 3 configuration.c:33 add_script_search_dir(): adding /home/sai/.openocd
Debug: 11 3 configuration.c:33 add_script_search_dir(): adding /usr/local/bin/../share/openocd/site
Debug: 12 3 configuration.c:33 add_script_search_dir(): adding /usr/local/bin/../share/openocd/scripts
Debug: 13 3 command.c:153 script_debug(): command - ocd_find interface/ftdi/olimex-arm-usb-ocd-h.cfg
Debug: 14 3 configuration.c:88 find_file(): found interface/ftdi/olimex-arm-usb-ocd-h.cfg
Debug: 15 3 command.c:153 script_debug(): command - adapter driver ftdi
Error: 16 3 adapter.c:458 handle_adapter_driver_command(): The specified debug interface was not found (ftdi)
Debug: 17 3 command.c:529 exec_command(): Command 'adapter driver' failed with error code -101
User : 18 3 command.c:601 command_run_line(): The following debug adapters are available:
1: usb_blaster
2: presto
3: buspirate

[srinivasa]

Error: 156 35 mpsse.c:356 mpsse_open(): unable to open ftdi device with vid 15ba, pid 002b, description 'Olimex OpenOCD JTAG ARM-USB-OCD-H', serial '*' at bus location '*'
Debug: 157 36 command.c:545 run_command(): Command 'init' failed with error code -100

[LubOlimex]

Seems like driver issue. Try installing the driver with Zading installer.

After installation of the program plug ARM-USB-OCD-H to the computer and you should see the device in the drop down menu with the interfaces populated, as well as the VID and PID boxes. If they don't get populated go to Options → List All Devices. After that select the WinUSB driver and click either the big "Install Driver" button or the "Reinstall Driver" button for each interface. The reinstall button replaces the
install button if some old driver associated with the debugger was left over.

Test again if it works.

If the issue remains maybe try the LibUSB driver instead of the WinUSB driver. Which driver is sued depends on the OpenOCD version, OpenOCD can be compiled with either driver support.

[srinivasa]

Hi, Olimex OpenOCD JTAG ARM-USB-OCD-H detected in usb device list, But when I issue below command, "JTAG scan chain interrogation failed: all zeroes".
Logs are catptured as below:

sai@sai:/usr/local/share/openocd$ sudo openocd  -f interface/ftdi/olimex-arm-usb-ocd-h.cfg -f board/rpi4b.cfg
Open On-Chip Debugger 0.12.0-dirty (2024-09-22-16:43)
Licensed under GNU GPL v2
For bug reports, read
   http://openocd.org/doc/doxygen/bugs.html
Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'.
Warn : Transport "jtag" was already selected
trst_only separate trst_push_pull

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 4000 kHz
Error: JTAG scan chain interrogation failed: all zeroes
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: bcm2711.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (0) in DAP response

[LubOlimex]

Moving forward now the drivers and the ARM-USB-OCD-H appear to be properly working.

The issue is either in the hardware connections OR in the rpi4b.cfg