[Solved] Identify the issue in the following FreeRTOS code snippet using xTaskNotifyGive(): void Task1(void *pvParameters) { ulTaskNotifyTake(pdTRUE, portMAX_DELAY); | FreeRTOS

FreeRTOS - Task Notifications

Identify the issue in the following FreeRTOS code snippet using xTaskNotifyGive():

void Task1(void *pvParameters) {
    ulTaskNotifyTake(pdTRUE, portMAX_DELAY);
}

void Task2(void *pvParameters) {
    xTaskNotifyGive();
}

AulTaskNotifyTake() is used incorrectly with pdTRUE parameter.

BxTaskNotifyGive() is called without specifying the task handle to notify.

CTask1 should not block indefinitely with portMAX_DELAY.

DTask2 should call ulTaskNotifyTake() instead of xTaskNotifyGive().

Step-by-Step Solution

Solution:

Step 1: Check xTaskNotifyGive() usage
This function requires a TaskHandle_t parameter to specify which task to notify.
Step 2: Analyze the code
Task2 calls xTaskNotifyGive() without any argument, which is invalid.
Final Answer:
xTaskNotifyGive() is called without specifying the task handle to notify. -> Option B
Quick Check:
Missing task handle parameter [OK]

Quick Trick: xTaskNotifyGive needs task handle argument [OK]

Common Mistakes:

Master "Task Notifications" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

More FreeRTOS Quizzes

Identify the issue in the following FreeRTOS code snippet using xTaskNotifyGive():