Graceful shutdown sequence in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a graceful shutdown sequence in FreeRTOS?

A graceful shutdown sequence is a planned process to safely stop tasks and release resources before the system powers down or resets, preventing data loss or corruption.

beginner

Why should tasks notify each other during a graceful shutdown?

Tasks notify each other to coordinate stopping work, ensuring all tasks finish their current jobs and clean up properly before the system shuts down.

intermediate

Which FreeRTOS function can be used to signal a task to stop during shutdown?

The function vTaskNotifyGive() or xTaskNotify() can be used to send notifications to tasks, signaling them to start their shutdown procedures.

intermediate

What role does vTaskDelete() play in a graceful shutdown?

vTaskDelete() is used to delete tasks that have completed their shutdown process, freeing up system resources cleanly.

advanced

How can you ensure data integrity during a FreeRTOS shutdown?

By signaling tasks to finish writing data, flushing buffers, and saving state before deleting tasks and powering down, you ensure data integrity.

What is the first step in a FreeRTOS graceful shutdown sequence?

A Flush hardware buffers

B Delete all tasks immediately

C Power off the device

D Notify tasks to stop work

The first step is to notify tasks to stop their work so they can clean up properly.

Which FreeRTOS API helps a task wait for a shutdown signal?

A vTaskDelay()

B xQueueSend()

C ulTaskNotifyTake()

D vTaskStartScheduler()

ulTaskNotifyTake() allows a task to wait for a notification, useful for shutdown signaling.

Why is it important to delete tasks during shutdown?

A To speed up the CPU

B To free system resources

C To restart the scheduler

D To increase task priority

Deleting tasks frees memory and other resources, preventing leaks.

What should tasks do before calling vTaskDelete() in shutdown?

A Complete current operations and clean up

B Start new tasks

C Ignore shutdown signals

D Reset the microcontroller

Tasks should finish work and clean resources before deletion.

Which of these is NOT part of a graceful shutdown?

A Powering off immediately without cleanup

B Notifying tasks to stop

C Saving important data

D Deleting tasks after cleanup

Powering off immediately without cleanup risks data loss and corruption.

Describe the steps involved in a FreeRTOS graceful shutdown sequence.

Think about how tasks communicate and clean up before shutdown.

Explain how task notifications help in coordinating a graceful shutdown in FreeRTOS.

Focus on how tasks know when to stop.

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