nRF51DK DFU BLE OAT

[JohnM]

Hello,

This is the first time I try to implement DFU to update my simple application OAT via BLE on the nRF51 DK.

My simple application is a simple peripheral which communicate with a RGB driver by I2C (so very simple because no BLE involved so far / and of course it works fine when flashed alone).

What I did:

1. erase board with nRFgo

2. Load Soft Device with nRFgo (SDK_11\components\softdevice\s130\hex\s130_nrf51_2.0.0_softdevice.hex)

3. in Keil compile and load Bootloader (SDK_11\examples\dfu\bootloader\pca10028\dual_bank_ble_s130\arm5_no_packs)

4. turn off nRF51DK, press Button4 and power on again

5. Load OAT with Android (nRFconnect) the application HRM as ZIP file ( SDK_11\examples\dfu\ble_dfu_send_hex\test_images_update_nrf51dfu_test_app_hrm_s130.zip

--> this works because after loading finished I can see the application HRM displayed in Android nRFconnect

But now I want to replace this HRM application by my simple application.

I've tried to generate the ZIP file with (nrfutil version 3.4.0):

nrfutil pkg generate app_dfu_package.zip --debug-mode --application My_nrf51422_xxac.hex --key-file key.pem --hw-version 51 --key-file private.pem --sd-req 0x67,0x80,0x87

But when I tried to load it with Android (nRFConnect) then it fails (either nothing happen after loading complete, either the DFU disconnects by itself)

So I miss something (like how this HRM app is well customized to fit with this SD and Bootloader and not my simple application...)

Thanks for you help (this might help a lot of pple to get stated with DFU OAT)

[JohnM]

Well, I've tried with my final BLE custom application and the whole process works (BLE OAT secure).

So for me, a basic application which does not use itself BLE (like simply blinking a LED), should be updatable OAT as well, can do more can do less... I will still find out how to achieve that in the future.