Why SysTick timer for RTOS tick in ARM Architecture? - Purpose & Use Cases

The Big Idea

What if your robot could keep perfect time without you lifting a finger?

The Scenario

Imagine you are building a small robot that needs to perform tasks like checking sensors and moving motors at precise time intervals. Without a timer, you try to keep track of time by counting instructions or guessing delays manually.

The Problem

This manual timing is slow and unreliable because the processor speed can vary, and guessing delays often leads to mistakes. Tasks may run too early or too late, causing the robot to behave unpredictably.

The Solution

The SysTick timer is a built-in hardware timer in ARM processors that automatically generates regular interrupts at precise intervals. This helps the RTOS keep track of time accurately and switch tasks smoothly without manual counting.

Before vs After

✗ Before

while(1) { do_task(); delay_somehow(); }

✓ After

SysTick_Config(tick_rate); // RTOS handles task switching

What It Enables

With the SysTick timer, your system can run multiple tasks reliably and on time, making complex real-time applications possible.

Real Life Example

In a drone, the SysTick timer helps the RTOS manage sensor readings, motor controls, and communication tasks precisely, ensuring stable flight.

Key Takeaways

Manual timing is unreliable and error-prone.

SysTick timer provides precise, automatic timing interrupts.

This enables smooth multitasking in real-time systems.

Practice

1. What is the main purpose of the SysTick timer in an RTOS?

easy

A. To generate regular interrupts for task switching

B. To increase CPU clock speed

C. To store data temporarily

D. To manage memory allocation

Solution

1. Step 1: Understand SysTick timer role

   The SysTick timer is designed to create periodic interrupts.

2. Step 2: Connect interrupts to RTOS function

   These interrupts allow the RTOS to switch tasks regularly.

3. Final Answer:

   To generate regular interrupts for task switching -> Option A

4. Quick Check:

   SysTick timer = periodic interrupts for RTOS [OK]

Hint: SysTick timer triggers interrupts for switching tasks [OK]

Common Mistakes:

• Confusing SysTick with CPU clock speed control
• Thinking SysTick stores data
• Assuming SysTick manages memory

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

easy

A. Write zero to the RELOAD register

B. Set the TICKINT bit in the SysTick CTRL register

C. Clear the ENABLE bit in the SysTick CTRL register

D. Disable the NVIC interrupt controller

Solution

1. Step 1: Identify the control register bits

   The SysTick CTRL register controls timer and interrupt enabling.

2. Step 2: Enable interrupt by setting TICKINT bit

   Setting the TICKINT bit enables SysTick interrupts.

3. Final Answer:

   Set the TICKINT bit in the SysTick CTRL register -> Option B

4. Quick Check:

   Enable interrupt = set TICKINT bit [OK]

Hint: Enable SysTick interrupt by setting TICKINT bit [OK]

Common Mistakes:

• Clearing ENABLE disables timer, not interrupt
• Writing zero to RELOAD stops timer from counting
• Disabling NVIC stops all interrupts, not just SysTick

3. Given a CPU clock of 48 MHz and a desired RTOS tick interval of 1 ms, what reload value should be set in the SysTick timer?

medium

A. 47999

B. 480

C. 48000

D. 47

Solution

1. Step 1: Calculate ticks per 1 ms interval

   CPU clock = 48,000,000 Hz means 48,000 ticks per 1 ms (since 1 ms = 0.001 s).

2. Step 2: Determine reload value

   Reload value = ticks per interval - 1 = 48000 - 1 = 47999.

3. Final Answer:

   47999 -> Option A

4. Quick Check:

   Reload = (CPU clock * tick interval) - 1 = 47999 [OK]

Hint: Reload = (CPU clock x interval) - 1 [OK]

Common Mistakes:

• Using CPU clock directly without subtracting 1
• Confusing microseconds with milliseconds
• Using too small reload value causing faster ticks

4. A developer sets the SysTick reload value to 0 and enables the timer and interrupt. What issue will occur?

medium

A. System will reset immediately

B. SysTick will never generate interrupts

C. CPU clock speed will increase

D. SysTick will generate interrupts continuously without delay

Solution

1. Step 1: Understand reload value effect

   A reload value of 0 means the timer counts from 0 to 0, triggering interrupt immediately.

2. Step 2: Resulting behavior

   This causes continuous interrupts with no delay, overwhelming the system.

3. Final Answer:

   SysTick will generate interrupts continuously without delay -> Option D

4. Quick Check:

   Reload=0 causes continuous interrupts [OK]

Hint: Reload 0 means no delay, interrupts fire nonstop [OK]

Common Mistakes:

• Assuming no interrupts occur with reload 0
• Thinking CPU clock changes due to SysTick
• Expecting system reset from this setting

5. In an RTOS using SysTick for task switching, if the CPU clock changes dynamically (e.g., due to power saving), what must be done to maintain correct tick timing?

hard

A. Disable SysTick and rely on software delays

B. Keep the reload value fixed regardless of clock changes

C. Update the SysTick reload value to match the new CPU clock frequency

D. Increase the interrupt priority of SysTick

Solution

1. Step 1: Recognize effect of CPU clock changes

   SysTick timer counts CPU clock cycles, so changing clock speed affects tick timing.

2. Step 2: Adjust reload value accordingly

   To keep tick interval constant, reload value must be recalculated based on new CPU clock.

3. Final Answer:

   Update the SysTick reload value to match the new CPU clock frequency -> Option C

4. Quick Check:

   Adjust reload for clock changes to keep tick timing [OK]

Hint: Reload value must match CPU clock for correct ticks [OK]

Common Mistakes:

• Ignoring clock changes and keeping reload fixed
• Disabling SysTick breaks RTOS timing
• Changing interrupt priority doesn't fix timing