I'm running a nRF52 device that's built on nRF5 SDK11, and it's remaining that way now due to regulatory reasons. My application needed to be updated to support bonding, and that's gone smoothly, however I wanted to ensure that a bonded firmware, when updated, transfers the bond transfers through the update process. I've successfully modified both the application and bootloader firmware to support this. Since the bootloader required modification (it needed a modified reserved memory configuration), the bootloader must be updated via OTA.
I've successfully performed updates of the application via OTA using a *.bin and *.dat pair, but I haven't quite figured out how to perform such an update of the bootloader. I've executed it on android via nRF Toolbox v2.9.0 using the DFU feature.
Currently I have an application hex file, a bootloader hex file (slightly altered and derived from the DFU example code supplied with SDK11), and a soft device file (S132, I believe v2.0.0). I'm seeking advice for creating file sets for updating the bootloader using the same technique as the application. I'm fine with it being a single zip package if that will work with my configuration. So far I've tried to create the package with the latest nRFUtil following guides like this: https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nrfutil%2FUG%2Fnrfutil%2Fnrfutil_pkg.html , but I end up getting errors attempting to perform the update.
For the bootloader alone, I tried a few variations without success:
nrfutil pkg generate --hw-version 52 --sd-req 0x81 --bootloader-version 3 --bootloader bootloader_app.hex bootloader_app.zip
nrfutil pkg generate --hw-version 52 --sd-req 0xFFFE --bootloader-version 3 --bootloader bootloader_app.hex bootloader_app.zip
nrfutil pkg generate --hw-version 52 --sd-req 0xFFFE --bootloader-version 3 --bootloader bootloader_app.hex --softdevice s132_nrf52_2.0.0_softdevice.hex --sd-id 0x81 --application application_app.hex --application-version 0xffff complete_app.zip
