xTaskNotifyGive() as lightweight semaphore in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is xTaskNotifyGive() used for in FreeRTOS?

xTaskNotifyGive() is used to send a notification to a task, often acting like a lightweight semaphore to unblock the task.

beginner

How does ulTaskNotifyTake() relate to xTaskNotifyGive()?

ulTaskNotifyTake() is used by a task to wait (block) until it receives a notification from xTaskNotifyGive(), similar to taking a semaphore.

intermediate

Why is xTaskNotifyGive() considered a lightweight semaphore?

Because it uses task notifications which are faster and use less memory than traditional semaphores in FreeRTOS.

intermediate

What happens if xTaskNotifyGive() is called multiple times before ulTaskNotifyTake() is called?

The notification count increments, allowing ulTaskNotifyTake() to return immediately multiple times, similar to counting semaphore behavior.

intermediate

Can xTaskNotifyGive() be used between tasks and interrupts?

Yes, but from an interrupt, you should use xTaskNotifyGiveFromISR() instead to safely notify a task.

What does xTaskNotifyGive() do in FreeRTOS?

A Creates a new task

B Sends a notification to unblock a task

C Deletes a semaphore

D Suspends a task

xTaskNotifyGive() sends a notification to a task, often used to unblock it like a semaphore.

Which function should a task call to wait for a notification given by xTaskNotifyGive()?

A ulTaskNotifyTake()

B vTaskDelay()

C xSemaphoreTake()

D xTaskNotifyWait()

ulTaskNotifyTake() blocks the task until it receives a notification from xTaskNotifyGive().

Why might you choose xTaskNotifyGive() over a traditional semaphore?

A It is lightweight and faster

B It is slower

C It requires more CPU cycles

D It uses more memory

xTaskNotifyGive() is lightweight and faster than traditional semaphores.

What happens if xTaskNotifyGive() is called twice before the task calls ulTaskNotifyTake() once?

A The notification count is 1

B The task is deleted

C The notification is lost

D The notification count is 2

Each call to xTaskNotifyGive() increments the notification count, so two calls mean count is 2.

Which function should be used to notify a task from an interrupt?

A ulTaskNotifyTake()

B xTaskNotifyGive()

C xTaskNotifyGiveFromISR()

D vTaskDelay()

xTaskNotifyGiveFromISR() is designed to safely notify a task from an interrupt context.

Explain how xTaskNotifyGive() and ulTaskNotifyTake() work together as a lightweight semaphore in FreeRTOS.

Think about how one task signals another to continue.

Describe the advantages of using task notifications as lightweight semaphores compared to traditional semaphores in FreeRTOS.

Consider performance and resource use.

Practice

1. What is the primary purpose of xTaskNotifyGive() in FreeRTOS?

easy

A. To send a simple signal from one task to another as a lightweight semaphore

B. To create a new task in the system

C. To delete a task permanently

D. To allocate memory dynamically

Solution

1. Step 1: Understand the function role

   xTaskNotifyGive() is designed to send a notification signal from one task to another.

2. Step 2: Compare with other options

   Creating or deleting tasks and memory allocation are unrelated to xTaskNotifyGive().

3. Final Answer:

   To send a simple signal from one task to another as a lightweight semaphore -> Option A

4. Quick Check:

   Signal sending = To send a simple signal from one task to another as a lightweight semaphore [OK]

Hint: Remember: xTaskNotifyGive() signals tasks like a lightweight semaphore [OK]

Common Mistakes:

• Confusing it with task creation or deletion functions
• Thinking it manages memory
• Assuming it blocks tasks directly

2. Which of the following is the correct syntax to send a notification using xTaskNotifyGive() to a task handle named xTaskHandle?

easy

A. xTaskNotifyGive(xTaskHandle, 1);

B. xTaskNotifyGive(&xTaskHandle);

C. xTaskNotifyGive(xTaskHandle);

D. xTaskNotifyGive();

Solution

1. Step 1: Recall function signature

   xTaskNotifyGive() takes a task handle as a parameter, not a pointer or extra arguments.

2. Step 2: Check each option

   xTaskNotifyGive(xTaskHandle); correctly passes the task handle. xTaskNotifyGive(&xTaskHandle); passes address (wrong), C adds an extra argument (wrong), D has no argument (wrong).

3. Final Answer:

   xTaskNotifyGive(xTaskHandle); -> Option C

4. Quick Check:

   Correct syntax = xTaskNotifyGive(xTaskHandle); [OK]

Hint: Pass the task handle directly without extra arguments [OK]

Common Mistakes:

• Passing pointer to task handle instead of handle itself
• Adding extra parameters
• Calling without any argument

3. Consider the following code snippet:

void Task1(void *pvParameters) {
    // Wait for notification
    ulTaskNotifyTake(pdTRUE, portMAX_DELAY);
    // Continue after notification
    printf("Task1 resumed\n");
}

void Task2(void *pvParameters) {
    // Notify Task1
    xTaskNotifyGive(Task1Handle);
}

What will be printed when Task2 calls xTaskNotifyGive()?

medium

A. Task2 resumes instead of Task1

B. Task1 resumed

C. Syntax error at compile time

D. No output, Task1 blocks forever

Solution

1. Step 1: Understand notification flow

   Task1 waits for a notification with ulTaskNotifyTake(). When Task2 calls xTaskNotifyGive(), it sends the notification.

2. Step 2: Effect of notification

   The notification unblocks Task1, so it prints "Task1 resumed".

3. Final Answer:

   Task1 resumed -> Option B

4. Quick Check:

   Notification received = Task1 prints [OK]

Hint: xTaskNotifyGive() wakes waiting task to continue [OK]

Common Mistakes:

• Assuming Task1 never resumes
• Confusing which task prints output
• Thinking code causes compile error

4. Identify the error in this code snippet using xTaskNotifyGive():

void TaskA(void *pvParameters) {
    ulTaskNotifyTake(pdFALSE, portMAX_DELAY);
    printf("TaskA running\n");
}

void TaskB(void *pvParameters) {
    xTaskNotifyGive(&TaskAHandle);
}

medium

A. Passing address of task handle instead of task handle to xTaskNotifyGive()

B. Using pdFALSE in ulTaskNotifyTake() causes immediate return

C. Missing delay in TaskB before notify

D. printf statement is incorrect syntax

Solution

1. Step 1: Check parameter passed to xTaskNotifyGive()

   The function expects a task handle, but &TaskAHandle passes its address, which is incorrect.

2. Step 2: Validate other parts

   Using pdFALSE is valid to clear notification count, no syntax error in printf, and delay is optional.

3. Final Answer:

   Passing address of task handle instead of task handle to xTaskNotifyGive() -> Option A

4. Quick Check:

   Correct parameter type needed = Passing address of task handle instead of task handle to xTaskNotifyGive() [OK]

Hint: Pass task handle directly, not its address [OK]

Common Mistakes:

• Passing pointer to handle instead of handle
• Misunderstanding pdFALSE effect
• Assuming printf syntax error

5. You want to use xTaskNotifyGive() as a lightweight semaphore to synchronize two tasks: Producer and Consumer. The Consumer waits for the notification before processing data. Which sequence correctly implements this synchronization?

hard

A. Producer calls ulTaskNotifyTake(pdTRUE, portMAX_DELAY);, Consumer calls xTaskNotifyGive(ProducerHandle);

B. Consumer calls xTaskNotifyGive() and Producer calls ulTaskNotifyTake()

C. Both tasks call xTaskNotifyGive() simultaneously without waiting

D. Consumer calls ulTaskNotifyTake(pdTRUE, portMAX_DELAY); to wait, Producer calls xTaskNotifyGive(ConsumerHandle); to signal

Solution

1. Step 1: Identify roles of tasks

   The Consumer should wait for a signal before processing, so it uses ulTaskNotifyTake() to block until notified.

2. Step 2: Producer signals Consumer

   The Producer sends the notification using xTaskNotifyGive() with the Consumer's task handle.

3. Final Answer:

   Consumer calls ulTaskNotifyTake(pdTRUE, portMAX_DELAY); to wait, Producer calls xTaskNotifyGive(ConsumerHandle); to signal -> Option D

4. Quick Check:

   Wait then signal = Consumer calls ulTaskNotifyTake(pdTRUE, portMAX_DELAY); to wait, Producer calls xTaskNotifyGive(ConsumerHandle); to signal [OK]

Hint: Consumer waits, Producer signals with xTaskNotifyGive() [OK]

Common Mistakes:

• Reversing roles of Producer and Consumer
• Both tasks signaling without waiting
• Using wrong task handles in calls