Why interrupts are needed in Embedded C - The Real Reasons

The Big Idea

What if your microcontroller could magically know exactly when to act without wasting a single moment?

The Scenario

Imagine you are watching a pot boil on the stove, but you have to keep checking it every few seconds to see if it's ready. Meanwhile, you can't do anything else because you must keep looking. This is like a microcontroller constantly checking if something happened, like a button press or a sensor signal.

The Problem

Manually checking for events all the time wastes time and power. It's slow because the microcontroller can't do other tasks while waiting. Also, it's easy to miss important events if the check isn't frequent enough, causing errors or delays.

The Solution

Interrupts let the microcontroller do other work and only stop to handle important events when they actually happen. It's like having a friend who taps you on the shoulder when the pot boils, so you don't have to keep looking.

Before vs After

✗ Before

while(1) { if(button_pressed()) { handle_button(); } }

✓ After

void ISR_button() { handle_button(); } // runs only when button pressed

What It Enables

Interrupts enable efficient multitasking and quick response to events without wasting time or power.

Real Life Example

In a smart home, interrupts allow a device to sleep and save battery, waking instantly when a doorbell rings or motion is detected.

Key Takeaways

Manual checking wastes time and can miss events.

Interrupts let the system respond immediately only when needed.

This improves efficiency, speed, and power use.

Practice

1. Why are interrupts needed in embedded C programming?

easy

A. To allow the program to respond quickly to important events

B. To make the program run slower

C. To avoid using functions

D. To increase the size of the program

Solution

1. Step 1: Understand the role of interrupts

   Interrupts let the program stop what it is doing and handle urgent tasks immediately.

2. Step 2: Compare options

   Only To allow the program to respond quickly to important events correctly states that interrupts help respond quickly to important events.

3. Final Answer:

   To allow the program to respond quickly to important events -> Option A

4. Quick Check:

   Interrupts = Quick response [OK]

Hint: Interrupts = fast response to events [OK]

Common Mistakes:

• Thinking interrupts slow down the program
• Confusing interrupts with normal function calls
• Believing interrupts increase program size unnecessarily

2. Which of the following is the correct syntax to declare an Interrupt Service Routine (ISR) in embedded C?

easy

A. void ISR_name() interrupt;

B. void ISR_name(void) __interrupt;

C. void ISR_name(void) __interrupt(0);

D. void ISR_name() __interrupt(5);

Solution

1. Step 1: Recall ISR declaration syntax

   In embedded C, ISRs are declared with the __interrupt keyword and the interrupt vector number in parentheses.

2. Step 2: Identify correct option

   void ISR_name(void) __interrupt(0); uses __interrupt(0), which is the correct form for declaring ISR with vector 0.

3. Final Answer:

   void ISR_name(void) __interrupt(0); -> Option C

4. Quick Check:

   ISR syntax = __interrupt(vector) [OK]

Hint: ISR needs __interrupt with vector number [OK]

Common Mistakes:

• Omitting the vector number in __interrupt
• Using interrupt without __
• Missing void parameter list

3. Consider this embedded C code snippet:

volatile int flag = 0;
void ISR_timer(void) __interrupt(1) {
    flag = 1;
}

int main() {
    while(flag == 0) {
        // wait for interrupt
    }
    return 0;
}

What is the role of the interrupt here?

medium

A. To set flag to 1 when timer interrupt occurs

B. To reset the flag to 0 continuously

C. To stop the program immediately

D. To cause a syntax error

Solution

1. Step 1: Analyze ISR function

   The ISR sets the variable flag to 1 when the interrupt occurs.

2. Step 2: Understand main loop behavior

   Main waits in a loop until flag becomes 1, meaning it waits for the interrupt to happen.

3. Final Answer:

   To set flag to 1 when timer interrupt occurs -> Option A

4. Quick Check:

   ISR sets flag = 1 [OK]

Hint: ISR changes flag to signal event [OK]

Common Mistakes:

• Thinking flag resets to 0 automatically
• Assuming interrupt stops program
• Confusing syntax error with correct code

4. Find the error in this ISR declaration:

void ISR_button() interrupt 2 {
    // handle button press
}

medium

A. ISR cannot have parameters

B. ISR function must return int

C. interrupt number 2 is invalid

D. Missing __ before interrupt keyword

Solution

1. Step 1: Check ISR declaration syntax

   In embedded C, the interrupt keyword must be preceded by double underscores: __interrupt.

2. Step 2: Verify other parts

   ISR functions return void and have no parameters, which is correct here. Interrupt number 2 is valid.

3. Final Answer:

   Missing __ before interrupt keyword -> Option D

4. Quick Check:

   ISR syntax needs __interrupt [OK]

Hint: ISR must use __interrupt keyword [OK]

Common Mistakes:

• Using single underscore or no underscore
• Changing return type from void
• Adding parameters to ISR

5. You want your embedded program to monitor a sensor and also perform other tasks without delay. How does using interrupts help achieve this?

hard

A. Interrupts require the program to wait for sensor manually

B. Interrupts pause other tasks and immediately run sensor code when triggered

C. Interrupts disable sensor monitoring to save power

D. Interrupts make the program run tasks one after another slowly

Solution

1. Step 1: Understand multitasking with interrupts

   Interrupts allow the program to stop current tasks and quickly handle sensor events.

2. Step 2: Compare options

   Interrupts pause other tasks and immediately run sensor code when triggered correctly describes how interrupts improve responsiveness by pausing other tasks to run sensor code immediately.

3. Final Answer:

   Interrupts pause other tasks and immediately run sensor code when triggered -> Option B

4. Quick Check:

   Interrupts = immediate sensor handling [OK]

Hint: Interrupts handle urgent tasks immediately [OK]

Common Mistakes:

• Thinking interrupts slow down program
• Believing interrupts disable sensors
• Assuming manual waiting is needed