This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DFU OTA complete package update

Hi,

I got an SDK15.2 project that we converted the bootloader to be both serial and ble for the dfu.

Unfortunately we have a few units in the field that have only the BLE version.

I created the new package, and updating the devices via serial works correct. I can update just the application, or I can update the entire bootloader and softdevice.

But when I try to use the zip package (full one) with the connect android app, (using the dfu) I only seem to be able to update the app image. The bootloader seems to stay the same.

Is this normal? Is there a way to update the bootloader over BLE DFU?

Parents Reply Children
  • Hi,

    The bootloader on there is standarnd OTA one from the sdk. The one I am trying to load on there is a modified version that includes both serial and ota.

    The image for the first setup was:

    nrfutil_5_0_0 pkg generate --hw-version 52 --softdevice s132_nrf52_6.1.0_softdevice.hex --sd-id 0xAF --sd-req 0xAF --bootloader bootloader.hex --bootloader-version 1 --application app.hex --application-version 1 --key-file key.pem package.zip

    And the new one is:

    nrfutil_5_0_0 pkg generate --hw-version 52 --softdevice s132_nrf52_6.1.0_softdevice.hex --sd-id 0xAF --sd-req 0xAF --bootloader bootloader2.hex --bootloader-version 2 --application app.hex --application-version 1 --key-file key.pem package.zip

    I can see that the app gets updated, but the bootloader stays the same

  • Hi Riaan, 

    It might relate to this issue. That is due to how the bootloader works and flash space limitations. It could be possible to do all in one go in a device with a log of flash and/or small softdevice and application, but that has not been handled specifically. 

    Try to update SD+BL first then APP. 

    -Amanda H.

Related