Task starvation and priority inversion in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is task starvation in FreeRTOS?

Task starvation happens when a low-priority task never gets CPU time because higher-priority tasks keep running. It means the low-priority task is 'starved' of processing time.

intermediate

Explain priority inversion in FreeRTOS.

Priority inversion occurs when a high-priority task waits for a resource held by a low-priority task, but a medium-priority task keeps running and blocks the low-priority task from releasing the resource.

intermediate

How does FreeRTOS help prevent priority inversion?

FreeRTOS uses priority inheritance. When a low-priority task holds a resource needed by a high-priority task, it temporarily inherits the higher priority to finish quickly and release the resource.

beginner

What is a real-life example of task starvation?

Imagine a busy cashier (high priority) always serving customers, so the cleaner (low priority) never gets a chance to clean the floor. The cleaner is starved of time.

beginner

Why is task starvation a problem in real-time systems?

Because some tasks may never run, causing missed deadlines or system failures. Real-time systems need all tasks to run on time to work correctly.

What causes task starvation in FreeRTOS?

A High-priority tasks always running and blocking low-priority tasks

B Low-priority tasks running too fast

C All tasks having the same priority

D Using too many semaphores

Task starvation happens when high-priority tasks keep running and prevent low-priority tasks from executing.

What is priority inversion?

A A low-priority task blocking a high-priority task indirectly

B A high-priority task running before a low-priority task

C All tasks running at the same priority

D A task losing its priority permanently

Priority inversion is when a low-priority task holds a resource needed by a high-priority task, causing the high-priority task to wait.

How does FreeRTOS solve priority inversion?

A By disabling interrupts

B By killing low-priority tasks

C By increasing stack size

D By using priority inheritance

FreeRTOS uses priority inheritance to temporarily raise the priority of the low-priority task holding the resource.

Which of these is a symptom of task starvation?

A All tasks run equally

B Tasks run out of memory

C A task never gets CPU time

D Tasks crash randomly

Task starvation means some tasks never get CPU time because others keep running.

Why is priority inversion dangerous in real-time systems?

A It speeds up low-priority tasks too much

B It can cause high-priority tasks to miss deadlines

C It disables interrupts

D It causes memory leaks

Priority inversion can delay high-priority tasks, causing them to miss critical deadlines.

Describe task starvation and how it affects system behavior in FreeRTOS.

Think about what happens when some tasks never get CPU time.

Explain priority inversion and how FreeRTOS uses priority inheritance to solve it.

Consider how a low-priority task can block a high-priority task.

Practice

1. What does task starvation mean in FreeRTOS?

easy

A. Some tasks never get CPU time because others run too much

B. All tasks get equal CPU time regardless of priority

C. Tasks run in a random order without priority

D. Tasks share CPU time only when a mutex is free

Solution

1. Step 1: Understand task scheduling in FreeRTOS

   FreeRTOS schedules tasks based on priority, so higher priority tasks run more often.

2. Step 2: Define task starvation

   Task starvation happens when low priority tasks never get CPU time because higher priority tasks keep running.

3. Final Answer:

   Some tasks never get CPU time because others run too much -> Option A

4. Quick Check:

   Task starvation = some tasks starve for CPU [OK]

Hint: Starvation means some tasks get no CPU time [OK]

Common Mistakes:

• Confusing starvation with equal CPU sharing
• Thinking tasks run randomly
• Assuming mutex controls CPU time directly

2. Which FreeRTOS API is used to create a mutex that supports priority inheritance?

easy

A. xQueueCreate()

B. xSemaphoreCreateMutex()

C. vTaskDelay()

D. xTaskCreate()

Solution

1. Step 1: Identify mutex creation functions

   FreeRTOS uses xSemaphoreCreateMutex() to create mutexes with priority inheritance.

2. Step 2: Differentiate other APIs

   xQueueCreate() creates queues, vTaskDelay() delays tasks, and xTaskCreate() creates tasks, not mutexes.

3. Final Answer:

   xSemaphoreCreateMutex() -> Option B

4. Quick Check:

   Mutex with priority inheritance = xSemaphoreCreateMutex() [OK]

Hint: Mutex with priority inheritance uses xSemaphoreCreateMutex() [OK]

Common Mistakes:

• Choosing xQueueCreate() for mutex
• Confusing task creation with mutex creation
• Using delay functions instead of mutex APIs

3. Given three tasks with priorities High (3), Medium (2), and Low (1). Low task holds a mutex needed by High task. What happens without priority inheritance?

medium

A. Medium task is blocked until High task finishes

B. Low task immediately releases the mutex

C. High task waits indefinitely while Medium task runs

D. High task preempts Low task and runs

Solution

1. Step 1: Understand priority inversion scenario

   Low priority task holds mutex needed by High priority task, so High task blocks waiting.

2. Step 2: Effect without priority inheritance

   Medium priority task runs, preventing Low task from running and releasing mutex, causing High task to wait indefinitely.

3. Final Answer:

   High task waits indefinitely while Medium task runs -> Option C

4. Quick Check:

   Priority inversion without inheritance = High task blocked [OK]

Hint: Without inheritance, medium task blocks low task, blocking high task [OK]

Common Mistakes:

• Assuming low task releases mutex immediately
• Thinking high task preempts low task despite mutex
• Believing medium task is blocked

4. Identify the problem in this FreeRTOS code snippet causing priority inversion:

void lowTask(void *pvParameters) {
  xSemaphoreTake(mutex, portMAX_DELAY);
  // long processing
  xSemaphoreGive(mutex);
  vTaskDelete(NULL);
}

void highTask(void *pvParameters) {
  xSemaphoreTake(mutex, portMAX_DELAY);
  // quick processing
  xSemaphoreGive(mutex);
  vTaskDelete(NULL);
}

medium

A. Mutex created without priority inheritance support

B. High task does not take the mutex

C. Low task never releases the mutex

D. Tasks have the same priority

Solution

1. Step 1: Analyze mutex usage in code

   Both tasks take and give the mutex correctly, so no misuse in code logic.

2. Step 2: Check for priority inversion cause

   If mutex was created without priority inheritance, low task holding mutex blocks high task causing priority inversion.

3. Final Answer:

   Mutex created without priority inheritance support -> Option A

4. Quick Check:

   Priority inversion fix needs mutex with priority inheritance [OK]

Hint: Check if mutex supports priority inheritance to fix inversion [OK]

Common Mistakes:

• Assuming high task does not take mutex
• Thinking low task never releases mutex
• Believing tasks have same priority

5. How can you prevent task starvation and priority inversion in a FreeRTOS system with multiple tasks sharing resources?

hard

A. Use busy-wait loops in low priority tasks to keep CPU busy

B. Assign all tasks the same priority to avoid conflicts

C. Avoid using any synchronization primitives like mutexes

D. Use mutexes with priority inheritance and design balanced task priorities

Solution

1. Step 1: Understand causes of starvation and inversion

   Starvation happens when low priority tasks never run; inversion when low priority blocks high priority.

2. Step 2: Apply solutions in FreeRTOS

   Using mutexes with priority inheritance prevents inversion; balanced priorities avoid starvation.

3. Final Answer:

   Use mutexes with priority inheritance and design balanced task priorities -> Option D

4. Quick Check:

   Priority inheritance + balanced priorities prevent issues [OK]

Hint: Combine priority inheritance mutexes with balanced priorities [OK]

Common Mistakes:

• Setting all tasks to same priority causing inefficiency
• Avoiding mutexes causing race conditions
• Using busy-wait wastes CPU and worsens starvation