After setting the readback protection, execute pinreset, the device is not running

[Jim]

After burning the application, the following operations were performed:
nrfjprog.exe -f NRF52 --rbp ALL
nrfjprog.exe -f NRF52 --pinreset

There are a total of 600 devices, all of which are equipped with batteries. 59 devices are found to be non-operational. If the non-operational devices are re-powered, the devices will operate normally. Is there a solution to this problem?

[Håkon Alseth]

Hi,

 

After burning the application, the following operations were performed:
nrfjprog.exe -f NRF52 --rbp ALL
nrfjprog.exe -f NRF52 --pinreset

There are a total of 600 devices, all of which are equipped with batteries. 59 devices are found to be non-operational. If the non-operational devices are re-powered, the devices will operate normally. Is there a solution to this problem?

It sounds like there is a race-condition happening in the firmware when the battery is connected. Have you tried debugging the situation?

Meaning, flash the devices with your firmware, do not do readback protection, then attach the battery to see if the issue persists?

 

If you get into the scenario, you can attach the debugger without resetting the target device to see if/where it is stuck in firmware.

 

Kind regards,

Håkon