Why priority design matters in FreeRTOS

Introduction

Priority design helps decide which task runs first in a program. It keeps important jobs fast and smooth.

When you have multiple tasks and some must finish quickly, like reading sensors.

When you want to avoid delays in critical actions, like stopping a machine.

When you want your program to respond fast to user input.

When some tasks can wait while others run immediately.

When you want to save power by running tasks efficiently.

Syntax

FreeRTOS

In FreeRTOS, you set priority when creating a task:

xTaskCreate(
  TaskFunction,      // Function that implements the task
  "TaskName",       // Name of the task
  StackDepth,        // Stack size in words, not bytes
  Parameters,        // Parameters to the task
  Priority,          // Priority number (higher means more important)
  &TaskHandle        // Task handle
);

Priority is a number; higher means the task runs before lower priority tasks.

Tasks with the same priority share CPU time fairly.

Examples

This creates a task named SensorTask with priority 3.

FreeRTOS

xTaskCreate(Task1, "SensorTask", 1000, NULL, 3, NULL);

This creates a LoggerTask with lower priority 1, so it runs after higher priority tasks.

FreeRTOS

xTaskCreate(Task2, "LoggerTask", 1000, NULL, 1, NULL);

Sample Program

This program creates two tasks: one high priority and one low priority. The high priority task runs first and prints its message every second. The low priority task runs only when the high priority task is waiting.

FreeRTOS

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

void HighPriorityTask(void *pvParameters) {
    for (;;) {
        printf("High priority task running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

void LowPriorityTask(void *pvParameters) {
    for (;;) {
        printf("Low priority task running\n");
        vTaskDelay(pdMS_TO_TICKS(1000));
    }
}

int main(void) {
    xTaskCreate(HighPriorityTask, "HighTask", 1000, NULL, 3, NULL);
    xTaskCreate(LowPriorityTask, "LowTask", 1000, NULL, 1, NULL);
    vTaskStartScheduler();
    return 0;
}

Important Notes

If a high priority task never waits, lower priority tasks may never run.

Design priorities carefully to avoid blocking important tasks.

Summary

Priority design controls which tasks run first.

Higher priority tasks get CPU time before lower ones.

Good priority design keeps your program fast and responsive.

Practice

1.

Why is task priority important in FreeRTOS?

easy

A. It determines which task runs first when multiple are ready.

B. It changes the task's memory size automatically.

C. It controls the task's stack overflow protection.

D. It sets the task's execution time limit.

Solution

1. Step 1: Understand task scheduling in FreeRTOS

   FreeRTOS uses task priorities to decide which task runs when multiple tasks are ready.

2. Step 2: Identify the role of priority

   The highest priority ready task gets CPU time first, ensuring important tasks run promptly.

3. Final Answer:

   It determines which task runs first when multiple are ready. -> Option A

4. Quick Check:

   Priority controls task execution order = A [OK]

Hint: Priority decides task run order, highest runs first [OK]

Common Mistakes:

• Confusing priority with memory size
• Thinking priority limits execution time
• Assuming priority controls stack protection

2.

Which of the following is the correct way to set a task priority in FreeRTOS?

vTaskPrioritySet(

easy

A. vTaskPrioritySet(TaskHandle_t xTask);

B. vTaskPrioritySet(TaskHandle_t xTask, UBaseType_t uxNewPriority);

C. vTaskPrioritySet(UBaseType_t uxNewPriority, TaskHandle_t xTask);

D. vTaskPrioritySet(UBaseType_t uxNewPriority);

Solution

1. Step 1: Recall FreeRTOS API for setting priority

   The function vTaskPrioritySet requires the task handle and the new priority as parameters.

2. Step 2: Check parameter order

   The correct order is first the task handle, then the new priority value.

3. Final Answer:

   vTaskPrioritySet(TaskHandle_t xTask, UBaseType_t uxNewPriority); -> Option B

4. Quick Check:

   Correct parameter order = C [OK]

Hint: Task handle first, then priority in vTaskPrioritySet [OK]

Common Mistakes:

• Swapping parameter order
• Missing one parameter
• Using wrong parameter types

3.

Given two tasks, TaskA with priority 3 and TaskB with priority 2, both ready to run, which task will FreeRTOS run first?

medium

A. TaskB

B. Depends on task creation order

C. Both run simultaneously

D. TaskA

Solution

1. Step 1: Compare task priorities

   TaskA has priority 3, TaskB has priority 2. Higher number means higher priority.

2. Step 2: Determine which task runs first

   FreeRTOS runs the highest priority ready task first, so TaskA runs before TaskB.

3. Final Answer:

   TaskA -> Option D

4. Quick Check:

   Higher priority runs first = B [OK]

Hint: Higher priority number runs first in FreeRTOS [OK]

Common Mistakes:

• Thinking lower number means higher priority
• Assuming tasks run simultaneously
• Believing creation order affects scheduling

4.

What is wrong with this code snippet?

vTaskPrioritySet(3, TaskHandle);

medium

A. Parameters are in wrong order.

B. Priority value 3 is invalid.

C. TaskHandle should be a number.

D. Function name is incorrect.

Solution

1. Step 1: Check function parameter order

   The correct order is (TaskHandle_t xTask, UBaseType_t uxNewPriority), but here it is reversed.

2. Step 2: Validate parameter types

   TaskHandle should be first, priority second. The code swaps them causing error.

3. Final Answer:

   Parameters are in wrong order. -> Option A

4. Quick Check:

   Correct parameter order matters = A [OK]

Hint: Task handle first, priority second in vTaskPrioritySet [OK]

Common Mistakes:

• Swapping parameters
• Using wrong data types
• Misnaming the function

5.

You have three tasks: Task1 (priority 2), Task2 (priority 2), and Task3 (priority 3). Task1 and Task2 share a resource and must not run simultaneously. How should you design priorities to keep the system responsive and safe?

hard

A. Use no priorities and rely on task delays.

B. Set all tasks to same priority to avoid conflicts.

C. Set Task3 highest priority, Task1 and Task2 equal lower priorities, use mutex for resource.

D. Set Task1 highest priority, Task2 medium, Task3 lowest.

Solution

1. Step 1: Assign highest priority to critical task

   Task3 has highest priority (3) to keep system responsive.

2. Step 2: Use equal lower priorities and mutex for shared resource

   Task1 and Task2 have same priority (2) and use a mutex to prevent simultaneous access.

3. Step 3: Avoid equal priorities without synchronization

   Equal priorities without mutex risk resource conflicts; delays reduce responsiveness.

4. Final Answer:

   Set Task3 highest priority, Task1 and Task2 equal lower priorities, use mutex for resource. -> Option C

5. Quick Check:

   Priority + mutex ensures safety and responsiveness = D [OK]

Hint: Use highest priority for critical task, mutex for shared resource [OK]

Common Mistakes:

• Ignoring resource protection
• Setting all tasks same priority without sync
• Using delays instead of priorities