Why scheduling determines real-time behavior in FreeRTOS - Visual Breakdown

Concept Flow - Why scheduling determines real-time behavior

Task Ready

→Scheduler Chooses Highest Priority Task

↓

Task Runs

↓

Task Blocks or Yields?

Yes→Scheduler Chooses Next Task

↓

Task Continues

↓

Task Completes or Waits

↓

Scheduler Runs Again

The scheduler picks which task runs based on priority and readiness, controlling real-time response.

Execution Sample

FreeRTOS

void vTask1(void *pvParameters) {
  while(1) {
    // Task 1 code
    vTaskDelay(pdMS_TO_TICKS(10));
  }
}

A simple FreeRTOS task that runs repeatedly and delays itself to allow other tasks to run.

Execution Table

Step	Scheduler Action	Task Selected	Task State	Reason
1	Start scheduler	Task1	Running	Highest priority task ready
2	Task1 calls vTaskDelay(10)	Idle Task	Running	Task1 blocked, scheduler picks Idle
3	Delay expires	Task1	Running	Task1 ready again, highest priority
4	Task1 runs	Task1	Running	No higher priority task ready
5	Task1 blocks again	Idle Task	Running	Task1 delays again
6	No other tasks ready	Idle Task	Running	Idle runs until next task ready
7	Task1 delay expires	Task1	Running	Task1 ready, scheduler switches
8	Task1 runs	Task1	Running	Continues execution
9	Scheduler stops	-	-	End of trace

💡 Scheduler stops after tracing task delay and resume cycle

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 5	After Step 7	Final
Task1 State	Ready	Blocked (delay)	Ready	Blocked (delay)	Ready	Running
Idle Task State	Ready	Running	Ready	Running	Ready	Ready

Key Moments - 3 Insights

Why does the scheduler switch to the Idle task when Task1 calls vTaskDelay?

Because Task1 becomes blocked (not ready), the scheduler must pick another ready task, which is the Idle task (see execution_table step 2).

How does the scheduler decide when to switch back to Task1?

When Task1's delay expires, it becomes ready again, so the scheduler picks it as the highest priority ready task (see execution_table step 3 and 7).

What happens if no other tasks are ready besides Idle?

The Idle task runs continuously until another task becomes ready, ensuring CPU is never idle without a task (see execution_table steps 2, 6).

Visual Quiz - 3 Questions

Look at the execution_table at step 2, which task is running and why?

A Idle Task is running because Task1 is blocked

B Task1 is running because it just started

C Task1 is running because delay has expired

D No task is running

💡 Hint

Check the 'Task Selected' and 'Reason' columns at step 2 in execution_table

At which step does Task1 become ready again after delay?

A Step 2

B Step 4

C Step 3

D Step 6

💡 Hint

Look for when Task1 state changes from blocked to running in variable_tracker and execution_table

If Task1 never called vTaskDelay, what would the scheduler do?

A Switch to Idle task frequently

B Keep running Task1 continuously

C Switch between multiple tasks

D Stop scheduler

💡 Hint

Consider what happens when a task never blocks or yields in execution_table

Concept Snapshot

FreeRTOS scheduling picks the highest priority ready task to run.
Tasks block or delay to let others run.
Scheduler switches tasks on blocking or priority changes.
This controls real-time responsiveness.
Idle task runs only when no other task is ready.

Full Transcript

In FreeRTOS, the scheduler controls which task runs based on priority and readiness. When a task like Task1 runs and then calls vTaskDelay, it blocks itself, so the scheduler switches to the Idle task. When the delay expires, Task1 becomes ready again and the scheduler switches back to it. This cycle shows how scheduling determines real-time behavior by managing task states and CPU time. The Idle task runs only when no other tasks are ready, ensuring the CPU is never idle without a task. Understanding this flow helps grasp how FreeRTOS achieves real-time responsiveness.