Why priority design matters in FreeRTOS - Quick Recap

Recall & Review

beginner

What is task priority in FreeRTOS?

Task priority is a number assigned to each task that tells the scheduler which task should run first. Higher priority tasks run before lower priority ones.

beginner

Why is priority design important in FreeRTOS?

Priority design ensures important tasks get CPU time when needed, preventing delays in critical operations and improving system responsiveness.

intermediate

What can happen if all tasks have the same priority?

If all tasks have the same priority, the scheduler switches between them equally, which may cause critical tasks to wait too long and miss deadlines.

advanced

How does priority inversion affect a FreeRTOS system?

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 slowing the system.

advanced

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

Using priority inheritance, where the low priority task temporarily inherits the higher priority to finish quickly and release the resource.

What does a higher task priority mean in FreeRTOS?

A The task uses less memory

B The task runs before lower priority tasks

C The task runs less often

D The task runs only when idle

Higher priority tasks get CPU time before lower priority tasks.

What problem occurs if all tasks have the same priority?

A Critical tasks may be delayed

B System crashes immediately

C Tasks never switch

D Memory leaks happen

Equal priority means critical tasks might wait too long, causing delays.

What is priority inversion?

A Tasks have no priority

B High priority task runs twice

C Low priority task blocks a high priority task

D Scheduler stops working

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

How does FreeRTOS help avoid priority inversion?

A Using round-robin scheduling

B Disabling interrupts

C Increasing stack size

D Priority inheritance

Priority inheritance lets a low priority task temporarily run at higher priority to release resources faster.

Why should priority design be planned carefully?

A To ensure important tasks run on time

B To use more memory

C To slow down the system

D To avoid using interrupts

Careful priority design ensures critical tasks get CPU time when needed.

Explain why task priority design matters in FreeRTOS and what can happen if it is not done properly.

Think about which tasks need to run first and what happens if they don't.

Describe priority inversion and how FreeRTOS handles it.

Consider a low priority task holding a resource needed by a high priority task.

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