WDT/OTA Bootloader

RE: WDT/OTA Bootloader

Vidar Berg — Wed, 14 Oct 2015 13:09:25 GMT

The problem is that there are no events during advertisement. Thus, WDT is not being fed in time as @Maulik Patel mentioned.

Another solution to creating an app timer instance is to lower the APP_ADV_TIMEOUT_IN_SECONDS which which will result in BLE_GAP_EVT_TIMEOUT every time the advertisement times out. Program execution will return to the endless loop once the event has been serviced and reload the timer. Note that advertising is restarted in this event, so it will never really time out.

RE: WDT/OTA Bootloader

SKo — Wed, 14 Oct 2015 09:02:40 GMT

I noticed a reset while debugging the bootloader. The WDT RUNNSTATUS Register changed from 1 running, to 0 not running. I think this reset is caused by the wdt?

RE: WDT/OTA Bootloader

Maulik Patel — Wed, 14 Oct 2015 08:53:49 GMT

Hi SKo,

Can you make sure that your application does not go into sleep in function sd_app_evt_wait(). I mean if there is no any event from SD up to Watch Dog Timeout then your chip will cause a Watch Dog Reset. What you can try is, create and add a dummy timer which is in repeated mode and keep expiring every second or so, which will help your bootloader in exiting from sd_app_evt_wait() function and reloading a watchdog timer and then again go into sleep if no activity is there.

I hope this helps you.

Regards, Maulik Patel