Watchdog task pattern in FreeRTOS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a watchdog timer with FreeRTOS API.

FreeRTOS

TimerHandle_t watchdogTimer = xTimerCreate("Watchdog", pdMS_TO_TICKS([1]), pdFALSE, NULL, watchdogCallback);

Drag options to blanks, or click blank then click option'

A2000

B10000

C1000

D5000

Attempts:

3 left

💡 Hint

Common Mistakes

Setting the timeout too short causing false triggers.

Using zero or negative values which are invalid.

The watchdog timer is set to 5000 milliseconds (5 seconds) to monitor task health.

2fill in blank

medium

Complete the code to start the watchdog timer after creation.

FreeRTOS

if (xTimerStart(watchdogTimer, [1]) != pdPASS) {
    // Handle error
}

Drag options to blanks, or click blank then click option'

A0

BportMAX_DELAY

C100

DpdMS_TO_TICKS(1000)

Attempts:

3 left

💡 Hint

Common Mistakes

Using a blocking delay unnecessarily.

Passing an invalid block time causing errors.

Passing 0 as block time means the call will not block if the timer command queue is full.

3fill in blank

hard

Fix the error in the watchdog task function to reset the timer correctly.

FreeRTOS

void WatchdogTask(void *pvParameters) {
    for (;;) {
        if (xTimerReset(watchdogTimer, [1]) != pdPASS) {
            // Handle reset failure
        }
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

Drag options to blanks, or click blank then click option'

A0

BportMAX_DELAY

CpdMS_TO_TICKS(1000)

D1000

Attempts:

3 left

💡 Hint

Common Mistakes

Using a blocking delay causing watchdog to miss resets.

Passing incorrect block time values.

Using 0 as block time ensures the reset command is sent without blocking.

4fill in blank

hard

Fill both blanks to create a dictionary of task names and their last heartbeat times.

FreeRTOS

typedef struct {
    char name[16];
    TickType_t lastHeartbeat;
} TaskStatus;

TaskStatus taskStatusArray[[1]];

void updateHeartbeat(const char* taskName, TickType_t tick) {
    for (int i = 0; i < [2]; i++) {
        if (strcmp(taskStatusArray[i].name, taskName) == 0) {
            taskStatusArray[i].lastHeartbeat = tick;
            break;
        }
    }
}

Drag options to blanks, or click blank then click option'

A5

B10

Attempts:

3 left

💡 Hint

Common Mistakes

Mismatching array size and loop limit causing out-of-bounds errors.

Using too small array size for the number of tasks.

The array size and loop limit must match the number of tasks monitored, here 10.

5fill in blank

hard

Fill all three blanks to implement the watchdog check function that resets system on timeout.

FreeRTOS

void checkWatchdog() {
    TickType_t currentTick = xTaskGetTickCount();
    for (int i = 0; i < [1]; i++) {
        if (currentTick - taskStatusArray[i].lastHeartbeat > [2]) {
            [3]();
        }
    }
}

Drag options to blanks, or click blank then click option'

A5

BpdMS_TO_TICKS(5000)

CsystemReset

D10

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong timeout values causing premature resets.

Calling wrong function or missing reset call.

The function loops over 10 tasks, checks if heartbeat is older than 5 seconds, and calls systemReset if so.

Practice

1. What is the main purpose of a watchdog task in FreeRTOS?

easy

A. To create new tasks dynamically during runtime

B. To monitor other tasks and reset the system if a task fails

C. To handle user input events

D. To manage memory allocation for tasks

Solution

1. Step 1: Understand the watchdog task role

   The watchdog task monitors the health of other tasks to ensure they are running correctly.

2. Step 2: Identify the action taken on failure

   If a task fails or stops responding, the watchdog task can reset the system or take corrective action.

3. Final Answer:

   To monitor other tasks and reset the system if a task fails -> Option B

4. Quick Check:

   Watchdog monitors and resets = A [OK]

Hint: Watchdog watches tasks and resets on failure [OK]

Common Mistakes:

• Confusing watchdog with task creation
• Thinking watchdog handles user input
• Assuming watchdog manages memory

2. Which of the following is the correct way to reset a watchdog timer in a FreeRTOS task?

easy

A. Call watchdog_reset() periodically from monitored tasks

B. Use xTaskCreate() to reset the timer

C. Call vTaskDelay() inside the watchdog task

D. Call vTaskDelete() on the watchdog task

Solution

1. Step 1: Identify how watchdog timers are reset

   Monitored tasks must periodically signal the watchdog by calling a reset function like watchdog_reset().

2. Step 2: Eliminate incorrect options

   vTaskDelay() delays a task but does not reset the watchdog timer. xTaskCreate() creates tasks, not reset timers. vTaskDelete() deletes tasks, not reset timers.

3. Final Answer:

   Call watchdog_reset() periodically from monitored tasks -> Option A

4. Quick Check:

   Reset watchdog by calling reset function = C [OK]

Hint: Reset watchdog by calling its reset function in tasks [OK]

Common Mistakes:

• Using delay functions to reset watchdog
• Trying to reset watchdog by creating or deleting tasks
• Confusing task management functions with watchdog reset

3. Consider this simplified watchdog task code snippet in FreeRTOS:

void WatchdogTask(void *pvParameters) {
    for (;;) {
        if (xSemaphoreTake(watchdogSemaphore, pdMS_TO_TICKS(1000)) == pdFALSE) {
            // No reset signal received
            vTaskDelay(pdMS_TO_TICKS(500));
            // Take recovery action
        } else {
            // Reset signal received
            vTaskDelay(pdMS_TO_TICKS(100));
        }
    }
}

What happens if the monitored task never calls xSemaphoreGive(watchdogSemaphore)?

medium

A. The watchdog task will detect no reset signal and take recovery action repeatedly

B. The watchdog task will keep waiting forever without action

C. The watchdog task will crash due to semaphore misuse

D. The watchdog task will reset the semaphore automatically

Solution

1. Step 1: Analyze semaphore wait behavior

   The watchdog task waits 1000 ms for a semaphore signal. If none arrives, xSemaphoreTake returns pdFALSE.

2. Step 2: Understand the consequence of no signal

   When no signal is received, the watchdog delays 500 ms and then takes recovery action repeatedly in the loop.

3. Final Answer:

   The watchdog task will detect no reset signal and take recovery action repeatedly -> Option A

4. Quick Check:

   No semaphore signal triggers recovery = A [OK]

Hint: No semaphore signal means watchdog triggers recovery [OK]

Common Mistakes:

• Assuming watchdog waits forever without action
• Thinking semaphore misuse causes crash here
• Believing semaphore resets automatically

4. Given this watchdog task snippet:

void WatchdogTask(void *pvParameters) {
    for (;;) {
        if (xSemaphoreTake(watchdogSemaphore, 0) == pdTRUE) {
            // Reset received
        } else {
            // No reset, take action
        }
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

What is the main problem with this code?

medium

A. The task deletes itself after one loop

B. The task delays too long after receiving a reset signal

C. The semaphore wait time is zero, so it never blocks to wait for reset signals

D. The semaphore is given incorrectly in the monitored task

Solution

1. Step 1: Examine semaphore wait time parameter

   The call xSemaphoreTake(watchdogSemaphore, 0) means it does not wait and returns immediately.

2. Step 2: Understand impact on watchdog behavior

   Because it never blocks, the watchdog may miss reset signals if they arrive after the check, causing false recovery actions.

3. Final Answer:

   The semaphore wait time is zero, so it never blocks to wait for reset signals -> Option C

4. Quick Check:

   Zero wait means no blocking = D [OK]

Hint: Semaphore wait time zero means no blocking, causing missed signals [OK]

Common Mistakes:

• Thinking delay length is the problem
• Assuming semaphore is given incorrectly without evidence
• Believing task deletes itself here

5. You want to implement a watchdog task that monitors three tasks: TaskA, TaskB, and TaskC. Each task must send a heartbeat signal every 500 ms. Which approach best ensures the watchdog detects a failure in any task within 2 seconds?

hard

A. Use one binary semaphore shared by all tasks; each task gives it every 500 ms

B. Use a single counting semaphore incremented by all tasks; watchdog resets counter every 2 seconds

C. Use three separate semaphores; watchdog waits up to 2 seconds for each semaphore in sequence

D. Use three separate semaphores; watchdog checks each semaphore with a 700 ms timeout and flags failure if any miss

Solution

1. Step 1: Understand heartbeat timing requirements

   Each task sends a heartbeat every 500 ms. The watchdog must detect failure within 2 seconds.

2. Step 2: Evaluate semaphore usage options

   Using separate semaphores allows independent monitoring. Checking each with a 700 ms timeout ensures missing any heartbeat triggers failure detection quickly.

3. Step 3: Compare with other options

   One shared semaphore (Use one binary semaphore shared by all tasks; each task gives it every 500 ms) cannot distinguish which task failed. Waiting 2 seconds per semaphore (Use three separate semaphores; watchdog waits up to 2 seconds for each semaphore in sequence) delays detection. Counting semaphore (Use a single counting semaphore incremented by all tasks; watchdog resets counter every 2 seconds) loses individual task info.

4. Final Answer:

   Use three separate semaphores; watchdog checks each semaphore with a 700 ms timeout and flags failure if any miss -> Option D

5. Quick Check:

   Separate semaphores + short timeout = fast failure detection = B [OK]

Hint: Separate semaphores with short timeout catch failures fast [OK]

Common Mistakes:

• Using one semaphore for all tasks losing failure detail
• Waiting too long per semaphore delaying detection
• Using counting semaphore losing individual task info