Open cesarferreira opened 4 years ago
It is up to your bootloader to reset itself to app mode after some time of inactivity, not the library. Which SDK (Nordic SDK, not Android SDK) is your DFU bootloader based on? Do you update only the app, or the SoftDevice as well? Are you using double-bank update?
thanks for the reply
Hi @cesarferreira, you have found a solution because I have the same problem
Hello, I have the same problem. I realized that in IOS, this problems not occurs. In fact, the DFU led indications are turned off immediately after launching the abort() operation. I searched the IOS DFUServiceController and it seems similar to DfuServiceController Android I got that NDK reset the device after 15 seconds sometimes. But most of times, I have to reinstall the firmware manually due to the NDK stays in DFU mode forever.
Thank you for you advice @Juan-GS but you update just the application or APP + BL + SD ? With IOS app example from Nordic my board never go back on the application it stay in DFU Mode but i can see my board advertise with bootloader name. You have add something in you bootloader for the transition to the application after abort ?
Hi @teodf, we only update the APP and we don't add anything to our bootloader after aborting.
In nRF5 SDK version 15 a new command "Abort" have been added, which should reset the device to app mode, but this library was designed before that and is not using it at the moment, relying on a timeout on the device side, like I wrote before. Shall we add it?
Yes I think it can be good to add the command, if it is developed in the SDK you might as well add it to the library.
If we use single-bank the command "abort" just stop the DFU and the nRF stays in DFU mode ? Or he has a solution to get back in the original application/firmware ?
With single back you can't restore the original fw. It'll stay in the bootloader mode, as there's no app available.
@philips77 Any chance this command will be added to the library?
I've added it to the backlog but can't promise any deadline.
Ok, thanks for the update
DFU Bootloader version:
Device information:
Your question When I abort (at 16% as shown on the logs below), the device stays in DFU mode forever (I've left it overnight and it never leaves it). If I remove the batteries, still doesnt reboot into the old app. The only way to make it work again is to use the NRFConnect app and force a DFU.zip to make it exit.
And according to the documentation:
the DFU bootloader will restore the old application
I was expecting this to happen. Am I not doing something correctly?Thanks in advance
Logs