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.

Practice

1. What is the main purpose of a graceful shutdown sequence in FreeRTOS?

easy

A. To immediately stop all tasks without waiting

B. To restart the scheduler automatically

C. To allow tasks to finish their work safely before stopping

D. To delete all tasks without cleanup

Solution

1. Step 1: Understand graceful shutdown concept

   Graceful shutdown means letting tasks complete their current work safely before stopping.

2. Step 2: Compare options

   Only To allow tasks to finish their work safely before stopping describes this safe stopping process; others describe abrupt or incorrect actions.

3. Final Answer:

   To allow tasks to finish their work safely before stopping -> Option C

4. Quick Check:

   Graceful shutdown = safe task completion [OK]

Hint: Graceful shutdown means safe stop, not immediate kill [OK]

Common Mistakes:

• Thinking shutdown means immediate task stop
• Confusing restart with shutdown
• Ignoring task cleanup before stopping

2. Which FreeRTOS function is commonly used to notify a task to start its shutdown process?

easy

A. vTaskDelete()

B. xTaskNotifyGive()

C. vTaskStartScheduler()

D. xQueueSend()

Solution

1. Step 1: Identify notification function

   xTaskNotifyGive() is used to send a notification to a task, often to signal events like shutdown.

2. Step 2: Eliminate other options

   vTaskDelete() deletes a task immediately, vTaskStartScheduler() starts the scheduler, xQueueSend() sends data to a queue, not a direct notification.

3. Final Answer:

   xTaskNotifyGive() -> Option B

4. Quick Check:

   Notify task to shutdown = xTaskNotifyGive() [OK]

Hint: Use xTaskNotifyGive() to signal tasks for shutdown [OK]

Common Mistakes:

• Using vTaskDelete() to notify instead of delete
• Confusing scheduler start with notification
• Sending shutdown signal via queue instead of notification

3. Given the code below, what will be the output if the shutdown flag is set to true?

bool shutdownFlag = false;
void TaskFunction(void *pvParameters) {
  while (!shutdownFlag) {
    // Do work
  }
  printf("Task stopped safely\n");
}

int main() {
  shutdownFlag = true;
  TaskFunction(NULL);
  return 0;
}

medium

A. Task stopped safely

B. No output, infinite loop

C. Compilation error

D. Task continues running

Solution

1. Step 1: Analyze the loop condition

   The loop runs while shutdownFlag is false. Since shutdownFlag is set true before calling TaskFunction, the loop is skipped.

2. Step 2: Check what happens after loop

   After the loop, the printf prints "Task stopped safely".

3. Final Answer:

   Task stopped safely -> Option A

4. Quick Check:

   shutdownFlag true skips loop, prints message [OK]

Hint: If shutdown flag true, loop exits and prints message [OK]

Common Mistakes:

• Assuming loop runs infinitely
• Confusing flag initial value
• Expecting compilation error due to bool usage

4. Identify the error in this shutdown sequence code snippet:

void ShutdownTask(void *pvParameters) {
  vTaskDelete(NULL);
  // Cleanup code here
}

medium

A. Task should call vTaskStartScheduler() before deletion

B. vTaskDelete(NULL) deletes all tasks, causing crash

C. Missing call to vTaskSuspendAll() before deletion

D. Cleanup code runs after task deletion, so it never executes

Solution

1. Step 1: Understand vTaskDelete behavior

   vTaskDelete(NULL) deletes the current task immediately, stopping execution at that point.

2. Step 2: Check code after deletion

   Cleanup code after vTaskDelete(NULL) will never run because the task is deleted before it.

3. Final Answer:

   Cleanup code runs after task deletion, so it never executes -> Option D

4. Quick Check:

   vTaskDelete stops task immediately, no code after runs [OK]

Hint: Code after vTaskDelete(NULL) won't run [OK]

Common Mistakes:

• Assuming cleanup runs after vTaskDelete
• Thinking vTaskDelete(NULL) deletes all tasks
• Confusing suspend with delete

5. You want to implement a graceful shutdown where multiple tasks stop safely before the scheduler stops. Which sequence is correct?

A) Set shutdown flag -> Wait for tasks to confirm stop -> Call vTaskEndScheduler()
B) Call vTaskEndScheduler() -> Set shutdown flag -> Tasks stop
C) Delete tasks immediately -> Set shutdown flag -> Stop scheduler
D) Stop scheduler -> Set shutdown flag -> Tasks stop

hard

A. Set shutdown flag -> Wait for tasks to confirm stop -> Call vTaskEndScheduler()

B. Call vTaskEndScheduler() -> Set shutdown flag -> Tasks stop

C. Delete tasks immediately -> Set shutdown flag -> Stop scheduler

D. Stop scheduler -> Set shutdown flag -> Tasks stop

Solution

1. Step 1: Understand graceful shutdown steps

   First, signal tasks to stop by setting a shutdown flag or notification.

2. Step 2: Wait for tasks to confirm they stopped

   Ensure tasks finish cleanup and confirm they stopped before stopping the scheduler.

3. Step 3: Stop the scheduler safely

   Call vTaskEndScheduler() only after tasks have stopped to avoid abrupt termination.

4. Final Answer:

   Set shutdown flag -> Wait for tasks to confirm stop -> Call vTaskEndScheduler() -> Option A

5. Quick Check:

   Signal tasks -> wait -> stop scheduler = correct shutdown [OK]

Hint: Signal tasks first, wait, then stop scheduler [OK]

Common Mistakes:

• Stopping scheduler before tasks finish
• Deleting tasks immediately without cleanup
• Setting flag after scheduler stops