FreeRTOS interrupt priority restrictions - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main reason FreeRTOS restricts interrupt priorities?

FreeRTOS restricts interrupt priorities to ensure that critical kernel operations are not interrupted by higher priority interrupts, which could cause data corruption or unpredictable behavior.

intermediate

What is the maximum interrupt priority that can safely call FreeRTOS API functions?

Only interrupts with priority equal to or numerically equal to or higher than configMAX_SYSCALL_INTERRUPT_PRIORITY can safely call FreeRTOS API functions that end with 'FromISR'.

intermediate

Why must interrupts with priority higher than configMAX_SYSCALL_INTERRUPT_PRIORITY avoid FreeRTOS API calls?

Because these higher priority interrupts can preempt the kernel, calling FreeRTOS API functions could cause race conditions or corrupt kernel data structures.

advanced

How does FreeRTOS define interrupt priority levels on Cortex-M microcontrollers?

FreeRTOS uses the NVIC priority scheme where lower numerical values mean higher priority. The configMAX_SYSCALL_INTERRUPT_PRIORITY sets a threshold numerically at or below which interrupts can safely use FreeRTOS API calls.

advanced

What could happen if an interrupt with too high priority calls FreeRTOS API functions?

It can cause kernel corruption, unpredictable system behavior, or crashes because the kernel is not designed to be safely interrupted at that priority level.

Which interrupt priority level can safely call FreeRTOS API functions?

A Any priority level

B Priority higher than configMAX_SYSCALL_INTERRUPT_PRIORITY

C Only the highest priority interrupts

D Priority equal or numerically equal to or higher than configMAX_SYSCALL_INTERRUPT_PRIORITY

Only interrupts with priority equal or numerically equal to or higher than configMAX_SYSCALL_INTERRUPT_PRIORITY can safely call FreeRTOS API functions.

What does configMAX_SYSCALL_INTERRUPT_PRIORITY represent?

A The number of interrupts supported

B The highest interrupt priority allowed to call FreeRTOS API

C The lowest interrupt priority in the system

D The maximum number of tasks

configMAX_SYSCALL_INTERRUPT_PRIORITY defines the highest interrupt priority that can safely call FreeRTOS API functions.

What happens if a high priority interrupt calls a FreeRTOS API function?

A The interrupt is ignored

B Nothing, it is safe

C Kernel data may become corrupted

D The system automatically lowers the interrupt priority

Calling FreeRTOS API functions from too high priority interrupts can corrupt kernel data.

In Cortex-M, which numerical priority value means higher priority?

A Lower numerical value

B Higher numerical value

C Zero always means lowest priority

D Priority is not numerical

In Cortex-M NVIC, lower numerical values represent higher interrupt priorities.

Why does FreeRTOS restrict interrupt priorities for API calls?

A To prevent kernel corruption and ensure system stability

B To allow all interrupts to run freely

C To increase interrupt speed

D To disable interrupts during API calls

Restricting interrupt priorities prevents kernel corruption and keeps the system stable.

Explain why FreeRTOS restricts which interrupt priorities can call its API functions.

Think about what happens if a very high priority interrupt interrupts the kernel.

Describe how interrupt priorities work on Cortex-M microcontrollers in relation to FreeRTOS API calls.

Consider how FreeRTOS uses priority numbers to decide safe API usage.

Practice

1.

What does configMAX_SYSCALL_INTERRUPT_PRIORITY control in FreeRTOS?

easy

A. The maximum number of interrupts allowed

B. The lowest interrupt priority allowed in the system

C. The highest interrupt priority that can safely call FreeRTOS API functions

D. The priority of the idle task

Solution

1. Step 1: Understand FreeRTOS interrupt priority limits

   FreeRTOS restricts API calls to interrupts at or below a certain priority level to maintain system stability.

2. Step 2: Role of configMAX_SYSCALL_INTERRUPT_PRIORITY

   This configuration sets the highest interrupt priority that can safely call FreeRTOS API functions.

3. Final Answer:

   The highest interrupt priority that can safely call FreeRTOS API functions -> Option C

4. Quick Check:

   configMAX_SYSCALL_INTERRUPT_PRIORITY = highest safe ISR priority [OK]

Hint: Remember: configMAX_SYSCALL_INTERRUPT_PRIORITY limits safe ISR API calls [OK]

Common Mistakes:

• Confusing highest with lowest priority
• Thinking it limits number of interrupts
• Assuming it sets task priorities

2.

Which of the following is the correct way to define configMAX_SYSCALL_INTERRUPT_PRIORITY in FreeRTOSConfig.h?

#define configMAX_SYSCALL_INTERRUPT_PRIORITY  ( ??? )

easy

A. 0x80 // Mid-level priority

B. 0x00 // Highest priority

C. 0xFF // Lowest priority

D. "5" // Priority as string

Solution

1. Step 1: Understand priority values in FreeRTOS

   Lower numeric values represent higher priorities; 0x00 is highest, 0xFF is lowest.

2. Step 2: Correct format for configMAX_SYSCALL_INTERRUPT_PRIORITY

   This macro must be a numeric value representing the highest interrupt priority allowed to call FreeRTOS API, typically a mid-level priority like 0x80.

3. Final Answer:

   0x80 // Mid-level priority -> Option A

4. Quick Check:

   Priority value must be numeric, not string [OK]

Hint: Use numeric hex values for priorities, not strings [OK]

Common Mistakes:

• Using string instead of numeric value
• Setting priority to 0x00 (too high)
• Using lowest priority 0xFF which disables API calls

3.

Given configMAX_SYSCALL_INTERRUPT_PRIORITY is set to 0x50, which ISR priority can safely call FreeRTOS API functions?

ISR Priority Options:
A) 0x40
B) 0x50
C) 0x60
D) 0x30

medium

A. 0x40

B. 0x30

C. 0x50

D. 0x60

Solution

1. Step 1: Compare ISR priorities with configMAX_SYSCALL_INTERRUPT_PRIORITY

   Only ISRs with priority equal or numerically higher (lower urgency) than 0x50 can call FreeRTOS API.

2. Step 2: Evaluate each option

   0x40 and 0x30 are higher priority (lower number) than 0x50, so cannot call API. 0x50 equals limit, allowed. 0x60 is lower priority (higher number), also allowed.

3. Final Answer:

   0x50 and 0x60 -> Option D

4. Quick Check:

   ISR priority must be >= configMAX_SYSCALL_INTERRUPT_PRIORITY [OK]

Hint: ISR priority must be equal or lower urgency than configMAX_SYSCALL_INTERRUPT_PRIORITY [OK]

Common Mistakes:

• Confusing numeric priority order
• Allowing higher urgency ISRs to call API
• Ignoring equal priority as allowed

4.

Identify the error in this ISR code snippet if configMAX_SYSCALL_INTERRUPT_PRIORITY is set to 0x60:

void ISR_Handler(void) {
    NVIC_SetPriority(IRQn, 0x40);
    vTaskNotifyGiveFromISR(taskHandle, NULL);
}

medium

A. ISR priority 0x40 is higher than allowed to call FreeRTOS API

B. vTaskNotifyGiveFromISR cannot be called from ISR

C. NVIC_SetPriority should not be called inside ISR

D. No error, code is correct

Solution

1. Step 1: Check ISR priority against configMAX_SYSCALL_INTERRUPT_PRIORITY

   Priority 0x40 is higher urgency (lower number) than 0x60, so ISR cannot safely call FreeRTOS API.

2. Step 2: Analyze API call in ISR

   Calling vTaskNotifyGiveFromISR requires ISR priority at or below 0x60, which is violated here.

3. Final Answer:

   ISR priority 0x40 is higher than allowed to call FreeRTOS API -> Option A

4. Quick Check:

   ISR priority must not exceed configMAX_SYSCALL_INTERRUPT_PRIORITY [OK]

Hint: ISR priority must be equal or lower urgency than configMAX_SYSCALL_INTERRUPT_PRIORITY [OK]

Common Mistakes:

• Ignoring priority set inside ISR
• Thinking API calls are always allowed in ISR
• Confusing priority numeric order

5.

You have two ISRs: ISR_A with priority 0x70 and ISR_B with priority 0x40. configMAX_SYSCALL_INTERRUPT_PRIORITY is set to 0x60. Which statement is true?

hard

A. Neither ISR can call FreeRTOS API

B. ISR_A can call FreeRTOS API, ISR_B cannot

C. Both ISRs can call FreeRTOS API safely

D. ISR_B can call FreeRTOS API, ISR_A cannot

Solution

1. Step 1: Compare ISR priorities with configMAX_SYSCALL_INTERRUPT_PRIORITY

   Only ISRs with priority numerically equal or higher (lower urgency) than 0x60 can call FreeRTOS API.

2. Step 2: Evaluate ISR_A and ISR_B priorities

   ISR_A priority 0x70 is lower urgency than 0x60, so it can call API. ISR_B priority 0x40 is higher urgency, so it cannot.

3. Final Answer:

   ISR_A can call FreeRTOS API, ISR_B cannot -> Option B

4. Quick Check:

   Only ISRs with priority >= configMAX_SYSCALL_INTERRUPT_PRIORITY call API [OK]

Hint: Only ISRs with priority numerically >= configMAX_SYSCALL_INTERRUPT_PRIORITY call API [OK]

Common Mistakes:

• Assuming higher urgency ISRs can call API
• Confusing numeric priority order
• Thinking all ISRs can call API regardless of priority