DFU flash issue

[vikas dubey]

Hi

I am trying to use DFU feature using nRF5_SDK_14.2.0_17b948a. I used given preexisted example hex files for bootloader and app and successfully able to use DFU feature.

Later I tried to build projects "nRF5_SDK_14.2.0_17b948a/examples/ble_peripheral/ble_app_buttonless_dfu" for application hex and "nRF5_SDK_14.2.0_17b948a/examples/dfu/bootloader_secure_ble" for bootloader hex.

I have generated hex file using makefile. But when flashed them on nrf52832 board, no application run. Attached hex files for further reference(bootloader settings, app, bootloader).

Please help me to figure out what went wrong.HexFiles.zip

[Rune Holmgren]

The DFU settings page you sent me is located at address 0x23000 on top of the application. The DFU settings page should be located at the very top of the flash, typically at (edit, this number used to say 0x78000) 0x7F000-0x7FFFF, as shown in the map below.

Best regards,
Rune Holmgren

[vikas dubey]

Hi,

Thanks for your input.

I build  "nRF5_SDK_14.2.0_17b948a/examples/dfu/bootloader_secure_ble /pca10040" which is non debug bootloader using gcc makefile. When I burned hex file using nprog. LED3 continuosly remains on, and no advertisement happened.

Later I build debug version and burned that, bootloader in dfu mode start advertising as DfuTarg.

I required non-debug bootloader as it is recommeded for production purpose.

Please check what went wrong.

0842.nrf52832_xxaa_s132.hex

 

[Rune Holmgren]

Hi,

The hex file you sent me seems to have content from 0x73000 and onwards. The default non debug bootloader will be placed from address 0x78000 and onwards when taken straight out of the SDK.

It is possible to move the bootloader if that is what you wanted to do, but it requires a few changes internally in the project to ensure UICR and Application data are placed correctly.

Best regards,
Rune Holmgren