Configuring watchdog timeout in Embedded C

Introduction

A watchdog timer helps reset a device if it stops working properly. Setting the timeout decides how long the device waits before resetting.

When you want to make sure your device recovers from freezes automatically.

When your device runs critical tasks and must not stay stuck.

When testing how long your system can run without problems.

When you want to save power by resetting after a certain time.

When debugging to check if your program hangs.

Syntax

Embedded C

void Watchdog_SetTimeout(uint32_t timeout_ms);

The timeout is usually given in milliseconds.

Check your device datasheet for allowed timeout values.

Examples

Sets the watchdog timeout to 1000 milliseconds (1 second).

Embedded C

Watchdog_SetTimeout(1000);

Sets the watchdog timeout to 5000 milliseconds (5 seconds).

Embedded C

Watchdog_SetTimeout(5000);

Sample Program

This program sets the watchdog timeout to 2000 milliseconds and then runs a simple loop printing messages.

Embedded C

#include <stdio.h>
#include <stdint.h>

// Simulated watchdog setup function
void Watchdog_SetTimeout(uint32_t timeout_ms) {
    printf("Watchdog timeout set to %u milliseconds.\n", timeout_ms);
}

int main() {
    // Set watchdog timeout to 2000 ms (2 seconds)
    Watchdog_SetTimeout(2000);
    
    // Simulate main program loop
    for (int i = 0; i < 3; i++) {
        printf("Running main loop iteration %d\n", i + 1);
    }
    return 0;
}

Important Notes

Always set the watchdog timeout long enough for your tasks to complete.

Remember to reset or 'kick' the watchdog regularly to avoid unwanted resets.

Consult your hardware manual for exact watchdog configuration details.

Summary

The watchdog timer helps recover from system hangs by resetting the device.

Configuring the timeout sets how long the system waits before resetting.

Use the timeout setting carefully to balance safety and normal operation.

Practice

1.

What is the main purpose of configuring a watchdog timer's timeout in embedded C?

easy

A. To enable debugging messages

B. To increase the CPU clock speed

C. To set how long the system waits before resetting if it hangs

D. To allocate memory for variables

Solution

1. Step 1: Understand watchdog timer role

   The watchdog timer resets the system if it stops responding.

2. Step 2: Identify timeout configuration purpose

   Timeout sets the wait time before reset triggers.

3. Final Answer:

   To set how long the system waits before resetting if it hangs -> Option C

4. Quick Check:

   Watchdog timeout = reset delay [OK]

Hint: Timeout controls reset delay after hang [OK]

Common Mistakes:

• Confusing timeout with CPU speed
• Thinking timeout allocates memory
• Assuming timeout enables debugging

2.

Which of the following is the correct syntax to set a watchdog timeout to 5000 milliseconds in embedded C?

void setup_watchdog() {
    // Set timeout here
}

easy

A. WDT_SetTimeout(5000);

B. WDT_SetTimeoutMs(5000);

C. watchdog.timeout = 5000;

D. set_watchdog(5000);

Solution

1. Step 1: Identify common watchdog API

   Many embedded C libraries use WDT_SetTimeoutMs() to set timeout in ms.

2. Step 2: Check syntax correctness

   WDT_SetTimeoutMs(5000); correctly sets 5000 ms timeout.

3. Final Answer:

   WDT_SetTimeoutMs(5000); -> Option B

4. Quick Check:

   Correct function name with ms unit [OK]

Hint: Look for function with 'TimeoutMs' for milliseconds [OK]

Common Mistakes:

• Using incorrect function names
• Assigning timeout to struct without function
• Using generic function names not in API

3.

Given the code below, what will be the watchdog timeout value after execution?

typedef struct {
    unsigned int timeout_ms;
} Watchdog;

Watchdog wdt;

void configure_watchdog(unsigned int t) {
    wdt.timeout_ms = t;
}

int main() {
    configure_watchdog(3000);
    configure_watchdog(7000);
    return wdt.timeout_ms;
}

medium

A. 7000

B. 3000

C. 0

D. Compilation error

Solution

1. Step 1: Trace function calls

   First call sets timeout_ms to 3000, second call overwrites it to 7000.

2. Step 2: Check return value

   Main returns wdt.timeout_ms, which is 7000 after second call.

3. Final Answer:

   7000 -> Option A

4. Quick Check:

   Last set timeout = 7000 [OK]

Hint: Last assignment overwrites previous timeout [OK]

Common Mistakes:

• Assuming first call value remains
• Confusing return value with function return
• Thinking timeout resets automatically

4.

Identify the error in the following watchdog timeout configuration code:

void setup_watchdog() {
    int timeout = 2000;
    WDT_SetTimeout(timeout);
    timeout = 5000;
}

medium

A. Timeout value is changed after setting watchdog, ineffective

B. WDT_SetTimeout requires unsigned int, not int

C. Missing return statement in function

D. Timeout variable should be global

Solution

1. Step 1: Analyze timeout variable usage

   Timeout is set to 2000 and passed to WDT_SetTimeout, then changed to 5000 but not applied.

2. Step 2: Understand effect of changing timeout after setting

   Changing timeout variable after setting watchdog has no effect on watchdog timeout.

3. Final Answer:

   Timeout value is changed after setting watchdog, ineffective -> Option A

4. Quick Check:

   Changing variable after call doesn't update watchdog [OK]

Hint: Set timeout once before calling watchdog function [OK]

Common Mistakes:

• Thinking variable change updates watchdog automatically
• Confusing variable type with function parameter
• Expecting return in void function

5.

You want to configure a watchdog timer that resets the system if it hangs for more than 10 seconds, but also want to avoid false resets during long processing tasks. Which approach is best?

hard

A. Set timeout to 20 seconds and never reset watchdog

B. Set timeout to 1 second to catch hangs quickly

C. Disable watchdog during long tasks

D. Set timeout to 10 seconds and reset watchdog regularly during long tasks

Solution

1. Step 1: Understand watchdog timeout role

   Timeout defines max hang time before reset; too short causes false resets.

2. Step 2: Balance timeout and reset calls

   Setting 10 seconds timeout and resetting watchdog during long tasks avoids false resets.

3. Final Answer:

   Set timeout to 10 seconds and reset watchdog regularly during long tasks -> Option D

4. Quick Check:

   Timeout + regular reset prevents false resets [OK]

Hint: Use longer timeout + reset watchdog in long tasks [OK]

Common Mistakes:

• Setting too short timeout causing resets
• Disabling watchdog risking no recovery
• Never resetting watchdog causing reset