Watchdog reset recovery in Embedded C - Mini Project: Build & Apply

Watchdog Reset Recovery

📖 Scenario: You are working on a small embedded system that uses a watchdog timer to reset the device if it gets stuck. Your task is to write code that detects if the last reset was caused by the watchdog and then recovers gracefully by clearing the reset flag.

🎯 Goal: Build a simple embedded C program that checks if the last reset was caused by the watchdog timer, clears the watchdog reset flag, and then prints a message indicating the reset cause.

📋 What You'll Learn

Create a variable reset_flags to simulate the reset status register with the watchdog reset bit set.

Create a constant WATCHDOG_RESET_BIT representing the watchdog reset flag bit mask.

Write code to check if the watchdog reset bit is set in reset_flags and clear it.

Print "Watchdog reset detected and cleared." if the watchdog reset was detected.

💡 Why This Matters

🌍 Real World

Embedded systems often use watchdog timers to reset devices stuck in bad states. Detecting and recovering from these resets helps maintain system reliability.

💼 Career

Understanding watchdog reset recovery is essential for embedded firmware developers working on reliable hardware devices like IoT gadgets, automotive controllers, and industrial machines.

1

DATA SETUP: Create reset flags variable

Create an unsigned integer variable called reset_flags and set it to 0x04 to simulate the watchdog reset flag being set.

Embedded C

# Create an unsigned int variable reset_flags and set it to 0x04
# Your code here

Hint

The value 0x04 means the third bit is set, which we will use as the watchdog reset flag.

2

CONFIGURATION: Define watchdog reset bit mask

Define a constant unsigned integer called WATCHDOG_RESET_BIT and set it to 0x04 to represent the watchdog reset flag bit mask.

Embedded C

unsigned int reset_flags = 0x04;
// Define WATCHDOG_RESET_BIT as 0x04
# Your code here

Hint

This constant helps us check and clear the watchdog reset bit easily.

3

CORE LOGIC: Check and clear watchdog reset flag

Write an if statement that checks if reset_flags has the WATCHDOG_RESET_BIT set. If yes, clear the watchdog reset bit from reset_flags using bitwise AND with the inverse of WATCHDOG_RESET_BIT.

Embedded C

unsigned int reset_flags = 0x04;
const unsigned int WATCHDOG_RESET_BIT = 0x04;
// Check if watchdog reset bit is set and clear it
# Your code here

Hint

Use bitwise AND & to check the bit and bitwise NOT ~ with AND &= to clear it.

4

OUTPUT: Print watchdog reset detection message

Add a printf statement inside the if block to print "Watchdog reset detected and cleared.".

Embedded C

unsigned int reset_flags = 0x04;
const unsigned int WATCHDOG_RESET_BIT = 0x04;

if (reset_flags & WATCHDOG_RESET_BIT) {
    reset_flags &= ~WATCHDOG_RESET_BIT;
    // Print message here
# Your code here
}

Hint

Use printf("Watchdog reset detected and cleared.\n"); inside the if block.

Practice

1.

What is the main purpose of checking the watchdog reset flag at system startup?

easy

A. To increase the watchdog timer interval

B. To disable the watchdog timer permanently

C. To detect if the system was restarted due to a watchdog timeout

D. To reset all system variables to zero

Solution

1. Step 1: Understand watchdog reset flag role

   The watchdog reset flag indicates if the last reset was caused by the watchdog timer expiring.

2. Step 2: Purpose of checking the flag at startup

   Checking this flag helps the program know if it needs to perform recovery actions after an unexpected reset.

3. Final Answer:

   To detect if the system was restarted due to a watchdog timeout -> Option C

4. Quick Check:

   Watchdog reset flag = detect watchdog reset [OK]

Hint: Watchdog flag shows if reset was watchdog-caused [OK]

Common Mistakes:

• Thinking the flag disables the watchdog
• Assuming it resets variables automatically
• Confusing flag with timer interval setting

2.

Which of the following code snippets correctly clears the watchdog reset flag in embedded C?

/* Assume WDT_RESET_FLAG is the flag variable */
// Clear the flag
?

easy

A. WDT_RESET_FLAG = 0;

B. clear(WDT_RESET_FLAG);

C. WDT_RESET_FLAG == 0;

D. reset_flag(WDT_RESET_FLAG);

Solution

1. Step 1: Identify correct syntax to clear a flag

   In embedded C, clearing a flag usually means setting its variable to zero.

2. Step 2: Analyze each option

   WDT_RESET_FLAG = 0; sets the flag to 0, which clears it. clear(WDT_RESET_FLAG); uses a non-standard function. WDT_RESET_FLAG == 0; uses comparison, not assignment. reset_flag(WDT_RESET_FLAG); uses an undefined function.

3. Final Answer:

   WDT_RESET_FLAG = 0; -> Option A

4. Quick Check:

   Clear flag = set to 0 [OK]

Hint: Clear flags by assigning zero directly [OK]

Common Mistakes:

• Using comparison operator '==' instead of assignment
• Calling undefined functions to clear flags
• Confusing clearing with resetting the whole system

3.

Consider the following code snippet that runs at system startup:

if (WDT_RESET_FLAG) {
    recover_from_watchdog();
    WDT_RESET_FLAG = 0;
} else {
    normal_startup();
}

What will happen if the system was reset by the watchdog timer?

medium

A. The system does nothing and hangs

B. The system calls recover_from_watchdog() and clears the flag

C. The system calls normal_startup() only

D. The system resets again immediately

Solution

1. Step 1: Check condition when watchdog reset flag is set

   If WDT_RESET_FLAG is true (non-zero), the if block executes.

2. Step 2: Follow code logic inside the if block

   The function recover_from_watchdog() is called, then the flag is cleared by setting it to zero.

3. Final Answer:

   The system calls recover_from_watchdog() and clears the flag -> Option B

4. Quick Check:

   Flag set = recover and clear flag [OK]

Hint: If flag set, run recovery then clear flag [OK]

Common Mistakes:

• Assuming normal_startup() runs after watchdog reset
• Thinking system hangs without recovery
• Believing system resets again immediately

4.

Identify the error in this watchdog reset recovery code snippet:

if (WDT_RESET_FLAG = 1) {
    recover_from_watchdog();
    WDT_RESET_FLAG = 0;
}

medium

A. Using assignment '=' instead of comparison '==' in the if condition

B. Not clearing the flag after recovery

C. Calling recover_from_watchdog() before checking the flag

D. Missing semicolon after the if statement

Solution

1. Step 1: Analyze the if condition syntax

   The condition uses '=' which assigns 1 to the flag instead of comparing it.

2. Step 2: Understand the impact of assignment in condition

   Assignment always returns true, so the if block runs every time, ignoring actual flag state.

3. Final Answer:

   Using assignment '=' instead of comparison '==' in the if condition -> Option A

4. Quick Check:

   Use '==' for comparison in if conditions [OK]

Hint: Use '==' in if conditions, not '=' [OK]

Common Mistakes:

• Confusing '=' (assign) with '==' (compare)
• Forgetting to clear the flag after recovery
• Misplacing semicolons inside if statements

5.

You want to implement a watchdog reset recovery that logs the reset cause and safely restarts the system only if the reset was caused by the watchdog. Which sequence of actions is correct?

hard

A. Clear watchdog reset flag, restart system, then log reset cause

B. Log reset cause only if watchdog reset flag is not set

C. Restart system immediately, then check and clear watchdog reset flag

D. Check watchdog reset flag, log reset cause, clear flag, then restart system

Solution

1. Step 1: Check the watchdog reset flag at startup

   This tells if the reset was caused by the watchdog timer.

2. Step 2: Log the reset cause and clear the flag before restarting

   Logging helps diagnose issues; clearing the flag prevents repeated recovery loops.

3. Step 3: Restart the system safely after handling the flag

   This ensures the system restarts only after recovery steps are done.

4. Final Answer:

   Check watchdog reset flag, log reset cause, clear flag, then restart system -> Option D

5. Quick Check:

   Check flag -> log -> clear -> restart [OK]

Hint: Always check flag before logging and restarting [OK]

Common Mistakes:

• Restarting before clearing the flag
• Logging after restart (won't execute)
• Ignoring the flag and restarting blindly