https://devzone.nordicsemi.com/f/nordic-q-a/25935/nrf52832-crashes-during-soft-device-updateHi, I am writing a boot loader which does not need to use the soft device as the image is being transferred over an SPI interface. I have merged the softdevice and my application code together to make a single payload to update. I am also storingen-USTelligent Community 13Sat, 14 Oct 2017 11:35:39 GMThttps://devzone.nordicsemi.com/thread/102169?ContentTypeID=1Sat, 14 Oct 2017 11:35:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:718d1e48-e192-4773-a61a-1363566a0212Raiyan<p>THANKS for the answer. I found that if I skip the MBR it does not crash and successfully boots into the boot loader. Even if the SD is not there.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/102168?ContentTypeID=1Fri, 13 Oct 2017 19:54:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:6826750e-adce-43ac-b083-b0cdb7db9747Turbo J<blockquote> <p>When trying to copy the binary from the external flash to the internal I am erasing from address 0x0 to 0x6FFFF which I have dedicated from the soft device and the application.</p> </blockquote> <p>Why? This will erase the MBR and the interrupt vector table (at address <code>0x00</code>). Until you can finish the writing - without interrupts or with a changed VTOR - the device will end up bricked in a power loss event.</p> <p>The MBR has its own syscalls to safely replace the SD. You should never erase the first flash sector in the field, as MBR should be identical across SD versions.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/102167?ContentTypeID=1Fri, 13 Oct 2017 18:42:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2e73980c-6ad5-41c2-ac61-b24356fb75edsuperpak<p>Hi, Raiyan. May I see your code for the bootloader and how you are writing to the internal flash?</p><div style="clear:both;"></div>