Graceful shutdown sequence in FreeRTOS - Step-by-Step Execution

Concept Flow - Graceful shutdown sequence

Receive shutdown signal

↓

Notify tasks to stop

↓

Complete current operations

↓

Release resources

↓

Delete tasks

↓

Stop scheduler

↓

System powered down

The system receives a shutdown signal, tells tasks to stop, waits for them to finish, cleans up, then stops the scheduler and powers down.

Execution Sample

FreeRTOS

void shutdown_sequence() {
  notify_tasks_stop();
  wait_tasks_complete();
  release_resources();
  vTaskEndScheduler();
}

This function runs the graceful shutdown by notifying tasks, waiting, cleaning up, and stopping the scheduler.

Execution Table

Step	Action	Details	Result
1	Receive shutdown signal	External event triggers shutdown	Start shutdown_sequence() called
2	notify_tasks_stop()	Send stop notification to all tasks	Tasks begin stopping work
3	wait_tasks_complete()	Wait until all tasks confirm stopped	All tasks have stopped safely
4	release_resources()	Free memory, close peripherals	Resources freed
5	vTaskEndScheduler()	Stop FreeRTOS scheduler	Scheduler stopped, system idle
6	System powered down	Hardware powers off or resets	Shutdown complete

💡 All tasks stopped and resources freed, scheduler stopped, system shutdown complete

Variable Tracker

Variable	Start	After notify_tasks_stop	After wait_tasks_complete	After release_resources	After vTaskEndScheduler	Final
tasks_running	true	false (tasks notified)	false (tasks stopped)	false	false (scheduler stopped)	N/A
resources_allocated	true	true	true	false	false	false
scheduler_running	true	true	true	true	false	false

Key Moments - 3 Insights

Why do we wait for tasks to complete instead of deleting them immediately?

Waiting ensures tasks finish their current work safely, avoiding data loss or corruption, as shown in step 3 of the execution_table.

What happens if we call vTaskEndScheduler() before wait_tasks_complete()?

The scheduler stops but tasks may still be running, causing undefined behavior. The correct order is wait_tasks_complete first (step 3), then stopping scheduler (step 5).

What is the role of vTaskEndScheduler() in the shutdown sequence?

It stops the scheduler after tasks are stopped and resources released, preventing further switching and enabling clean power down, as shown in step 5.

Visual Quiz - 3 Questions

Look at the execution_table, at which step do all tasks confirm they have stopped?

A Step 3

B Step 4

C Step 2

D Step 5

💡 Hint

Check the 'Details' column for step 3 where tasks confirm stopped.

According to variable_tracker, what is the state of 'scheduler_running' after vTaskEndScheduler()?

A true

B undefined

C false

D still running

💡 Hint

Look at the 'scheduler_running' row under 'Final' column.

If we skip release_resources(), what would be the state of 'resources_allocated' after shutdown?

A false

B true

C N/A

D unknown

💡 Hint

Refer to variable_tracker row 'resources_allocated' after 'release_resources' step.

Concept Snapshot

Graceful shutdown in FreeRTOS:
1. Notify tasks to stop
2. Wait for tasks to finish
3. Release resources
4. Stop scheduler
Ensures safe system power down without data loss.

Full Transcript

In FreeRTOS, a graceful shutdown sequence starts when the system receives a shutdown signal. It notifies all running tasks to stop their work. Then it waits until all tasks confirm they have stopped to avoid data loss. After that, it releases all allocated resources like memory and peripherals. Finally, the scheduler is stopped, and the system powers down safely. This sequence ensures all parts stop in the right order for a clean shutdown.