Why interrupts are needed in Embedded C - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define an interrupt service routine (ISR) function.

Embedded C

void [1]() {
    // ISR code here
}

Drag options to blanks, or click blank then click option'

AISR_Handler

Bmain

Cloop

Dsetup

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'main' or 'loop' as ISR function name.

The function that handles an interrupt is called an ISR (Interrupt Service Routine). Naming it ISR_Handler is a common practice.

2fill in blank

medium

Complete the code to enable global interrupts in the microcontroller.

Embedded C

sei(); // [1] interrupts

Drag options to blanks, or click blank then click option'

Areset

Bdisable

Cignore

Denable

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing enable with disable or reset.

The sei() function enables global interrupts in many embedded C environments.

3fill in blank

hard

Fix the error in the code to correctly declare an ISR for timer overflow.

Embedded C

ISR([1]) {
    // Timer overflow code
}

Drag options to blanks, or click blank then click option'

Atimer_interrupt

BTIMER0_OVF_vect

Cmain

Doverflow_handler

Attempts:

3 left

💡 Hint

Common Mistakes

Using generic or incorrect names like 'main' or 'timer_interrupt'.

The correct vector name for Timer0 overflow interrupt is TIMER0_OVF_vect.

4fill in blank

hard

Fill both blanks to create a dictionary that maps interrupt names to their priority levels.

Embedded C

const int interrupt_priority[] = {
    [[1]] = 1,
    [[2]] = 2
};

Drag options to blanks, or click blank then click option'

ATIMER0_OVF_vect

BUSART_RX_vect

CADC_vect

DINT0_vect

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid or duplicate interrupt names.

We map TIMER0_OVF_vect to priority 1 and USART_RX_vect to priority 2 as an example.

5fill in blank

hard

Fill all three blanks to complete the code that checks if an interrupt flag is set and clears it.

Embedded C

if ([1] & (1 << [2])) {
    [3] |= (1 << [2]); // Clear flag
}

Drag options to blanks, or click blank then click option'

ATIFR

BTOV0

DTIMSK

Attempts:

3 left

💡 Hint

Common Mistakes

Using wrong registers or bits to check or clear flags.

The TIFR register holds interrupt flags. TOV0 is the Timer0 overflow flag bit. Clearing the flag is done by writing 1 to the bit in TIFR.

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