OTA firmware update

[Sébastien Schiesser]

Good morning,

Based on different articles, I set up a nrf52832 with S132 3.1.0, the secure bootloader found in "SDK_12.2.0/examples/dfu/bootloader_secure" and the buttonless dfu ("SDK_12.2.0/examples/ble_peripheral/experimental_ble_app_buttonless_dfu") with some bugfixes found here.

Everything works fine except one thing for which I don't how to work around:

1. My app is running, advertising under let's say "Nordic_Buttonless".
2. When I connect (with nRF connect on Android 4.4.2), I have one writable characteristic to enter into DFU mode, which I select, confirm and send (as a request).
3. Then I press the DFU icon and select the distribution packet.
4. When the packet starts uploading, the peripheral disconnects and restarts in bootloader mode, advertising under "dfuTarg".
5. "dfuTarg" automatically reconnects to nRF connect and would be ready for DFU... but the old ("Nordic_Buttonless") connection is still trying to upload the distribution packet. So I have to kill nRF connect and restart it to enable DFU.

Could it be possible to avoid point 3. and proceed to the system reset in bootloader mode without having an ongoing upload running? I'm not sure how the whole program works and cannot use the console to debug (when nrf_log is enabled, the free version of uVision runs out of its limits).

Thanks, Sébastien

[bjorn-spockeli]

Hi Sébastien, the known issues with the buttonless example from SDK v12.x.x has been fixed in SDK v13.0.0. In fact the example has been re-written with a much simpler and better way to switch from the application to the bootloader. If it is an option, then I would strongly recommend moving to SDK v13.0.0.

[Sébastien Schiesser]

Thanks Bjørn for the answer. Since our current development state is not yet critical, I'll change to v13 and use the new example application.