Why task notifications are lightweight in FreeRTOS

Introduction

Task notifications let tasks send simple messages quickly without using extra memory. They are fast and use little CPU power.

When a task needs to quickly tell another task that an event happened.

When you want to avoid using bigger communication tools like queues or semaphores.

When you want to save memory in small embedded systems.

When you want to keep your program responsive by reducing waiting time.

When you want simple signaling between tasks without complex data.

Syntax

FreeRTOS

BaseType_t xTaskNotify(
    TaskHandle_t xTaskToNotify,
    uint32_t ulValue,
    eNotifyAction eAction
);

xTaskToNotify is the task you want to notify.

ulValue is the number or flag you send with the notification.

Examples

Send a notification without changing the value.

FreeRTOS

xTaskNotify(taskHandle, 0, eNoAction);

Set bit 1 in the notification value to signal an event.

FreeRTOS

xTaskNotify(taskHandle, 2, eSetBits);

Overwrite the notification value with 5.

FreeRTOS

xTaskNotify(taskHandle, 5, eSetValueWithOverwrite);

Sample Program

This program creates two tasks. Task1 sends a notification with value 42 to Task2. Task2 waits for the notification and prints the value it received.

FreeRTOS

#include "FreeRTOS.h"
#include "task.h"
#include <stdio.h>

TaskHandle_t Task1Handle = NULL;
TaskHandle_t Task2Handle = NULL;

void Task1(void *pvParameters) {
    printf("Task1: Sending notification to Task2\n");
    xTaskNotify(Task2Handle, 42, eSetValueWithOverwrite);
    vTaskDelete(NULL);
}

void Task2(void *pvParameters) {
    uint32_t ulNotificationValue = 0;
    xTaskNotifyWait(0x00, 0xFFFFFFFF, &ulNotificationValue, portMAX_DELAY);
    printf("Task2: Received notification with value %lu\n", ulNotificationValue);
    vTaskDelete(NULL);
}

int main(void) {
    xTaskCreate(Task2, "Task2", 1000, NULL, 1, &Task2Handle);
    xTaskCreate(Task1, "Task1", 1000, NULL, 1, &Task1Handle);
    vTaskStartScheduler();
    return 0;
}

Important Notes

Task notifications use the task's own memory, so no extra memory is needed.

They are faster than queues because they avoid copying data.

Only one notification value is stored per task, so they are best for simple signals.

Summary

Task notifications are a quick way for tasks to send simple signals.

They use less memory and CPU than other communication methods.

Best for small messages or flags, not for large data.

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