SDK 12.3 DFU problem

RE: SDK 12.3 DFU problem

bjorn-spockeli — Sat, 28 Oct 2017 12:12:57 GMT

Happy to help :) I would appreciate if you could mark the answer as accepted/correct by clicking the check mark in the grey circle to the left of the answer.

RE: SDK 12.3 DFU problem

summer — Sat, 28 Oct 2017 02:45:52 GMT

ok ,l get it,thank you very much.

RE: SDK 12.3 DFU problem

bjorn-spockeli — Fri, 27 Oct 2017 13:22:47 GMT

The legacy bootloader (SDK v11.0.0) would timeout and reset to the applicaiton if there was no DFU activity. This feature did not make it in to the Secure Bootloader that was introduced in SDK v12.x.x, but it was later added in SDK v13.0.0 and all subsequent SDK versions.

So if you do not want to migrate to SDK v13.0.0 or newer, then you configure the WDT in the bootloader to achieve the same behavior, see this answer.

If you already have enabled the WDT in the application, then you will need to feed it in the bootloader, just make sure to only feed it if there is DFU activity. If the application WDT timeout interval is to long, then you can use the RTC as suggested in this answer.

RE: SDK 12.3 DFU problem

secondbest — Thu, 26 Oct 2017 14:14:16 GMT

I have the same problem too. The device stay in the bootloader mode(advertising dfutarg name) and the current consumption is nearly 5mA in this situation. Any solution??