Error: JTAG scan chain interrogation failed: all zeroes

Started by srinivasa, October 05, 2024, 01:00:52 PM

Previous topic - Next topic

srinivasa

Hi,
I'm trying enable Olimex OpenOCD JTAG ARM-USB-OCD-H interfaced to rpi5.Getting below "JTAG scan chain interrogation failed: all zeroes" after issuing below cmd: any clue.

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

=================================================================
FTDI device detected in dmesgs as below:

[10326.785553] usb 1-2: new high-speed USB device number 4 using xhci_hcd
[10327.142688] usb 1-2: New USB device found, idVendor=15ba, idProduct=002b, bcdDevice= 7.00
[10327.142692] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10327.142695] usb 1-2: Product: Olimex OpenOCD JTAG ARM-USB-OCD-H
[10327.142697] usb 1-2: SerialNumber: OL2794DF
[10327.159804] ftdi_sio 1-2:1.1: FTDI USB Serial Device converter detected
[10327.159838] usb 1-2: Detected FT2232H
[10327.162632] usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0


LubOlimex

This logs shows that the problem is somewhere between the JTAG and the target. This means 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
Technical support and documentation manager at Olimex