vTaskDelay() for periodic tasks in FreeRTOS - Step-by-Step Execution

Concept Flow - vTaskDelay() for periodic tasks

Task starts

↓

Execute task code

↓

Call vTaskDelay(delay)

↓

Task blocked for delay ticks

↓

Delay ends, task ready

↓

Scheduler runs task again

↩Back to Execute task code

The task runs its code, then calls vTaskDelay to pause for a fixed time, making the task periodic by repeating this cycle.

Execution Sample

FreeRTOS

void Task(void *pvParameters) {
  for(;;) {
    // Do work
    vTaskDelay(100 / portTICK_PERIOD_MS);
  }
}

This task runs forever, doing work then delaying for 100 milliseconds each cycle.

Execution Table

Step	Action	Task State	Delay Time Left (ticks)	Scheduler Behavior
1	Task starts and runs code	Running	0	Task runs
2	Calls vTaskDelay(100)	Blocked	100	Task blocked, scheduler runs other tasks
3	Tick interrupt decrements delay	Blocked	99	Task still blocked
4	Tick interrupt decrements delay	Blocked	50	Task still blocked
5	Tick interrupt decrements delay	Blocked	1	Task still blocked
6	Tick interrupt decrements delay to 0	Ready	0	Task ready to run
7	Scheduler runs task again	Running	0	Task runs again
8	Task repeats loop	Running	0	Task runs
9	Calls vTaskDelay(100)	Blocked	100	Task blocked again
10	Execution continues similarly...	Blocked/Ready	Varies	Cycle repeats

💡 Task never exits; it loops forever with periodic delays.

Variable Tracker

Variable	Start	After Step 2	After Step 6	After Step 9	Final
Task State	Running	Blocked	Ready	Blocked	Repeats
Delay Time Left (ticks)	0	100	0	100	Cycles

Key Moments - 3 Insights

Why does the task become blocked after calling vTaskDelay?

Because vTaskDelay tells the scheduler to pause the task for the specified ticks, so it moves from Running to Blocked state as shown in step 2 of the execution_table.

How does the task become ready again after delay?

Each tick interrupt reduces the delay count. When it reaches zero (step 6), the task state changes from Blocked to Ready, so the scheduler can run it again.

Does vTaskDelay guarantee exact periodic timing?

vTaskDelay delays for at least the specified ticks, but actual timing depends on scheduler and other tasks. The task runs periodically but may have small timing variations.

Visual Quiz - 3 Questions

Look at the execution_table, what is the Task State immediately after calling vTaskDelay?

A Running

B Ready

C Blocked

D Suspended

💡 Hint

Check Step 2 in the execution_table where vTaskDelay is called.

At which step does the delay time left reach zero, making the task ready again?

A Step 3

B Step 6

C Step 5

D Step 7

💡 Hint

Look at the Delay Time Left column in the execution_table.

If the delay passed to vTaskDelay is doubled, how does the Delay Time Left change at Step 2?

A It doubles

B It stays the same

C It halves

D It becomes zero

💡 Hint

Refer to the Delay Time Left value at Step 2 in the execution_table.

Concept Snapshot

vTaskDelay(delayTicks) pauses a task for delayTicks ticks.
Task state changes from Running to Blocked during delay.
Delay counts down each tick until zero.
When zero, task becomes Ready and runs again.
Used to create periodic tasks with fixed wait times.

Full Transcript

This visual trace shows how vTaskDelay creates periodic tasks in FreeRTOS. The task runs its code, then calls vTaskDelay with a delay in ticks. This moves the task to Blocked state, pausing it. Each tick interrupt reduces the delay count. When the delay reaches zero, the task becomes Ready and the scheduler runs it again. This cycle repeats forever, making the task periodic. The execution table tracks task state and delay time step-by-step. Key moments explain why the task blocks and how it becomes ready again. The quiz tests understanding of task states and delay timing. This helps beginners see how vTaskDelay controls task timing visually.