1.6.27 1.7.27 1.10.24 1.11.24 1.12.25 1.13.23 1.14.18 1.15.19 1.17.21 1.22.29 1.23.28 1.24.24 Watchdog Timer (WDT)

Using The Library

The Watchdog Timer (WDT) runs independent of the rest of the system, causing system resets whenever it times out. However, the application software should ensure that the timeout never occurs by resetting the WDT periodically as long as the software is in a known healthy state.

If the system hangs or program execution is corrupted, the WDT will not receive its periodic reset, and will eventually time out and cause a system reset.

In many systems, there is an obvious upper boundary to the amount of time each iteration of the main application loop can be expected to run, before a malfunction can be assumed (either due to a deadlock waiting on hardware or software, or due to other means).

When the Watchdog is configured with a timeout period equal to this upper boundary, a malfunction in the system will force a full system reset to allow for a graceful recovery.

Window Mode

In many system, there is also lower boundary to the amount of time each iteration of the main application loop can be expected to run. To guard against a system failure resetting the Watchdog in a tight loop (or a failure in the system application causing the main loop to run faster than expected) a "Window" mode can be enabled to disallow resetting of the Watchdog counter before a certain period of time. If the Watchdog is not reset after the window opens but not before the Watchdog expires, the system will reset.

Here is an example code to enable watchdog timer and keep clearing at regular intervals

WDT_Enable();

while ( true )
{
    // Application Code

    WDT_Clear();
}

Library Interface

Watchdog Timer peripheral library provides the following interfaces:

Functions