Task notification vs queue performance in FreeRTOS - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send a task notification to unblock the task.

FreeRTOS

xTaskNotifyGive([1]);

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

AxSemaphore

BxTaskNotify

CxQueueHandle

DxTaskHandle

Attempts:

3 left

💡 Hint

Common Mistakes

Using a queue handle instead of a task handle.

Confusing the notification function with queue send functions.

The function xTaskNotifyGive() requires the handle of the task to notify, which is xTaskHandle.

2fill in blank

medium

Complete the code to receive a notification and unblock the task.

FreeRTOS

ulTaskNotifyTake([1], portMAX_DELAY);

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

ApdTRUE

BpdFALSE

CpdFAIL

DpdPASS

Attempts:

3 left

💡 Hint

Common Mistakes

Passing pdFALSE which does not clear the notification value.

Using unrelated constants like pdPASS or pdFAIL.

The first parameter of ulTaskNotifyTake() is pdTRUE to clear the notification value on exit.

3fill in blank

hard

Fix the error in the queue send function to avoid blocking the task indefinitely.

FreeRTOS

xQueueSend([1], &item, 0);

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

AxQueue

BxTaskHandle

CxSemaphore

DxNotification

Attempts:

3 left

💡 Hint

Common Mistakes

Using a task handle instead of a queue handle.

Confusing notification handles with queue handles.

The first parameter of xQueueSend() must be a queue handle, here xQueue.

4fill in blank

hard

Fill both blanks to create a dictionary mapping task names to their notification counts, filtering tasks with counts greater than 5.

FreeRTOS

task_notifications = {task_name: [1] for task_name, count in tasks.items() if count [2] 5}

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

Acount

B>

C<

Dtask_name

Attempts:

3 left

💡 Hint

Common Mistakes

Using task names as values instead of counts.

Using the wrong comparison operator.

The dictionary comprehension maps task_name to count for counts greater than 5.

5fill in blank

hard

Fill all three blanks to create a dictionary of tasks with notification counts above zero, using uppercase task names as keys.

FreeRTOS

active_tasks = {{ [1]: [2] for [3], count in tasks.items() if count > 0 }}

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

Atask_name.upper()

Bcount

Ctask_name

Dcount > 0

Attempts:

3 left

💡 Hint

Common Mistakes

Using the condition inside the dictionary instead of the comprehension filter.

Mixing up keys and values.

The dictionary keys are uppercase task names, values are counts, iterating over task_name and count.

Practice

1. Which statement best describes the performance difference between FreeRTOS task notifications and queues?

easy

A. Task notifications and queues have the same performance.

B. Queues are faster and use less memory than task notifications.

C. Task notifications are faster and use less memory than queues.

D. Queues are only used for signaling, not data transfer.

Solution

1. Step 1: Understand task notifications

   Task notifications are designed as lightweight signals between tasks, using minimal resources.

2. Step 2: Compare with queues

   Queues provide more flexibility but require more memory and processing time, making them slower.

3. Final Answer:

   Task notifications are faster and use less memory than queues. -> Option C

4. Quick Check:

   Task notifications = faster, less memory [OK]

Hint: Task notifications are lightweight signals, queues hold data [OK]

Common Mistakes:

• Thinking queues are always faster
• Confusing signaling with data transfer
• Assuming task notifications can hold large data

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

easy

A. xTaskNotifyGive(taskHandle);

B. xQueueSend(queueHandle, &data, portMAX_DELAY);

C. xTaskNotifySend(taskHandle, 0);

D. xQueueReceive(queueHandle, &data, 0);

Solution

1. Step 1: Identify task notification sending functions

   The function xTaskNotifyGive() is used to send a notification to a task.

2. Step 2: Differentiate from queue functions

   xQueueSend() and xQueueReceive() are queue operations, not task notifications.

3. Final Answer:

   xTaskNotifyGive(taskHandle); -> Option A

4. Quick Check:

   Send notification = xTaskNotifyGive() [OK]

Hint: Use xTaskNotifyGive() to send notifications, not queue functions [OK]

Common Mistakes:

• Using queue functions to send notifications
• Confusing xTaskNotifySend with xTaskNotifyGive
• Incorrect parameters in notification functions

3. Consider the following code snippet in FreeRTOS:

uint32_t value = 0;
if (xTaskNotifyWait(0x00, 0xFFFFFFFF, &value, 0) == pdTRUE) {
    // Notification received
    process(value);
} else {
    // No notification
    process(0);
}

What will happen if a task notification with value 5 was sent before this check?

medium

A. process(0) will be called because timeout is zero.

B. process(5) will be called because notification value is received.

C. The code will block until a notification arrives.

D. An error occurs because value is not initialized.

Solution

1. Step 1: Understand xTaskNotifyWait behavior

   This function checks for a notification and retrieves its value if available, returning pdTRUE.

2. Step 2: Analyze the timeout and notification value

   Since a notification with value 5 was sent before, the function returns immediately with pdTRUE and sets value to 5.

3. Final Answer:

   process(5) will be called because notification value is received. -> Option B

4. Quick Check:

   Notification received = process(value) [OK]

Hint: If notification sent, xTaskNotifyWait returns true immediately [OK]

Common Mistakes:

• Assuming zero timeout causes blocking
• Ignoring the notification value received
• Thinking uninitialized value causes error

4. Given this FreeRTOS code snippet, what is the main issue?

uint32_t notifyValue;
if (xTaskNotifyWait(0, 0xFFFFFFFF, ¬ifyValue, portMAX_DELAY) == pdTRUE) {
    // Process notification
    process(notifyValue);
}
// Later
xQueueSend(queueHandle, &data, 0);

medium

A. xQueueSend is called without checking if the queue is full.

B. xTaskNotifyWait cannot be used with queues.

C. notifyValue is not initialized before use.

D. Using portMAX_DELAY in xTaskNotifyWait can cause indefinite blocking.

Solution

1. Step 1: Analyze xTaskNotifyWait usage

   Using portMAX_DELAY causes the task to block indefinitely until a notification arrives.

2. Step 2: Consider implications

   This indefinite block can cause deadlocks if notifications are not sent, which is a common issue.

3. Final Answer:

   Using portMAX_DELAY in xTaskNotifyWait can cause indefinite blocking. -> Option D

4. Quick Check:

   portMAX_DELAY = indefinite block risk [OK]

Hint: portMAX_DELAY blocks forever; use timeout carefully [OK]

Common Mistakes:

• Ignoring blocking behavior of portMAX_DELAY
• Assuming notifyValue must be initialized
• Confusing queue and notification usage

5. You need to send multiple integer values from one task to another in FreeRTOS with minimal delay. Which approach is best for performance and why?

hard

A. Use task notifications only for signaling and queues for data transfer.

B. Use a queue to send each integer separately, ensuring order and data integrity.

C. Use global variables protected by mutexes to share data.

D. Use task notifications with bitwise encoding to send multiple values quickly.

Solution

1. Step 1: Understand task notifications limitations

   Task notifications are fast but designed for simple signals or small data (like a single 32-bit value).

2. Step 2: Consider queues for multiple data items

   Queues can hold multiple messages and maintain order, suitable for sending multiple integers reliably.

3. Step 3: Choose best practice

   Use task notifications for signaling and queues for actual data transfer to balance performance and correctness.

4. Final Answer:

   Use task notifications only for signaling and queues for data transfer. -> Option A

5. Quick Check:

   Notifications = signals, queues = data [OK]

Hint: Notifications signal; queues transfer multiple data items [OK]

Common Mistakes:

• Trying to encode multiple values in notifications
• Ignoring data integrity with global variables
• Assuming notifications can replace queues for data