OpenOCD - JLink segger - failed to download

[sape_4812941]

Hi, 

We have a design that use the laird Sterling EWB (cyw4343w + STM32f4x). I was running test on the sterling laird ewb dev kit via USB (FTDI chip)  and everything works fine. Now we are trying to use the JTAG connector with our JLINK segger and we are not able to program the board (our board and the dev kit that as a Jtag connector header). 

"**** OpenOCD failed - ensure you have installed the driver from the drivers directory, and that the debugger is not running **** In Linux this may be due to USB access permissions. In a virtual machine it may be due to USB passthrough settings. Check in the task list that another OpenOCD process is not running. Check that you have the correct target and JTAG device plugged in. ****"
Downloading DCT ...

Here's what we have done so far : 

• Change the Jlink driver for the usblibK (3.1.0.0 and 3.0.7.0 try both)
• Add reset_config trst_and_srst srst_push_pull  to the jlink.cfg file 
• Change JTAG ?= CYW9WCD1EVAL1 for JTAG ?= jlink.

Our make target look like : "app folder"."app-name"-LAIRD_EWB JTAG=jlink download run.

We try every combination of everything listed but we always add the same result. 

In the openocd_log.txt, we got this error (attached files) : 

Error: JTAG scan chain interrogation failed: all ones
Error: Check JTAG interface, timings, target power, etc.

Any help would be appreciated, we are running out of solutions here, 

Thank you. 

[Aditi_B]

Hi,

Can you share the snapshot of the device manager? I basically want to check how is your Jlink connection being enumerated.

Thanks

Aditi

[sape_4812941]

Thanks for the answer, sorry for the delay normally I received Email when I got a reply, 

Anyway here's the device manager : 

In the mean time we have done a lot of testing and still not able to push any firmware into our board. 

We also try with the olimex arm USB tiny-H and got the same result.  We managed to push a firmware via the JLINK command line interface but we need to do it in Wiced. We always got the : JTAG scan chain interrogation failed: all zeroes or all ones error. 

Thanks 

[sape_4812941 · Accepted solution]

We found the solution. Our custom board link the JTAG SRST to the TRST of our module. We need to specify this to the JLINK.cfg file by adding (reset_config srst_pulls_trst). We also had to remove the reset line from the STM32f4x.cfg file .