Can I upgrade the firmware between different softdevice? From s132 to s113

[Susan_cfx]

Hi Nordic Team,

Can I upgrade the firmware between different softdevice? From s132 to s113

firmware 1: sd: s132_nrf52_7.0.1_softdevice.hex , bootloader: secure bootloader based on the sdk nRF5_SDK_17.0.0_9d13099, application: custom application 1 based on sdk17.0.0

firmware 2: sd: s132_nrf52_7.2.0_softdevice.hex , bootloader: secure bootloader based on the sdk nRF5_SDK_17.1.0_ddde560, application: custom application 1 based on sdk17.1.0

firmware 3 : sd: s113_nrf52_7.0.1_softdevice.hex, bootloader: secure bootloader based on the sdk nRF5_SDK_16.0.0_98a08e2, application: another custom application based on sdk16.0.0

I can upgrade the SD+BL+APP from firmware 1 to firmware 2 successfully,  but when upgrade firmware 1 to firmware 3, it will raise an error, attached the picture.

I use this command to generate the zip package.
nrfutil.exe pkg generate --hw-version 52 --sd-req 0xCB,0xCC,0x0101 --sd-id 0xCC --softdevice s113_nrf52_7.0.1_softdevice.hex --bootloader-version 3 --bootloader s113_bootloader.hex --application-version 2 --application application_s113_release.hex --key-file private.pem DFU_stdToCustom_SD_BL_APP.zip

Any problem about the command?

I also try by the android app Toolbox, uploading part 1/2, when the process up to 100%, it raise an error: upload failed: DFU device disconneted.

Please help to analy this issue, we have some products with firmware 1, need to upgrade to firmware 3. Thank you very much.

Best wishes,

Susan

[Amanda Hsieh]

Hi Susan, 

I think it could try the following command:

nrfutil.exe pkg generate --hw-version 52 --sd-req 0xCB,0xCC --sd-id 0xCC --softdevice s113_nrf52_7.0.1_softdevice.hex --bootloader-version 3 --bootloader s113_bootloader.hex --application-version 2 --application application_s113_release.hex --key-file private.pem DFU_stdToCustom_SD_BL_APP.zip

Since SDK 16.0, the bootloader now disallows upgrading the SoftDevice to another family (e.g. s140 -> s113). If it still cannot work, maybe that is the reason.  

Regards,
Amanda

[Susan_cfx]

Hi Amanda,

I try your command, it still raise the same error when the upgrade to 100%. 

We want to upgrade the softdevice from s132_nrf52_7.0.1_softdevice.hex  to s113_nrf52_7.0.1_softdevice.hex.

Do you have  solution? Thank you very much.

Best wishes,

Susan

[Amanda Hsieh]

Hi Susan, 

If you use the debug version of the bootloader, you might get the information. From SDK 16.0, the bootloader now disallows upgrading the SoftDevice to another family (e.g. s140 -> s113), so the bootloader will validate app is not valid.

-Amanda