> Error: JTAG scan chain interrogation failed: all ones
Almost certainly the target TDO is stuck at 1 for some reason, so you need to
check your target, debug connection, wiring etc.
What is the nature of your target device/board?
________________________________
From: Abe Lapped <abe19285...@gmail.com>
Sent: Thursday, July 13, 2023 9:50:25 PM
To: Tommy Murphy <tommy_mur...@hotmail.com>;
openocd-devel@lists.sourceforge.net <openocd-devel@lists.sourceforge.net>;
dietmar....@outlook.com <dietmar....@outlook.com>; fercer...@gmail.com
<fercer...@gmail.com>
Subject: Re: Olimex ARM-USB-OCD-H Driver Issue
Thank you all for your input. I've downloaded the xPack version and updated my
drivers (hopefully correctly). Now, when I go to run it, I get an "all ones"
error.
Here is my output:
$ ./openocd -f olimex-arm-usb-ocd-h.cfg -f ks869x.cfg
xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-15:04)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
0
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : clock speed 6000 kHz
Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.
Error: Trying to use configured scan chain anyway...
Error: ks869x.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Info : Embedded ICE version 15
Error: unknown EmbeddedICE version (comms ctrl: 0xffffffff)
Info : ks869x.cpu: hardware has 2 breakpoint/watchpoint units
Info : starting gdb server for ks869x.cpu on 3333
Info : Listening on port 3333 for gdb connections
Warn : ThumbEE -- incomplete support
target halted in ThumbEE state due to watchpoint-and-breakpoint, current mode:
System
cpsr: 0xffffffff pc: 0xfffffff9
MMU: enabled, D-Cache: enabled, I-Cache: enabled
Any idea?
Side note, sorry if I'm not using the mail list correctly.. I'm not familiar
with it. Should I just reply to openocd-devel and cc the rest of the
participants? Thanks!
On Thu, 13 Jul 2023 at 15:18, Tommy Murphy
<tommy_mur...@hotmail.com<mailto:tommy_mur...@hotmail.com>> wrote:
Zadig 2.5 is also outdated.
I would use the latest, 2.8.
And, as mentioned earlier, a much more up to date version of OpenOCD.
Note that if you're writing you own scripts then some commands may differ with
a later OpenOCD - e.g. `ftdi vid_pid` rather than the legacy `ftdi_vid_pid`
command although the older command formats usually generate warnings rather
than errors.
