OTA fails,it stay at bootloader mode.

[Alice]

Hi all,

I'm using nRF5 SDK V12.2 to do the OTA for nRF52832 . In general, it's ok. However, if I close the bluetooth function on the phone or close the DFU app from the nRF toolbox to make some bad condition, the OTA is interrupted and it will stay at bootloader all the time and never switch to the original application. For the nRF5 SDK V11.0, the bootloader will switch to the original application when OTA fails. So could you tell me how to make it witch to the original application when OTA fails? Thanks.

nRF52_clife_SDK_0511.hex s132_nrf52_3.0.0_softdevice.hex nRF52_bootloader_V12.2_timeout.hex nRF52_clife_SDK_setting_0511.hex nRF52_SDK_APP_SD_BL_0511_V1.0.hex

nRF52_bootloader_V12.2.hex

[bjorn-spockeli]

Hi Alice,

you are correct that the Secure Bootloader in SDK v12.x.x will not timeout if there is no DFU activity and jump to the original application.

You can implement a timeout using the WDT, see this answer, or you can use the RTC, see this answer. I recommend using the WDT approach as this is the easiest to implement.

Best regards

Bjørn

[bjorn-spockeli]

Do you mean that after you flash the BL+Settings+Application+ SoftDevice the nRF52 jumps to the application? Or do you mean that you cannot etter the bootloader from the application? If its the latter , how are you triggering the switch from application to bootloader? Is it by holding down a button or have you implemented buttonless DFU?

[bjorn-spockeli]

Are you using the WDT in your application?

[Alice]

It's OK now. There is something wrong with my PC