[nRF Connect SDK]Sometimes DFU failed to update binary without confirm.

[Tim Hwang]

Target nRF52832(nrf52dk_nrf52832)
SDK NCS v1.9.1

I have trouble with DFU.
I could implement SMP server into my project according to your guide.
(+) Add DFU support to your application - Software - nRF Connect SDK guides - Nordic DevZone (nordicsemi.com)

My target goes to DFU mode when I received command from remote MCU via UART. (advertise SMP UUID)
I could update ota.bin using Android  nRF Connect Device Manager app

The problem is the End stage of DFU, it is necessary to reset once and confirm it.
But My project is require to enter DFU mode manually.

I'm not sure if I have to confirm it. Sometimes I could update binary without confirm.
So please make sure if I have to have confirm state. It seems that I have to confirm it according to following link.
SMP Server Sample — Zephyr Project Documentation (nordicsemi.com)


If I have to have confirm state, how can I get reset reason? In this case, I goes to DFU mode automatically.
I believe you already have know-how.

Thanks in advance.

[Sigurd]

Hi,

Call boot_write_img_confirmed() after you have done your initialization in main(). 

Similar to how it's done e.g. here: https://github.com/nrfconnect/sdk-nrf/blob/v1.9.1/samples/nrf9160/aws_fota/src/main.c#L462

[Tim Hwang]

Thanks for updating. I'll test it.

[Tim Hwang]

I had to store ota mode using "settings_save_one" API.
If ota mode is set, ota broadcast begin. Then I could finish my ota update well.
And also call boot_write_img_confirmed().

Thanks.