https://devzone.nordicsemi.com/f/nordic-q-a/17987/softdevice-bootloader-update-from-s2-0-1-to-3-0-0-does-not-bootI am trying to update my S132v2.0.1 devices over the air to S132v3.0.0 and am getting no bootup, even after swapping dfu_dual_bank.c from the answer below. devzone.nordicsemi.com/.../ Although the SD seems to update, NRFUtil shows the bootloaderen-USTelligent Community 13Mon, 28 Nov 2016 08:55:15 GMThttps://devzone.nordicsemi.com/thread/69350?ContentTypeID=1Mon, 28 Nov 2016 08:55:15 GMT137ad170-7792-4731-bb38-c0d22fbe4515:dab3ab07-6495-4149-b599-e7d9818c2818bjorn-spockeli<p>I believe that the case you&#39;re referring to is regarding the update from a Legacy bootloader + S132 v2.0.x to a legacy bootloader + S132 v3.0.0, where you have to implement a bugfix in order to successfully perform a DFU. The bugfix is explained in this post</p> <p><a href="https://devzone.nordicsemi.com/question/97019/updating-from-s132-v20x-to-s132-v300-with-dual-bank-bootloader-from-sdk-v1100-does-not-work/">devzone.nordicsemi.com/.../</a></p> <p>In order to update from the bootloader in SDK v11.0.0 (now referred to as Legacy) to the bootloader in SDK v12.x.0 ( referred to as Secure) you have to ensure that the start address of the legacy bootloader that is flashed to your devices is identical to that of the new Secure Bootloader as this cannot be changed at runtime without erasing the entire chip.</p> <p>The default start address of the legacy bootloader is 0x0007A000, while the default start address of the Secure bootloader is 0x78000, i.e. the legacy bootloader start address must be set to 0x78000 so that there is room for the new Secure bootloader.</p> <p>Like the legacy to legacy update, you have to add a bugfix to the Legacy bootloader, as explained in the post linked to above.</p> <p>Best regards</p> <p>Bjørn</p><div style="clear:both;"></div>