DFU of SDK15.3

[Hansome]

Based on nRF5_SDK_15.3.0_59ac345 at nRF52810

>nrfutil settings generate --family NRF52810 --application app.hex --application-version 0x01 --bootloader-version 0x01 --bl-settings-version 0x01 settings.hex

Note: Generating a DFU settings page with backup page included.
This is only required for bootloaders from nRF5 SDK 15.1 and newer.
If you want to skip backup page generation, use --no-backup option.

Generated Bootloader DFU settings .hex file and stored it in: settings.hex

Bootloader DFU Settings:
* File:                     settings.hex
* Family:                   NRF52810
* Start Address:            0x0002F000
* CRC:                      0xB93557C8
* Settings Version:         0x00000001 (1)
* App Version:              0x00000001 (1)
* Bootloader Version:       0x00000001 (1)
* Bank Layout:              0x00000000
* Current Bank:             0x00000000
* Application Size:         0x0000A1D0 (41424 bytes)
* Application CRC:          0xBEFCF277
* Bank0 Bank Code:          0x00000001
* Softdevice Size:          0x00000000 (0 bytes)
* Boot Validation CRC:      0x00000000
* SD Boot Validation Type:  0x00000000 (0)
* App Boot Validation Type: 0x00000000 (0)

>mergehex.exe -m s112_nrf52_6.1.1_softdevice.hex app.hex -o sd_and_app.hex
Parsing input hex files.
Merging files.
Storing merged file.

>mergehex.exe -m sd_and_app.hex bl.hex -o sd_and_app_and_bl.hex
Parsing input hex files.
Merging files.
Storing merged file.

>mergehex.exe -m sd_and_app_and_bl.hex settings.hex -o all.hex
Parsing input hex files.
Merging files.
Storing merged file.

Bootloader = examples\dfu\secure_bootloader\pca10040e_ble\

Application,

Program Size: Code=36132 RO-data=5176 RW-data=496 ZI-data=7224 

After program all.hex to device, nRFGo Studio cann't see the bootloader area

So, DFU is failed, who can tell me the solution, or how to debug the bootloader? Thanks!

The previous SDK15.2 is OK, so SDK15.3...

[Hung Bui]

Hi Hansome, 

I'm not sure why the bootloader doesn't work. However, regarding the problem that nRFGo Studio doesn't display that the bootloader is flashed, I think it's related to this: https://devzone.nordicsemi.com/f/nordic-q-a/44768/sdk-15-3-cannot-program-default-bootloader

The address of the bootloader now stored inside the MBR, not in the UICR. 

The nRFGo Studio is deprecated application and replaced by nRF Connect application. 

I would suggest you to test with the bootloader and the softdevice only first. You can flash using nrfjprog.exe application.  Make sure you can see the device advertising as  DFUTarg, before testing combining with application. 

[Hansome]

Where are the new operation steps or guide by SDK15.3?

[Hung Bui]

Hi Hansome, 

Please just follow the documentation of the bootloader. 

The only note is that when you flash using Keil from the second time, you may erase the MBR, so you need to comment out the code to write to MBR inside nrf_bootloader_info.c. But remember to enable it again if you flashing the bootloader the first time (after a chip erase for example)