This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SDK 12.3 DFU problem

hi everyone ,I want to ask you a question, I use the SDK12.3, when the device from the application transformation to the bootloader, when DFU is failed, why the deice is stays in the bootloader mode,rather than go to the application patterns?Anybody know what this is?

Parents
  • 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.

  • 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.

Reply Children
No Data
Related