DFU

[harrys]

Hi, 

i am working on nrf52dk . i want to do DFU with BLE can you provide any document link. 

[Amanda Hsieh]

Hi, 

Check out https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/getting-started-with-nordics-secure-dfu-bootloader 

-Amanda H.

[harrys]

i have merged the two hex files "secure bootloader dfu example code" and "softdevice_hex file". programmed it in nrf52dk.

now nrf52dk is advertising "dfuTarg". when i program the device (blinky_ble_code) with nrf mobile app. programming done but nrf52dk is still advertising "dfuTarg".

[harrys]

1.using mergehex to mergehex files

$ mergehex -m C:/Users/techn/Desktop/dfu/secure_bootloader_ble_s132_pca10040.hex C:/Users/techn/Desktop/dfu/s132_nrf52_
7.2.0_softdevice.hex -o C:/Users/techn/Desktop/dfu/bootloader.hex
Parsing input files.
Merging file "secure_bootloader_ble_s132_pca10040.hex" into output.
Merging file "s132_nrf52_7.2.0_softdevice.hex" into output.
Storing merged file.

2.command i am using for dfu pakage generate.

nrfutil pkg generate --hw-version 52 --application-version 1 --application ble_app_blinky_pca10040_s132.hex --sd-req 0x0101 --key-file private.key app_dfu_blinky.zip

Zip created at app_dfu_blinky.zip

[Amanda Hsieh]

Hi, 

Please use bootloader debuger version under SDK\nRF5_SDK_17.0.2\examples\dfu\secure_bootloader\pca10040_s132_ble_debug, and provide the log from J-Link RTT Vierwer or Segger.   

I would suggest you compile the ble_app_blinky_pca10040_s132 project and test the image under nRF5_SDK_17.0.2\examples\ble_peripheral\ble_app_blinky\pca10040\s132\ses\Output\Release\Exe

-Amanda H.

[harrys]

yes it works with "pca10040_s132_ble_debug". not with "pca10040_s132_ble".

[Amanda Hsieh]

Hi, 

They are almost the same except for the debug function, so pca10040_s132_ble should work. I have tested both can work. Erase the kit (nrfjprog --eraseall) before program the image. 

-Amanda H.

[harrys]

can you verify my steps.

1.merged hex file secure bootloader and soft device used with following command.

"mergehex -m C:/Users/techn/Desktop/dfu/secure_bootloader_ble_s132_pca10040.hex C:/Users/techn/Desktop/dfu/s132_nrf52_7.2.0_softdevice.hex -o C:/Users/techn/Desktop/d fu/bootloader.hex"

2.generated dfu pkg with following command.

"nrfutil pkg generate --hw-version 52 --application-version 1 --application ble_app_blinky_pca10040_s132.hex --sd-req 0x0101 --key-file private.key app_dfu_blinky.zip
Zip created at app_dfu_blinky.zip"

3.programmed generated dfu zip file with mobile app "nordic_connect".

4.after the programming done . nrf52dk advertise "dfutarg". can you tell any thing i am missing in  these steps

[Amanda Hsieh]

The procedure and commands look correct. The same flow can work with "pca10040_s132_ble_debug", then it supposed to work with "pca10040_s132_ble". 

-Amanda H.

[harrys]

i have not merged softdevice hex file and secure bootloader dfu debug.hex  in debug example .

i directly programmed it with SEGGER EMBEDDED STUDIO. and then programmed blinky.zip file with mobile app. and it works.

[Amanda Hsieh]

Hi, 

The segger will load the softdevice hex before programming the secure_bootloader_ble_s112_pca10040_debug if you check the log. That is the same as you did merge and program. You could press "build and run" in the segger for pca10040_s132_ble. It did the same thing. 

-Amanda H.

[harrys]

yes it works. thank you

[harrys]

can  you tell me how i  can do the same with ble_buttonless_dfu example.