Hard real-time vs soft real-time in FreeRTOS - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding Hard Real-Time Systems

Which statement best describes a hard real-time system?

A A system where every deadline must be met strictly, or the system fails.

B A system where missing a deadline occasionally is acceptable without serious consequences.

C A system that processes tasks without any timing constraints.

D A system that prioritizes tasks randomly without deadlines.

💡 Hint

Think about what happens if a deadline is missed in safety-critical systems.

Hard real-time systems require strict adherence to deadlines. Missing a deadline can cause system failure or hazards.

❓ Predict Output

intermediate

Task Priority Impact on Deadline in FreeRTOS

Consider two FreeRTOS tasks: TaskA with priority 3 and TaskB with priority 2. TaskA must complete within 10ms. What happens if TaskB runs longer than expected?

What is the likely outcome regarding TaskA's deadline?

FreeRTOS

void TaskA(void *pvParameters) {
  // Critical task
  for(;;) {
    // Must finish within 10ms
    vTaskDelay(pdMS_TO_TICKS(5));
    // Perform critical work
  }
}

void TaskB(void *pvParameters) {
  for(;;) {
    // Runs longer than expected
    vTaskDelay(pdMS_TO_TICKS(20));
  }
}

A TaskA may miss its deadline if TaskB blocks system resources.

B TaskA will always meet its deadline because it has higher priority.

C TaskB will preempt TaskA causing TaskA to miss its deadline.

D Both tasks run simultaneously without affecting each other.

💡 Hint

Remember how FreeRTOS schedules tasks based on priority.

In FreeRTOS, higher priority tasks preempt lower priority ones. TaskA with priority 3 will run before TaskB with priority 2, so TaskA meets its deadline.

❓ Predict Output

advanced

Soft Real-Time Deadline Miss Behavior

In a soft real-time system, what is the typical behavior when a task misses its deadline?

Consider this FreeRTOS task code snippet:

void SoftTask(void *pvParameters) {
  for(;;) {
    // Simulate variable processing time
    vTaskDelay(pdMS_TO_TICKS(rand() % 15));
    // Process data
  }
}

A The system halts immediately upon deadline miss.

B The system raises a hard fault and resets.

C The task is killed and restarted automatically.

D The task continues running; occasional deadline misses are tolerated.

💡 Hint

Soft real-time systems allow some flexibility in timing.

Soft real-time systems tolerate occasional deadline misses without catastrophic failure; tasks continue running.

🧠 Conceptual

advanced

Choosing Between Hard and Soft Real-Time

Which scenario best requires a hard real-time system?

A A weather app updating forecasts every hour.

B A video streaming app where occasional frame drops are acceptable.

C An industrial robot arm controlling precise movements in a factory.

D A background file backup process running overnight.

💡 Hint

Think about when timing failures cause physical harm or damage.

Industrial robots require strict timing to avoid accidents, so hard real-time is necessary.

🔧 Debug

expert

Diagnosing Deadline Miss in FreeRTOS Hard Real-Time Task

A FreeRTOS hard real-time task sometimes misses its deadline. Which of the following code snippets is the most likely cause?

void HardTask(void *pvParameters) {
  for(;;) {
    // Critical work
    vTaskDelay(pdMS_TO_TICKS(5));
    // Heavy processing
    for(int i=0; i<1000000; i++) {
      // Busy wait
    }
  }
}

A The busy wait loop blocks the CPU, preventing timely task switching.

B The task priority is too high, causing starvation of other tasks.

C The vTaskDelay call causes the task to run too often.

D The task uses too little CPU time, so deadlines are missed.

💡 Hint

Consider how busy waiting affects multitasking in FreeRTOS.

Busy waiting blocks the CPU, preventing other tasks from running and causing deadline misses in hard real-time tasks.