vTaskPrioritySet() dynamic priority in FreeRTOS - Step-by-Step Execution

Concept Flow - vTaskPrioritySet() dynamic priority

Start with Task at Priority P

↓

Call vTaskPrioritySet(Task, NewPriority)

↓

Check if NewPriority is valid

↓

Update Task Priority

↓

Scheduler adjusts task order

↓

Task runs with new priority

This flow shows how calling vTaskPrioritySet changes a task's priority dynamically, then the scheduler updates task order accordingly.

Execution Sample

FreeRTOS

vTaskPrioritySet(xTaskHandle, 3);
// Task priority changes from 1 to 3
// Scheduler reorders tasks based on new priority

This code changes a task's priority from 1 to 3 dynamically at runtime.

Execution Table

Step	Action	Current Priority	New Priority	Scheduler Reaction	Result
1	Task created	1	-	Task added to ready list at priority 1	Task priority = 1
2	Call vTaskPrioritySet(xTaskHandle, 3)	1	3	Scheduler reorders tasks	Task priority updated to 3
3	Scheduler runs	3	-	Task moved to higher priority queue	Task runs sooner
4	Call vTaskPrioritySet(xTaskHandle, 0)	3	0	Scheduler reorders tasks	Task priority updated to 0 (lowest)
5	Scheduler runs	0	-	Task moved to lowest priority queue	Task runs later
6	Call vTaskPrioritySet(xTaskHandle, 6)	0	6	Scheduler reorders tasks	Task priority updated to 6 (highest)
7	Scheduler runs	6	-	Task moved to highest priority queue	Task runs immediately
8	Call vTaskPrioritySet(xTaskHandle, 10)	6	10	Invalid priority (above max)	Priority unchanged, error handled
9	End	-	-	-	Execution stops

💡 Execution stops after invalid priority attempt or normal completion

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	After Step 8	Final
Task Priority	1	3	0	6	6	6

Key Moments - 3 Insights

Why doesn't the task priority change when an invalid priority is set?

Because vTaskPrioritySet checks if the new priority is within valid limits before updating. See execution_table row 8 where priority 10 is invalid, so priority stays at 6.

How does changing priority affect when the task runs?

Scheduler moves the task to the queue matching its new priority. Higher priority tasks run sooner. See rows 3, 5, and 7 for scheduler reactions.

Can a task priority be set lower than zero?

No, priorities below zero are invalid and ignored, similar to above max priority. This prevents errors and keeps scheduler stable.

Visual Quiz - 3 Questions

Look at the execution_table at step 4, what is the task priority after vTaskPrioritySet is called?

A 3

B 6

C 0

D 1

💡 Hint

Check the 'New Priority' and 'Result' columns at step 4 in execution_table.

At which step does the scheduler move the task to the highest priority queue?

A Step 7

B Step 5

C Step 3

D Step 2

💡 Hint

Look for 'Task moved to highest priority queue' in the Scheduler Reaction column.

If you try to set a task priority above the max allowed, what happens according to the execution_table?

A Priority is set to max allowed

B Priority remains unchanged and error is handled

C Priority is set to zero

D Task is deleted

💡 Hint

See step 8 in execution_table for handling invalid priority.

Concept Snapshot

vTaskPrioritySet(TaskHandle, NewPriority)
- Changes task priority dynamically
- Scheduler reorders tasks immediately
- NewPriority must be valid (0 to configMAX_PRIORITIES-1)
- Higher priority tasks run before lower ones
- Invalid priorities are ignored

Full Transcript

This visual trace shows how vTaskPrioritySet changes a FreeRTOS task's priority at runtime. Starting with a task at priority 1, calling vTaskPrioritySet with a new priority updates the task's priority if valid. The scheduler then reorders tasks so higher priority tasks run sooner. If an invalid priority is given, the change is ignored to keep system stability. The variable tracker shows the task priority changing step-by-step. Key moments clarify why invalid priorities don't change the task and how priority affects scheduling. The quiz tests understanding of priority changes and scheduler reactions.