DFU Migration SDK 13.0.0/S132 SD 4.0.3 to SDK 14.2.0/S132 SD 5.0.0

[WestCoastDaz]

We have a large number of units in the field running on SDK 13.0.0/S132 SD 4.0.3 and in order to add new functionality we need to migrate to SDK 14.2.0/S132 SD 5.0.0 via DFU.

Can this migration be done via DFU?  I know the Nordic bootloader supports updating the SD but until know we haven't had a need.

If this can be done, then my questions are:

1. Is there a particular order of operations that needs to be performed for this to work?
2. Can we continue to use the bootloader from SDK 13 with SD 5.0.0 or does the bootloader need to be updated as well?
3. Is there anything else we should consider before undertaking this?  This post talks about issues with the bootloader in SKD 13 but doesn't mention what they are or what the work around is.  "In addition, there is a bug in SDK 13.1.0 which requires a workaround in the new bootloader when you upgrade devices already shipped."

Thanks!

[bjorn-spockeli]

HI Darren, 

Q1: You'll need to perform a SD+ BL update first, this will delete the application on the device. After the SD+Bl update has finished you need to DFU in the new app. You can create a DFU package that includes all 3, i.e SD, Bl and APP and then the Nordic Android or iOS DFU library will perform the updates in the order described above. 

Q2: You need to update the bootloader if you're updating to a new SoftDevice version, otherwise the SoftDevice API will not be compatible. So if you want to use the bootloader from SDK v13.0.0, then you will need to recompile it against the header files of the new SoftDevice and then perform a SD v5.0.0 + BL update. 

Q3: I believe the bug referred to in the post you linked to is this. This bug was fixed in SDK v14.1.0 so this should not be an issue for you. 

Best regards

Bjørn