Thanks Stefan. The zip file making and updating steps work perfectly for me, if I follow your steps and make it from your stock pre-built "dfu_test_app_hrm_s132.hex". My question is how and from where "dfu_test_app_hrm_s132.hex" was built? I tried to built it from the example both "ble_app_hrs/pca10040/s132_with_dfu" and "s132", then make the zip and update, but it doesn't seem to work. Didn't boot up after update. Thx.
------------------------------- history --------------------------------
I am trying to build my own application that will be updated via DFU UART. I can update your given example in examples/dfu/hci_dfu_send_hex/test_images_dual_bank_update_nrf52/dfu_test_app_hrm_s132.zip I am curious from what example source codes you built the file? Thanks.
1 answer
Hi
The zip file that is valid for bootloader upload is made from the ble_app_hrs example in the SDK, which is also precompiled in the \examples\dfu\ble_dfu_send_hex\test_images_update_nrf52\dfu_test_app_hrm_s132.hex file.
With the hex file, you can create the zip file as instructed here and here. You may however need to define a different softdevice ID restriction. You could also just select 0xfffe as softdevice restriction, which is a wildcard and will allow any softdevice. More list of softdevice IDs is here.