OTA DFU bootloader updating issue

[cristian.anceschi]

Hi All

I’m making a few tests on a custom board equipped with a nRF51822-AA device trying to update the firmware with a newest one based on a more recent SDK

The original code is based on the old SDK 7.1.0 / 7.2.0 release

Bootloader: nRF51_SDK_7.2.0_cf547b5… → dual_bank_ble_s110

Softdevice: s110_nrf51822_7.1.0_softdevice.hex

The first test I made is update the bootloader with a new one. Same SDK, just change the switch that launches the bootloader at the reset.

It seems to me that it is not possible to update the Booloader code with distribution packet file or with an .hex + .dat files.

For updating I’m using DFU in the nRF Connect app.

Even though the app says the updating procedure had success, but when the nRF51822 is reset, the working mode of the bootloader code doesn’t change

Is this due to the old release of the SDK?

Is there a procedure to update the firmware with the more recent bootloader and softdevice via OTA DFU?

In one single step or moving through a few steps?

Thanks in advance for your support

Cristian

[Vidar Berg]

Hello Cristian,

Bootloader updates should be supported in this release. Are you able to debug the bootloader to see if maybe the update is aborted because the post validation step is failing (dfu_init_postvalidate)? I am thinking it might be a mistmatch between the CRC value in the init packet and the calculated CRC of the received bootloader image.

Best regards,

Vidar