ARM-USB-TINY usage issues

[mangokid]

After moving to a new system I have been unable to get this JTAG adapter working again with OpecOCD 0.9.0 (I have also made some attempts at using 0.7 but havnt had success with the ftd2xx drivers testing). The target in this case has been tested with the same debugger on a windows platform so I am confident it is not a hardware issue. There is only one device in the chain (STM32f1).

Code Select Expand


openocd -f /usr/local/share/openocd/scripts/interface/olimex-arm-usb-tiny-h.cfg -f /usr/local/share/openocd/scripts/target/stm32f1x.cfg


this yields

Code Select Expand


Open On-Chip Debugger 0.9.0 (2016-09-28-11:21)
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: 1000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Info : clock speed 1000 kHz
Info : JTAG tap: stm32f1x.cpu tap/device found: 0x3ba00477 (mfg: 0x23b, part: 0xba00, ver: 0x3)
Info : JTAG tap: stm32f1x.bs tap/device found: 0x16410041 (mfg: 0x020, part: 0x6410, ver: 0x1)
Info : TAP auto0.tap does not have IDCODE
Info : TAP auto1.tap does not have IDCODE
Info : TAP auto2.tap does not have IDCODE
Info : TAP auto3.tap does not have IDCODE
Info : TAP auto4.tap does not have IDCODE
Info : TAP auto5.tap does not have IDCODE
Info : TAP auto6.tap does not have IDCODE
Info : TAP auto7.tap does not have IDCODE
Info : TAP auto8.tap does not have IDCODE
Info : TAP auto9.tap does not have IDCODE
Info : TAP auto10.tap does not have IDCODE
Info : TAP auto11.tap does not have IDCODE
Info : TAP auto12.tap does not have IDCODE
Info : TAP auto13.tap does not have IDCODE
Info : TAP auto14.tap does not have IDCODE
Info : TAP auto15.tap does not have IDCODE
Info : TAP auto16.tap does not have IDCODE
Info : TAP auto17.tap does not have IDCODE
Info : TAP auto18.tap does not have IDCODE
Warn : Unexpected idcode after end of chain: 83 0x00000000
Warn : Unexpected idcode after end of chain: 115 0x00000000
Warn : Unexpected idcode after end of chain: 147 0x00000000
Warn : Unexpected idcode after end of chain: 179 0x00000000
Warn : Unexpected idcode after end of chain: 211 0x00000000
Warn : Unexpected idcode after end of chain: 243 0x00000000
Warn : Unexpected idcode after end of chain: 275 0x00000000
Warn : Unexpected idcode after end of chain: 307 0x00000000
Warn : Unexpected idcode after end of chain: 339 0x00000000
Warn : Unexpected idcode after end of chain: 371 0x00000000
Warn : Unexpected idcode after end of chain: 403 0x00000000
Warn : Unexpected idcode after end of chain: 435 0x00000000
Warn : Unexpected idcode after end of chain: 467 0x00000000
Warn : Unexpected idcode after end of chain: 499 0x00000000
Warn : Unexpected idcode after end of chain: 531 0x00000000
Warn : Unexpected idcode after end of chain: 563 0x00000000
Warn : Unexpected idcode after end of chain: 595 0x00000000
Warn : Unexpected idcode after end of chain: 627 0x00000000
Error: double-check your JTAG setup (interface, speed, ...)
Error: Trying to use configured scan chain anyway...
Warn : AUTO auto0.tap - use "jtag newtap auto0 tap -irlen 2 -expected-id 0x00000000"
Error: auto0.tap: IR capture error; saw 0x0000 not 0x0001
Warn : Bypassing JTAG setup events due to errors
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened
Error: Debug regions are unpowered, an unexpected reset might have happened


The result is the same when using

Code Select Expand


openocd -f /usr/local/share/openocd/scripts/interface/ftdi/olimex-arm-usb-tiny-h.cfg -f /usr/local/share/openocd/scripts/target/stm32f1x.cfg


I suspect there is some error with the ftdi drivers somewhere. It is also suspicious that with 0.7 I would have similar results but OpenOCD would exit with a segmentation fault when reset was issued. Changing speeds also seems to have no effect.

Any help would be appreciated 

Platform: 64 - Ubunutu 16 4.4.0-38-generic

[JohnS]

Probably best to post on the oocd ML and they'll want -d3 log.

Forget the ftd2xx they've been fairly bad at best.

Worth also detailing the target on the ML.

John