PendSV and SysTick exceptions in ARM Architecture

Introduction

PendSV and SysTick are special signals in ARM processors that help manage time and switching tasks smoothly.

When you want to switch between different tasks in a program without losing data.

When you need a timer to trigger actions regularly, like blinking an LED every second.

When building an operating system that runs many programs at once.

When you want to handle background tasks without stopping the main program.

When you need precise timing for events in embedded devices.

Core Concept

ARM Architecture

PendSV_Handler(void) {
    // Code to handle task switching
}

SysTick_Handler(void) {
    // Code to handle timer tick
}

Both PendSV and SysTick are exception handlers, special functions called automatically by the processor.

PendSV is usually used for switching tasks, while SysTick is used as a timer interrupt.

Key Points

This example shows PendSV used to switch tasks by saving and restoring their states.

ARM Architecture

void PendSV_Handler(void) {
    // Save current task state
    // Switch to next task
    // Restore next task state
}

This example shows SysTick used as a timer to keep track of time and trigger actions.

ARM Architecture

void SysTick_Handler(void) {
    // Increment system tick count
    // Perform periodic actions
}

Detailed Explanation

This simple program counts 5 timer ticks using SysTick, then calls PendSV to simulate a task switch.

ARM Architecture

volatile unsigned int system_ticks = 0;

void SysTick_Handler(void) {
    system_ticks++; // Increase tick count every time SysTick fires
}

void PendSV_Handler(void) {
    // Imagine switching tasks here
    // For simplicity, just print a message
    // (In real ARM code, printing is not typical in handlers)
}

int main(void) {
    // Setup SysTick to fire every 1ms (not shown here)
    // Main loop
    while (system_ticks < 5) {
        // Wait until 5 ticks have passed
    }
    // After 5 ticks, simulate PendSV call
    PendSV_Handler();
    return 0;
}

Important Notes

PendSV is a low priority interrupt, so it runs after other interrupts finish.

SysTick is a built-in timer that helps keep track of time in embedded systems.

These exceptions help build multitasking systems on ARM processors.

Summary

PendSV is used for switching tasks smoothly in ARM systems.

SysTick is a timer interrupt that helps keep track of time.

Together, they help create responsive and multitasking embedded programs.

Practice

1. What is the primary purpose of the PendSV exception in ARM processors?

easy

A. To reset the processor

B. To provide a regular timer interrupt

C. To handle task switching smoothly in the background

D. To manage memory access

Solution

1. Step 1: Understand PendSV role

   PendSV is designed to handle context switching between tasks without interrupting the main program flow.

2. Step 2: Compare with other exceptions

   Unlike SysTick, which provides timing interrupts, PendSV is specifically for smooth task switching.

3. Final Answer:

   To handle task switching smoothly in the background -> Option C

4. Quick Check:

   PendSV = task switching [OK]

Hint: PendSV = background task switcher [OK]

Common Mistakes:

• Confusing PendSV with SysTick timer
• Thinking PendSV resets the processor
• Assuming PendSV manages memory

2. Which of the following is the correct way to enable the SysTick timer in ARM Cortex-M processors?

easy

A. Set the CTRL register's ENABLE bit to 1

B. Clear the CTRL register's ENABLE bit to 0

C. Write 0xFFFFFFFF to the LOAD register

D. Disable the PendSV exception

Solution

1. Step 1: Identify SysTick control

   The SysTick timer is controlled by the CTRL register, where setting the ENABLE bit starts the timer.

2. Step 2: Eliminate incorrect options

   Clearing ENABLE stops the timer, writing max to LOAD sets reload value but doesn't enable, and disabling PendSV is unrelated.

3. Final Answer:

   Set the CTRL register's ENABLE bit to 1 -> Option A

4. Quick Check:

   SysTick enable = CTRL ENABLE bit set [OK]

Hint: Enable SysTick by setting CTRL ENABLE bit [OK]

Common Mistakes:

• Confusing enabling with disabling bits
• Thinking LOAD register enables timer
• Mixing PendSV control with SysTick

3. Consider this simplified ARM Cortex-M code snippet:

SysTick->LOAD = 1000 - 1;
SysTick->VAL = 0;
SysTick->CTRL = 7;

What does the value 7 in SysTick->CTRL represent?

medium

A. Enable SysTick, enable interrupt, and use processor clock

B. Disable SysTick and interrupts

C. Enable SysTick only without interrupts

D. Reset SysTick counter

Solution

1. Step 1: Decode CTRL register bits

   Value 7 in binary is 0b111, meaning bits ENABLE(0), TICKINT(1), and CLKSOURCE(2) are set.

2. Step 2: Understand each bit meaning

   ENABLE starts the timer, TICKINT enables interrupt, CLKSOURCE selects processor clock.

3. Final Answer:

   Enable SysTick, enable interrupt, and use processor clock -> Option A

4. Quick Check:

   CTRL=7 means all three bits set [OK]

Hint: 7 in CTRL means enable + interrupt + clock source [OK]

Common Mistakes:

• Ignoring interrupt enable bit
• Assuming 7 disables timer
• Confusing bits order

4. A developer writes this code to trigger PendSV manually:

SCB->ICSR |= (1 << 28);

But the PendSV exception does not occur. What is the likely cause?

medium

A. ICSR register is read-only

B. SysTick timer is disabled

C. PendSV cannot be triggered manually

D. PendSV priority is not set low enough

Solution

1. Step 1: Understand PendSV triggering

   Writing to ICSR bit 28 sets the PendSV pending flag, but PendSV only runs if its priority is low enough.

2. Step 2: Identify common mistake

   If PendSV priority is higher or equal to other interrupts, it won't run even if pending.

3. Final Answer:

   PendSV priority is not set low enough -> Option D

4. Quick Check:

   PendSV priority must be low to run [OK]

Hint: PendSV needs low priority to run when pending [OK]

Common Mistakes:

• Assuming ICSR is read-only
• Thinking SysTick affects PendSV trigger
• Believing PendSV can't be triggered manually

5. In a real-time operating system (RTOS) on ARM Cortex-M, how do PendSV and SysTick work together to manage multitasking?

hard

A. PendSV triggers timer interrupts; SysTick switches tasks

B. SysTick triggers regular interrupts; PendSV performs context switching after SysTick

C. Both PendSV and SysTick handle memory management

D. SysTick disables PendSV during task switching

Solution

1. Step 1: Understand SysTick role in RTOS

   SysTick generates periodic interrupts to keep track of time slices and trigger scheduler checks.

2. Step 2: Understand PendSV role in RTOS

   PendSV is triggered by the scheduler to perform the actual task context switch smoothly in the background.

3. Step 3: Combine roles for multitasking

   SysTick signals when to switch; PendSV does the switch, enabling efficient multitasking.

4. Final Answer:

   SysTick triggers regular interrupts; PendSV performs context switching after SysTick -> Option B

5. Quick Check:

   SysTick = timer, PendSV = switcher [OK]

Hint: SysTick triggers; PendSV switches tasks [OK]

Common Mistakes:

• Swapping roles of PendSV and SysTick
• Thinking both handle memory
• Assuming SysTick disables PendSV