ISR-to-task notification pattern in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the ISR-to-task notification pattern in FreeRTOS?

It is a way for an Interrupt Service Routine (ISR) to send a signal or notification to a task, letting the task know that an event has happened and it can now run or process data.

intermediate

Why use task notifications instead of queues or semaphores for ISR-to-task communication?

Task notifications are faster and use less memory because they are built into the task control block. They avoid the overhead of queues or semaphores, making them ideal for quick ISR-to-task signaling.

beginner

Which FreeRTOS API function is used inside an ISR to notify a task?

xTaskNotifyFromISR() is used inside an ISR to send a notification to a task safely without blocking.

intermediate

What parameter in xTaskNotifyFromISR() helps decide if a context switch should happen immediately?

The parameter 'pxHigherPriorityTaskWoken' is a pointer to a variable that FreeRTOS sets to pdTRUE if a higher priority task was woken by the notification. This lets the ISR request a context switch right after it finishes.

beginner

How does a task wait for a notification from an ISR?

The task calls ulTaskNotifyTake() or xTaskNotifyWait(), which blocks the task until the notification arrives, allowing the task to sleep efficiently until needed.

Which function is used inside an ISR to notify a task in FreeRTOS?

A xTaskNotifyFromISR()

B xQueueSend()

C vTaskDelay()

D xSemaphoreGive()

xTaskNotifyFromISR() is specifically designed for sending notifications from an ISR to a task.

What does the 'pxHigherPriorityTaskWoken' parameter do in xTaskNotifyFromISR()?

A Specifies the task to notify

B Indicates if a higher priority task was woken and a context switch is needed

C Sets the notification value

D Blocks the ISR until the task responds

It tells the kernel if a context switch should happen immediately after the ISR.

Why are task notifications preferred over queues for ISR-to-task signaling?

A They are slower but more reliable

B They can only be used in tasks, not ISRs

C They use less memory and are faster

D They require more CPU time

Task notifications are lightweight and fast, making them ideal for ISR-to-task communication.

Which function does a task call to wait for a notification from an ISR?

A xTaskNotifyFromISR()

B xQueueReceive()

C vTaskDelay()

D ulTaskNotifyTake()

ulTaskNotifyTake() blocks the task until a notification is received.

What happens if a task notification is sent but the task is not waiting?

A The notification is stored until the task waits

B The system crashes

C The notification is lost

D The ISR blocks until the task is ready

Task notifications are stored in the task's notification value until the task reads them.

Explain how an ISR can notify a task using the ISR-to-task notification pattern in FreeRTOS.

Think about how the ISR signals and how the task waits.

Describe the advantages of using task notifications for ISR-to-task communication compared to other methods like queues or semaphores.

Focus on speed and resource use.

Practice

1. What is the main purpose of the ISR-to-task notification pattern in FreeRTOS?

easy

A. To allow an interrupt to quickly notify a task to run

B. To create a new task from an ISR

C. To pause a task until an interrupt finishes

D. To disable interrupts during task execution

Solution

1. Step 1: Understand ISR and task roles

   ISRs handle hardware events quickly, tasks do longer processing.

2. Step 2: Identify notification purpose

   The pattern lets ISR tell a task to run without delay.

3. Final Answer:

   To allow an interrupt to quickly notify a task to run -> Option A

4. Quick Check:

   ISR notifies task [OK]

Hint: ISR signals task to run fast using notifications [OK]

Common Mistakes:

• Thinking ISR creates tasks
• Believing tasks pause interrupts
• Confusing disabling interrupts with notifications

2. Which function is correctly used inside an ISR to notify a task in FreeRTOS?

easy

A. vTaskNotifyGiveFromISR()

B. ulTaskNotifyTake()

C. xTaskCreate()

D. vTaskDelay()

Solution

1. Step 1: Identify ISR notification function

   Inside ISR, use vTaskNotifyGiveFromISR() to notify tasks.

2. Step 2: Differentiate task functions

   ulTaskNotifyTake() is used in tasks, not ISRs.

3. Final Answer:

   vTaskNotifyGiveFromISR() -> Option A

4. Quick Check:

   Notify from ISR = vTaskNotifyGiveFromISR() [OK]

Hint: Use vTaskNotifyGiveFromISR() inside ISR only [OK]

Common Mistakes:

• Using ulTaskNotifyTake() inside ISR
• Calling xTaskCreate() in ISR
• Using vTaskDelay() inside ISR

3. Given this code snippet, what will be the output printed by the task?

void ISR_Handler() {
    BaseType_t xHigherPriorityTaskWoken = pdFALSE;
    vTaskNotifyGiveFromISR(taskHandle, &xHigherPriorityTaskWoken);
    portYIELD_FROM_ISR(xHigherPriorityTaskWoken);
}

void TaskFunction(void *pvParameters) {
    for(;;) {
        ulTaskNotifyTake(pdTRUE, portMAX_DELAY);
        printf("Task notified!\n");
    }
}

medium

A. No output, task never notified

B. Task notified! (printed each time ISR runs)

C. Compilation error due to missing parameters

D. Task notified! printed once then stops

Solution

1. Step 1: Analyze ISR notification call

   ISR calls vTaskNotifyGiveFromISR() to notify the task each time it runs.

2. Step 2: Check task notification wait

   Task waits indefinitely with ulTaskNotifyTake(), then prints on notification.

3. Final Answer:

   Task notified! (printed each time ISR runs) -> Option B

4. Quick Check:

   ISR notifies task -> prints each time [OK]

Hint: Task prints after each ISR notification [OK]

Common Mistakes:

• Assuming task never wakes
• Confusing function parameters
• Thinking output prints only once

4. Identify the error in this ISR-to-task notification code snippet:

void ISR_Handler() {
    vTaskNotifyGive(taskHandle);
}

void TaskFunction(void *pvParameters) {
    ulTaskNotifyTake(pdTRUE, portMAX_DELAY);
    printf("Notified\n");
}

medium

A. printf() cannot be used in tasks

B. Missing infinite loop in TaskFunction

C. Incorrect parameter in ulTaskNotifyTake()

D. Using vTaskNotifyGive() inside ISR instead of vTaskNotifyGiveFromISR()

Solution

1. Step 1: Check ISR notification function

   vTaskNotifyGive() is not safe inside ISR; must use vTaskNotifyGiveFromISR().

2. Step 2: Verify task code correctness

   TaskFunction can have single call; infinite loop is common but not error here.

3. Final Answer:

   Using vTaskNotifyGive() inside ISR instead of vTaskNotifyGiveFromISR() -> Option D

4. Quick Check:

   ISR notification function must end with FromISR [OK]

Hint: Use FromISR suffix functions inside ISRs [OK]

Common Mistakes:

• Calling task functions inside ISR
• Ignoring FromISR suffix importance
• Assuming printf() is disallowed in tasks

5. You want to notify a task from multiple ISRs using ISR-to-task notifications. Which approach ensures the task processes all notifications without missing any?

hard

A. Use vTaskNotifyGiveFromISR() once and ulTaskNotifyTake() once; task processes only one notification

B. Use xTaskNotifyGive() in ISRs and ulTaskNotifyTake() in task with zero timeout

C. Use ulTaskNotifyTake() with clear count and call vTaskNotifyGiveFromISR() in each ISR; task loops to process all notifications

D. Use a global variable incremented in ISRs and checked in task without notifications

Solution

1. Step 1: Understand multiple ISR notifications

   Each ISR calls vTaskNotifyGiveFromISR() to increment notification count.

2. Step 2: Task processes all notifications

   Task uses ulTaskNotifyTake(pdTRUE, portMAX_DELAY) in a loop to clear all counts and process each notification.

3. Final Answer:

   Use ulTaskNotifyTake() with clear count and call vTaskNotifyGiveFromISR() in each ISR; task loops to process all notifications -> Option C

4. Quick Check:

   Multiple ISR notifications require counting and looping [OK]

Hint: Loop ulTaskNotifyTake() to handle multiple ISR signals [OK]

Common Mistakes:

• Assuming one notification covers all ISR events
• Using non-FromISR functions in ISR
• Ignoring notification count clearing