[Solved] What is wrong with this task notification wait call? uint32_t ulValue; xTaskNotifyWait(0x01, 0x01, &ulValue, 1000); | FreeRTOS

FreeRTOS - Task Notifications

What is wrong with this task notification wait call?

uint32_t ulValue;
xTaskNotifyWait(0x01, 0x01, &ulValue, 1000);

AThe clear bits mask and wait bits mask are the same, causing immediate return

BThe timeout value must be portMAX_DELAY for notifications

CulValue pointer must be NULL if not interested in notification value

DThe function cannot be called with non-zero clear bits mask

Step-by-Step Solution

Solution:

Step 1: Understand xTaskNotifyWait parameters
Clear bits mask clears bits before waiting; wait bits mask specifies bits to wait for.
Step 2: Analyze masks
Using the same mask for clear and wait means bits are cleared before checking, causing immediate return.
Final Answer:
Clear and wait bits masks are the same, causing immediate return -> Option A
Quick Check:
Clear bits mask should differ from wait bits mask [OK]

Quick Trick: Don't clear bits you are waiting for in xTaskNotifyWait [OK]

Common Mistakes:

Master "Task Notifications" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

More FreeRTOS Quizzes

What is wrong with this task notification wait call?