This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Using legacy bootloader SDK V.11.0 with SDK V.12.0

Hello,

I just encounter a compatibility issue between the two SDK (11 Vs 12).

So i have so product on the market base on SDK V.11.0.

I m developping an update based on SDK V.12.0 but the dfu service provide in the SDK V.12.0 seems not compatible with the bootloader present in SDK V.11.0.

So my product cannot have their bootloader updated because of the memory constraint.

Is there anyway to update my products based on SDK V.12.0 with a dfu service that will work with the legacy bootloader ?

If yes how should i do that ? should i use the dfu service present in SDK V.11 ?

Thanks for your help !

Parents
  • When you state that you cannot update the bootloader due to memory constraints, do you mean that there is not enough flash for the new Secure Bootloader, the application and the S130 v2.0.x SoftDevice? Or did you mean that you're not able to update to the Secure Bootloader since it is larger than the Legacy bootloader and you've only allocated ~15kB and not ~24kB which is required by the Secure bootloader.

    In any case, you should be able to compile the legacy bootloader from SDK v11.0.0 against the headers of the S130 v2.0.x SoftDevice so that the legacy bootloader is compatible with SDK v12.x.x.

Reply
  • When you state that you cannot update the bootloader due to memory constraints, do you mean that there is not enough flash for the new Secure Bootloader, the application and the S130 v2.0.x SoftDevice? Or did you mean that you're not able to update to the Secure Bootloader since it is larger than the Legacy bootloader and you've only allocated ~15kB and not ~24kB which is required by the Secure bootloader.

    In any case, you should be able to compile the legacy bootloader from SDK v11.0.0 against the headers of the S130 v2.0.x SoftDevice so that the legacy bootloader is compatible with SDK v12.x.x.

Children
No Data
Related