Why runtime monitoring catches RTOS bugs in FreeRTOS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start the FreeRTOS scheduler.

FreeRTOS

vTaskStartScheduler[1];

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

A()

B;

C{}

D[]

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting parentheses causes a syntax error.

The function vTaskStartScheduler() starts the RTOS scheduler and requires parentheses even if no arguments are passed.

2fill in blank

medium

Complete the code to create a task with FreeRTOS API.

FreeRTOS

xTaskCreate(TaskFunction, "Task1", 1000, NULL, [1], NULL);

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

A0

BvTaskStartScheduler

C1

DNULL

Attempts:

3 left

💡 Hint

Common Mistakes

Using NULL or zero may create a task with no priority.

The priority parameter in xTaskCreate is an integer. Here, 1 sets the task priority.

3fill in blank

hard

Fix the error in the task delay call to avoid runtime bugs.

FreeRTOS

vTaskDelay([1]);

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

A1000 * portTICK_PERIOD_MS

B1000 / portTICK_PERIOD_MS

C1000

DportTICK_PERIOD_MS

Attempts:

3 left

💡 Hint

Common Mistakes

Using raw milliseconds causes incorrect delays and timing bugs.

FreeRTOS expects delay time in ticks. Dividing milliseconds by portTICK_PERIOD_MS converts ms to ticks correctly.

4fill in blank

hard

Fill both blanks to correctly check if a queue send was successful.

FreeRTOS

if (xQueueSend(queue, &data, [1]) == [2]) { /* success */ }

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

AportMAX_DELAY

BpdPASS

C0

DpdFAIL

Attempts:

3 left

💡 Hint

Common Mistakes

Using zero timeout causes immediate failure if queue is full.

xQueueSend uses portMAX_DELAY to wait indefinitely. It returns pdPASS on success.

5fill in blank

hard

Fill all three blanks to create a runtime monitoring hook for stack overflow detection.

FreeRTOS

void vApplicationStackOverflowHook(TaskHandle_t [1], char *[2]) {
    [3];
}

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

AxTask

BpcTaskName

CtaskDISABLE_INTERRUPTS()

DvTaskDelete(xTask)

Attempts:

3 left

💡 Hint

Common Mistakes

Calling vTaskDelete inside the hook may cause issues.

The hook receives the task handle xTask and task name pcTaskName. Disabling interrupts with taskDISABLE_INTERRUPTS() prevents further damage.

Practice

1. Why is runtime monitoring important in FreeRTOS for catching bugs?

easy

A. It observes the system while running to find timing and interaction issues

B. It compiles the code faster

C. It replaces the need for unit testing

D. It automatically fixes bugs in the code

Solution

1. Step 1: Understand runtime monitoring purpose

   Runtime monitoring watches the RTOS as it runs to detect hidden bugs that only appear during execution.

2. Step 2: Identify what kinds of bugs it catches

   It catches timing issues, resource conflicts, and task interaction problems that static analysis or compile-time checks miss.

3. Final Answer:

   It observes the system while running to find timing and interaction issues -> Option A

4. Quick Check:

   Runtime monitoring = watches running system [OK]

Hint: Runtime monitoring finds bugs only visible during execution [OK]

Common Mistakes:

• Thinking it speeds up compilation
• Believing it replaces testing
• Assuming it fixes bugs automatically

2. Which FreeRTOS configuration option enables runtime monitoring features?

easy

A. configUSE_TIMERS

B. configUSE_PREEMPTION

C. configMAX_PRIORITIES

D. configUSE_TRACE_FACILITY

Solution

1. Step 1: Identify runtime monitoring related config

   Runtime monitoring requires trace facilities to collect task and system event data.

2. Step 2: Match config option to trace feature

   configUSE_TRACE_FACILITY enables trace data collection needed for runtime monitoring.

3. Final Answer:

   configUSE_TRACE_FACILITY -> Option D

4. Quick Check:

   Trace facility config = runtime monitoring enabled [OK]

Hint: Trace facility config enables runtime monitoring [OK]

Common Mistakes:

• Choosing timer or priority configs unrelated to monitoring
• Confusing preemption with monitoring features

3. Given this FreeRTOS trace output snippet showing task switch times, what bug can runtime monitoring help detect?

TaskA switched out at 100ms
TaskB switched in at 100ms
TaskA switched in at 105ms
TaskB switched out at 110ms

medium

A. Task switch times overlap causing resource conflicts

B. TaskA is starving and never runs

C. TaskB runs longer than expected causing timing issues

D. No bug, tasks switch correctly

Solution

1. Step 1: Analyze task switch timing

   TaskB runs from 100ms to 110ms (10ms), TaskA runs from 105ms to 105ms (0ms), overlapping occurs.

2. Step 2: Identify timing issue

   TaskB runs longer than expected, overlapping TaskA's scheduled run, causing timing problems.

3. Final Answer:

   TaskB runs longer than expected causing timing issues -> Option C

4. Quick Check:

   Overlapping run times = timing bug [OK]

Hint: Look for overlapping task run times in trace output [OK]

Common Mistakes:

• Ignoring overlapping times
• Assuming no bug if tasks switch
• Confusing starvation with timing overlap

4. You enabled runtime monitoring but see no data collected. What is the most likely cause?

medium

A. configUSE_TRACE_FACILITY is set to 0

B. The FreeRTOS kernel is not running

C. The hardware timer is too fast

D. The tasks have no delays

Solution

1. Step 1: Check runtime monitoring prerequisites

   Runtime monitoring requires configUSE_TRACE_FACILITY enabled to collect trace data.

2. Step 2: Identify cause of no data

   If configUSE_TRACE_FACILITY is 0, no trace data is collected, so monitoring shows no data.

3. Final Answer:

   configUSE_TRACE_FACILITY is set to 0 -> Option A

4. Quick Check:

   Trace facility disabled = no monitoring data [OK]

Hint: Check trace facility config if no monitoring data appears [OK]

Common Mistakes:

• Assuming kernel not running without verifying
• Blaming timer speed incorrectly
• Thinking task delays affect monitoring data

5. How can runtime monitoring help detect a subtle deadlock caused by two tasks waiting on each other's resources in FreeRTOS?

hard

A. By automatically restarting the tasks to break the deadlock

B. By showing tasks stuck in blocked state with no progress over time

C. By increasing task priorities to force execution

D. By disabling interrupts to isolate the problem

Solution

1. Step 1: Understand deadlock symptoms in runtime

   Deadlock causes tasks to wait indefinitely, appearing as blocked with no state changes.

2. Step 2: Identify monitoring role

   Runtime monitoring tracks task states and timing, revealing tasks stuck without progress.

3. Final Answer:

   By showing tasks stuck in blocked state with no progress over time -> Option B

4. Quick Check:

   Blocked tasks with no progress = deadlock detected [OK]

Hint: Look for tasks blocked without state changes over time [OK]

Common Mistakes:

• Thinking monitoring fixes deadlocks automatically
• Confusing priority changes with monitoring
• Assuming disabling interrupts helps detect deadlocks