FreeRTOS interrupt priority restrictions - Time & Space Complexity

Time Complexity: FreeRTOS interrupt priority restrictions

O(n)

Understanding Time Complexity

When working with FreeRTOS, interrupt priority rules affect how often and how quickly interrupts run.

We want to understand how the number of interrupt priority checks grows as more interrupts are used.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Example ISR with priority check
void vExampleISR(void) {
    BaseType_t xHigherPriorityTaskWoken = pdFALSE;
    if (uxInterruptPriority <= configMAX_SYSCALL_INTERRUPT_PRIORITY) {
        // Safe to call FreeRTOS API
        xSemaphoreGiveFromISR(xSemaphore, &xHigherPriorityTaskWoken);
    }
    portYIELD_FROM_ISR(xHigherPriorityTaskWoken);
}
    

This code checks if the interrupt priority is allowed to call FreeRTOS APIs and then signals a semaphore.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: The priority check and semaphore give happen every time the interrupt fires.
• How many times: Once per interrupt occurrence, which depends on hardware events.

How Execution Grows With Input

As the number of interrupts increases, the system must handle more priority checks and context switches.

Input Size (number of interrupts)	Approx. Operations
10	10 priority checks and possible semaphore signals
100	100 priority checks and possible semaphore signals
1000	1000 priority checks and possible semaphore signals

Pattern observation: The operations grow linearly with the number of interrupts handled.

Final Time Complexity

Time Complexity: O(n)

This means the time spent checking priorities and handling interrupts grows directly with how many interrupts occur.

Common Mistake

[X] Wrong: "Interrupt priority checks happen only once regardless of interrupt count."

[OK] Correct: Each interrupt triggers its own priority check, so more interrupts mean more checks.

Interview Connect

Understanding how interrupt priority checks scale helps you design responsive and safe real-time systems.

Self-Check

"What if we decreased configMAX_SYSCALL_INTERRUPT_PRIORITY to allow more interrupts to call FreeRTOS APIs? How would the time complexity change?"

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