RE: STLINK-V2 -> ChipID = 0 / timed out while waiting for target halted

VyacheslavSS — Fri, 10 Jul 2020 15:15:46 GMT

that problem solved.

/usr/local/bin/openocd -f $(OPENOCD_HOME)/interface/stlink-dap.cfg -f $(OPENOCD_HOME)/target/nrf52.cfg

and

>dap apreg 1 0x04 0x01

unlocking chip.

And next. Chip is 52840

I download SDK nrf5_SDK_for_Mesh_v4.2.0_src.

Then upload softdevice: s140_nrf52_6.0.0_softdevice.hex (or s140_nrf52_7.0.1_softdevice.hex)

and demo: blinky_nrf52840_xxAA_s140_6.0.0.hex (or blinky_nrf52840_xxAA_s140_7.0.1.hex)

by:

write_blinky600:
$(OCD) -c init -c "reset halt" -c "flash write_image $(BLINKY_FILE_140_600)" -c "flash write_image $(BLINKY_FILE_140_600)" -c reset -c exit

write_blinky701:
$(OCD) -c init -c "reset halt" -c "flash write_image $(SOFTDEV_140_701)" -c "flash write_image $(BLINKY_FILE_140_701)" -c reset -c exit

Output log:

Open On-Chip Debugger 0.10.0+dev-01321-ge8cfdd4a-dirty (2020-07-10-11:52)
Licensed under GNU GPL v2
For bug reports, read
openocd.org/.../bugs.html
Info : auto-selecting first available session transport "hla_swd". To override use 'transport select <transport>'.
Info : The selected transport took over low-level target control. The results might differ compared to plain JTAG/SWD

nRF52 device has a CTRL-AP dedicated to recover the device from AP lock.
A high level adapter (like a ST-Link) you are currently using cannot access
the CTRL-AP so 'nrf52_recover' command will not work.
Do not enable UICR APPROTECT.

Info : clock speed 1000 kHz
Info : STLINK V2J29S7 (API v2) VID:PID 0483:3748
Info : Target voltage: 3.176563
Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
Info : starting gdb server for nrf52.cpu on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000880 msp: 0x20000400
Info : nRF52840-xxAA(build code: C0) 1024kB Flash, 256kB RAM
Warn : Flash protection of this nRF device is not supported
wrote 1656 bytes from file /home/shubin/electronic/firmware/nrf/nrf5_SDK_for_Mesh_v4.2.0_src/bin/blinky/blinky_nrf52840_xxAA_s140_6.0.0.hex in 0.097093s (16.656 KiB/s)

wrote 1656 bytes from file /home/shubin/electronic/firmware/nrf/nrf5_SDK_for_Mesh_v4.2.0_src/bin/blinky/blinky_nrf52840_xxAA_s140_6.0.0.hex in 0.091625s (17.650 KiB/s)

Looking for device at nRF Blinky Android software. Nothing found

Led not blinked.

One time, i don't remember, what combination was used, the diode began to blink with a frequency of 2 Hz, but device scanner nothing found.

RE: STLINK-V2 -> ChipID = 0 / timed out while waiting for target halted

Andreas — Fri, 10 Jul 2020 12:48:28 GMT

Hi,

Unfortunately we do not know this debugger and do not support it. We know that some have used it and that it might work in some cases or with some tools, but we can not give any guarantees. There is some material on Devzone, I recommend that you try searching for your answer.

Best regards,

Andreas