https://devzone.nordicsemi.com/f/nordic-q-a/115213/customized-bootloader-without-mcubootHello. I wanna develop customized bootloader using C. There&#39;s two purpose for this. 1) Select application area : Slot 1 for main application and Slot 2 for new firmware(Partially updated or fully updated) 2) Manufacturing Test Mode Canen-USTelligent Community 13Thu, 03 Oct 2024 16:25:52 GMThttps://devzone.nordicsemi.com/thread/504890?ContentTypeID=1Thu, 03 Oct 2024 16:25:52 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4dc4935a-e775-4220-857e-055fceec1298Menon<p>Hello,</p> <p>I believe the answer is yes, you can develop a custom bootloader and integrate it with the nRF Connect SDK. However, the support I can provide for the development will be very limited or possibly nonexistent. A better approach I can suggest is customizing MCUboot and leveraging Zephyr’s capabilities within NCS. This way, you can efficiently achieve both functionalities. The nRF Connect SDK uses MCUboot as the default bootloader, and it offers the flexibility to handle multi-slot applications and selective booting. Since<a href="https://github.com/nrfconnect/sdk-mcuboot"> MCUboot is a submodule in the nRF Connect SDK</a>, you can modify the local copy within your SDK. If you need to make significant changes, it might be a good idea to fork the MCUboot repository or create a patch.</p> <p>Kind regards,<br />Abhijith</p><div style="clear:both;"></div>