Is bootloader in sdk12 Compatible with the bootloader before sdk12

[jasonbu]

as I found the sample code in sdk12 , the bootloader is quite different with bootloader in sdk11,

event uuid has got changed, is it possible to be compatible?

dual bank got a good feature that if processing abort, it can boot correctly.

And if erase the 0x7F000, this feature may not got full support?

[bjorn-spockeli]

No, the UUID of the DFU Service is different for the Secure DFU bootloader since we need a way do distinguish between Secure DFU and Legacy DFU.

Our Android DFU Library, found here, is compatible with both Secure and Legacy DFU, i.e. it will recognize the UUID and then perform either Legacy or Secure DFU. The iOS library will also support both Legacy and Secure DFU, but it has not been release to GitHub yet.

Furthermore, you should note that the Secure Bootloader in SDK 12.0.0 is larger (~24kB) compared to the bootloader in SDK 11.0.0 (~16kB). This means that if you only allocated 16kB to the bootloader, then you will not be able to update to the bootloader from SDK v12 since there is not enough space.

[bjorn-spockeli]

No, the legacy bootloader has been replaced with the Secure DFU bootloader and will not be developed any further. If you need the firmware images to be signed and verified by the bootloader then you have to use the Secure DFU bootloader, but there is currently no support for sharing bonding information in the SDK v12.0.0 release. This is because the buttonless DFU feature, shich used the bond sharing feature, has been moved to experimental due to the entire bootloader library being rewritten. We expect this to be moved out of experimental in a future release.