ARM-USB-TINY and Windows 10

[jmaynard]

Trying to get OpenOCD 0.10 running on my Windows 10 laptop with an ARM-USB-TINY. It's a custom board with an Atmel ATSAMV70. I've used Zadig 2.3 to install the WinUSB drivers. So far, I think I've done everything right, but when I start OpenOCD, I get this:

c:\sbc6\Tools\openocd-0.10.0\bin-x64>openocd -f interface/ftdi/olimex-jtag-tiny.cfg -f target/atsamv.cfg
Open On-Chip Debugger 0.10.0
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>'.
adapter speed: 1800 kHz
cortex_m reset_config sysresetreq
Info : flash bank command
Error: libusb_open() failed with LIBUSB_ERROR_NOT_SUPPORTED
Info : clock speed 1800 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: samv.cpu: IR capture error; saw 0x00 not 0x01
Warn : Bypassing JTAG setup events due to errors
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Invalid ACK (0) in DAP response
Error: Could not initialize the debug port

I'm pretty sure I'm missing something dumb, but what?

Update: I've tried the steps in the recent post about uninstalling and running FTClean and then reinstalling. I can't seem to get it to run no matter what I do.

[JohnS]

All zeroes is almost always a hardware problem (as it basically says).  You get to guess why.

John

[LubOlimex]

Indeed, this doesn't seem like a driver issue. If the JTAG is unrecognized it ends with something like "Error: unable to open ftdi device with vid xxxx, pid xxxx, description 'Olimex OpenOCD JTAG ARM-USB-TINY' and serial '*'"

Check the hardware connections. Check if the target is powered.

Maybe test with other version of OpenOCD.

Best regards,
Lub/OLIMEX

[jmaynard]

I tried this with the previous version of our board (with an AT91SAM7X) that I'd had working before. Sure enough, it worked fine with that.

A bit more digging in the datasheet and come to find out that the SAM V70 series uses JTAG-SWD. I've got a couple of ARM-JTAG-SWD adpters ordered, and we'll see where that goes.

So it's not a software problem. Thanks for your help.