Is it possible upgrading from nrf52 sdk 14.0 to sdk 16.0?

[Light]

Hi，we had finished application development on nrf52832 long ago, based on nrf52 sdk 14.0(with softdevice 5.0). But now we get feedback which is a bug has been fixed on sdk 16.0(with softdevice 7.0). We want to solve this problem by DFU since a lot of productions have appeared on the market. We did the test, but not work(see attatchment). Is this possible technically?

[Turbo J]

What was the nrfutil command line for generating the .zip file?

Looks like you used the wrong sd_req parameter, and now the old bootloader just rejects the update. Note: You need to update both BL and SD in one go (read: in one dfu zip file), as the bootloader depends on the correct SD version.

[Light]

Thanks for reply, the nrfutil command line as follow:

nrfutil pkg generate --hw-version 32 --key-file private.pem --application-version 1 --application app.hex --sd-req 0xcb --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xcb --bootloader bootloader.hex --bootloader-version 1 pkg.zip
pause 

[Turbo J]

The nrf52832 chip is too small for triple DFU - you need to update BL+SD first, and then application in a second step using a different zip file.

For the BL+SD update, you need --sd-req matching your OLD sd, either 0x9D for SD132 5.0.0 or 0xA0 for SD132 v5.0.1 should work.

Caution: Check BL start address (e.g. in linker script). If the new BL is larger (lower address value), you cannot use DFU for upgrade.

[Light]

hi Turbo J 

I use this command generate the pkg.zip (BL+SD)

nrfutil pkg generate --bootloader bootloader14.hex --bootloader-version 2 --softdevice s132_nrf52_7.0.1_softdevice.hex --sd-id 0xCB --hw-version 32 --sd-req 0x9D --key-file private.pem PKG.zip
pause

when dfu in nrfconnect and catch the fault as follow：

BL is based on sdk 14.0 `s secure dfu example。

I also used the "--sd-req 0x9D,0xCB" AND not work!

thanks！