This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

S140 bootloader,no timeout?

Hi,

I use the bootloader in the SDK V13.0, I found that no timeout as the SDK v12.x. However, I have added the WDT to the bootloader refer to the link link text it still stay at the bootloader and never switch to the application from bootloader when the WDT timeout.

image description

Parents
  • I think there is no problem for the WDT setting. Because the device would reset when the WDT timout occurs after I do OTA successful.

    I merge the four files(applicaiton,bootloader,softdevice,bootloader setting) into one file then program to the chip, I found that it stays at the bootloader and broadcast as "DfuTarg", not the application.At this time, if I do OTA and then close bluetooth function or close the APP to make a bad condition, bootloader wouldn't timeout even if I wait a long time. However, if I do OTA successfully, at this time it will run the application, not bootloader. Then I do OTA again and make a bad condition to test WDT, I found that the device reset when the WDT timout occurs.

    So it seems that I have found something. After I program merged file, it should run the application, not the bootloader. In fact, it runs the bootloader. So I think the main problem is how to make it run application when program it firstly. I use the same way for SDK V12.x, it wouldn't meet the problem and it would run the application first.

Reply
  • I think there is no problem for the WDT setting. Because the device would reset when the WDT timout occurs after I do OTA successful.

    I merge the four files(applicaiton,bootloader,softdevice,bootloader setting) into one file then program to the chip, I found that it stays at the bootloader and broadcast as "DfuTarg", not the application.At this time, if I do OTA and then close bluetooth function or close the APP to make a bad condition, bootloader wouldn't timeout even if I wait a long time. However, if I do OTA successfully, at this time it will run the application, not bootloader. Then I do OTA again and make a bad condition to test WDT, I found that the device reset when the WDT timout occurs.

    So it seems that I have found something. After I program merged file, it should run the application, not the bootloader. In fact, it runs the bootloader. So I think the main problem is how to make it run application when program it firstly. I use the same way for SDK V12.x, it wouldn't meet the problem and it would run the application first.

Children
No Data
Related