Questions on ERASEALL and UICR registers.https://devzone.nordicsemi.com/f/nordic-q-a/93937/questions-on-eraseall-and-uicr-registersHello, I got several questions below: 1. Once the CTRL_AP setup was already configured below, even if NVMC.ERASEALL is set , does that mean UICR registers ( NRF_UICR -&gt; APPROTECT, and etc ) can&#39;t be changed anymore? /* Prevent from unlockingen-USTelligent Community 13Wed, 16 Nov 2022 21:34:28 GMTRE: Questions on ERASEALL and UICR registers.https://devzone.nordicsemi.com/thread/396092?ContentTypeID=1Wed, 16 Nov 2022 21:34:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:093be38f-7dab-4533-8d4b-c07a6f5f507bNaeem Maroof<p>Hi Jaewook,</p> <p>Thankyou for contacting DevZone at NordicSemi.</p> <p>To enable port protection access for both secure and non-secure modes, we use registers UICR.SECUREAPPROTECT and UICR.APPROTECT, as well as CTRLAP.APPROTECT.DISABLE and CTRLAP.SECUREAPPROTECT.DISABLE; that is what you are doing.</p> <p>Erase protection (ERASEPROTECT) protects the flash and UICR parts of the non-volatile memory from being erased. Erase protection can be temporarily disabled from the control access port.</p> <p>1) So yes, as per your case description, contents of UICR will not be changed.<br />2) Yes, such a setup should run every boot as it is app level.</p> <p>In fact you can setup your project to see as you have described and observe value and status of registers.</p> <p>Thanks,<br />Naeem</p><div style="clear:both;"></div>