Problem with ARM-USB-TINY-H

[aho]

I have an Olimex ARM-USB-OCD-H which works fine. Then I also bought an ARM-USB-TINY-H for my colleague, since we do not need the serial port and power from the ARM-USB-OCD-H.

The problem now is that the ARM-USB-OCD-H works fine, but not the ARM-USB-TINY-H.

When I start OpenOCD with the ARM-USB-OCD-H, it says:

Code Select Expand

Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : FTDI SWD mode enabled
adapter speed: 1800 kHz
cortex_m reset_config sysresetreq
Info : flash bank command
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Info : clock speed 1800 kHz
Info : SWD DPIDR 0x0bd11477
Warn : Silicon bug: single stepping will enter pending exception handler!
Info : atsame70q21.cpu: hardware has 8 breakpoints, 4 watchpoints


When I start OpenOCD with the ARM-USB-TINY-H, it says:

Code Select Expand

Open On-Chip Debugger 0.10.0
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : FTDI SWD mode enabled
adapter speed: 1800 kHz
cortex_m reset_config sysresetreq
Info : flash bank command
srst_only separate srst_gates_jtag srst_open_drain connect_deassert_srst
Info : clock speed 1800 kHz
Info : SWD DPIDR 0x0bd11477
Error: Could not initialize the debug port


I suppose I have installed the drivers correctly using the Zadig program.
What could that be?

I im using the ARM-JTAG-SWD interface.

[LubOlimex]

Some ideas:

1. Where did you place the ARM-JTAG-SWD? It should be connected directly to the ARM-USB-TINY-H (not via a cable).

2. What are the exact commands that you issue? I guess you changed the cfg from olimex-arm-usb-ocd-h.cfg to olimex-arm-usb-tiny-h.cfg but who knows.

3. What is your target? What is the voltage of the target? Consider that ARM-USB-OCD-H can work at lower voltages - 1.65V – 5.0V DC range while ARM-USB-TINY-H works from 2V to 5V.

[aho]

Thanks for your reply.

1. Where did you place the ARM-JTAG-SWD? It should be connected directly to the ARM-USB-TINY-H (not via a cable).

The ARM-JTAG-SWD is connected directy to the ARM-USB-TINY-H. Between the ARM-JTAG-SWD and the target there is a cable.

Usb cable ---- ARM-USB-OCD-H or -TINY-H ---- ARM-JTAG-SWD ---- cable ---- target

I use the same cables and ARM-JTAG-SWD, I just switch the ARM-USB-OCD-H and the ARM-USB-TINY-H.

2. What are the exact commands that you issue? I guess you changed the cfg from olimex-arm-usb-ocd-h.cfg to olimex-arm-usb-tiny-h.cfg but who knows.

These are the configuration files I use:

For the ARM-USB-TINY-H

Code Select Expand

source [find interface/ftdi/olimex-arm-usb-tiny-h.cfg]
source [find interface/ftdi/olimex-arm-jtag-swd.cfg]

set CHIPNAME atsame70q21

source [find target/atsamv.cfg]

reset_config srst_only


For the ARM-USB-OCD-H

Code Select Expand


source [find interface/ftdi/olimex-arm-usb-ocd-h.cfg]
source [find interface/ftdi/olimex-arm-jtag-swd.cfg]

set CHIPNAME atsame70q21

source [find target/atsamv.cfg]

reset_config srst_only


3. What is your target? What is the voltage of the target? Consider that ARM-USB-OCD-H can work at lower voltages - 1.65V – 5.0V DC range while ARM-USB-TINY-H works from 2V to 5V.

I use the Atmel SAME70Xplained eval board.
The supply voltage of the CPU is 3.3V.

Is there anything else I could try?
Could it be that the ARM-USB-TINY-H is defective?

[LubOlimex]

Hmm this forum user used ARM-USB-TINY-H with the same board successfully: https://www.olimex.com/forum/index.php?topic=6012.0 - maybe there is more feedback for similar setup online.

Also try with the slightly different "reset_config srst_only srst_pulls_trst".

> Could it be that the ARM-USB-TINY-H is defective?

It can be damaged somehow. We test each unit empirically and DOD is unlikely but the board can get damaged during transportation, or the customer can damage it unknowingly.

> Is there anything else I could try?

If you doubt the ARM-USB-TINY-H is faulty, the best idea would be to test it with another target chip via JTAG (without the SWD adapter). I would suggest testing with something popular like STM32, since this would clear probable problems with the OpenOCD configurations.

It is also worth checking and posting in the OpenOCD forum lists, someone from the OpenOCD community might know more about the nature of this error.

[aho]

The ARM-USB-TINY-H works with an STM32, both JTAG and SWD with the adapter, so it is not defective.

I don't know why it would not work with the Atmel.

For the time being, I will be using the ARM-USB-OCD-H since that works.