Tick timer and scheduler in FreeRTOS - Mini Project: Build & Apply

Tick Timer and Scheduler in FreeRTOS

📖 Scenario: You are working on a simple embedded system using FreeRTOS. Your task is to set up the tick timer and create a basic scheduler that switches between two tasks periodically.

🎯 Goal: Build a FreeRTOS program that initializes the tick timer, creates two tasks, and uses the scheduler to switch between them, printing messages to show task execution.

📋 What You'll Learn

Create two tasks named Task1 and Task2

Set up the FreeRTOS tick timer with a tick rate of 1000 Hz

Use the FreeRTOS scheduler to switch between the tasks

Each task should print a message indicating it is running

Run the scheduler to start task switching

💡 Why This Matters

🌍 Real World

Embedded systems often use FreeRTOS to manage multiple tasks like sensor reading, communication, and control loops efficiently.

💼 Career

Understanding FreeRTOS tick timer and scheduler is essential for embedded software developers working on real-time applications.

1

Create two FreeRTOS tasks

Write code to create two tasks named Task1 and Task2 using xTaskCreate. Each task should run a function that prints a unique message in an infinite loop with a delay.

FreeRTOS

#include "FreeRTOS.h"
#include "task.h"
#include 

void Task1(void *pvParameters) {
    while(1) {
        printf("Task 1 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

void Task2(void *pvParameters) {
    while(1) {
        printf("Task 2 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

int main(void) {
    // Create Task1 using xTaskCreate
    // Create Task2 using xTaskCreate
    return 0;
}

Hint

Use xTaskCreate to create each task with the function name, a name string, stack size, parameters as NULL, priority 1, and no task handle.

2

Configure the FreeRTOS tick timer rate

Add a macro definition to set the FreeRTOS tick rate to 1000 Hz by defining configTICK_RATE_HZ as 1000 before including FreeRTOS headers.

FreeRTOS

#define configTICK_RATE_HZ 1000
// Your code here

#include "FreeRTOS.h"
#include "task.h"
#include 

void Task1(void *pvParameters) {
    while(1) {
        printf("Task 1 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

void Task2(void *pvParameters) {
    while(1) {
        printf("Task 2 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

int main(void) {
    xTaskCreate(Task1, "Task1", configMINIMAL_STACK_SIZE, NULL, 1, NULL);
    xTaskCreate(Task2, "Task2", configMINIMAL_STACK_SIZE, NULL, 1, NULL);
    return 0;
}

Hint

Define configTICK_RATE_HZ before including FreeRTOS headers to set the tick timer frequency.

3

Start the FreeRTOS scheduler

Add a call to vTaskStartScheduler() in main() after creating the tasks to start the FreeRTOS scheduler and begin task switching.

FreeRTOS

#define configTICK_RATE_HZ 1000

#include "FreeRTOS.h"
#include "task.h"
#include 

void Task1(void *pvParameters) {
    while(1) {
        printf("Task 1 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

void Task2(void *pvParameters) {
    while(1) {
        printf("Task 2 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

int main(void) {
    xTaskCreate(Task1, "Task1", configMINIMAL_STACK_SIZE, NULL, 1, NULL);
    xTaskCreate(Task2, "Task2", configMINIMAL_STACK_SIZE, NULL, 1, NULL);
    // Start the scheduler here
    return 0;
}

Hint

Call vTaskStartScheduler() after creating tasks to start the FreeRTOS scheduler.

4

Run and observe task switching output

Run the program and observe the output. It should print alternating messages from Task 1 is running and Task 2 is running every second.

FreeRTOS

#define configTICK_RATE_HZ 1000

#include "FreeRTOS.h"
#include "task.h"
#include 

void Task1(void *pvParameters) {
    while(1) {
        printf("Task 1 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

void Task2(void *pvParameters) {
    while(1) {
        printf("Task 2 is running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

int main(void) {
    xTaskCreate(Task1, "Task1", configMINIMAL_STACK_SIZE, NULL, 1, NULL);
    xTaskCreate(Task2, "Task2", configMINIMAL_STACK_SIZE, NULL, 1, NULL);
    vTaskStartScheduler();
    // Observe output
}

Hint

Run the program on a FreeRTOS-supported environment or simulator to see the alternating task messages every second.

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