[Solved] Find the bug in this shutdown notification code:void Task(void *pvParameters) { for (;;) { ulTaskNotifyTake(pdFALSE, portMAX_DELAY); if (shutdownRequested) { break; } } vTaskDelete(NULL); } | FreeRTOS

FreeRTOS - Design Patterns for RTOS

Find the bug in this shutdown notification code:

void Task(void *pvParameters) {
  for (;;) {
    ulTaskNotifyTake(pdFALSE, portMAX_DELAY);
    if (shutdownRequested) {
      break;
    }
  }
  vTaskDelete(NULL);
}

AportMAX_DELAY causes infinite wait, blocking shutdown

BvTaskDelete(NULL) should be outside the loop

CshutdownRequested is not updated inside the loop

DpdFALSE should be pdTRUE to clear notification count

Step-by-Step Solution

Solution:

Step 1: Understand ulTaskNotifyTake parameters
First parameter pdTRUE clears notification count on exit; pdFALSE does not.
Step 2: Identify impact of pdFALSE here
Not clearing notification causes ulTaskNotifyTake to return immediately repeatedly, causing busy loop.
Final Answer:
pdFALSE should be pdTRUE to clear notification count -> Option D
Quick Check:
Clear notification with pdTRUE to avoid busy loop [OK]

Quick Trick: Use pdTRUE to clear notification count after take [OK]

Common Mistakes:

Using pdFALSE causing repeated immediate returns
Misunderstanding portMAX_DELAY usage
Ignoring notification clearing

Master "Design Patterns for RTOS" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More FreeRTOS Quizzes

Find the bug in this shutdown notification code:

Step 1: Understand ulTaskNotifyTake parameters

Step 2: Identify impact of pdFALSE here

Final Answer:

Quick Check:

Want More Practice?