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

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

alutun — Tue, 21 Feb 2017 01:24:05 GMT

I will try that and let you know, thanks for the fast answer !

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

bjorn-spockeli — Mon, 20 Feb 2017 16:23:31 GMT

Yes, then you add the DFU service from SDK v11.0.0 as described on this Infocenter page in your SDK v12.2.0 application.

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

alutun — Mon, 20 Feb 2017 12:20:32 GMT

Yes indeed i only allocated 15 Kb for the old bootloader.

So what do you mean by compiling the bootloader ? My issue is in fact that i cannot touch the bootloader but i want to integrate the dfu service into my app (on SDK V12.x.x) and be compatible with my already existing legacy bootloader ? Is that possible if yes i should use the duf service provide in SDK v11.0.0 and compile inside the SDK V.12.x.x is that right ?

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

bjorn-spockeli — Mon, 20 Feb 2017 10:20:28 GMT

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.