Hard real-time vs soft real-time in FreeRTOS - When to Use Which

The Big Idea

What if a tiny delay in your code could cause a robot to crash or a heart to stop beating on time?

The Scenario

Imagine you are controlling a robot arm that must stop immediately if it detects an obstacle. You try to check the sensor manually in your code without strict timing rules.

The Problem

Without clear timing guarantees, your robot might react too late or inconsistently. This delay can cause accidents or damage because your code can't promise when it will respond.

The Solution

Hard real-time systems guarantee that critical tasks finish within a strict deadline every time, while soft real-time systems aim to meet deadlines but allow occasional delays. This helps you design safe and reliable control programs.

Before vs After

✗ Before

while(true) {
  if(sensor_detects_obstacle()) {
    stop_robot();
  }
  // no timing guarantees
}

✓ After

vTaskDelayUntil(&lastWakeTime, period);
if(sensor_detects_obstacle()) {
  stop_robot();
}
// guaranteed timing in hard real-time

What It Enables

This concept enables building systems that can reliably control machines or processes where timing is critical for safety and performance.

Real Life Example

In a pacemaker device, hard real-time ensures the heart receives electrical pulses exactly on time to keep a steady heartbeat, preventing life-threatening delays.

Key Takeaways

Hard real-time means strict, guaranteed timing for critical tasks.

Soft real-time allows some timing flexibility but aims to be fast.

Choosing the right type helps build safe and efficient embedded systems.

Practice

1. Which statement best describes a hard real-time system in FreeRTOS?

easy

A. Tasks can miss deadlines occasionally without major issues.

B. Tasks run only when the CPU is idle.

C. Tasks must meet deadlines strictly without any misses.

D. Tasks have no timing constraints.

Solution

1. Step 1: Understand hard real-time definition

   Hard real-time means deadlines are strict and must never be missed.

2. Step 2: Compare options with definition

   The statement 'Tasks must meet deadlines strictly without any misses' matches the definition of hard real-time.

3. Final Answer:

   Tasks must meet deadlines strictly without any misses. -> Option C

4. Quick Check:

   Hard real-time = strict deadlines [OK]

Hint: Hard real-time means no deadline misses allowed [OK]

Common Mistakes:

• Confusing hard real-time with soft real-time
• Thinking tasks run only when CPU is idle
• Ignoring timing constraints

2. Which FreeRTOS API function is used to delay a task for a specific time period?

easy

A. vTaskDelay()

B. xTaskCreate()

C. vTaskStartScheduler()

D. xQueueSend()

Solution

1. Step 1: Identify delay function in FreeRTOS

   vTaskDelay() pauses a task for a given tick count, controlling timing.

2. Step 2: Check other options

   xTaskCreate() creates tasks, vTaskStartScheduler() starts the OS, xQueueSend() sends to queues.

3. Final Answer:

   vTaskDelay() -> Option A

4. Quick Check:

   Delay task = vTaskDelay() [OK]

Hint: Delay tasks with vTaskDelay() in FreeRTOS [OK]

Common Mistakes:

• Confusing task creation with delay
• Using scheduler start as delay
• Mixing queue functions with delays

3. Consider this FreeRTOS task priority setup:

Task A priority = 3
Task B priority = 2
Task C priority = 1

If Task A blocks for 100ms using vTaskDelay(), which task runs next?

medium

A. Task A again immediately

B. Task B

C. Task C

D. No task runs until Task A finishes delay

Solution

1. Step 1: Understand task priorities and blocking

   Task A has highest priority (3) but blocks for 100ms, so it is not ready.

2. Step 2: Identify next highest priority ready task

   Task B has priority 2 and is ready, so it runs next.

3. Final Answer:

   Task B -> Option B

4. Quick Check:

   Next task after blocking = highest ready priority [OK]

Hint: Next runs highest priority ready task after delay [OK]

Common Mistakes:

• Assuming blocked task runs immediately
• Ignoring task priorities
• Thinking no task runs during delay

4. Identify the error in this FreeRTOS code snippet for a hard real-time task:

void vTaskFunction(void *pvParameters) {
  while(1) {
    // Critical processing
    vTaskDelay(1000);
  }
}

What is the problem?

medium

A. vTaskDelay should be replaced with vTaskDelete.

B. The task function lacks a return statement.

C. The infinite loop will crash FreeRTOS.

D. Using vTaskDelay causes deadline misses in hard real-time tasks.

Solution

1. Step 1: Analyze vTaskDelay in hard real-time context

   vTaskDelay pauses the task, which can cause missing strict deadlines in hard real-time.

2. Step 2: Check other options for correctness

   Return statement is not needed in infinite loop, infinite loops are normal, vTaskDelete deletes task, not delay.

3. Final Answer:

   Using vTaskDelay causes deadline misses in hard real-time tasks. -> Option D

4. Quick Check:

   Hard real-time tasks avoid vTaskDelay [OK]

Hint: Hard real-time tasks avoid delays that cause misses [OK]

Common Mistakes:

• Thinking infinite loops crash FreeRTOS
• Confusing vTaskDelay with task deletion
• Expecting return in infinite loops

5. You need to design a FreeRTOS system where some tasks must never miss deadlines (hard real-time), and others can miss occasionally (soft real-time). Which approach best achieves this?

hard

A. Assign highest priorities to hard real-time tasks and use vTaskDelay carefully for soft real-time tasks.

B. Use vTaskDelay for all tasks to simplify timing.

C. Assign equal priorities to all tasks and rely on round-robin scheduling.

D. Run hard real-time tasks only when soft real-time tasks are idle.

Solution

1. Step 1: Understand priority and delay roles in FreeRTOS

   Hard real-time tasks need highest priority to avoid preemption and deadline misses.

2. Step 2: Use vTaskDelay carefully for soft real-time tasks

   Soft real-time tasks can tolerate delays, so vTaskDelay helps manage their timing without affecting hard real-time tasks.

3. Step 3: Evaluate other options

   Equal priorities or running hard real-time tasks only when soft are idle do not guarantee deadlines.

4. Final Answer:

   Assign highest priorities to hard real-time tasks and use vTaskDelay carefully for soft real-time tasks. -> Option A

5. Quick Check:

   Priority + careful delay = mixed real-time system [OK]

Hint: Prioritize hard real-time tasks highest, delay soft tasks [OK]

Common Mistakes:

• Giving equal priority to all tasks
• Using delays in hard real-time tasks
• Running hard real-time tasks only after soft tasks