Why software timers are useful in FreeRTOS - Visual Breakdown

Concept Flow - Why software timers are useful

Start Timer

↓

Timer Counts Down

↓

Timer Expires?

No→Wait

Yes↓

Execute Callback

↓

Restart or Stop Timer

A software timer starts counting down, waits until it expires, then runs a callback function automatically.

Execution Sample

FreeRTOS

void timerCallback(TimerHandle_t xTimer) {
    // Code to run when timer expires
}

TimerHandle_t myTimer = xTimerCreate("MyTimer", pdMS_TO_TICKS(1000), pdTRUE, NULL, timerCallback);
xTimerStart(myTimer, 0);

This code creates a repeating software timer that calls timerCallback every 1000 milliseconds.

Execution Table

Step	Timer State	Time Left (ms)	Condition	Action	Output
1	Created	1000	Timer started?	Start timer countdown	No output
2	Running	700	Timer expired?	Wait	No output
3	Running	300	Timer expired?	Wait	No output
4	Expired	0	Timer expired?	Execute callback	Callback runs
5	Running	1000	Auto-reload?	Restart timer	No output
6	Running	700	Timer expired?	Wait	No output
...	...	...	...	...	...
Exit	Stopped	-	Timer stopped externally?	Stop timer	No output

💡 Timer stops when explicitly stopped or system shuts down

Variable Tracker

Variable	Start	After Step 1	After Step 4	After Step 5	Final
Timer State	Not created	Created	Expired	Running	Stopped or Running
Time Left (ms)	-	1000	0	1000	-

Key Moments - 3 Insights

Why does the timer callback run automatically without manual checking?

Because the timer system checks the countdown internally and calls the callback when time reaches zero, as shown in execution_table step 4.

What happens if the timer is set to auto-reload?

The timer restarts automatically after expiring, shown in execution_table step 5, so the callback runs repeatedly without restarting manually.

Can the timer be stopped before it expires?

Yes, the timer can be stopped externally, which ends the countdown and prevents the callback, as indicated in the exit row of execution_table.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Timer State at Step 4?

A Running

B Expired

C Created

D Stopped

💡 Hint

Check the 'Timer State' column in execution_table row for Step 4

At which step does the timer restart automatically if auto-reload is enabled?

A Step 2

B Step 4

C Step 5

D Exit

💡 Hint

Look for 'Restart timer' action in execution_table

If the timer is stopped externally, what happens to the callback execution?

A Callback does not run

B Callback runs after stopping

C Callback runs immediately

D Callback runs repeatedly

💡 Hint

Refer to the exit row in execution_table where timer is stopped

Concept Snapshot

Software timers count down in the background.
When they expire, they run a callback function automatically.
They can be one-shot or auto-reloading.
Timers free your code from manual time checks.
You can start, stop, or reset timers anytime.

Full Transcript

Software timers in FreeRTOS help run code after a delay or repeatedly without manual checking. The timer starts counting down when created and started. When the countdown reaches zero, the timer automatically calls a callback function. If set to auto-reload, the timer restarts and calls the callback repeatedly. You can stop the timer anytime to prevent the callback. This makes managing timed events easier and cleaner in your programs.

Practice

1. Why are software timers useful in FreeRTOS?

easy

A. They allow running code after a delay without blocking other tasks.

B. They increase the CPU speed automatically.

C. They replace the need for tasks entirely.

D. They store data permanently in memory.

Solution

1. Step 1: Understand the purpose of software timers

   Software timers let you schedule code to run later or repeatedly without stopping other tasks.

2. Step 2: Compare options to this purpose

   Only They allow running code after a delay without blocking other tasks. describes this behavior correctly; others describe unrelated features.

3. Final Answer:

   They allow running code after a delay without blocking other tasks. -> Option A

4. Quick Check:

   Software timers = delayed non-blocking code [OK]

Hint: Think: timers run code later without stopping tasks [OK]

Common Mistakes:

• Confusing timers with speeding up CPU
• Thinking timers replace tasks
• Assuming timers store data permanently

2. Which FreeRTOS API function is used to start a software timer?

easy

A. vTaskDelay()

B. vTaskDelete()

C. xQueueSend()

D. xTimerStart()

Solution

1. Step 1: Identify the function to start timers

   The FreeRTOS API uses xTimerStart() to begin a software timer.

2. Step 2: Eliminate unrelated functions

   vTaskDelay() delays tasks, xQueueSend() sends data to queues, vTaskDelete() deletes tasks, so they are incorrect.

3. Final Answer:

   xTimerStart() -> Option D

4. Quick Check:

   Start timer = xTimerStart() [OK]

Hint: Start timers with xTimerStart() function [OK]

Common Mistakes:

• Confusing task delay with timer start
• Using queue functions for timers
• Deleting tasks instead of starting timers

3. What will happen if a software timer is set with a 1000ms period and auto-reload enabled?

medium

A. The timer callback never runs.

B. The timer callback runs once after 1000ms.

C. The timer callback runs repeatedly every 1000ms.

D. The timer callback runs immediately and stops.

Solution

1. Step 1: Understand auto-reload behavior

   When auto-reload is enabled, the timer restarts automatically after each period.

2. Step 2: Apply to 1000ms period

   The callback runs every 1000ms repeatedly, not just once or immediately.

3. Final Answer:

   The timer callback runs repeatedly every 1000ms. -> Option C

4. Quick Check:

   Auto-reload timer = repeated callback [OK]

Hint: Auto-reload means repeat callback every period [OK]

Common Mistakes:

• Thinking callback runs only once
• Assuming callback runs immediately
• Believing callback never runs

4. You created a software timer but its callback never runs. What is a likely cause?

medium

A. The timer was not started with xTimerStart().

B. The timer period was set to zero.

C. The callback function has no parameters.

D. The timer was created with xTimerCreate() correctly.

Solution

1. Step 1: Check timer start requirement

   After creating a timer, you must start it with xTimerStart() for callbacks to run.

2. Step 2: Evaluate other options

   Zero period is invalid but usually causes errors; callback parameters are fixed by API; correct creation alone doesn't start timer.

3. Final Answer:

   The timer was not started with xTimerStart(). -> Option A

4. Quick Check:

   Timer callback runs only if started [OK]

Hint: Always start timers with xTimerStart() after creation [OK]

Common Mistakes:

• Forgetting to start the timer
• Setting invalid timer periods silently
• Assuming creation auto-starts timer

5. You want to check a sensor every 500ms without blocking other tasks. How should you use a FreeRTOS software timer?

hard

A. Create a timer with 0ms period to check sensor continuously.

B. Create a timer with 500ms period, auto-reload enabled, and put sensor check in callback.

C. Use vTaskDelay(500) inside a task to check sensor periodically.

D. Create a one-shot timer with 500ms period and restart it manually each time.

Solution

1. Step 1: Identify periodic sensor check requirement

   You want to check sensor every 500ms repeatedly without blocking.

2. Step 2: Choose timer setup for repeated checks

   Auto-reload timer with 500ms period runs callback repeatedly without blocking tasks.

3. Step 3: Eliminate other options

   One-shot requires manual restart, vTaskDelay blocks task, 0ms period is invalid.

4. Final Answer:

   Create a timer with 500ms period, auto-reload enabled, and put sensor check in callback. -> Option B

5. Quick Check:

   Periodic sensor check = auto-reload timer [OK]

Hint: Use auto-reload timer for repeated periodic actions [OK]

Common Mistakes:

• Using one-shot timers for repeated tasks
• Blocking tasks with vTaskDelay
• Setting invalid zero period timers