Why RTOS over bare-metal in FreeRTOS - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why use an RTOS instead of bare-metal for multitasking?

Consider a microcontroller project that needs to handle multiple tasks like sensor reading, communication, and user interface. Why might using an RTOS be better than bare-metal programming?

A RTOS allows tasks to run seemingly at the same time by managing task switching automatically.

B Bare-metal programming always uses more memory than RTOS.

C RTOS eliminates the need for interrupts completely.

D Bare-metal code cannot handle more than one task.

💡 Hint

Think about how multitasking is handled and what RTOS provides automatically.

RTOS manages multiple tasks by switching between them quickly, giving the illusion of simultaneous execution. Bare-metal requires manual task management.

❓ Predict Output

intermediate

What is the output of this FreeRTOS task scheduling example?

Given two FreeRTOS tasks with different priorities, what will be printed to the console?

FreeRTOS

void Task1(void *pvParameters) {
  for (;;) {
    printf("Task1 running\n");
    vTaskDelay(pdMS_TO_TICKS(100));
  }
}

void Task2(void *pvParameters) {
  for (;;) {
    printf("Task2 running\n");
    vTaskDelay(pdMS_TO_TICKS(50));
  }
}

int main() {
  xTaskCreate(Task1, "Task1", 1000, NULL, 1, NULL);
  xTaskCreate(Task2, "Task2", 1000, NULL, 2, NULL);
  vTaskStartScheduler();
  return 0;
}

A Only Task2 running repeatedly.

B Task2 running\nTask1 running\nTask2 running\nTask1 running\n...

C Only Task1 running repeatedly.

D Task1 running\nTask2 running\nTask1 running\nTask2 running\n...

💡 Hint

Higher priority tasks run before lower priority ones and can preempt them.

Task2 has higher priority (2) than Task1 (1), so Task2 runs whenever ready, preempting Task1.

🔧 Debug

advanced

Identify the problem in this bare-metal multitasking attempt

This bare-metal code tries to run two tasks by calling their functions in a loop. What is the main issue?

FreeRTOS

void taskA() {
  while(1) {
    // do something
  }
}

void taskB() {
  while(1) {
    // do something else
  }
}

int main() {
  while(1) {
    taskA();
    taskB();
  }
  return 0;
}

A taskA never returns, so taskB is never called.

B Both tasks run simultaneously without issues.

C The main loop causes a stack overflow.

D taskB runs before taskA causing a race condition.

💡 Hint

Consider what happens when a function has an infinite loop.

taskA has an infinite loop and never returns, so taskB is never reached or executed.

📝 Syntax

advanced

Which FreeRTOS API call is correct to create a task?

Choose the correct syntax to create a FreeRTOS task named "MyTask" with priority 3.

A xTaskCreate(MyTask, 3, "MyTask", 1000, NULL, NULL);

B xTaskCreate("MyTask", MyTask, 1000, NULL, 3, NULL);

C xTaskCreate("MyTask", 1000, MyTask, NULL, 3, NULL);

D xTaskCreate(MyTask, "MyTask", 1000, NULL, 3, NULL);

💡 Hint

Check the order of parameters: function pointer, name, stack size, parameters, priority, handle.

The correct order is: task function, name string, stack size, parameters, priority, task handle pointer.

🚀 Application

expert

How does RTOS improve responsiveness compared to bare-metal?

In a system with multiple time-critical tasks, how does using an RTOS improve responsiveness over bare-metal programming?

A RTOS disables all interrupts to avoid delays, improving responsiveness.

B RTOS runs all tasks in parallel on multiple cores automatically.

C RTOS uses preemptive scheduling to switch tasks immediately when higher priority tasks become ready.

D Bare-metal systems cannot use interrupts, so RTOS is needed for responsiveness.

💡 Hint

Think about how RTOS handles task priorities and switching.

RTOS preemptive scheduling allows immediate switching to higher priority tasks, improving response time.