After DFU (OTA) successful firmware update, device needs to power cycle

RE: After DFU (OTA) successful firmware update, device needs to power cycle

TigerD — Thu, 18 Feb 2021 18:01:44 GMT

Hi RMV,

This was long time ago. I couldn't remember what exactly resolved this. I have already handed this firmware to someone else. Based on my best recollection, nRFConnect app for Andriod may not very reliable, while nRF Toolkit app works OK. I believe there is a timeout constant to establish a communication not longer enough. Certainly, that is also related to client-side firmware. I did that way with the purpose of lowering power consumption.

Regards,

David

RE: After DFU (OTA) successful firmware update, device needs to power cycle

RVM — Thu, 18 Feb 2021 17:51:00 GMT

It is not clear to me what the resolution to this problem really is.

Is it that one should use a specific tool on the phone to explicitly manage the reset sequence?
The nRF Connect and the nRF Toolkit both have DFU capabilities -- does the discussion above suggest that only one of the two actually simulates a full reset of the MCU and start all over as desired?

Or is this a deficiency in the boot loader firmware that needs to be filled in using an explicit software call to reset the SoC.

RE: After DFU (OTA) successful firmware update, device needs to power cycle

TigerD — Fri, 05 Jun 2020 15:36:47 GMT

Amanda,

I tested again, I found that the DFU reset application and application runs without cold reboot by using the nRFToolBox – DFU app on the Android Phone.

The application is reset and activated without cold reboot by using nRFconnect tool app – DFU menu function. But the new loaded application is immediately entering DFU mode again after it is activated by bootloader after updating . That is the reason that the new loaded application behaves not running. A cold reboot certainly clears the state. I confirmed that the new loaded application goes back into application mode by clicking the DISCONNECT menu button on the nRFConnect app without needing a cold reboot. That is the symptom. As far as whether the root cause is because some bad setting on the application code or in the nRF Connect app, I don’t know at this point.

With DFU tool in the nRFtoolBox, it seems consistently working ok so far. I think we can live with that by using nRFToolBox only.

Thank you,

David

RE: After DFU (OTA) successful firmware update, device needs to power cycle

Amanda Hsieh — Fri, 22 May 2020 09:45:50 GMT

Hi David,

Did you modify the example of ble_app_buttonless_dfu and Secure_Bootloader?

Did you combine ble_app_buttonless_dfu application, bootloader and softdevice image with the Bootloader settings page?

I would recommend you to go through this blog post in order to get started with our DFU solution: https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/getting-started-with-nordics-secure-dfu-bootloader.

-Amanda H.

RE: After DFU (OTA) successful firmware update, device needs to power cycle

TigerD — Wed, 20 May 2020 19:24:28 GMT

I tested the example ble_app_buttonless_dfu in the folder

../nRF5_SDK_15.3.0_59ac345/examples/ble_peripheral

And I tested on the nRF52840 dev board. The firmware is updated through OTA, but it needs to toggle the power switch to run the application.

I looked into the ../components/libraries/nrf_bootloader/nrf_bootloader_app_start.c

there is nrf_bootloader_app_start();

AND in the nrf_bootoader_app_start_final.c , there is nrf_bootloader_app_start_final(), app_start(), I don't know which function is the last call to jump to application. Or is it possible the settings generated through nrfutil tool is not right. But application can be started from bootloader after power cycle. I believe there is something in the secure_bootloader code, not resetting the CPU (softReset) after successfully updated firmware. It is difficult to debug bootloader.

Please help on this item.

Thank you,

David

RE: After DFU (OTA) successful firmware update, device needs to power cycle

TigerD — Wed, 20 May 2020 14:00:48 GMT

Amanda,

Sorry, I must have copied from other places.

But my main question is Bootloader seems not resetting after firmware update. That should be in the securebootloader, right? The secure_bootloader is the one under dfu folder.

Any suggestions to what part is missing for not doing software reset?

Thank you,

david

RE: After DFU (OTA) successful firmware update, device needs to power cycle

Amanda Hsieh — Wed, 20 May 2020 11:51:01 GMT

Hi David,

[quote user="TigerD"]//NRF_POWER->GPREGRET = BOOTLOADER_DFU_START;[/quote]

I could not find this code in the main.c of Buttonless DFU Template Application example. Which example are you using?

Power.GPREGRET register is the general purpose retention register. BOOTLOADER_DFU_START is a magic number to signal that the bootloader should enter DFU mode because of the signal from Buttonless DFU in the main app.

[quote user="TigerD"]//peer_manager_Init(); [/quote]

peer_manager_Init() is used to initial Peer Manager which manages BLE security (encryption, pairing, and bonding). Please see the Peer Manager Usage section for the detail.

-Amanda H.

RE: After DFU (OTA) successful firmware update, device needs to power cycle

TigerD — Tue, 19 May 2020 13:15:20 GMT

Also, in my application code, main.c, I commented out:

//NRF_POWER->GPREGRET = BOOTLOADER_DFU_START;

//peer_manager_Init();

The OTA firmware update still works. I don't know what functional roles for both lines of code?

Is it safe if they are commented out? I tested it seems to work with or without.

David