https://devzone.nordicsemi.com/f/nordic-q-a/117783/serial-recovery-mynewt-bootloaderLesson 8 of &quot;nRF Connect SDK Intermediate&quot; DevAcademy course deals with Bootloaders. I&#39;ve successfully done the exercise of updating firmware using the off-the-shelf mcuboot bootloader. Unfortunately our actual product does not include a button so ween-USTelligent Community 13Wed, 08 Jan 2025 06:02:02 GMThttps://devzone.nordicsemi.com/thread/517372?ContentTypeID=1Wed, 08 Jan 2025 06:02:02 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0937d97d-eb50-4a86-889d-236b9c163073Spi<p>Hello Vidar. Thanks for your response.&nbsp; Using the off-the-shelf mcuboot and off-the-shelf west.yml would be ideal (and I think BOOT_SERIAL_BOOT_MODE could be what we need).&nbsp; If that fails I might come back with follow-up questions as to the specifics of &quot;forking&quot; the bootloader plus getting a modified west.yml to point to that fork.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/517120?ContentTypeID=1Tue, 07 Jan 2025 05:49:04 GMT137ad170-7792-4731-bb38-c0d22fbe4515:f4ea2972-4e80-461b-bfe5-797fe5e253c5Vidar Berg<p>Hello,</p> <p>Yes, you can create your own west manifest (see <a href="https://docs.zephyrproject.org/latest/develop/west/workspaces.html#t2-star-topology-application-is-the-manifest-repository">T2: Star topology, application is the manifest repository</a>) and specify additional dependencies, such as another fork of the bootloader. But&nbsp;MCUBoot already supports other methods for buttonless entry into serial recovery:&nbsp;<a href="https://github.com/nrfconnect/sdk-mcuboot/blob/b82206c15fff357c151c24bf97c99c4348d14a46/boot/zephyr/Kconfig.serial_recovery#L139">https://github.com/nrfconnect/sdk-mcuboot/blob/b82206c15fff357c151c24bf97c99c4348d14a46/boot/zephyr/Kconfig.serial_recovery#L139</a>.</p> <p>Best regards,</p> <p>Vidar&nbsp;</p><div style="clear:both;"></div>