DFU error from SD132v3.0.0 SDK12.1 to SD132V5.0.0 SDK14.0

[JosePastor23]

Hi,

I'm trying to port my project from SDk12.1 to SDK14.0, I've got everything working fine except the DFU process. The main issue is that we've got some devices distributed an I'm not able to re-flash them from scracht. I want to update by dfu SD+BL+APP to the SDK14.

I've created the zip package using nrfutil with the following command:

nrfutil pkg generate --application APP.hex --application-version 4 --softdevice s132_nrf52_5.0.0_softdevice.hex --bootloader bootloader_SDK14.hex --bootloader-version 6 --hw-version 52 --sd-req 0x8c --sd-id 0x9D --key-file private_key.pem out.zip

When I try to update by OTA using the nRF Connect pc version and a PCA 10031 dongle the SD and bootloader update seems to work probperly but after that there isn't a new connection to update the application and there isn't any device advertising. The error message I get in nRF Connect is:

Both bootloaders are used as are presented in the examples folder wihtout any modification. Only setting public_key.c.

The dfu process flashing SD132v5 and bootloader_sd14 and then using the same zip package ends without errors.

Is there any known issue involved in the OTA-DFU from SDK12.1 to SDK14.0?

Thanks,

Jose Pastor

[shibshab]

Try using SDK 14.1.0. There was a bug in the 14.0.0 (and older) bootloders where updating to a bigger softdevice would not work.

[JosePastor23]

Thanks, with SDK14.1 the updating works like a charm!