Softdevice, bootloader and App update in queue via mobile apphttps://devzone.nordicsemi.com/f/nordic-q-a/19353/softdevice-bootloader-and-app-update-in-queue-via-mobile-appHi, Is there any way to force Android and iOS to update softdevice, bootloader and application from single zip file in queue? I mean, first update softdevice, then bootloader and on the end application to ensure dualbank update which is essential foren-USTelligent Community 13Wed, 01 Feb 2017 09:21:55 GMTRE: Softdevice, bootloader and App update in queue via mobile apphttps://devzone.nordicsemi.com/thread/75075?ContentTypeID=1Wed, 01 Feb 2017 09:21:55 GMT137ad170-7792-4731-bb38-c0d22fbe4515:fc2f611d-0885-41ab-aeb3-c4c9ae19de67bjorn-spockeli<p>Happy to help! However, just be aware that the bootloader and softDevice must be compatible. For example, if you want to update from S132 v2.0.0 to S132 v3.0.0, then you cannot update the BL or SD individually as the bootloader is compiled with the S132 v2.0.0 headers or the S132 v2.0.0 is not compatible with a bootloader compiled with the S132 v3.0.0 headers. This is why we recommend updating the SD and BL as a combined image.</p><div style="clear:both;"></div>RE: Softdevice, bootloader and App update in queue via mobile apphttps://devzone.nordicsemi.com/thread/75074?ContentTypeID=1Wed, 01 Feb 2017 08:55:49 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a4cf0cf9-2bb3-4c6c-a678-e984e0e8fcaeMuniek<p>Yes you&#39;re right, but bootloader, softdevice and application may change in the future. Devices will be updated by customers, so the best solution for us is to update bootloader, softdevice and app separately. According to the page you&#39;ve sent, firstly bootloader and softdeive are copied to free memory space which may be too small. It will be safer for us to copy bootloader, install it and then copy softdevice and install. Thanks for your help!</p><div style="clear:both;"></div>RE: Softdevice, bootloader and App update in queue via mobile apphttps://devzone.nordicsemi.com/thread/75073?ContentTypeID=1Wed, 01 Feb 2017 08:26:06 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3be2d90b-28ce-44c7-a901-beed66ae1683bjorn-spockeli<p>The S132 v3.0.0 (120kB) + MBR(4kB) will take up a total of 124kB, i.e. the application space region starts at 0x1F000. The Secure Bootloader in SDK v12.x.0 starts at 0x78000, which leaves 356kB for the application space. If we subtract the application size from the total size of the application space region, i.e. 356kB-120kB , we&#39;re left with 236kB. A combined S132 v3.0.0 and bootloader will have a size of 120kB + 24kb = 144kB. This means that the Secure Bootloader will perform a Dual Bank update of the SoftDevice and Bootloader without erasing the application, see <a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.sdk5.v12.2.0/lib_bootloader_dfu_banks.html?cp=4_0_1_3_5_1_2_0_0#lib_bootloader_dfu_dual_banks_sd">this</a> Infocenter page, as long as the application is not larger than 356kB - 144kB = 212kB.</p><div style="clear:both;"></div>RE: Softdevice, bootloader and App update in queue via mobile apphttps://devzone.nordicsemi.com/thread/75072?ContentTypeID=1Wed, 01 Feb 2017 07:35:54 GMT137ad170-7792-4731-bb38-c0d22fbe4515:2632af3b-0108-4b62-b477-ade74c9e6763Muniek<p>SoftDevice 132_3.0.0, SDK 12.1.0 and application weights 120Kb Thanks!</p><div style="clear:both;"></div>RE: Softdevice, bootloader and App update in queue via mobile apphttps://devzone.nordicsemi.com/thread/75071?ContentTypeID=1Wed, 01 Feb 2017 07:22:29 GMT137ad170-7792-4731-bb38-c0d22fbe4515:c6760214-3504-4a78-9f5a-3b68a1c5ba16bjorn-spockeli<p>Hi Muniek, which SDK and SoftDevice version are you using and how large is your application?</p><div style="clear:both;"></div>