I was doing power profiling using the PPK. All was working OK, as far as I went. I disconnected the PPK, and returned to normal debugging with stand-alone DK. Now I can't get the DK to respond.
Symptoms:
- JLink appears as a mass storage device when I plug it in to the USB.
- When I try to download code using JLink GDB I get
J-Link GDB Server failed: Could not connect to target. Please check if target is powered and if ribbon cable is plugged properly.
For more details, see the JLinkGDBServerCL.exe console.
- When I try to erase the DK, J-Flash Lite 6.12 says:
Communication timed out: Requested 20 bytes, received 0 bytes ! Could not read hardware status! Erase Thread exited Initialization of debug session failed. Could not connect to target.
- When I tried resetting, I got
nrfjprog --recover -f NRF52 --log nrfjprog verion 9.2.0
FUNCTION: open_dll. FUNCTION: open_dll. FUNCTION: enum_emu_snr. FUNCTION: enum_emu_snr. FUNCTION: enum_emu_snr. FUNCTION: enum_emu_snr. FUNCTION: connect_to_emu_with_snr. FUNCTION: connect_to_emu_with_snr. FUNCTION: connect_to_emu_without_snr. FUNCTION: enum_emu_snr. Device "NRF52832_XXAA" selected. FUNCTION: recover. FUNCTION: recover. JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -1. JLinkARM.dll CORESIGHT_WriteAPDPReg returned error -102. FUNCTION: close_dll. FUNCTION: close_dll.
- When I plugged the PPK back onto the DK and "erase" and "downloads" work, but it appears the code is not being downloaded into the DK.
I've read all through the PPK documentation thoroughly, and I can't see anything I have missed, but maybe there is something fundamental I misunderstand?
