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
  • 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 ?

Reply
  • 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 ?

Children
No Data
Related