Window watchdog concept in Embedded C - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a Window Watchdog (WWDG) in embedded systems?

A Window Watchdog is a hardware timer that resets the system if the software fails to refresh it within a specific time window, helping to recover from software faults.

intermediate

How does the Window Watchdog differ from a traditional watchdog timer?

Unlike a traditional watchdog that resets if not refreshed anytime before timeout, the Window Watchdog requires refreshing only within a specific time window, preventing early or late refreshes.

beginner

What happens if the Window Watchdog is refreshed too early or too late?

Refreshing too early or too late causes the Window Watchdog to trigger a system reset, ensuring the software behaves correctly within the expected timing window.

beginner

Why is the Window Watchdog useful in embedded programming?

It helps detect software faults like infinite loops or deadlocks by enforcing timing constraints on the software's refresh calls, improving system reliability.

intermediate

Describe the typical steps to use a Window Watchdog in embedded C.

1. Initialize the watchdog timer with a timeout window.
2. Start the watchdog.
3. Periodically refresh the watchdog within the allowed window.
4. If refresh is missed or too early, the watchdog resets the system.

What does the Window Watchdog monitor in an embedded system?

A The timing of software refresh calls

B The CPU temperature

C The battery voltage

D The memory usage

The Window Watchdog monitors when the software refreshes it to ensure it happens within a specific time window.

What happens if the Window Watchdog is refreshed too early?

A Watchdog timer pauses

B System reset is triggered

C Nothing happens

D Watchdog timeout is extended

Refreshing too early violates the timing window and causes the watchdog to reset the system.

Which of the following is a key benefit of using a Window Watchdog?

A Improves network speed

B Increases CPU speed

C Reduces power consumption

D Detects software stuck in loops by timing refreshes

The Window Watchdog helps detect software faults like infinite loops by enforcing refresh timing.

In embedded C, what is the main function of refreshing the Window Watchdog?

A To reset the watchdog timer within the allowed window

B To disable the watchdog permanently

C To increase the watchdog timeout

D To read sensor data

Refreshing resets the watchdog timer countdown, preventing a system reset if done correctly.

What is the consequence of missing the Window Watchdog refresh?

A System speed doubles

B Watchdog enters sleep mode

C System reset occurs

D Nothing happens

If the refresh is missed, the watchdog assumes a fault and resets the system.

Explain the concept of a Window Watchdog and why it is important in embedded systems.

Think about how the watchdog helps catch software errors by checking when it is refreshed.

Describe the steps to implement a Window Watchdog in an embedded C program.

Consider what you must do before and during the program to keep the watchdog happy.

Practice

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

easy

A. To increase the processing speed of the microcontroller

B. To reset the system if the software fails to refresh the timer within a specific time window

C. To store data temporarily during program execution

D. To provide power backup during system failure

Solution

1. Step 1: Understand the watchdog timer function

   A watchdog timer monitors if the software is running correctly by expecting periodic refreshes.

2. Step 2: Identify the role of the window watchdog

   The window watchdog resets the system if the refresh happens too early or too late, ensuring software reliability.

3. Final Answer:

   To reset the system if the software fails to refresh the timer within a specific time window -> Option B

4. Quick Check:

   Window watchdog resets system on missed or mistimed refresh [OK]

Hint: Watchdog resets system if refresh is outside allowed time [OK]

Common Mistakes:

• Confusing watchdog with memory storage
• Thinking watchdog speeds up the processor
• Assuming watchdog provides power backup

2. Which of the following is the correct way to refresh a window watchdog timer in embedded C?

easy

A. Call WWDG_Refresh() function within the allowed time window

B. Call WWDG_Refresh() only once at system startup

C. Disable the watchdog timer before refreshing

D. Refresh the watchdog timer continuously without delay

Solution

1. Step 1: Understand watchdog refresh requirements

   The watchdog must be refreshed periodically within a specific time window to avoid reset.

2. Step 2: Identify correct refresh method

   Calling WWDG_Refresh() within the allowed time window is the correct way to refresh.

3. Final Answer:

   Call WWDG_Refresh() function within the allowed time window -> Option A

4. Quick Check:

   Refresh watchdog periodically inside time window [OK]

Hint: Refresh watchdog periodically, not just once or too fast [OK]

Common Mistakes:

• Refreshing only once at startup
• Disabling watchdog before refresh
• Refreshing too frequently causing reset

3. Consider this code snippet using a window watchdog timer:

void main() {
  WWDG_Init();
  while(1) {
    delay(50);  // delay in ms
    WWDG_Refresh();
  }
}

If the allowed refresh window is between 40ms and 60ms, what will happen?

medium

A. The system will reset because refresh is too early

B. The system will reset because refresh is too late

C. The system will run normally without reset

D. The system will freeze due to watchdog error

Solution

1. Step 1: Analyze the refresh timing

   The code delays 50ms before refreshing the watchdog, which is within the 40-60ms window.

2. Step 2: Determine system behavior

   Since refresh happens inside the allowed window, the system will not reset and runs normally.

3. Final Answer:

   The system will run normally without reset -> Option C

4. Quick Check:

   Refresh at 50ms inside 40-60ms window = no reset [OK]

Hint: Check if refresh delay fits inside allowed window [OK]

Common Mistakes:

• Assuming 50ms is too early or too late
• Confusing delay units
• Ignoring the watchdog window limits

4. The following code causes the system to reset unexpectedly. What is the likely error?

void main() {
  WWDG_Init();
  while(1) {
    WWDG_Refresh();
    delay(30);  // delay in ms
  }
}

Assuming the allowed refresh window is 40ms to 60ms.

medium

A. Not calling WWDG_Refresh() frequently enough

B. Delay is too long causing late refresh

C. Missing WWDG_Init() call

D. Refreshing the watchdog too early before the window opens

Solution

1. Step 1: Check refresh timing relative to window

   The code refreshes the watchdog immediately, then delays 30ms, so refresh happens every ~30ms.

2. Step 2: Compare with allowed window

   Since the window starts at 40ms, refreshing at 30ms is too early and causes reset.

3. Final Answer:

   Refreshing the watchdog too early before the window opens -> Option D

4. Quick Check:

   Refresh before 40ms window causes reset [OK]

Hint: Refresh only after window opens, not before [OK]

Common Mistakes:

• Thinking delay is too long
• Ignoring refresh order
• Assuming missing init causes reset here

5. You want to design a system using a window watchdog timer that resets if the refresh happens outside 100ms to 200ms window. Which approach correctly implements this behavior in embedded C?

hard

A. Refresh the watchdog every 150ms

B. Refresh the watchdog every 50ms

C. Refresh the watchdog every 250ms

D. Refresh the watchdog only once at startup

Solution

1. Step 1: Understand the allowed refresh window

   The watchdog must be refreshed between 100ms and 200ms to avoid reset.

2. Step 2: Evaluate each refresh timing option

   Refreshing at 50ms is too early, 150ms is inside window, 250ms is too late, and once at startup is insufficient.

3. Final Answer:

   Refresh the watchdog every 150ms -> Option A

4. Quick Check:

   Refresh inside 100-200ms window avoids reset [OK]

Hint: Refresh watchdog only inside allowed time window [OK]

Common Mistakes:

• Refreshing too early or too late
• Refreshing only once
• Ignoring window timing constraints