openocd 0.8.0 and olimex-arm-usb-ocd-h

Started by patricky22, February 10, 2022, 03:12:05 AM

Previous topic - Next topic



Can not connect jtag.  Get the following errors:

Microsoft Windows [Version 10.0.19042.1466]
(c) Microsoft Corporation. All rights reserved.

C:\Users\patrick.yang>openocd.exe -f ./interface/ftdi/olimex-arm-usb-ocd-h.cfg -f ./target/str710.cfg
Open On-Chip Debugger 0.9.0-rc1 (2015-04-24-22:09)
Licensed under GNU GPL v2
For bug reports, read
adapter speed: 10 kHz
trst_and_srst srst_pulls_trst 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>'.
Info : clock speed 10 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: str710.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 : str710.cpu: hardware has 2 breakpoint/watchpoint units
Warn : ThumbEE -- incomplete support

1. Installed driver through Zadig with WinUSB driver.
2. The olimex-arm-usb-ocd-h debugger probe can be recognized in the Windows device manage.
3. The MCU is STR711F.

Thank you for the help in advance!



JTAG and OpenOCD seems fine. The issue is between the JTAG and the target. This is quite serious error message - it means nothing is working between the JTAG and target. If you remove the calbe bettween the JTAG and target you will probably have the same error message.

It can be caused by improper cabling, wrong reset line, it also can be that the str710.cfg is not working nice. Make sure to search online for the error, aka:

"Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc."
Technical support and documentation manager at Olimex


You are correct.  Got the same errors when unplugged the cable from the board.

MCU STR711FR2T6 is used on the board.  Shall I use the target file str710.cfg or other config file?




First investigate the hardware connections between the debugger and the target make sure all JTAG signals are properly connected. Make sure you are using SRST for reset. Often people use TRST, instead of SRST. For the most common JTAG setup - TRST is an optional signal, while SRST is mandatory. Try different reset strategies since this part "trst_and_srst srst_pulls_trst srst_gates_jtag trst_push_pull srst_open_drain connect_deassert_srst" seems like all reset strategies are put into the config.

Check the OpenOCD mail lists and related forums for someone experiencing issues with  str710.cfg. Notice that STR710 is old chip, so there should be plenty of info online.
Technical support and documentation manager at Olimex