Deferred interrupt processing pattern in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main idea behind the Deferred Interrupt Processing Pattern?

It means handling only the quick, urgent part of an interrupt in the interrupt service routine (ISR) and postponing the longer, complex work to a safer time outside the ISR.

beginner

Why should long tasks be deferred from the ISR in FreeRTOS?

Because ISRs should be short to avoid blocking other interrupts and keep the system responsive. Deferring long tasks prevents delays and priority inversion.

intermediate

Name two common methods to defer interrupt processing in FreeRTOS.

1. Using a task notification or semaphore to signal a task from the ISR.
2. Using a queue to send data from the ISR to a task for processing.

intermediate

What is the role of a 'bottom half' in the Deferred Interrupt Processing Pattern?

The 'bottom half' is the part of the interrupt handling done outside the ISR, usually in a task, where the heavy or slow processing happens safely.

intermediate

How does using a queue in deferred interrupt processing improve system design?

It safely passes data from the ISR to a task without blocking, allowing the ISR to finish quickly and the task to process data when ready.

What should an ISR do in the Deferred Interrupt Processing Pattern?

A Complete all processing before exiting

B Perform only quick, essential work and defer the rest

C Wait for other tasks to finish

D Disable all interrupts permanently

ISRs should be short and defer longer work to keep the system responsive.

Which FreeRTOS feature is commonly used to signal a task from an ISR?

A Mutex lock

B Timer callback

C Memory allocation

D Task notification

Task notifications are lightweight and efficient for signaling tasks from ISRs.

Why is it bad to do long processing inside an ISR?

A It increases memory usage

B It saves CPU time

C It can block other interrupts and reduce system responsiveness

D It improves multitasking

Long ISRs delay other interrupts and can cause missed events.

What is a common data structure used to pass information from ISR to task in FreeRTOS?

A Queue

B Linked list

C Stack

D Array

Queues safely transfer data between ISRs and tasks without blocking.

In the deferred interrupt pattern, where does the 'bottom half' run?

A In a FreeRTOS task

B Inside the ISR

C In hardware

D In the bootloader

The bottom half runs in a task context to handle longer processing safely.

Explain the Deferred Interrupt Processing Pattern and why it is important in FreeRTOS.

Think about how to keep interrupts fast and system smooth.

Describe two ways to defer work from an ISR to a task in FreeRTOS.

Focus on FreeRTOS synchronization tools.

Practice

1. What is the main purpose of the deferred interrupt processing pattern in FreeRTOS?

easy

A. To move heavy processing from the ISR to a task for better system responsiveness

B. To execute all interrupt code inside the ISR for faster response

C. To disable all interrupts during task execution

D. To avoid using semaphores or queues in interrupt handling

Solution

1. Step 1: Understand ISR limitations

   Interrupt Service Routines (ISRs) should be short to keep system responsive.

2. Step 2: Role of deferred processing

   Heavy or time-consuming work is moved to a task, triggered by ISR using semaphores or queues.

3. Final Answer:

   To move heavy processing from the ISR to a task for better system responsiveness -> Option A

4. Quick Check:

   Deferred processing = move work out of ISR [OK]

Hint: Heavy work belongs in tasks, not ISRs [OK]

Common Mistakes:

• Thinking all work should be done inside ISR
• Believing interrupts should be disabled during tasks
• Ignoring use of semaphores or queues

2. Which of the following is the correct way to notify a task from an ISR in FreeRTOS?

easy

A. vTaskDelay()

B. xSemaphoreGive()

C. xSemaphoreGiveFromISR()

D. xQueueSend()

Solution

1. Step 1: Identify ISR-safe functions

   Functions called from ISRs must be ISR-safe variants, like xSemaphoreGiveFromISR().

2. Step 2: Compare options

   xSemaphoreGive() is for tasks, not ISRs; vTaskDelay() is a task delay; xQueueSend() is not ISR-safe.

3. Final Answer:

   xSemaphoreGiveFromISR() -> Option C

4. Quick Check:

   Use FromISR functions inside ISRs [OK]

Hint: Use FromISR suffix functions inside ISRs [OK]

Common Mistakes:

• Using task-only functions inside ISR
• Calling blocking functions in ISR
• Not using FromISR variants

3. Consider this snippet inside an ISR in FreeRTOS:

BaseType_t xHigherPriorityTaskWoken = pdFALSE;
xSemaphoreGiveFromISR(xSemaphore, &xHigherPriorityTaskWoken);
portYIELD_FROM_ISR(xHigherPriorityTaskWoken);

What is the purpose of portYIELD_FROM_ISR() here?

medium

A. To reset the semaphore count

B. To request a context switch if a higher priority task was woken

C. To delay the ISR until the task runs

D. To disable interrupts after giving the semaphore

Solution

1. Step 1: Understand xHigherPriorityTaskWoken

   This flag indicates if giving the semaphore woke a higher priority task.

2. Step 2: Role of portYIELD_FROM_ISR()

   If the flag is true, portYIELD_FROM_ISR() requests a context switch to run the higher priority task immediately.

3. Final Answer:

   To request a context switch if a higher priority task was woken -> Option B

4. Quick Check:

   portYIELD_FROM_ISR triggers context switch [OK]

Hint: portYIELD_FROM_ISR triggers immediate task switch [OK]

Common Mistakes:

• Thinking it disables interrupts
• Assuming it delays ISR execution
• Confusing it with semaphore reset

4. You wrote this ISR code to notify a task:

void ISR_Handler(void) {
    xSemaphoreGive(xSemaphore);
}

Why might this cause problems in FreeRTOS?

medium

A. xSemaphoreGive() is not safe to call from an ISR

B. The semaphore is given twice accidentally

C. The ISR does not clear the interrupt flag

D. The task will never unblock

Solution

1. Step 1: Check function usage in ISR

   xSemaphoreGive() is a task-level function and is not safe to call inside an ISR.

2. Step 2: Correct function to use

   Inside ISR, xSemaphoreGiveFromISR() must be used to safely notify the task.

3. Final Answer:

   xSemaphoreGive() is not safe to call from an ISR -> Option A

4. Quick Check:

   Use FromISR functions in ISRs [OK]

Hint: Never call task functions inside ISR, use FromISR versions [OK]

Common Mistakes:

• Calling task functions inside ISR
• Forgetting to clear interrupt flags
• Assuming semaphore gives always unblock tasks

5. You want to implement deferred interrupt processing where an ISR signals a task to process sensor data. Which sequence correctly follows FreeRTOS best practices?

hard

A. Task polls sensor data continuously, ISR disables interrupts

B. ISR processes sensor data directly, then calls vTaskDelay()

C. ISR sends data via xQueueSend(), task never blocks

D. ISR calls xSemaphoreGiveFromISR(), then task waits on semaphore and processes data

Solution

1. Step 1: ISR role in deferred processing

   ISR should be short and only notify the task using xSemaphoreGiveFromISR().

2. Step 2: Task role in processing

   The task waits on the semaphore and processes sensor data when notified.

3. Final Answer:

   ISR calls xSemaphoreGiveFromISR(), then task waits on semaphore and processes data -> Option D

4. Quick Check:

   ISR signals, task processes data [OK]

Hint: ISR signals; task does heavy work [OK]

Common Mistakes:

• Doing heavy work inside ISR
• Using blocking calls inside ISR
• Not synchronizing task and ISR properly