https://devzone.nordicsemi.com/f/nordic-q-a/79097/how-to-make-non-secure-slim-ota-bootloader-on-nrf52810Hello, I found this blog post in google and I decide to try it. I have couple of NrF52810 currently that we struggle with the limited space and the solution described in the post it&#39;s doable for purpose of the project. I did manage to build secure bootloaderen-USTelligent Community 13Wed, 01 Sep 2021 11:10:17 GMThttps://devzone.nordicsemi.com/thread/327569?ContentTypeID=1Wed, 01 Sep 2021 11:10:17 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e629ffbc-e9f5-4d18-a61c-6eeed6fd7741Amanda Hsieh<p>Hi,</p> <p>Seems that post lost some detail.&nbsp;&nbsp;</p> <p>You need to do more changes than just disable NRF_CRYPTO_ENABLED. There is an &quot;open bootloader&quot; project in the SDK, but this still requires signature verification for bootloader updates, but not application or softdevice. Removing signature verification altogether and removing the crypto-related code would require a bit of work as the code has not been written with that in mind. I do not expect it is a huge task though, as you can see how signature verification is skipped with the open bootloader project.&nbsp;</p> <p>Regards,&nbsp;<br />Amanda&nbsp;</p><div style="clear:both;"></div>