DFU OTA complete package update

RE: DFU OTA complete package update

Amanda Hsieh — Mon, 21 Sep 2020 10:26:43 GMT

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.

RE: DFU OTA complete package update

Riaan — Thu, 17 Sep 2020 00:11:29 GMT

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

RE: DFU OTA complete package update

Amanda Hsieh — Wed, 16 Sep 2020 12:46:51 GMT

Hi Riann,

[quote user=""]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.[/quote]

Do you use the unmodified bootloader example to update to the new one?

What is the command you use to generate the package?

-Amanda H.