Why software timers are useful in FreeRTOS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a software timer with FreeRTOS.

FreeRTOS

TimerHandle_t xTimer = xTimerCreate("Timer", pdMS_TO_TICKS([1]), pdTRUE, 0, vTimerCallback);

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

AxTimerStart

B1000

CpdFALSE

DvTimerCallback

Attempts:

3 left

💡 Hint

Common Mistakes

Using the callback function name instead of the timer period.

Confusing pdTRUE and pdFALSE for auto-reload.

Passing the start function instead of the period.

The timer period is set in milliseconds. Here, 1000 ms means the timer triggers every 1 second.

2fill in blank

medium

Complete the code to start the software timer after creation.

FreeRTOS

if (xTimer != NULL) { xTimer[1](xTimer, 0); }

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

AxTimerStart

BxTimerDelete

CxTimerStop

DxTimerReset

Attempts:

3 left

💡 Hint

Common Mistakes

Using xTimerStop instead of xTimerStart.

Trying to delete the timer immediately.

Resetting the timer before starting it.

xTimerStart starts the timer so it begins counting and calling the callback.

3fill in blank

hard

Fix the error in the callback function signature for a FreeRTOS software timer.

FreeRTOS

void [1](TimerHandle_t xTimer) {
    // Timer callback code
}

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

AvTimerCallbackFunction

BTimerCallback

CTimerCallbackFunction

DvTimerCallback

Attempts:

3 left

💡 Hint

Common Mistakes

Using a different function name than the one passed to xTimerCreate.

Not matching the exact function signature.

The callback function name is user-defined but commonly starts with 'v' and matches the name used when creating the timer.

4fill in blank

hard

Fill both blanks to create a software timer that does not auto-reload and starts immediately.

FreeRTOS

TimerHandle_t xTimer = xTimerCreate("OneShot", pdMS_TO_TICKS([1]), [2], 0, vTimerCallback);
xTimerStart(xTimer, 0);

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

A500

BpdFALSE

CpdTRUE

D1000

Attempts:

3 left

💡 Hint

Common Mistakes

Using pdTRUE for auto-reload when one-shot is needed.

Setting the period too high or too low without reason.

The timer period is 500 ms and pdFALSE means the timer is one-shot (does not auto-reload).

5fill in blank

hard

Fill all three blanks to create a periodic timer with a 2-second period and start it.

FreeRTOS

TimerHandle_t xTimer = xTimerCreate("Periodic", pdMS_TO_TICKS([1]), [2], 0, [3]);
xTimerStart(xTimer, 0);

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

AvTimerCallback

B2000

CpdTRUE

DpdFALSE

Attempts:

3 left

💡 Hint

Common Mistakes

Using pdFALSE for periodic timers.

Mixing up the order of arguments.

Using the wrong callback function name.

The timer period is 2000 ms (2 seconds), pdTRUE means it auto-reloads, and the callback function is vTimerCallback.

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