Window watchdog concept in Embedded C

Introduction

A window watchdog helps keep an embedded system safe by making sure the program is running correctly and on time.

When you want to reset the system if it gets stuck or runs too slow.

When you need to detect if a task is not completed within a certain time window.

When you want to improve system reliability by recovering from software errors automatically.

When you want to monitor critical parts of your embedded program to avoid freezes.

When you want to avoid system crashes caused by unexpected delays or infinite loops.

Syntax

Embedded C

/* Example pseudocode for Window Watchdog setup and refresh */
void WWDG_Init(void) {
    // Enable clock for WWDG
    // Set window value (time window)
    // Set counter value (timeout)
    // Enable WWDG
}

void WWDG_Refresh(void) {
    // Reload the counter within the allowed window
}

The window watchdog timer must be refreshed only during a specific time window.

Refreshing too early or too late causes a system reset.

Examples

This sets the allowed time window and starts the watchdog timer.

Embedded C

/* Initialize WWDG with window = 80, counter = 127 */
WWDG->CFR = 80;  // Set window value
WWDG->CR = 0x7F;  // Set counter and enable WWDG

Refreshing the counter resets the timer if done inside the window.

Embedded C

/* Refresh WWDG counter within window */
WWDG->CR = 0x7F;  // Reload counter to prevent reset

Sample Program

This program initializes the window watchdog and refreshes it three times during normal operation to prevent reset.

Embedded C

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

// Simulated registers for example
uint8_t WWDG_CFR = 0;
uint8_t WWDG_CR = 0;

void WWDG_Init(void) {
    WWDG_CFR = 80;  // Set window value
    WWDG_CR = 0x7F;  // Set counter and enable WWDG
    printf("WWDG initialized with window=80 and counter=127\n");
}

void WWDG_Refresh(void) {
    // Refresh counter within window
    WWDG_CR = 0x7F;
    printf("WWDG refreshed\n");
}

int main(void) {
    WWDG_Init();
    // Simulate normal operation
    for (int i = 0; i < 3; i++) {
        // Do some work
        printf("Working... iteration %d\n", i+1);
        // Refresh watchdog
        WWDG_Refresh();
    }
    return 0;
}

Important Notes

Always refresh the watchdog timer within the allowed window to avoid unwanted resets.

Window watchdogs are stricter than regular watchdogs because they check timing more precisely.

Use watchdogs to improve system safety in critical embedded applications.

Summary

A window watchdog timer helps detect software problems by requiring timely refreshes.

Refreshing too early or too late causes a system reset, helping catch errors.

It is useful to keep embedded systems running safely and reliably.

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