Choosing priorities for real applications in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the main purpose of task priorities in FreeRTOS?

Task priorities determine the order in which tasks are scheduled to run. Higher priority tasks run before lower priority ones, ensuring critical tasks get CPU time first.

beginner

Why should you avoid giving all tasks the same priority in a real application?

If all tasks have the same priority, the scheduler switches between them in a round-robin way, which may cause important tasks to wait too long and miss deadlines.

intermediate

How does priority inversion affect real-time applications?

Priority inversion happens when a low priority task holds a resource needed by a high priority task, causing the high priority task to wait and potentially miss deadlines.

intermediate

What is a common method to prevent priority inversion in FreeRTOS?

FreeRTOS uses priority inheritance, where the low priority task temporarily inherits the higher priority to finish its work and release the resource faster.

beginner

How should you assign priorities when tasks have different timing requirements?

Assign higher priorities to tasks with stricter timing or deadlines, and lower priorities to less critical or background tasks to ensure timely execution.

In FreeRTOS, which task will run first?

A The task with the longest runtime

B The task created first

C The task with the lowest priority

D The task with the highest priority

FreeRTOS always runs the task with the highest priority that is ready to run.

What happens if two tasks have the same priority in FreeRTOS?

A They run in round-robin fashion

B They run simultaneously

C Only one runs forever

D The system crashes

Tasks with the same priority share CPU time equally using round-robin scheduling.

Which problem occurs when a low priority task blocks a high priority task?

A Deadlock

B Race condition

C Priority inversion

D Starvation

Priority inversion happens when a low priority task holds a resource needed by a high priority task.

How does FreeRTOS handle priority inversion?

A By priority inheritance

B By ignoring it

C By killing the low priority task

D By increasing system clock speed

FreeRTOS uses priority inheritance to temporarily raise the low priority task's priority.

Which task should get the highest priority?

A The task with the least work

B The task with the strictest timing requirements

C The task that runs longest

D The task created last

Tasks with strict timing or deadlines should have higher priority to meet real-time constraints.

Explain how to choose task priorities in a real FreeRTOS application.

Think about which tasks need to run first and which can wait.

Describe what priority inversion is and how FreeRTOS solves it.

Imagine a slow worker holding a tool needed by a fast worker.

Practice

1. In FreeRTOS, what does a higher task priority number mean?

easy

A. The task runs before lower priority tasks

B. The task uses less memory

C. The task runs slower

D. The task is paused

Solution

1. Step 1: Understand task priority meaning

   In FreeRTOS, task priority determines which task the scheduler runs first.

2. Step 2: Higher number means higher priority

   A higher priority number means the task is more important and runs before lower priority tasks.

3. Final Answer:

   The task runs before lower priority tasks -> Option A

4. Quick Check:

   Higher priority = runs first [OK]

Hint: Higher number means task runs first [OK]

Common Mistakes:

• Thinking higher priority means slower task
• Confusing priority with memory usage
• Assuming priority pauses the task

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

easy

A. xTaskCreate(taskFunction, "Task", stackSize, NULL, -1, NULL);

B. xTaskCreate(taskFunction, "Task", stackSize, NULL, "high", NULL);

C. xTaskCreate(taskFunction, "Task", stackSize, NULL, 5, NULL);

D. xTaskCreate(taskFunction, "Task", stackSize, NULL, 0.5, NULL);

Solution

1. Step 1: Check parameter for priority in xTaskCreate

   The fifth parameter in xTaskCreate is the task priority and must be an integer.

2. Step 2: Validate options

   xTaskCreate(taskFunction, "Task", stackSize, NULL, 5, NULL); uses integer 5, which is valid. xTaskCreate(taskFunction, "Task", stackSize, NULL, "high", NULL); uses a string, invalid. xTaskCreate(taskFunction, "Task", stackSize, NULL, -1, NULL); uses negative priority, invalid. xTaskCreate(taskFunction, "Task", stackSize, NULL, 0.5, NULL); uses float, invalid.

3. Final Answer:

   xTaskCreate(taskFunction, "Task", stackSize, NULL, 5, NULL); -> Option C

4. Quick Check:

   Priority must be integer >= 0 [OK]

Hint: Priority is an integer in xTaskCreate [OK]

Common Mistakes:

• Using string or float for priority
• Using negative numbers for priority
• Confusing parameter order

3. Given three tasks with priorities: TaskA=3, TaskB=5, TaskC=2. Which task will run first when all are ready?

medium

A. TaskA

B. They run simultaneously

C. TaskC

D. TaskB

Solution

1. Step 1: Compare task priorities

   TaskB has priority 5, TaskA has 3, TaskC has 2.

2. Step 2: Highest priority runs first

   Since 5 is highest, TaskB runs first when all are ready.

3. Final Answer:

   TaskB -> Option D

4. Quick Check:

   Highest priority = 5 = TaskB [OK]

Hint: Highest priority number runs first [OK]

Common Mistakes:

• Choosing lowest priority task
• Thinking tasks run simultaneously
• Ignoring priority values

4. You set two tasks with the same priority in FreeRTOS. What is a likely issue?

medium

A. Tasks will share CPU time but may cause unpredictable timing

B. Tasks may starve lower priority tasks

C. One task will never run

D. System will crash immediately

Solution

1. Step 1: Understand equal priority behavior

   Tasks with same priority share CPU time via time slicing.

2. Step 2: Effects of equal priority

   This can cause unpredictable timing because tasks switch frequently, but no starvation occurs.

3. Final Answer:

   Tasks will share CPU time but may cause unpredictable timing -> Option A

4. Quick Check:

   Same priority = time slicing, possible timing issues [OK]

Hint: Same priority tasks share CPU, timing may vary [OK]

Common Mistakes:

• Assuming one task never runs
• Expecting system crash
• Ignoring time slicing behavior

5. You have three tasks: SensorRead (must respond fast), DataLogging (less urgent), and UIUpdate (medium urgency). How should you assign priorities?

hard

A. DataLogging=3, UIUpdate=2, SensorRead=1

B. SensorRead=3, UIUpdate=2, DataLogging=1

C. UIUpdate=3, SensorRead=2, DataLogging=1

D. All tasks priority 1

Solution

1. Step 1: Identify task urgency

   SensorRead must respond fastest, so highest priority. UIUpdate is medium, DataLogging less urgent.

2. Step 2: Assign priorities accordingly

   Assign SensorRead=3 (highest), UIUpdate=2, DataLogging=1 (lowest).

3. Final Answer:

   SensorRead=3, UIUpdate=2, DataLogging=1 -> Option B

4. Quick Check:

   Fastest task gets highest priority [OK]

Hint: Fastest task gets highest priority [OK]

Common Mistakes:

• Giving low priority to fastest task
• Assigning same priority to all
• Reversing urgency order