DFU program not loading

RE: DFU program not loading

Vojislav — Thu, 07 Nov 2019 15:39:11 GMT

Thank you all for the help, I managed to do the DFU correctly. At first, I did not understand concept correctly so that is why it did not work out. I suggest that you change your DFU guide a bit, and be more clear about every step.

Best regards,
Voja.

RE: DFU program not loading

Sigurd — Wed, 18 Sep 2019 09:16:29 GMT

[quote userid="80703" url="~/f/nordic-q-a/52124/dfu-program-not-loading/210062"]When I am building the nRF5_SDK_15.3.0\examples\dfu\secure_bootloader I get only the bootloader hex, this project does not include the application?[/quote]

That is correct.

[quote userid="80703" url="~/f/nordic-q-a/52124/dfu-program-not-loading/210062"]If that is true then I understand your questions better, and obviously, I am just uploading the new bootloader, but I still do not understand why the adv name is not changing...[/quote]

You upload a bootloader as the application. I.e. you used --application when specifying the hex file. If you wanted to do a bootloader DFU, then you should use --bootloader. See this page.

RE: DFU program not loading

Vojislav — Tue, 17 Sep 2019 10:08:34 GMT

Hi,

My main concern is that I do not understand how this works. This is what I understand so far, and please correct me if I am wrong:

There is:
1. Bootloader
2. application
3. Softdevice

When I am building the nRF5_SDK_15.3.0\examples\dfu\secure_bootloader I get only the bootloader hex, this project does not include the application?
If that is true then I understand your questions better, and obviously, I am just uploading the new bootloader, but I still do not understand why the adv name is not changing...

Best regards,
Voja.

RE: DFU program not loading

Duy — Sat, 14 Sep 2019 03:14:39 GMT

Hello,

Have you checked if the name is redefined? You can

[quote userid="80703" url="~/f/nordic-q-a/52124/dfu-program-not-loading"]10. To see the change when the new appication code us updated after the dfu I changed the device name in the sdk_config.h file. to
#define NRF_DFU_BLE_ADV_NAME "DfuTargv1"
and build the application again. [/quote]

You changed this in the bootloader or the application?

[quote userid="80703" url="~/f/nordic-q-a/52124/dfu-program-not-loading"][/quote]

13. After the firmware is uploaded I get this screen which seems ok:

and the nRF52 dev board is disconnected, so the LEDs 1 and 2 are again ON but the device does not change the name to DfuTargv1

Are you sure that you are uploading the application? As I understand, you changed the name of the bootloader and then you upload the bootloader again though DFU...

As you see, after your firmware is uploaded, you still see the LED1 and LED2, so it means you are still in the bootloader.

Please correct me if I misunderstood you.

Best regards,

Duy