https://devzone.nordicsemi.com/f/nordic-q-a/30257/new-nrf52832-will-not-start-with-softdevice-s132-sdk14-2I have two nRF52832 devices. One of them I have been using for a while and the other is brand new. My BLE application will flash and run just fine on the old device but not on the new one. I have flashed S132 and the application code using the same procedureen-USTelligent Community 13Wed, 07 Feb 2018 19:39:31 GMThttps://devzone.nordicsemi.com/thread/120166?ContentTypeID=1Wed, 07 Feb 2018 19:39:31 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c4fcf6ff-f1de-4089-a57c-18c3ffed3998YYZ<p>Thanks for the prompt response Vidar, that seems to have fixed it.&nbsp;</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/120018?ContentTypeID=1Tue, 06 Feb 2018 20:56:27 GMT137ad170-7792-4731-bb38-c0d22fbe4515:d8d0ad4f-6c74-4f38-973a-dff6e810f6c0Vidar Berg<p>Hi,</p> <p>The master boot record (MBR) assumes that a bootloader is present if UICR-&gt;NRFFW[0] has been written to (<a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s132.sds/dita/softdevices/s130/mbr_bootloader/mbr_sd_reset_behavior.html?cp=2_3_1_0_11_2">MBR startup sequence</a>). Did you check that address as well? Assuming this register is set the solution would be to do a full chip erase or an UICR erase. I&#39;m not sure if jlink commander supports full erase / uicr erase, you may have to write to the NVMC peripheral directly in that case. With nrfjprog you can use the following commands:</p> <ul> <li>nrfjprog -e // full chiperase</li> <li>nrfjprog --eraseuicr &nbsp; </li> </ul><div style="clear:both;"></div>