Why RTOS over bare-metal in FreeRTOS - Performance Analysis

Time Complexity: Why RTOS over bare-metal

O(n)

Understanding Time Complexity

When choosing between RTOS and bare-metal programming, it's important to understand how task management affects execution time.

We want to see how the system's work grows as tasks increase or become more complex.

Scenario Under Consideration

Analyze the time complexity of task switching in an RTOS compared to a bare-metal loop.

// Bare-metal main loop
while(1) {
  task1();
  task2();
  task3();
}

// RTOS task scheduler snippet
void vTaskSwitchContext() {
  // Select next ready task
  // Save context of current task
  // Load context of next task
}
    

The bare-metal code runs tasks one after another in a fixed loop. The RTOS scheduler switches between tasks based on priority and readiness.

Identify Repeating Operations

Look at what repeats as the system runs.

• Primary operation: Task execution and context switching
• How many times: Bare-metal runs tasks sequentially every loop; RTOS switches tasks whenever needed, which can be many times per second

How Execution Grows With Input

As the number of tasks increases, how does the work change?

Number of Tasks (n)	Approx. Operations per Cycle
3	Bare-metal: 3 tasks; RTOS: 3 tasks + context switches
10	Bare-metal: 10 tasks; RTOS: 10 tasks + more context switches
100	Bare-metal: 100 tasks; RTOS: 100 tasks + many context switches

Pattern observation: Bare-metal work grows linearly with tasks; RTOS adds overhead from switching, which grows with task count and frequency.

Final Time Complexity

Time Complexity: O(n)

This means the total work grows roughly in direct proportion to the number of tasks running.

Common Mistake

[X] Wrong: "RTOS always makes the system slower because of overhead."

[OK] Correct: RTOS overhead exists but helps manage many tasks efficiently, making complex systems easier and more reliable.

Interview Connect

Understanding how task management affects time helps you explain design choices clearly and shows you grasp system behavior beyond code.

Self-Check

What if we added task priorities and interrupts? How would the time complexity change?

Practice

1. Why is using an RTOS often better than programming on bare-metal for complex embedded systems?

easy

A. Because bare-metal code runs faster without any overhead

B. Because RTOS requires no knowledge of hardware

C. Because RTOS handles multiple tasks with scheduling and timing automatically

D. Because bare-metal systems never crash

Solution

1. Step 1: Understand task management differences

   RTOS automatically manages multiple tasks with scheduling and timing, while bare-metal requires manual handling.

2. Step 2: Compare complexity and reliability

   RTOS improves reliability by handling task switching and timing, reducing manual errors common in bare-metal.

3. Final Answer:

   Because RTOS handles multiple tasks with scheduling and timing automatically -> Option C

4. Quick Check:

   RTOS manages tasks automatically [OK]

Hint: RTOS automates multitasking; bare-metal needs manual control [OK]

Common Mistakes:

• Thinking bare-metal is always faster without considering complexity
• Assuming RTOS removes need for hardware knowledge
• Believing bare-metal systems never crash

2. Which of the following is the correct way to create a task in FreeRTOS?

easy

A. xTaskCreate(TaskFunction, "TaskName", StackSize, NULL, Priority, NULL);

B. createTask(TaskFunction, Priority);

C. TaskCreate(TaskFunction, StackSize);

D. xCreateTask(TaskFunction, "TaskName");

Solution

1. Step 1: Recall FreeRTOS task creation syntax

   The correct function is xTaskCreate with parameters: function, name, stack size, parameters, priority, and task handle.

2. Step 2: Match options to syntax

   Only xTaskCreate(TaskFunction, "TaskName", StackSize, NULL, Priority, NULL); matches the correct FreeRTOS API call with all required parameters.

3. Final Answer:

   xTaskCreate(TaskFunction, "TaskName", StackSize, NULL, Priority, NULL); -> Option A

4. Quick Check:

   FreeRTOS task creation = xTaskCreate(...) [OK]

Hint: Remember FreeRTOS uses xTaskCreate with 6 parameters [OK]

Common Mistakes:

• Using incorrect function names like createTask
• Omitting required parameters
• Confusing parameter order

3. Given this FreeRTOS code snippet, what will be the output on the serial console?

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

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

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

medium

A. Both tasks print at the same rate

B. Task1 prints twice as often as Task2

C. No output because scheduler is not started

D. Task2 prints twice as often as Task1

Solution

1. Step 1: Analyze delay times for each task

   Task1 delays 1000 ms between prints; Task2 delays 500 ms between prints.

2. Step 2: Compare print frequencies

   Task2 runs twice as often because 500 ms delay is half of 1000 ms delay.

3. Final Answer:

   Task2 prints twice as often as Task1 -> Option D

4. Quick Check:

   Shorter delay means more prints [OK]

Hint: Shorter vTaskDelay means more frequent prints [OK]

Common Mistakes:

• Confusing which task has shorter delay
• Assuming tasks run sequentially, not concurrently
• Ignoring vTaskStartScheduler call

4. This FreeRTOS code snippet does not behave as expected. What is the main problem?

void Task(void *pvParameters) {
  while(1) {
    // Do some work
    vTaskDelay(1000);
  }
}

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

medium

A. vTaskStartScheduler should be called before creating tasks

B. vTaskDelay needs pdMS_TO_TICKS macro for delay time

C. xTaskCreate missing priority parameter

D. Task function must return an int

Solution

1. Step 1: Check vTaskDelay usage

   vTaskDelay expects ticks, but 1000 is milliseconds; pdMS_TO_TICKS converts ms to ticks.

2. Step 2: Identify correct delay call

   Correct call is vTaskDelay(pdMS_TO_TICKS(1000)) to delay 1000 ms properly.

3. Final Answer:

   vTaskDelay needs pdMS_TO_TICKS macro for delay time -> Option B

4. Quick Check:

   Delay in ticks, not ms [OK]

Hint: Always convert ms to ticks with pdMS_TO_TICKS [OK]

Common Mistakes:

• Passing milliseconds directly to vTaskDelay
• Thinking task functions must return int
• Calling scheduler before creating tasks

5. You want to improve responsiveness in a sensor monitoring system by switching from bare-metal to FreeRTOS. Which approach best uses FreeRTOS features to achieve this?

hard

A. Create separate tasks for sensor reading, data processing, and communication with different priorities

B. Run all code sequentially in one task with long delays

C. Use FreeRTOS only to replace delay functions but keep one big task

D. Disable interrupts and rely on polling in a single task

Solution

1. Step 1: Identify how RTOS improves responsiveness

   RTOS allows multiple tasks with priorities, so critical tasks run promptly.

2. Step 2: Evaluate options for task design

   Creating separate tasks for sensor reading, processing, and communication with priorities uses RTOS strengths best.

3. Final Answer:

   Create separate tasks for sensor reading, data processing, and communication with different priorities -> Option A

4. Quick Check:

   Separate prioritized tasks improve responsiveness [OK]

Hint: Use multiple prioritized tasks for better responsiveness [OK]

Common Mistakes:

• Keeping all code in one task with delays
• Using RTOS only for delays, not multitasking
• Disabling interrupts reduces responsiveness