Configuring watchdog timeout in Embedded C - Quick Revision & Summary

Recall & Review

beginner

What is a watchdog timer in embedded systems?

A watchdog timer is a hardware timer that resets the system if the software becomes unresponsive or stuck, helping to recover from errors automatically.

beginner

Why do we configure the watchdog timeout period?

We configure the watchdog timeout period to set how long the system can run without resetting the watchdog before it triggers a system reset, balancing safety and normal operation.

beginner

Which unit is commonly used to set the watchdog timeout?

The watchdog timeout is commonly set in milliseconds or seconds, depending on the hardware timer's clock and prescaler settings.

intermediate

How do you typically change the watchdog timeout in embedded C code?

You change the watchdog timeout by configuring specific registers related to the watchdog timer, often by setting prescaler and reload values according to the desired timeout period.

beginner

What happens if the watchdog timer is not reset before the timeout?

If the watchdog timer is not reset (or 'kicked') before the timeout expires, it triggers a system reset to recover from a possible software fault.

What is the main purpose of configuring a watchdog timeout?

A To configure the display brightness

B To set how long the system waits before resetting if unresponsive

C To save power during sleep mode

D To increase the CPU clock speed

The watchdog timeout defines how long the system can run without resetting the watchdog before it triggers a reset.

Which action resets the watchdog timer to prevent a system reset?

A Increasing the clock frequency

B Turning off the power supply

C Writing a specific value to the watchdog register

D Disabling interrupts

Resetting the watchdog timer usually involves writing a specific value to its control register to prevent timeout.

If the watchdog timeout is set too short, what might happen?

A The system may reset too often, even during normal operation

B The system will never reset

C The CPU speed will increase

D The memory size will increase

A very short timeout can cause unwanted resets because the system may not reset the watchdog in time during normal tasks.

What is a common unit for watchdog timeout configuration?

A Milliseconds

B Bytes

C Volts

D Degrees Celsius

Timeouts are usually set in time units like milliseconds or seconds.

Which register setting is often involved in configuring watchdog timeout?

A Data direction register

B Analog-to-digital converter register

C Interrupt mask register

D Prescaler and reload value

Prescaler and reload values control the timing interval of the watchdog timer.

Explain how to configure a watchdog timer timeout in embedded C.

Think about how hardware timers use clock division and reload values to set time intervals.

Describe what happens if the watchdog timer is not reset before the timeout expires.

Consider why watchdog timers exist in embedded systems.

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