openocd-devel

Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

I have recently purchased an Olimex ARM-USB-OCD-U debugger but am
experiencing a driver issue. I used Zadig to install WinUSB
(v6.1.7600.16385) drivers for ARM-USB-OCD-H (both interfaces 0 and 1).
https://imgur.com/a/Rjl58i3
https://imgur.com/a/eb11sSZ

After restarting my computer (Windows 10 Enterprise - x64), and connecting
the ARM-USB-OCD-H (USB-C <-> USB-C), the yellow light turns solid, and it
appears as a USB device:
https://imgur.com/a/BPue8wJ

Using the precompiled OpenOCD 0.9.0 found here: [url="
https://freddiechopin.info/en/download/category/4-openocd"]
0.9.0Freddiechoppin.info[/url], I navigated to the bin-x64 folder and added
the olimex-arm-usb-ocd-h ftdi interface config file, after adding the
following two lines to the end, for auto probing:
reset_config trst_and_srst
jtag_rclk 8

The config file (olimex-arm-usb-ocd-h-autprobe.cfg) looks like this:
[code]#
# Olimex ARM-USB-OCD-H
#
# http://www.olimex.com/dev/arm-usb-ocd-h.html
#
interface ftdi
ftdi_device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
ftdi_vid_pid 0x15ba 0x002b
ftdi_layout_init 0x0908 0x0b1b
ftdi_layout_signal nSRST -oe 0x0200
ftdi_layout_signal nTRST -data 0x0100
ftdi_layout_signal LED -data 0x0800
reset_config trst_and_srst
jtag_rclk 8
[/code]

I am connected to a target at this point (20-pin ICE JTAG).
>From a GIT bash MINGW terminal in the bin-x64 folder, I run:
$ ./openocd -f olimex-arm-usb-ocd-h-autprobe.cfg

Which yields:
[code]Open On-Chip Debugger 0.9.0-rc1 (2015-04-24-22:09)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
trst_and_srst separate srst_gates_jtag trst_push_pull srst_open_drain
connect_deassert_srst
Info : auto-selecting first available session transport "jtag". To override
use 'transport select <transport>'.
RCLK - adaptive
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : RCLK (adaptive clock speed)
Warn : There are no enabled taps.  AUTO PROBING MIGHT NOT WORK!!
[/code]

For a more verbose output, I re-ran with the -d3 debug flag, which yielded:
[code]Open On-Chip Debugger 0.9.0-rc1 (2015-04-24-22:09)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
User : 13 0 command.c:546 command_print(): debug_level: 3
Debug: 14 0 options.c:98 add_default_dirs(): bindir=bin-x64
Debug: 15 0 options.c:99 add_default_dirs(): pkgdatadir=
Debug: 16 0 options.c:100 add_default_dirs():
run_prefix=C:/Users/dhaymes/Desktop/o/openocd-0.9.0-rc1/
Debug: 17 0 configuration.c:44 add_script_search_dir(): adding
C:\Users\dhaymes/.openocd
Debug: 18 0 configuration.c:44 add_script_search_dir(): adding
C:\Users\dhaymes\AppData\Roaming/OpenOCD
Debug: 19 0 configuration.c:44 add_script_search_dir(): adding
C:/Users/dhaymes/Desktop/o/openocd-0.9.0-rc1//site
Debug: 20 0 configuration.c:44 add_script_search_dir(): adding
C:/Users/dhaymes/Desktop/o/openocd-0.9.0-rc1//scripts
Debug: 21 0 configuration.c:84 find_file(): found
olimex-arm-usb-ocd-h-autprobe.cfg
Debug: 22 0 command.c:145 script_debug(): command - ocd_command ocd_command
type ocd_interface ftdi
Debug: 23 0 command.c:145 script_debug(): command - interface ocd_interface
ftdi
Debug: 25 0 command.c:366 register_command_handler(): registering
'ocd_ftdi_device_desc'...
Debug: 26 0 command.c:366 register_command_handler(): registering
'ocd_ftdi_serial'...
Debug: 27 16 command.c:366 register_command_handler(): registering
'ocd_ftdi_channel'...
Debug: 28 16 command.c:366 register_command_handler(): registering
'ocd_ftdi_layout_init'...
Debug: 29 16 command.c:366 register_command_handler(): registering
'ocd_ftdi_layout_signal'...
Debug: 30 16 command.c:366 register_command_handler(): registering
'ocd_ftdi_set_signal'...
Debug: 31 16 command.c:366 register_command_handler(): registering
'ocd_ftdi_vid_pid'...
Debug: 32 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_ftdi_device_desc Olimex OpenOCD JTAG ARM-USB-OCD-H
Debug: 33 16 command.c:145 script_debug(): command - ftdi_device_desc
ocd_ftdi_device_desc Olimex OpenOCD JTAG ARM-USB-OCD-H
Debug: 35 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_ftdi_vid_pid 0x15ba 0x002b
Debug: 36 16 command.c:145 script_debug(): command - ftdi_vid_pid
ocd_ftdi_vid_pid 0x15ba 0x002b
Debug: 38 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_ftdi_layout_init 0x0908 0x0b1b
Debug: 39 16 command.c:145 script_debug(): command - ftdi_layout_init
ocd_ftdi_layout_init 0x0908 0x0b1b
Debug: 41 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_ftdi_layout_signal nSRST -oe 0x0200
Debug: 42 16 command.c:145 script_debug(): command - ftdi_layout_signal
ocd_ftdi_layout_signal nSRST -oe 0x0200
Debug: 44 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_ftdi_layout_signal nTRST -data 0x0100
Debug: 45 16 command.c:145 script_debug(): command - ftdi_layout_signal
ocd_ftdi_layout_signal nTRST -data 0x0100
Debug: 47 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_ftdi_layout_signal LED -data 0x0800
Debug: 48 16 command.c:145 script_debug(): command - ftdi_layout_signal
ocd_ftdi_layout_signal LED -data 0x0800
Debug: 50 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_reset_config trst_and_srst
Debug: 51 16 command.c:145 script_debug(): command - reset_config
ocd_reset_config trst_and_srst
User : 53 16 command.c:546 command_print(): trst_and_srst separate
srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst
Debug: 54 16 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_transport select
Debug: 55 16 command.c:145 script_debug(): command - ocd_transport
ocd_transport select
Info : 56 16 transport.c:287 jim_transport_select(): auto-selecting first
available session transport "jtag". To override use 'transport select
<transport>'.
Debug: 57 16 command.c:366 register_command_handler(): registering
'ocd_jtag_flush_queue_sleep'...
Debug: 58 16 command.c:366 register_command_handler(): registering
'ocd_jtag_rclk'...
Debug: 59 16 command.c:366 register_command_handler(): registering
'ocd_jtag_ntrst_delay'...
Debug: 60 16 command.c:366 register_command_handler(): registering
'ocd_jtag_ntrst_assert_width'...
Debug: 61 16 command.c:366 register_command_handler(): registering
'ocd_scan_chain'...
Debug: 62 28 command.c:366 register_command_handler(): registering
'ocd_jtag_reset'...
Debug: 63 28 command.c:366 register_command_handler(): registering
'ocd_runtest'...
Debug: 64 28 command.c:366 register_command_handler(): registering
'ocd_irscan'...
Debug: 65 28 command.c:366 register_command_handler(): registering
'ocd_verify_ircapture'...
Debug: 66 28 command.c:366 register_command_handler(): registering
'ocd_verify_jtag'...
Debug: 67 28 command.c:366 register_command_handler(): registering
'ocd_tms_sequence'...
Debug: 68 28 command.c:366 register_command_handler(): registering
'ocd_wait_srst_deassert'...
Debug: 69 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 70 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 71 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 72 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 73 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 74 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 75 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 76 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 77 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 78 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 79 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 80 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 81 28 command.c:366 register_command_handler(): registering
'ocd_jtag'...
Debug: 82 28 command.c:366 register_command_handler(): registering
'ocd_svf'...
Debug: 83 28 command.c:366 register_command_handler(): registering
'ocd_xsvf'...
Debug: 84 28 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_transport select
Debug: 85 28 command.c:145 script_debug(): command - ocd_transport
ocd_transport select
Debug: 86 28 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_jtag_rclk 8
Debug: 87 28 command.c:145 script_debug(): command - jtag_rclk
ocd_jtag_rclk 8
Debug: 89 28 core.c:1638 jtag_config_rclk(): handle jtag rclk
Debug: 90 28 core.c:1596 adapter_khz_to_speed(): convert khz to interface
specific speed value
Debug: 91 28 core.c:1596 adapter_khz_to_speed(): convert khz to interface
specific speed value
User : 92 28 command.c:546 command_print(): RCLK - adaptive
Debug: 93 28 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_init
Debug: 94 28 command.c:145 script_debug(): command - init ocd_init
Debug: 96 28 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_target init
Debug: 97 28 command.c:145 script_debug(): command - ocd_target ocd_target
init
Debug: 99 28 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_target names
Debug: 100 28 command.c:145 script_debug(): command - ocd_target ocd_target
names
Debug: 101 28 target.c:1313 handle_target_init_command(): Initializing
targets...
Debug: 102 28 ftdi.c:625 ftdi_initialize(): ftdi interface using shortest
path jtag state transitions
Error: 103 60 mpsse.c:140 open_matching_device(): libusb_open() failed with
LIBUSB_ERROR_NOT_SUPPORTED
Debug: 104 65 mpsse.c:363 mpsse_purge(): -
Debug: 105 65 mpsse.c:644 mpsse_loopback_config(): off
Debug: 106 65 mpsse.c:689 mpsse_set_frequency(): target 0 Hz
Debug: 107 65 mpsse.c:681 mpsse_rtck_config(): on
Debug: 108 65 core.c:1596 adapter_khz_to_speed(): convert khz to interface
specific speed value
Debug: 109 65 core.c:1599 adapter_khz_to_speed(): have interface set up
Debug: 110 65 mpsse.c:689 mpsse_set_frequency(): target 0 Hz
Debug: 111 65 mpsse.c:681 mpsse_rtck_config(): on
Debug: 112 65 core.c:1596 adapter_khz_to_speed(): convert khz to interface
specific speed value
Debug: 113 65 core.c:1599 adapter_khz_to_speed(): have interface set up
Info : 114 65 core.c:1386 adapter_init(): RCLK (adaptive clock speed)
Debug: 115 65 openocd.c:137 handle_init_command(): Debug Adapter init
complete
Debug: 116 65 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_transport init
Debug: 117 65 command.c:145 script_debug(): command - ocd_transport
ocd_transport init
Debug: 119 65 transport.c:240 handle_transport_init(): handle_transport_init
Debug: 120 65 core.c:730 jtag_add_reset(): SRST line released
Debug: 121 65 core.c:754 jtag_add_reset(): TRST line released
Debug: 122 65 core.c:328 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 123 65 command.c:145 script_debug(): command - ocd_command
ocd_command type ocd_jtag arp_init
Debug: 124 65 command.c:145 script_debug(): command - ocd_jtag ocd_jtag
arp_init
Debug: 125 65 core.c:1397 jtag_init_inner(): Init JTAG chain
Warn : 126 65 core.c:1413 jtag_init_inner(): There are no enabled taps.
AUTO PROBING MIGHT NOT WORK!!
Debug: 127 65 core.c:328 jtag_call_event_callbacks(): jtag event: TAP reset
Debug: 128 65 core.c:1058 jtag_examine_chain(): DR scan interrogation for
IDCODE/BYPASS
Debug: 129 65 core.c:328 jtag_call_event_callbacks(): jtag event: TAP reset
[/code]

Both times, the light on the debugger would go from yellow to red as soon
as I ran OpenOCD.
While I don't have a fully formed target configuration file yet, if I'm
understanding correctly, there is a problem (libusb_open() failed with
LIBUSB_ERROR_NOT_SUPPORTED) connecting to my Olimex device.

I do not think this is a cable issue, as I have tried this with a USB-C to
USB-C as well as a USB-A to USB-C, both with the same result.

Is this a driver issue?

Thank you,

Re: Olimex ARM-USB-OCD-H Driver Issue

[Paul F. <fer...@gm...>]

Hi,

On Thu, Jul 13, 2023 at 01:46:04PM -0400, Abe Lapped wrote:
> I have recently purchased an Olimex ARM-USB-OCD-U debugger but am experiencing a
> driver issue. I used Zadig to install WinUSB (v6.1.7600.16385) drivers for
> ARM-USB-OCD-H (both interfaces 0 and 1).

I think README.Windows says you need to install WinUSB for the
composite device parent.

> [1]https://imgur.com/a/Rjl58i3
> [2]https://imgur.com/a/eb11sSZ
> After restarting my computer (Windows 10 Enterprise - x64), and connecting the
> ARM-USB-OCD-H (USB-C <-> USB-C), the yellow light turns solid, and it appears as
> a USB device:
> [3]https://imgur.com/a/BPue8wJ
> Using the precompiled OpenOCD 0.9.0 found here:

Please use current version of OpenOCD, not something from year 2015.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

> Please use current version of OpenOCD, not something from year 2015.

I'd second that! If you can't build it yourself or find another binary distribution then you could try the xPack version:

* https://xpack.github.io/dev-tools/openocd/
* https://xpack.github.io/dev-tools/openocd/releases/

Re: Olimex ARM-USB-OCD-H Driver Issue

[Dietmar M. <die...@ou...>]

I’ve used zadig for ARM-USB-OCD-H. (At least for *that* probe), do NOT install for BOTH interface 0 and 1 - ONLY device 0. Interface 1 is a standard FTDI comm port, which can be installed using drivers from FTDI’s website. You would need to specify the driver manually. Use the last option in the list. However, interface 1 is not needed for JTAG debugging.

Sent from my iPhone

> On Jul 13, 2023, at 1:58 PM, Paul Fertser <fer...@gm...> wrote:
> 
> Hi,
> 
>> On Thu, Jul 13, 2023 at 01:46:04PM -0400, Abe Lapped wrote:
>> I have recently purchased an Olimex ARM-USB-OCD-U debugger but am experiencing a
>> driver issue. I used Zadig to install WinUSB (v6.1.7600.16385) drivers for ARM-USB-OCD-H (both interfaces 0 and 1).
> 
> I think README.Windows says you need to install WinUSB for the
> composite device parent.
> 
>> [1]https://imgur.com/a/Rjl58i3
>> [2]https://imgur.com/a/eb11sSZ
>> After restarting my computer (Windows 10 Enterprise - x64), and connecting the
>> ARM-USB-OCD-H (USB-C <-> USB-C), the yellow light turns solid, and it appears as
>> a USB device:
>> [3]https://imgur.com/a/BPue8wJ
>> Using the precompiled OpenOCD 0.9.0 found here:
> 
> Please use current version of OpenOCD, not something from year 2015.
> 
> -- 
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fer...@gm...
> 

Re: Olimex ARM-USB-OCD-H Driver Issue

[Paul F. <fer...@gm...>]

On Thu, Jul 13, 2023 at 06:16:13PM +0000, Dietmar May wrote:
> I’ve used zadig for ARM-USB-OCD-H. (At least for *that* probe), do
> NOT install for BOTH interface 0 and 1 - ONLY device 0. Interface 1
> is a standard FTDI comm port, which can be installed using drivers
> from FTDI’s website. You would need to specify the driver
> manually. Use the last option in the list. However, interface 1 is
> not needed for JTAG debugging.

But that also might depend on windows version. Which one were you
testing that on?

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...

Re: Olimex ARM-USB-OCD-H Driver Issue

[Paul F. <fer...@gm...>]

On Fri, Jul 14, 2023 at 11:27:43AM -0400, Abe Lapped wrote:
> Here is a shot of my pinout, if it helps:
> [1]image.png

Have you tried measuring the voltage on pin 1 of the connector? It
should be Vcc from the target.

-- 
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fer...@gm...

Re: Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

Thank you for the suggestion. Just measured, and the input voltage (3.3V)
is correct!

On Fri, 14 Jul 2023 at 11:51, Paul Fertser <fer...@gm...> wrote:

> On Fri, Jul 14, 2023 at 11:27:43AM -0400, Abe Lapped wrote:
> > Here is a shot of my pinout, if it helps:
> > [1]image.png
>
> Have you tried measuring the voltage on pin 1 of the connector? It
> should be Vcc from the target.
>
> --
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fer...@gm...
>

Re: Olimex ARM-USB-OCD-H Driver Issue

[Dietmar M. <die...@ou...>]

Windows 10/11 w/zadig 2.5

Sent from my iPhone

> On Jul 13, 2023, at 2:25 PM, Paul Fertser <fer...@gm...> wrote:
> 
> On Thu, Jul 13, 2023 at 06:16:13PM +0000, Dietmar May wrote:
>> I’ve used zadig for ARM-USB-OCD-H. (At least for *that* probe), do
>> NOT install for BOTH interface 0 and 1 - ONLY device 0. Interface 1
>> is a standard FTDI comm port, which can be installed using drivers
>> from FTDI’s website. You would need to specify the driver
>> manually. Use the last option in the list. However, interface 1 is
>> not needed for JTAG debugging.
> 
> But that also might depend on windows version. Which one were you
> testing that on?
> 
> -- 
> Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
> mailto:fer...@gm...

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

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.

Re: Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

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 <tom...@ho...> 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.
>

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

> 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 <abe...@gm...>
Sent: Thursday, July 13, 2023 9:50:25 PM
To: Tommy Murphy <tom...@ho...>; ope...@li... <ope...@li...>; die...@ou... <die...@ou...>; fer...@gm... <fer...@gm...>
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 <tom...@ho...<mailto:tom...@ho...>> 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.

Re: Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

Thank you for the input!

The target device is a KSZ8695X with a 20 pin ICE connector. It has its own
external power supply and the status lights are up. I tried unplugging the
cable from the target completely and running again, and got the same error.
The Olimex debuggers light stays solid yellow when I run the openOCD
command, where before it was turning red.


On Thu, 13 Jul 2023 at 16:55, Tommy Murphy <tom...@ho...> wrote:

> > 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 <abe...@gm...>
> *Sent:* Thursday, July 13, 2023 9:50:25 PM
> *To:* Tommy Murphy <tom...@ho...>;
> ope...@li... <ope...@li...>;
> die...@ou... <die...@ou...>; fer...@gm... <
> fer...@gm...>
> *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 <tom...@ho...>
> 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.
>
>

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

Are you absolutely sure that the debugger connector is orientated correctly with pin 1's matching?

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

> I tried unplugging the cable from the target completely and running again, and got the same error.

That makes sense since TDO on the Olimex will most likely be pulled or floating high by default so it'll be read as 1 when disconnected. The fact that it's reading high when connected is the issue. As I mentioned before, maybe the connector is not orientated properly (at both ends - Olimex and board connector). If it is then the issue may be board related. Either there's some jumper or other configuration needed for the debug connection to work, the debug block is locked from access on some way, the board is faulty, etc.

Re: Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

Good morning,

Thank you for this. I just checked the pin configuration and retried on
another board. The board is definitely powered on (the status lights come
on) and the cable orientation is correct, but I'm still getting the same
error... could it be something to do with my configuration files?

Interface:
adapter driver ftdi
ftdi device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
ftdi vid_pid 0x15ba 0x002b

ftdi layout_init 0x0908 0x0b1b
ftdi layout_signal nSRST -oe 0x0200
ftdi layout_signal nTRST -data 0x0100
ftdi layout_signal LED -data 0x0800

#jtag_nsrst_delay 200
#jtag_ntrst_delay 200
transport select jtag

reset_config srst_only

target:
if { [info exists CHIPNAME] } {
   set  _CHIPNAME $CHIPNAME
} else {
   set  _CHIPNAME ks869x
}

adapter speed 6000

# jtag scan chain
jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id
0xe

set _TARGETNAME $_CHIPNAME.cpu

target create $_TARGETNAME arm920t -endian little -chain-position
$_TARGETNAME

$_TARGETNAME configure -work-area-phys 0x10000 -work-area-size 0x40000
-work-area-backup 0

Thank you,


On Thu, 13 Jul 2023 at 17:49, Tommy Murphy <tom...@ho...> wrote:

> > I tried unplugging the cable from the target completely and running
> again, and got the same error.
>
> That makes sense since TDO on the Olimex will most likely be pulled or
> floating high by default so it'll be read as 1 when disconnected. The fact
> that it's reading high when connected is the issue. As I mentioned before,
> maybe the connector is not orientated properly (at both ends - Olimex and
> board connector). If it is then the issue may be board related. Either
> there's some jumper or other configuration needed for the debug connection
> to work, the debug block is locked from access on some way, the board is
> faulty, etc.
>

Re: Olimex ARM-USB-OCD-H Driver Issue

[Michael S. <mi...@sc...>]

On 14.07.23 15:55, Abe Lapped wrote:
> Good morning,
>
> Thank you for this. I just checked the pin configuration and retried 
> on another board. The board is definitely powered on (the status 
> lights come on) and the cable orientation is correct, but I'm still 
> getting the same error... could it be something to do with my 
> configuration files?

What about the reset config? Keeping the target in reset, or not 
de-asserting reset at the right time might make the JTAG port unresponsive.

cu

Michael

Re: Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

Here is a shot of my pinout, if it helps:
[image: image.png]

On Fri, 14 Jul 2023 at 09:55, Abe Lapped <abe...@gm...> wrote:

> Good morning,
>
> Thank you for this. I just checked the pin configuration and retried on
> another board. The board is definitely powered on (the status lights come
> on) and the cable orientation is correct, but I'm still getting the same
> error... could it be something to do with my configuration files?
>
> Interface:
> adapter driver ftdi
> ftdi device_desc "Olimex OpenOCD JTAG ARM-USB-OCD-H"
> ftdi vid_pid 0x15ba 0x002b
>
> ftdi layout_init 0x0908 0x0b1b
> ftdi layout_signal nSRST -oe 0x0200
> ftdi layout_signal nTRST -data 0x0100
> ftdi layout_signal LED -data 0x0800
>
> #jtag_nsrst_delay 200
> #jtag_ntrst_delay 200
> transport select jtag
>
> reset_config srst_only
>
> target:
> if { [info exists CHIPNAME] } {
>    set  _CHIPNAME $CHIPNAME
> } else {
>    set  _CHIPNAME ks869x
> }
>
> adapter speed 6000
>
> # jtag scan chain
> jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 0x1 -irmask 0xf
> -expected-id 0xe
>
> set _TARGETNAME $_CHIPNAME.cpu
>
> target create $_TARGETNAME arm920t -endian little -chain-position
> $_TARGETNAME
>
> $_TARGETNAME configure -work-area-phys 0x10000 -work-area-size 0x40000
> -work-area-backup 0
>
> Thank you,
>
>
> On Thu, 13 Jul 2023 at 17:49, Tommy Murphy <tom...@ho...>
> wrote:
>
>> > I tried unplugging the cable from the target completely and running
>> again, and got the same error.
>>
>> That makes sense since TDO on the Olimex will most likely be pulled or
>> floating high by default so it'll be read as 1 when disconnected. The fact
>> that it's reading high when connected is the issue. As I mentioned before,
>> maybe the connector is not orientated properly (at both ends - Olimex and
>> board connector). If it is then the issue may be board related. Either
>> there's some jumper or other configuration needed for the debug connection
>> to work, the debug block is locked from access on some way, the board is
>> faulty, etc.
>>
>

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

What happens when you simply do the following - using the Olimex configuration script already bundled with OpenOCD and not any custom scripts that you have created yourself?

`openocd -f interface/ftdi/olimex-arm-usb-ocd-h.cfg`

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

Also, you said that the target device is a Microchip KSZ8695X, but what is the board or is it some custom board? If it's a custom board then how was the debug connection verified as working?
________________________________
From: Tommy Murphy <tom...@ho...>
Sent: Friday, July 14, 2023 5:02:01 PM
To: Abe Lapped <abe...@gm...>; ope...@li... <ope...@li...>; die...@ou... <die...@ou...>; fer...@gm... <fer...@gm...>
Subject: Re: Olimex ARM-USB-OCD-H Driver Issue

What happens when you simply do the following - using the Olimex configuration script already bundled with OpenOCD and not any custom scripts that you have created yourself?

`openocd -f interface/ftdi/olimex-arm-usb-ocd-h.cfg`

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

Please attach/post logs rather than screenshots as not everybody can read the latter easily. I also can't see your post on the mailing list archive so it may have been blocked because of the images.

Re: Olimex ARM-USB-OCD-H Driver Issue

[Abe L. <abe...@gm...>]

Understood, thank you. I'm now at a point where I can interact with the SOC
and write to its memory using openOCD, but I can't see or interact with the
flash on the chip? Any idea how I would do this?

On Tue, 25 Jul 2023 at 13:07, Tommy Murphy <tom...@ho...> wrote:

> Please attach/post logs rather than screenshots as not everybody can read
> the latter easily. I also can't see your post on the mailing list archive
> so it may have been blocked because of the images.
>

Re: Olimex ARM-USB-OCD-H Driver Issue

[Tommy M. <tom...@ho...>]

>  I'm now at a point where I can interact with the SOC and write to its memory using openOCD, but I can't see or interact with the flash on the chip? Any idea how I would do this?

Impossible to comment without further details.
________________________________
From: Abe Lapped <abe...@gm...>
Sent: Tuesday 25 July 2023 20:09
To: Tommy Murphy <tom...@ho...>; mi...@sc... <mi...@sc...>; Paul Fertser <fer...@gm...>; die...@ou... <die...@ou...>; ope...@li... <ope...@li...>
Subject: Re: Olimex ARM-USB-OCD-H Driver Issue

Understood, thank you. I'm now at a point where I can interact with the SOC and write to its memory using openOCD, but I can't see or interact with the flash on the chip? Any idea how I would do this?

On Tue, 25 Jul 2023 at 13:07, Tommy Murphy <tom...@ho...<mailto:tom...@ho...>> wrote:
Please attach/post logs rather than screenshots as not everybody can read the latter easily. I also can't see your post on the mailing list archive so it may have been blocked because of the images.