Hard real-time vs soft real-time in FreeRTOS

Introduction

Understanding hard and soft real-time helps you design systems that respond on time. This is important for safety and performance.

When building a system that controls a car's brakes (hard real-time).

When making a video player that should avoid delays but can tolerate some (soft real-time).

When programming a robot arm that must move exactly on schedule (hard real-time).

When creating a sensor data logger where occasional delays are okay (soft real-time).

Syntax

FreeRTOS

// FreeRTOS does not have special syntax for hard or soft real-time.
// It depends on how you design tasks and priorities.

// Example task creation:
xTaskCreate(TaskFunction, "TaskName", stackSize, parameters, priority, &taskHandle);

FreeRTOS uses task priorities to help meet timing needs.

Hard real-time means missing a deadline is a failure; soft real-time means occasional misses are allowed.

Examples

This task runs with the highest priority to meet strict deadlines.

FreeRTOS

// Hard real-time task example
void HardRealTimeTask(void *pvParameters) {
    TickType_t xLastWakeTime = xTaskGetTickCount();
    const TickType_t xFrequency = pdMS_TO_TICKS(50);
    for(;;) {
        // Do critical work
        vTaskDelayUntil(&xLastWakeTime, xFrequency);
    }
}

// Created with high priority
xTaskCreate(HardRealTimeTask, "HardTask", 1000, NULL, configMAX_PRIORITIES - 1, NULL);

This task runs with lower priority and can tolerate some delay.

FreeRTOS

// Soft real-time task example
void SoftRealTimeTask(void *pvParameters) {
    for(;;) {
        // Do less critical work
        vTaskDelay(pdMS_TO_TICKS(100));
    }
}

// Created with lower priority
xTaskCreate(SoftRealTimeTask, "SoftTask", 1000, NULL, 1, NULL);

Sample Program

This program creates two tasks: one hard real-time with high priority running every 50 ms, and one soft real-time with lower priority running every 200 ms.

FreeRTOS

#include "FreeRTOS.h"
#include "task.h"
#include <stdio.h>

void HardRealTimeTask(void *pvParameters) {
    TickType_t xLastWakeTime = xTaskGetTickCount();
    const TickType_t xFrequency = pdMS_TO_TICKS(50); // 50 ms
    for(;;) {
        printf("Hard real-time task running\n");
        vTaskDelayUntil(&xLastWakeTime, xFrequency);
    }
}

void SoftRealTimeTask(void *pvParameters) {
    for(;;) {
        printf("Soft real-time task running\n");
        vTaskDelay(pdMS_TO_TICKS(200)); // 200 ms
    }
}

int main(void) {
    xTaskCreate(HardRealTimeTask, "HardTask", 1000, NULL, configMAX_PRIORITIES - 1, NULL);
    xTaskCreate(SoftRealTimeTask, "SoftTask", 1000, NULL, 1, NULL);
    vTaskStartScheduler();
    for(;;); // Should never reach here
    return 0;
}

Important Notes

Hard real-time tasks must finish work before their deadline every time.

Soft real-time tasks can miss deadlines sometimes without big problems.

Use task priorities and timing functions in FreeRTOS to manage real-time behavior.

Summary

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

Soft real-time means deadlines are important but can be missed occasionally.

FreeRTOS helps by letting you set task priorities and delays to control timing.

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