Update Softdevice via DFU

RE: Update Softdevice via DFU

Vidar Berg — Mon, 10 Aug 2020 13:10:36 GMT

The bootloader and Softdevice images are merged into one binary image and transferred to the target in go, and only when the entire image has been received and validated will the bootloader start the activation process. And the copy routines used for activation are designed to be able to withstand unexpected resets due to power loss, etc.

The device will fall back to DFU mode once the new SD and BL is activated, and will then be ready to receive the new app update from the DFU master

The update sequences are described in more detail here: Dual-bank and single-bank updates

RE: Update Softdevice via DFU

Riaan — Sat, 08 Aug 2020 23:25:50 GMT

I will create a new bootloader with the same sdk17, and give your solution a go.

One question on that is, is it safe to update the bootloader and the sofdevice in this manner?

If I understand it correctly then each one will be sent over and updated one by one. If for whatever reason something fails during this update process, will the device be bricked?

Aka, if the bootloader is updated, and say the main app, but not the softdevice. If the device restarts will the bootloader try and run the new app, which will fail as the softdevice is not the one required.

I am not sure what fail safes are in place for such events. In the field we have seen that just updating the app sometimes fails, but we just try again and it works. So I am a bit worried to update the bootloader and softdevice as well.

RE: Update Softdevice via DFU

Vidar Berg — Fri, 07 Aug 2020 14:41:06 GMT

Hello,

When doing a major SD update (v6-->v7) you also need to include a new app and bootloader that is compatible with the new API and layout (ie depending on softdevice, the app may require a new start address).

Please try run nrfutil with the arguments I've added below:

"nrfutlis_6_1_0.exe pkg generate --hw-version 52 --sd-req 0xCB, 0xA8 --bootloader <new bootloader>.hex --bootloader-version <version> --application bleApp.hex --application-version 1 --key-file key.pem --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCB bleApp.zip".

I added 0xA8 to the sd req list because it's FWID for s132 v6.0.0 that you have running on your device.

RE: Update Softdevice via DFU

Riaan — Fri, 07 Aug 2020 08:30:15 GMT

So I think I added the image in
"nrfutlis_6_1_0.exe pkg generate --hw-version 52 --sd-req 0xCB --application bleApp.hex --application-version 1 --key-file key.pem --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCB bleApp.zip".

I can see my package size grew a bit, so I take it is correct.

But I still get the "Extended Error 0x07: The array of supported SoftDevices for the update does not contain the FWID of the current SoftDevice."