NVIC (Nested Vectored Interrupt Controller) in ARM Architecture - Time & Space Complexity
When working with the NVIC, it is important to understand how interrupt handling time grows as the number of interrupts increases.
We want to know how the time to process interrupts changes when more interrupts are enabled or pending.
Analyze the time complexity of checking and servicing interrupts in NVIC.
// Simplified NVIC interrupt handling loop
while (1) {
for (int i = 0; i < NUM_INTERRUPTS; i++) {
if (NVIC->ISPR[i / 32] & (1 << (i % 32))) {
NVIC->ICPR[i / 32] = (1 << (i % 32)); // Clear pending
handle_interrupt(i); // Service interrupt
}
}
}
This code checks each possible interrupt line to see if it is pending, clears it, and then handles it.
Identify the loops, recursion, array traversals that repeat.
- Primary operation: Looping through all interrupt lines to check pending status.
- How many times: Once per main loop iteration, checking each interrupt line.
As the number of interrupts (n) increases, the time to check all lines grows proportionally.
| Input Size (n) | Approx. Operations |
|---|---|
| 10 | 10 checks |
| 100 | 100 checks |
| 1000 | 1000 checks |
Pattern observation: The number of checks grows linearly with the number of interrupts.
Time Complexity: O(n)
This means the time to check and handle interrupts grows directly in proportion to the number of interrupt lines.
[X] Wrong: "Checking interrupts happens instantly regardless of how many interrupts exist."
[OK] Correct: Each interrupt line must be checked, so more interrupts mean more work and longer checking time.
Understanding how interrupt checking scales helps you reason about system responsiveness and efficiency in embedded systems.
"What if the NVIC used a hardware priority encoder to find the highest priority pending interrupt instead of checking all lines? How would the time complexity change?"
Practice
NVIC in ARM microcontrollers?Solution
Step 1: Understand NVIC's role
NVIC stands for Nested Vectored Interrupt Controller, which manages interrupts.Step 2: Identify its main function
It enables, disables, and prioritizes interrupts so the processor can respond quickly to important events.Final Answer:
To manage and prioritize multiple interrupts efficiently -> Option BQuick Check:
NVIC controls interrupts = B [OK]
- Confusing NVIC with clock or memory functions
- Thinking NVIC stores program code
- Assuming NVIC increases processor speed
Solution
Step 1: Identify function purpose
NVIC_EnableIRQ is used to enable a specific interrupt request (IRQ).Step 2: Compare other options
NVIC_DisableIRQ disables interrupts, NVIC_SetPriority sets priority, NVIC_ClearPendingIRQ clears pending interrupts.Final Answer:
NVIC_EnableIRQ(IRQn); -> Option CQuick Check:
Enable interrupt function = NVIC_EnableIRQ [OK]
- Confusing enable with disable functions
- Mixing priority setting with enabling
- Using clear pending instead of enable
NVIC_SetPriority(TIM2_IRQn, 2); NVIC_EnableIRQ(TIM2_IRQn); NVIC_SetPriority(USART1_IRQn, 1); NVIC_EnableIRQ(USART1_IRQn);Which interrupt has higher priority?
Solution
Step 1: Understand priority values
Lower numeric priority value means higher priority in NVIC.Step 2: Compare priorities set
TIM2_IRQn is set to 2, USART1_IRQn is set to 1, so USART1_IRQn has higher priority.Final Answer:
USART1_IRQn has higher priority -> Option AQuick Check:
Lower number = higher priority = USART1_IRQn [OK]
- Assuming higher number means higher priority
- Ignoring priority values and focusing on enable order
- Confusing IRQ names
NVIC_EnableIRQ(EXTI0_IRQn); NVIC_DisableIRQ(EXTI1_IRQn);What is the likely mistake?
Solution
Step 1: Analyze the code
The code enables EXTI0_IRQn but disables EXTI1_IRQn, which are different interrupts.Step 2: Identify the mistake
If the goal was to disable EXTI0_IRQn, disabling EXTI1_IRQn is incorrect.Final Answer:
They enabled EXTI0_IRQn but disabled EXTI1_IRQn instead -> Option DQuick Check:
Mismatch in IRQ numbers = mistake [OK]
- Disabling wrong interrupt number
- Believing disable function doesn't work
- Thinking priority affects disabling
SENSOR_IRQn and COMM_IRQn?Solution
Step 1: Recall NVIC priority rules
Lower numeric priority means higher priority and can preempt others.Step 2: Apply to SENSOR and COMM interrupts
To let SENSOR_IRQn preempt COMM_IRQn, SENSOR_IRQn must have a lower priority number.Final Answer:
Set SENSOR_IRQn priority lower than COMM_IRQn (e.g., SENSOR=0, COMM=1) -> Option AQuick Check:
Lower number = higher priority = SENSOR_IRQn preempts [OK]
- Assigning higher number for higher priority
- Disabling interrupts instead of prioritizing
- Setting equal priorities expecting preemption
Ready to prove it?
Pass the test and this pattern moves unknown
