October 17, 2021, 06:01:46 am

JTAG/ ARM-USB-OCD Problem

Started by alfie.1980, February 03, 2016, 03:21:16 pm

Previous topic - Next topic

alfie.1980

February 03, 2016, 03:21:16 pm Last Edit: February 03, 2016, 03:22:47 pm by alfie.1980
Hi,

I am trying to have a working tool chain including:

- Open On-Chip Debugger 0.9.0
- Luna Service Release 2 (4.4.2)
- ARM-USB-OCD
- Custom STM32F4 HW platform

I am trying to establish the JTAG connection but receiving the following error:

xxxx:~/Downloads/openocd-0.9.0$ openocd -f /usr/local/share/openocd/scripts/interface/ftdi/olimex-arm-usb-ocd.cfg -f /usr/local/share/openocd/scripts/target/stm32f4x.cfg
Open On-Chip Debugger 0.9.0 (2016-02-03-13:44)
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: 2000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
none separate
cortex_m reset_config sysresetreq
Info : clock speed 2000 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: stm32f4x.cpu: IR capture error; saw 0x0f not 0x01
Warn : Bypassing JTAG setup events due to errors
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction
Warn : Invalid ACK 0x7 in JTAG-DP transaction


That would be great if someone give me some hints to find the problem!

Thanks and best regards,

Alfie.

LubOlimex

Hey,

This problem appears usually due to:

1) Wrong or incomplete connections between the debugger and the target. I would recommend you to take a look at one of our STM32F4 designs and compare the JTAG connector. For example, refer to the schematic of STM32-H407 (which is also an open-hardware board and the Eagle files are available at the product's page): https://www.olimex.com/Products/ARM/ST/STM32-H407/resources/STM32-H407_Rev_B_sch.pdf

2) The on-board code uses one of the wires that handle the JTAG interface. Make sure you are not using any of the signals used for the JTAG interface. Alternatively, set the board to boot from another location or memory (in case the code in the default boot locations does bug the JTAG lines).

Best regards,
Lub/OLIMEX
Technical support and documentation manager at Olimex