Why software timers are useful in FreeRTOS

Introduction

Software timers help run tasks after a delay or repeatedly without blocking the main program. They make managing time-based actions easy and efficient.

To turn off a device automatically after some time.

To check sensor data regularly every few seconds.

To retry a failed operation after waiting a bit.

To create a timeout for waiting on an event.

To schedule periodic updates or maintenance tasks.

Syntax

FreeRTOS

TimerHandle_t xTimerCreate(
    const char * const pcTimerName,
    const TickType_t xTimerPeriodInTicks,
    const UBaseType_t uxAutoReload,
    void * const pvTimerID,
    TimerCallbackFunction_t pxCallbackFunction
);

xTimerCreate creates a new software timer.

pxCallbackFunction is the function called when the timer expires.

Examples

This creates a one-shot timer that runs once after 1000 milliseconds.

FreeRTOS

TimerHandle_t myTimer = xTimerCreate("MyTimer", pdMS_TO_TICKS(1000), pdFALSE, NULL, myCallback);

This creates a timer that repeats every 500 milliseconds.

FreeRTOS

TimerHandle_t periodicTimer = xTimerCreate("Periodic", pdMS_TO_TICKS(500), pdTRUE, NULL, periodicCallback);

Sample Program

This program creates a one-shot timer that prints a message after 2 seconds. It simulates waiting by printing "Waiting..." every second.

FreeRTOS

#include "FreeRTOS.h"
#include "timers.h"
#include <stdio.h>

void vTimerCallback(TimerHandle_t xTimer) {
    printf("Timer expired!\n");
}

int main(void) {
    TimerHandle_t xTimer = xTimerCreate("OneShot", pdMS_TO_TICKS(2000), pdFALSE, NULL, vTimerCallback);
    if (xTimer != NULL) {
        xTimerStart(xTimer, 0);
    }
    // Simulate scheduler running and waiting for timer
    for (int i = 0; i < 3; i++) {
        vTaskDelay(pdMS_TO_TICKS(1000));
        printf("Waiting... %d seconds\n", i + 1);
    }
    return 0;
}

// Dummy vTaskDelay for simulation
void vTaskDelay(const TickType_t xTicksToDelay) {
    // Just a placeholder to simulate delay
}

Important Notes

Software timers run in the timer service task, so they don't block your main tasks.

Always start the timer with xTimerStart() after creating it.

Use pdMS_TO_TICKS() to convert milliseconds to ticks for timer periods.

Summary

Software timers let you run code after a delay or repeatedly without blocking.

They are useful for time-based actions like timeouts and periodic checks.

Creating and starting timers is simple with FreeRTOS API functions.

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