I am testing OTA DFU using NRF toolbox on Android. I have no problem updating my application using a zip file generated with nrfutil.
nrfutil.exe pkg generate --application nrf52832_xxaa.hex --key-file priv.pem --hw-version 52 --sd-req 0x9D --application-version 0x02 application.zip
However I would like to be able to update my bootloader OTA. I generate a zip file in a similar way from the bootloader .hex file.
nrfutil.exe pkg generate --bootloader bootloader0_2.hex --key-file priv.pem --hw-version 52 --sd-req 0x9D --bootloader-version 0x0000001 bootloader0_2.zip
Am I correct in assuming that the bootloader itself can be updated in this way via OTA DFU? Or do I need to update the bootloader by connecting to the application itself? I was under the impression that the bootloader could update itself.
Has anyone else managed to do a firmware -only update using the android App?
An application engineer at Nordic tried the same steps that you tried and got the same error. Seems there is a bug in the Android toolbox app that will be fixed soon. He suggests you try using the nrf connect app instead of the nrf toolbox app for updating the bootloader.
Hi Bjorn, thank you very much for your reply. I can confirm that the latest version (from this morning) of the NRF Connect app does not have the same bug and can successfully do all combinations of firmware update (BL, APP, SOFT) with my code.
Great! Good to hear!