I'm attempting to create a DFU update using the the ble_app_uart example coupled with the BLE DFU bootloader. It's not unlike this case.
SDK = v16.0.0
nrfutil = v6.0.0a0 (python) and v6.0.0a1 (exe)
nRF Connect for Desktop v3.2.0
Windows 10
S132 v7.0.1 on nRF52832
I had this working about six months ago with SDK v15.3.0, but when I try to re-create a working setup, I get the same error again.
Here are the commands I used:
nrfutil keys generate dfu_private_key.pem
nrfutil keys display --key pk --format code --out_file dfu_public_key.c dfu_private_key.pem
nrfutil pkg generate --application ble_app_uart_pca10040_s132.hex --application-version-string "1.0.0" --hw-version 52 --sd-req 0xCB --key-file C:\u-blox\nRF5_SDK_16.0.0_98a08e2\examples\dfu\dfu_private_key.pem app_v1.zip
I did *not* create a bootloader_settings.hex file yet (it worked without before).
I compiled the secure_bootloader_ble_s132_pca10040 SES project with the new public key, then uploaded it using SES, which also brought along the SoftDevice.
When I attempt to perform the update with nRF Connect, I get the error.
Is a bootloader_settings.hex file needed at this point now?
Any other thoughts?