Unable to flash due to high reset pin

[Bjarne Kvæstad]

Hi

I'm currently working on the 10028 DK board, which was working flawlessly until I used the J-link RTT Viewer, and pushed the IF BOOT/RESET-button. Now, when I try to flash the MCU I get this in Keil:

*JLink Info: Device "NRF51422_XXAC" selected. JLink info:

DLL: V5.12f, compiled May 17 2016 16:03:35 Firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Nov 14 2016 16:58:29 Hardware: V1.00 S/N : 681151478
**JLink Warning: RESET (pin 15) high, but should be low. Please check target hardware. ***JLink Error: Communication timed out: Requested 20 bytes, received 0 bytes ! Could not read hardware status! Error: Flash Download failed

• Target DLL has been cancelled

I've tried to update to the newest J-Link bootloader, with no luck I've tried to recover the device as explained here, but get this output:

nrfjprog --recover --family NRF51

Recovering device. This operation might take 30s. ERROR: Cannot connect to any nRF device. Please make sure a device is ERROR: connected to the debugger and supplied.

Using nRFgo Studio, does not work either, nRFgo is crashing if i try to connect to the debugger.

Also, I know that the MCU is still running because the LED 1-4 are flashing as expected.

[endnode]

Have you upgraded to latest SEGGER J-Link and NRFTOOLs/nRF Go Studio? It seems you are using old version (SEGGER J-Link V5.12f) but hard to tell from what you have here...

[Bjarne Kvæstad]

Both SEGGER J-link and NRFTOOLS applications was downloaded today, and should be the newest version. But it seems like Keil is using a old dll.

[endnode]

I've now noticed you have pushed IF BOOT/RESET button. Note that if you press it long time then you put auxiliary MCU (Atmel generic MCU with SEGGER J-Link OB FW or mBed FW) to bootloader mode. If so then it will stop working as SWD to target nRF5x chip on the board... if it is not the case then I would use different machine, there are several Q&As on this forum where users claim how something doesn't work for days and then it works instantly on different system...

[Bjarne Kvæstad]

The debugger is set in bootloader mode if the reset button is held down during powerup, and is not the case here. I've now tried from an other computer with a simular setup, but with the same results, RESET-pin high...

[Vidar Berg]

I've seen this isse before, but has always been able to recover by powercycling the kit. You could try to re-program the Jlink fw and see if that helps: put the kit in DFU mode and copy the following FW image to the BOOTLOADER drive.