Why priority design matters in FreeRTOS - Visual Breakdown

Concept Flow - Why priority design matters

Start Tasks

↓

Task with Highest Priority Runs

↓

Lower Priority Tasks Wait

↓

If Higher Priority Task Blocks or Delays

↓

Next Highest Priority Task Runs

↓

Repeat Until All Tasks Complete or Blocked

Tasks run based on priority: highest priority ready task runs first, lower priority tasks wait. Proper priority design avoids blocking important tasks.

Execution Sample

FreeRTOS

Task1 (Priority 3) runs
Task2 (Priority 2) runs
Task3 (Priority 1) runs
Higher priority tasks preempt lower ones

Shows how tasks with different priorities run, with higher priority tasks running before lower ones.

Execution Table

Step	Running Task	Task Priorities	Action	Result
1	Task1	Task1=3, Task2=2, Task3=1	Task1 starts running	Task1 runs
2	Task1	Task1=3, Task2=2, Task3=1	Task1 continues	Task1 runs
3	Task2	Task1=3 (blocked), Task2=2, Task3=1	Task1 blocks, Task2 runs	Task2 runs
4	Task2	Task1=3 (blocked), Task2=2, Task3=1	Task2 continues	Task2 runs
5	Task3	Task1=3 (blocked), Task2=2 (blocked), Task3=1	Task2 blocks, Task3 runs	Task3 runs
6	Idle	All tasks blocked	All tasks blocked, idle runs	Idle runs
7	Task1	Task1=3 ready	Task1 ready again, preempts idle	Task1 runs

💡 Execution stops when all tasks are blocked or completed.

Variable Tracker

Variable	Start	After Step 3	After Step 5	After Step 7
Task1 State	Ready	Blocked	Blocked	Ready
Task2 State	Ready	Running	Blocked	Blocked
Task3 State	Ready	Ready	Running	Blocked
CPU Running Task	Task1	Task2	Task3	Task1

Key Moments - 3 Insights

Why does Task2 run only after Task1 blocks?

Because Task1 has higher priority (3) and runs first; Task2 (priority 2) runs only when Task1 is blocked, as shown in execution_table step 3.

What happens if a higher priority task becomes ready while a lower priority task is running?

The higher priority task preempts the lower priority one immediately, as seen in step 7 where Task1 preempts idle.

Why is priority design important in FreeRTOS?

To ensure critical tasks run promptly and lower priority tasks do not block them, preventing delays or missed deadlines.

Visual Quiz - 3 Questions

Look at the execution_table, which task runs at step 5?

A Task1

B Task3

C Task2

D Idle

💡 Hint

Check the 'Running Task' column at step 5 in execution_table.

At which step does Task1 become blocked?

A Step 3

B Step 1

C Step 5

D Step 7

💡 Hint

Look at Task1 State in variable_tracker after step 3.

If Task1 never blocks, what happens to Task2 and Task3?

A They run normally after Task1

B They run simultaneously with Task1

C They never get CPU time

D They run before Task1

💡 Hint

Recall that higher priority tasks preempt lower ones; see concept_flow and execution_table.

Concept Snapshot

FreeRTOS runs tasks by priority.
Highest priority ready task runs first.
Lower priority tasks wait if higher priority is ready.
Proper priority design avoids blocking critical tasks.
Preemption ensures responsiveness.
Blocking or delays let lower priority tasks run.

Full Transcript

In FreeRTOS, tasks have priorities. The system always runs the highest priority task that is ready. Lower priority tasks wait until higher priority tasks block or delay. This ensures important tasks get CPU time first. If a higher priority task becomes ready while a lower priority task runs, it preempts the lower one immediately. Proper priority design is important to avoid blocking critical tasks and to keep the system responsive. The execution table shows tasks running step-by-step based on their priority and state changes. Variable tracking shows how task states and CPU running task change over time.