Why task notifications are lightweight in FreeRTOS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send a task notification in FreeRTOS.

FreeRTOS

xTaskNotifyGive([1]);

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

AxTaskToNotify

BxTaskHandle

CxQueueHandle

DxSemaphore

Attempts:

3 left

💡 Hint

Common Mistakes

Using a queue or semaphore handle instead of a task handle.

Confusing the task handle variable name.

The function xTaskNotifyGive() sends a notification to the specified task handle, which is xTaskToNotify here.

2fill in blank

medium

Complete the code to wait for a task notification with a timeout.

FreeRTOS

ulTaskNotifyTake([1], pdMS_TO_TICKS(1000));

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

ApdPASS

BpdTRUE

CportMAX_DELAY

DpdFALSE

Attempts:

3 left

💡 Hint

Common Mistakes

Using pdFALSE which does not clear the notification value.

Confusing the parameter with timeout values.

The first parameter pdTRUE clears the notification value on exit, which is common when waiting for a notification.

3fill in blank

hard

Fix the error in the code to send a notification with a value.

FreeRTOS

xTaskNotify([1], 0x01, eSetBits);

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

AxTaskToNotify

BxTaskHandle

CNULL

DxQueueHandle

Attempts:

3 left

💡 Hint

Common Mistakes

Passing NULL or queue handle instead of task handle.

Using an undefined variable name.

The first argument must be the task handle to notify, which is xTaskToNotify.

4fill in blank

hard

Fill both blanks to create a task notification value and check if a bit is set.

FreeRTOS

uint32_t notifValue = [1];
if (notifValue [2] 0x01) {
    // Bit 0 is set
}

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

AulTaskNotifyValueClear(NULL, 0x01)

B&

D|

Attempts:

3 left

💡 Hint

Common Mistakes

Using bitwise OR instead of AND for checking bits.

Not clearing notification bits properly.

The function ulTaskNotifyValueClear() reads and clears bits, and the bitwise AND operator & checks if bit 0 is set.

5fill in blank

hard

Fill all three blanks to send a notification, wait for it, and clear the value.

FreeRTOS

xTaskNotify([1], 0x02, eSetBits);
uint32_t value = ulTaskNotifyTake([2], portMAX_DELAY);
value = ulTaskNotifyValueClear([3], 0x02);

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

AxTaskToNotify

BpdTRUE

DpdFALSE

Attempts:

3 left

💡 Hint

Common Mistakes

Using different task handles for send and clear.

Using pdFALSE which does not clear notification value.

Use the task handle xTaskToNotify to send and clear notifications, and pdTRUE to clear the notification value when waiting.

Practice

1. Why are task notifications considered lightweight in FreeRTOS?

easy

A. Because they require complex synchronization mechanisms

B. Because they use minimal CPU and memory resources

C. Because they can send large amounts of data quickly

D. Because they use separate hardware interrupts

Solution

1. Step 1: Understand task notification purpose

   Task notifications are designed to send simple signals or flags between tasks.

2. Step 2: Analyze resource usage

   They avoid heavy data copying and complex synchronization, using minimal CPU and memory.

3. Final Answer:

   Because they use minimal CPU and memory resources -> Option B

4. Quick Check:

   Lightweight means low resource use = C [OK]

Hint: Lightweight means less CPU and memory use [OK]

Common Mistakes:

• Thinking task notifications handle large data
• Confusing with hardware interrupts
• Assuming complex synchronization is needed

2. Which of the following is the correct way to send a task notification in FreeRTOS?

easy

A. xTaskNotify(taskHandle, value, eSetBits);

B. xTaskNotifySend(taskHandle, value);

C. xTaskNotifyReceive(taskHandle, &value);

D. xTaskNotifyGive(taskHandle);

Solution

1. Step 1: Recall FreeRTOS notification API

   The function xTaskNotify() sends a notification with a value and action.

2. Step 2: Identify correct syntax

   xTaskNotify(taskHandle, value, eSetBits); is the correct call to send a notification with bits set.

3. Final Answer:

   xTaskNotify(taskHandle, value, eSetBits); -> Option A

4. Quick Check:

   Sending notification uses xTaskNotify with action [OK]

Hint: Use xTaskNotify with handle, value, and action [OK]

Common Mistakes:

• Using xTaskNotifyGive without parameters
• Confusing send and receive functions
• Using non-existent functions like xTaskNotifySend

3. Consider this code snippet in FreeRTOS:

BaseType_t xHigherPriorityTaskWoken = pdFALSE;
xTaskNotifyFromISR(taskHandle, 0x01, eSetBits, &xHigherPriorityTaskWoken);
if(xHigherPriorityTaskWoken) {
    portYIELD_FROM_ISR();
}

What is the main reason this notification method is lightweight?

medium

A. It uses direct-to-task notification without queues

B. It copies large data buffers efficiently

C. It disables all interrupts during notification

D. It creates a new task for each notification

Solution

1. Step 1: Analyze notification method in ISR

   The function xTaskNotifyFromISR() sends a notification directly to a task without using queues.

2. Step 2: Understand why this is lightweight

   Direct notification avoids overhead of queue management and data copying, making it fast and low resource.

3. Final Answer:

   It uses direct-to-task notification without queues -> Option A

4. Quick Check:

   Direct notification avoids queues = A [OK]

Hint: Direct notification avoids queues, making it lightweight [OK]

Common Mistakes:

• Thinking it copies large data buffers
• Assuming interrupts are disabled fully
• Believing it creates new tasks

4. You wrote this code to notify a task:

void notifyTask() {
    xTaskNotify(taskHandle, 0x01, eSetValueWithOverwrite);
}

But the task never receives the notification. What is the likely problem?

medium

A. Notifications require queues to work

B. eSetValueWithOverwrite is not a valid action

C. The taskHandle is NULL or invalid

D. You must call xTaskNotifyGive instead

Solution

1. Step 1: Check task handle validity

   If taskHandle is NULL or invalid, notification cannot be delivered.

2. Step 2: Verify notification action and function

   eSetValueWithOverwrite is valid, and xTaskNotify is correct for sending notifications.

3. Final Answer:

   The taskHandle is NULL or invalid -> Option C

4. Quick Check:

   Invalid task handle blocks notification = A [OK]

Hint: Check taskHandle is valid before notifying [OK]

Common Mistakes:

• Using wrong notification action
• Assuming queues are needed for notifications
• Confusing xTaskNotifyGive with xTaskNotify

5. You want to use task notifications to signal multiple events to a task without using queues. Which approach best keeps notifications lightweight and efficient?

hard

A. Send multiple notifications with eSetValueWithOverwrite to store last event only

B. Use global variables and disable interrupts to signal events

C. Create a queue to hold all event data and notify task on queue change

D. Use a single notification value with bitwise flags and eSetBits action

Solution

1. Step 1: Understand notification capabilities

   Task notifications can hold a 32-bit value, ideal for bitwise flags representing multiple events.

2. Step 2: Choose efficient notification method

   Using eSetBits action sets bits without overwriting, allowing multiple event flags in one notification.

3. Final Answer:

   Use a single notification value with bitwise flags and eSetBits action -> Option D

4. Quick Check:

   Bitwise flags + eSetBits = efficient lightweight signaling [OK]

Hint: Use bit flags with eSetBits for multiple events [OK]

Common Mistakes:

• Overwriting notification value losing events
• Using queues which add overhead
• Using global variables risking race conditions