nrjprog failed for an unknown reason

[Jonatan Martinez]

Hi, 

I'm trying to flash the firmware to some custom built pcb's with NRF52840 on it. The first time I flash it, it works great.

Then, if I try to erase the chip (or any other operation) it fails:

ERROR: nrfjprog failed for an unknown reason. Run the same command again with
ERROR: argument --log, contact Nordic Semiconductor and provide the generated
ERROR: log.log file to them. 

I've generated and attached the log file.

Thank you for your help

7752.log.log

[Håkon Alseth]

Hi,

 

I'm trying to flash the firmware to some custom built pcb's with NRF52840 on it. The first time I flash it, it works great.

This indicates that there's no issues with the hardware connection, which is good.

If a device is asserting early in the firmware process, you will get into a reset loop (default assertion behavior is soft reset), which can be hard to recover from.

 

Could you try "nrfjprog --recover -f nrf52" ?

If that still fails, could you try this recover loop, while you power on/off the custom board (keep debugger powered while doing this):

https://devzone.nordicsemi.com/f/nordic-q-a/45078/nrf52832-not-connected-anymore-after-first-trying-to-debug-keil/177579#177579

 

Kind regards,

Håkon

[jjvicentenavarrete]

Hi all,

It seems that this issue is the same that the one exposed in this thread (not fixed):

https://devzone.nordicsemi.com/f/nordic-q-a/38869/unable-to-recover-nrf52832-with-jlink-after-reset-event

https://electronics.stackexchange.com/questions/204996/stm32-st-link-cannot-connect-to-mcu-after-successful-programming

It has something to do with the reset line of the Jlink (not sure if nrfjprog is involved). It keeps asserted any time the debugger gets connected. This line is correctly pulled up so, i assume is the debugger which is forcing the line to gow low.

It happens ONLY with a Jlink Base but, it doesn´t with a Jlink Edu.

Is there any known bug in nrfjprog tools regarding this issue?