Not secured dfu sdk 12

RE: Not secured dfu sdk 12

bjorn-spockeli — Wed, 18 Jan 2017 12:58:57 GMT

I have attached the s132_nrf52_3.0.0_migration-document that lists the changes between S132 v2.0.0 and S132 v3.0.0 to my answer.

RE: Not secured dfu sdk 12

max — Mon, 16 Jan 2017 14:02:44 GMT

you have a guide of changes for dfu? i need the sdk 11 dfu work, it is in production.

RE: Not secured dfu sdk 12

bjorn-spockeli — Mon, 16 Jan 2017 13:19:27 GMT

You have to modify the bootloader project so that all the functions with sd_-prefix is compatible with the S132 v3.0.0 headers. If you look inside the softdevice_enable() then you'll see that it call sd_-functions calls, like sd_ble_enable. Some of these calls have changed from SDK v11 to SDK v12 and you have to refer the API reference of the S132 v3.0.0 to see which modifications you have to do.

RE: Not secured dfu sdk 12

bjorn-spockeli — Mon, 16 Jan 2017 12:59:17 GMT

The headers for the softdevices can be found in components\softdevice\s132\headers.

RE: Not secured dfu sdk 12

max — Mon, 16 Jan 2017 12:44:06 GMT

where i can fined the headers? i need a normal dfu sdk 11.0.0 s132 that works for sd v3.0 thanks

RE: Not secured dfu sdk 12

bjorn-spockeli — Mon, 16 Jan 2017 12:07:41 GMT

Hi Max,

the bootloader in SDK v12.x.0 currently only supports secure DFUs, i.e only accepts signed firmware images.

You can port the legacy bootloader from SDK v11.0.0 to SDK v12x.0.0 by compiling the bootloader project against the S132 v3.x.0 headers.

Here is the Migration Document:

s132_nrf52_3.0.0_migration-document.pdf

Best regards

Bjørn