Watchdog timer operation in Embedded C - Step-by-Step Execution

Concept Flow - Watchdog timer operation

Start Program

↓

Initialize Watchdog Timer

↓

Enter Main Loop

↓

Reset Watchdog Timer?

No→Watchdog Timer Counts Down

↓

Watchdog Timer Expires

↓

Continue Normal Operation

↓

System Reset

The watchdog timer is set up and regularly reset in the main loop to prevent system reset. If not reset in time, it triggers a system reset.

Execution Sample

Embedded C

void main() {
  WDT_Init();
  while(1) {
    WDT_Reset();
    // normal tasks
  }
}

This code initializes the watchdog timer and resets it continuously inside the main loop to avoid system reset.

Execution Table

Step	Watchdog Timer State	Action	Result	System State
1	Stopped	Call WDT_Init()	Watchdog timer started with timeout	Running
2	Counting down	Enter main loop	Timer counts down	Running
3	Counting down	Call WDT_Reset()	Timer reset to full timeout	Running
4	Counting down	Perform normal tasks	No change to timer	Running
5	Counting down	Call WDT_Reset()	Timer reset again	Running
6	Counting down	Simulate missed reset	Timer continues counting down	Running
7	Near zero	No reset called	Timer expires	System Reset triggered
8	Reset	System restarts	Program restarts from beginning	Running

💡 Execution stops because the watchdog timer expires without reset, causing a system reset.

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 6	After Step 7	Final
Watchdog Timer	Stopped	Full timeout	Full timeout	Counting down	Expired	Reset

Key Moments - 3 Insights

Why does the system reset if WDT_Reset() is not called in time?

Because the watchdog timer counts down and triggers a system reset when it reaches zero without being reset, as shown in step 7 of the execution_table.

What happens when WDT_Reset() is called inside the main loop?

The watchdog timer is reset to its full timeout value, preventing the system reset, as seen in steps 3 and 5.

Does normal task execution affect the watchdog timer?

No, normal tasks do not change the watchdog timer unless WDT_Reset() is called, as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the watchdog timer state after step 5?

A Stopped

B Expired

C Full timeout (reset)

D Counting down near zero

💡 Hint

Check the 'Watchdog Timer State' column at step 5 in the execution_table.

At which step does the system reset get triggered?

A Step 4

B Step 7

C Step 3

D Step 2

💡 Hint

Look for 'System Reset triggered' in the 'System State' column in the execution_table.

If WDT_Reset() was never called, how would the timer state change by step 6?

A It would be counting down and near expiration

B It would be reset to full timeout

C It would remain stopped

D It would cause immediate system reset at step 2

💡 Hint

Refer to the 'Watchdog Timer State' progression in variable_tracker and execution_table steps 2 to 6.

Concept Snapshot

Watchdog Timer Operation:
- Initialize watchdog timer at program start
- Regularly call WDT_Reset() inside main loop
- If WDT_Reset() is missed, timer counts down to zero
- Timer expiration triggers system reset
- Prevents system hang by forcing restart

Full Transcript

This visual execution shows how a watchdog timer works in embedded C. First, the watchdog timer is initialized and started. Then the program enters the main loop where it regularly calls WDT_Reset() to reset the timer countdown. If the reset is missed, the timer counts down to zero and triggers a system reset. This mechanism helps recover from software hangs by restarting the system automatically. The execution table traces each step, showing timer state changes and system state. The variable tracker follows the watchdog timer value over time. Key moments clarify why resets are needed and how normal tasks do not affect the timer. The quiz tests understanding of timer states and reset timing.

Practice

1. What is the main purpose of a watchdog timer in embedded systems?

easy

A. To provide power to the microcontroller

B. To increase the processing speed of the CPU

C. To reset the system if the program stops responding

D. To store data temporarily during program execution

Solution

1. Step 1: Understand watchdog timer function

   A watchdog timer monitors the program to detect if it stops responding or freezes.

2. Step 2: Identify watchdog timer action

   If the program fails to reset the watchdog timer in time, the watchdog resets the system to recover from the freeze.

3. Final Answer:

   To reset the system if the program stops responding -> Option C

4. Quick Check:

   Watchdog timer resets system on freeze = D [OK]

Hint: Watchdog resets system if program hangs [OK]

Common Mistakes:

• Thinking watchdog speeds up CPU
• Confusing watchdog with memory storage
• Assuming watchdog provides power

2. Which of the following is the correct way to reset (kick) a watchdog timer in embedded C?

easy

A. watchdog_reset();

B. reset_watchdog();

C. kick_watchdog();

D. wdt_reset();

Solution

1. Step 1: Recall standard watchdog reset function

   In many embedded C libraries, the function to reset the watchdog timer is wdt_reset().

2. Step 2: Check other options

   Other options like watchdog_reset(), reset_watchdog(), and kick_watchdog() are not standard function names and will cause errors.

3. Final Answer:

   wdt_reset(); -> Option D

4. Quick Check:

   Standard watchdog reset function = wdt_reset() [OK]

Hint: Use wdt_reset() to reset watchdog in embedded C [OK]

Common Mistakes:

• Using non-standard function names
• Forgetting parentheses in function call
• Confusing reset with initialization

3. What will be the output of the following code snippet if the watchdog is not reset within 5 seconds?

void main() {
  setup_watchdog(5); // 5 seconds timeout
  while(1) {
    // No watchdog reset here
  }
  printf("Running");
}

medium

A. The program prints 'Running' continuously

B. The program resets after 5 seconds and never prints 'Running'

C. The program prints 'Running' once and stops

D. Compilation error due to missing watchdog reset

Solution

1. Step 1: Analyze watchdog setup and loop

   The watchdog is set with a 5-second timeout, but inside the infinite loop, the watchdog reset function is never called.

2. Step 2: Understand watchdog behavior on timeout

   Since the watchdog is not reset, after 5 seconds it triggers a system reset. The printf statement is never reached.

3. Final Answer:

   The program resets after 5 seconds and never prints 'Running' -> Option B

4. Quick Check:

   No watchdog reset causes reset before printf = A [OK]

Hint: No watchdog reset means system resets before print [OK]

Common Mistakes:

• Assuming printf runs before reset
• Thinking program runs normally without reset
• Confusing compile error with runtime reset

4. Identify the error in this watchdog usage code snippet:

void main() {
  setup_watchdog(10);
  while(1) {
    if (some_condition) {
      wdt_reset();
    }
  }
}

medium

A. Watchdog is reset only conditionally, may cause unexpected reset

B. Watchdog timeout is too long for embedded systems

C. Missing initialization of watchdog timer

D. Incorrect function name for watchdog reset

Solution

1. Step 1: Review watchdog reset condition

   The watchdog reset wdt_reset() is called only if some_condition is true, so it may not be called regularly.

2. Step 2: Understand watchdog requirement

   Watchdog must be reset regularly regardless of conditions to prevent system reset. Conditional reset risks unexpected resets.

3. Final Answer:

   Watchdog is reset only conditionally, may cause unexpected reset -> Option A

4. Quick Check:

   Conditional watchdog reset risks reset = C [OK]

Hint: Always reset watchdog regularly, not conditionally [OK]

Common Mistakes:

• Ignoring conditional reset risk
• Thinking timeout length is error
• Assuming missing initialization

5. You want to use a watchdog timer to reset your embedded system if it freezes, but only after 3 seconds of no reset. Which approach correctly implements this behavior?

hard

A. Initialize watchdog with 3 seconds timeout and call wdt_reset() regularly within 3 seconds

B. Initialize watchdog with 10 seconds timeout and call wdt_reset() every 5 seconds

C. Initialize watchdog with 1 second timeout and call wdt_reset() every 4 seconds

D. Do not initialize watchdog and reset system manually every 3 seconds

Solution

1. Step 1: Set watchdog timeout to desired reset delay

   To reset after 3 seconds of no reset, watchdog timeout must be set to 3 seconds.

2. Step 2: Reset watchdog regularly within timeout

   Call wdt_reset() regularly before 3 seconds elapse to prevent reset during normal operation.

3. Final Answer:

   Initialize watchdog with 3 seconds timeout and call wdt_reset() regularly within 3 seconds -> Option A

4. Quick Check:

   Timeout = 3s and regular reset = B [OK]

Hint: Timeout matches reset interval; reset watchdog before timeout [OK]

Common Mistakes:

• Setting timeout longer than reset interval
• Resetting watchdog less frequently than timeout
• Not initializing watchdog at all