Softdevice update through DFU

[jev]

My current hardware is based on SoftDevice SD132, v6.0.0 as provided with SDK 15.0.0. I would like to update it to use SoftDevice 6.1.0 (as part of SDK 15.2.0) and perhaps later even to an S332 once it becomes available. The ZIP files we produce for updating are not accepted in the existing hardware (based on SDK15 + SD132 v6.0.0) when it is build for SDK15.2 + SD1432 v.6.1.0). Can this be done through the air using nRF Connect for windows? 

[jev]

Ah, okay. That might help, thanks.

Just to make sure.. assuming software n relies on SD v6.0.0 and software n+1 (and later) relies on SD v.6.1.0, customers will always be forced to update to n+1 before going to n+2. There is no trick to do that in one go?

[bjorn-spockeli]

You generate a SD+BL+APP Zip file with nrfutil and then the nRF DFU Library used by the iOS/Android apps and nRF Connect for Desktop will automatically split the DFU procedure into a SD+BL and a APP update. This will look as one update for the end user. 

The reason it is done in two steps is because there is not enough room for the new SD, BL and APP in addition to the old SD, BL and APP. 

[jev]

Okay, clear. Thanks Bjørn!

[[email protected]]

Hi Jev,

I got same error message like that you got

"DFU failed with error: When writing 'EXECUTE' command to Control Point Characteristic of DFU Target: Operation code 4 (EXECUTE) failed on DFU Target. Result code 11 (EXTENDED_ERROR) Extended error code 7 (SD_VERSION_FAILURE)."

Do you resolved this issue yet?

I am using Embedded Studio; run on Windows 10; nRF5_SDK_15.0.0_a53641a; I am using this tutorial

nRF52832-buttonless-dfu-development-tutorial

and stopped at

Step 3 - Create our own FW.zip package which we can upload to the device over BLE

6. Click the DFU button, and browse to the FW.zip file we just created and select this one, click “Start DFU”. The SD will be uploaded first, then the application

Please help me if you could.