Why Tick timer and scheduler in FreeRTOS? - Purpose & Use Cases

The Big Idea

What if your tiny device could juggle many jobs perfectly without you lifting a finger?

The Scenario

Imagine you are trying to run multiple tasks on a tiny microcontroller, like turning on lights, reading sensors, and sending data. If you try to do each task one after another manually, you have to keep track of time yourself and switch tasks by hand.

The Problem

Doing this manually is slow and tricky. You might forget to check the time, tasks could block each other, or some tasks might never get a chance to run. It's easy to make mistakes and your device might freeze or behave unpredictably.

The Solution

The tick timer and scheduler in FreeRTOS handle all this for you. The tick timer acts like a heartbeat, regularly telling the system to check which task should run next. The scheduler then switches tasks smoothly and fairly, so all your tasks get time to do their job without you managing every detail.

Before vs After

✗ Before

while(1) {
  readSensor();
  sendData();
  controlLights();
  delay(100);
}

✓ After

vTaskStartScheduler();
// Tasks run independently and switch automatically

What It Enables

It lets your microcontroller run many tasks efficiently and reliably, like a skilled conductor leading an orchestra.

Real Life Example

In a smart home device, the tick timer and scheduler let the system read temperature, respond to button presses, and send updates over Wi-Fi all at once without freezing or missing anything.

Key Takeaways

Manual task switching is slow and error-prone.

Tick timer provides a regular time signal to manage tasks.

Scheduler switches tasks automatically for smooth multitasking.

Practice

1. What is the main role of the tick timer in FreeRTOS?

easy

A. To handle input/output operations

B. To store task priorities

C. To allocate memory for tasks

D. To count time in small steps called ticks

Solution

1. Step 1: Understand tick timer function

   The tick timer counts time in small units called ticks, which are the basic time measurement in FreeRTOS.

2. Step 2: Differentiate from other functions

   Other options like storing priorities or handling I/O are not related to the tick timer's role.

3. Final Answer:

   To count time in small steps called ticks -> Option D

4. Quick Check:

   Tick timer = counts ticks [OK]

Hint: Tick timer counts time steps, not priorities or memory [OK]

Common Mistakes:

• Confusing tick timer with task priority management
• Thinking tick timer handles memory or I/O
• Mixing tick timer with scheduler directly

2. Which of the following is the correct way to delay a task for 100 ticks in FreeRTOS?

easy

A. xTaskDelay(100);

B. vTaskDelay(1000);

C. vTaskDelay(100);

D. delayTask(100);

Solution

1. Step 1: Identify correct function name

   The correct FreeRTOS function to delay a task is vTaskDelay().

2. Step 2: Check parameter correctness

   The parameter is the number of ticks to delay. For 100 ticks, vTaskDelay(100); is correct.

3. Final Answer:

   vTaskDelay(100); -> Option C

4. Quick Check:

   Delay task = vTaskDelay(ticks) [OK]

Hint: Use vTaskDelay with tick count to pause tasks [OK]

Common Mistakes:

• Using wrong function name like xTaskDelay or delayTask
• Passing milliseconds instead of ticks
• Using too large or incorrect delay values

3. Consider this code snippet in FreeRTOS:

TickType_t start = xTaskGetTickCount();
vTaskDelay(50);
TickType_t end = xTaskGetTickCount();
TickType_t diff = end - start;

What is the expected value of diff?

medium

A. 0

B. 50

C. 100

D. Depends on task priority

Solution

1. Step 1: Understand xTaskGetTickCount()

   This function returns the current tick count since the scheduler started.

2. Step 2: Analyze vTaskDelay(50)

   The task delays itself for 50 ticks, so the tick count advances by 50 during the delay.

3. Step 3: Calculate difference

   Subtracting start from end gives the delay duration, which should be 50 ticks.

4. Final Answer:

   50 -> Option B

5. Quick Check:

   Delay ticks = 50 [OK]

Hint: Delay of 50 ticks means tick count difference is 50 [OK]

Common Mistakes:

• Assuming delay is zero or doubled
• Thinking task priority affects tick count difference
• Confusing ticks with milliseconds

4. What is wrong with this FreeRTOS code snippet?

vTaskDelay(0);
TickType_t ticks = xTaskGetTickCount();

medium

A. vTaskDelay(0) does not delay the task

B. xTaskGetTickCount() returns an error

C. vTaskDelay requires a pointer argument

D. TickType_t is not a valid type

Solution

1. Step 1: Check vTaskDelay parameter

   Passing 0 to vTaskDelay means no delay; the task yields but continues immediately.

2. Step 2: Verify xTaskGetTickCount()

   This function correctly returns the current tick count; no error here.

3. Final Answer:

   vTaskDelay(0) does not delay the task -> Option A

4. Quick Check:

   Delay(0) means no wait [OK]

Hint: vTaskDelay(0) yields but does not pause task [OK]

Common Mistakes:

• Expecting delay with zero ticks
• Thinking xTaskGetTickCount returns error
• Misunderstanding TickType_t type

5. You want a task to run every 200 ticks precisely using FreeRTOS. Which approach ensures this timing despite task execution time?

hard

A. Use vTaskDelayUntil() with a previous wake time variable

B. Use vTaskDelay(200) at the end of the task loop

C. Use xTaskGetTickCount() inside the task and delay manually

D. Use vTaskDelay(100) twice in the task loop

Solution

1. Step 1: Understand vTaskDelay() limitation

   Using vTaskDelay(200) delays from current time, so task execution time adds up causing drift.

2. Step 2: Use vTaskDelayUntil() for fixed periodic timing

   vTaskDelayUntil() uses a previous wake time to maintain exact periodic intervals regardless of execution time.

3. Step 3: Evaluate other options

   Manual delay or multiple delays do not guarantee precise timing; only vTaskDelayUntil() does.

4. Final Answer:

   Use vTaskDelayUntil() with a previous wake time variable -> Option A

5. Quick Check:

   Precise periodic task = vTaskDelayUntil() [OK]

Hint: Use vTaskDelayUntil() for exact periodic task timing [OK]

Common Mistakes:

• Using vTaskDelay causes timing drift
• Trying manual delay calculations
• Ignoring task execution time in timing