https://devzone.nordicsemi.com/f/nordic-q-a/117512/nrf52840-time-to-reboot-after-ble-otaI am performing OTA of nRF52840 with BLE. It is working fine but device takes around 20 seconds to reboot after OTA image data is transferred to nRF52840 via nRF device manager app. Is there a way to reduce this time or reboot as soon as data transferen-USTelligent Community 13Mon, 23 Dec 2024 13:59:40 GMThttps://devzone.nordicsemi.com/thread/516136?ContentTypeID=1Mon, 23 Dec 2024 13:59:40 GMT137ad170-7792-4731-bb38-c0d22fbe4515:53dc6a84-2e97-41f8-b2d0-2afbd2352e54Sigurd Hellesvik<p>Hi,</p> <p>This reboot delay is due to <a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/mcuboot/design.html">swap</a>. If you got a large application, it can take some time.</p> <p>One alternative is to use <a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/mcuboot/design.html">direct-xip</a> instead. This has some downsides, like that you have to find which slot is active to do DFU. it is a reason we use swap by default after all.</p> <p>However, if you need really fast reboot after DFU, this could be the feature you need.</p> <p>For more information on why the swap takes time, see &nbsp;<a href="https://devzone.nordicsemi.com/f/nordic-q-a/110315/start-of-application-takes-ages-after-dfu-process-is-complete">Start of application takes ages after DFU process is complete</a> . (It uses the nRF5 SDK instead of the nRF Connect SDK, but the erase timings are the same in HW either way)</p> <p>Regards,<br />Sigurd Hellesvik </p><div style="clear:both;"></div>