Is bootloader in sdk12 Compatible with the bootloader before sdk12

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

bjorn-spockeli — Tue, 15 Nov 2016 08:56:18 GMT

@rajkumar: I am afraid that we do not have any documentation on how to add bond sharing to the Secure Bootloader in SDK 12.x.0.

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

Raj — Mon, 14 Nov 2016 18:04:22 GMT

Hi Bjorn Spockeli, Is their any post or document releated to add bond sharing feature in SDK12.1.0 or we need to wait for future release?

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

bjorn-spockeli — Mon, 12 Sep 2016 12:28:36 GMT

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.

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

jasonbu — Mon, 12 Sep 2016 12:05:49 GMT

so we have to migrate the legacy bootloader in sdk12 as peer manager module updated? i think it should be done with sdk release ...

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

bjorn-spockeli — Mon, 12 Sep 2016 12:01:16 GMT

The Legacy bootloader has been replaced by the Secure DFU bootloader and is therefore not present in SDK 12. The peer data sharing feature,i.e. share peer address and bonding information between the the application and bootloader was not added to the SDK v12.0.0 release since the bootloader has migrated to the Peer Manager module.

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

jasonbu — Mon, 12 Sep 2016 11:22:14 GMT

so, secure dfu and Legacy dfu got different uuid now.And a new question: legacy dfu in sdk11 got a feature that will pass the bond info to bootloader, As sdk12 got a buge change about bond info, how to continue using these feature? i do not found legacy bootloader code sample in sdk12

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

bjorn-spockeli — Mon, 12 Sep 2016 11:18:04 GMT

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.

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

jasonbu — Mon, 12 Sep 2016 09:29:05 GMT

yes,that is one of demands, also i found uuid has changed, so android and iOS code will have to make a huge change if we want to use the sdk12 bootloader? event never care the secure dfu

RE: Is bootloader in sdk12 Compatible with the bootloader before sdk12

bjorn-spockeli — Mon, 12 Sep 2016 09:21:58 GMT

Do you mean if it is possible to update the bootloader from SDK v11.0.0 to SDK v12.0.0 with DFU?