https://devzone.nordicsemi.com/f/nordic-q-a/80772/after-setting-the-readback-protection-execute-pinreset-the-device-is-not-runningAfter 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-operationalen-USTelligent Community 13Mon, 18 Oct 2021 15:10:46 GMThttps://devzone.nordicsemi.com/thread/334670?ContentTypeID=1Mon, 18 Oct 2021 15:10:46 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c3ad06c3-7c02-4552-8856-447f2f3a62acH&#229;kon Alseth<p>Hi,</p> <p>&nbsp;</p> [quote user=""]<p>After burning the application, the following operations were performed:<br /> nrfjprog.exe -f NRF52 --rbp ALL<br />nrfjprog.exe -f NRF52 --pinreset</p> <p>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?</p>[/quote] <p>It sounds like there is a race-condition happening in the firmware when the battery is connected. Have you tried debugging the situation?</p> <p>Meaning, flash the devices with your firmware, do not do readback protection, then attach the battery to see if the issue persists?</p> <p>&nbsp;</p> <p>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.</p> <p>&nbsp;</p> <p>Kind regards,</p> <p>Håkon</p><div style="clear:both;"></div>