Bare-metal vs RTOS execution model in Embedded C

Introduction

Understanding how programs run on small devices helps you choose the right way to control hardware. Bare-metal and RTOS are two ways to run code on embedded systems.

When you want simple control of hardware without extra software layers.

When you need to run multiple tasks at the same time in an organized way.

When your device has limited memory and you want to keep things small.

When your project needs precise timing and task management.

When you want to learn how embedded systems work at a low level.

Syntax

Embedded C

/* Bare-metal main loop example */
int main() {
    while(1) {
        // Run tasks one by one
    }
    return 0;
}

/* RTOS task example */
void Task1(void *params) {
    while(1) {
        // Task code
        vTaskDelay(1000 / portTICK_PERIOD_MS);
    }
}

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

Bare-metal code runs in a simple loop without an operating system.

RTOS uses tasks and a scheduler to manage multiple jobs at once.

Examples

This code runs forever, turning an LED on and off with a delay.

Embedded C

/* Bare-metal example: toggle LED */
int main() {
    while(1) {
        toggleLED();
        delay(500);
    }
}

This RTOS code runs two tasks blinking different LEDs at different speeds.

Embedded C

/* RTOS example: two tasks blinking LEDs */
void Task1(void *params) {
    while(1) {
        toggleLED1();
        vTaskDelay(500 / portTICK_PERIOD_MS);
    }
}

void Task2(void *params) {
    while(1) {
        toggleLED2();
        vTaskDelay(1000 / portTICK_PERIOD_MS);
    }
}

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

Sample Program

This program counts from 0 to 4 and prints each number. It shows a simple bare-metal style loop without multitasking.

Embedded C

/* Simple bare-metal loop printing numbers */
#include <stdio.h>

int main() {
    int count = 0;
    while(count < 5) {
        printf("Count: %d\n", count);
        count++;
    }
    return 0;
}

Important Notes

Bare-metal is simpler but can get messy with many tasks.

RTOS helps organize multiple tasks but needs more memory and setup.

Choosing depends on your project size, complexity, and hardware limits.

Summary

Bare-metal runs one task in a loop, simple and direct.

RTOS runs many tasks with a scheduler, better for complex jobs.

Pick bare-metal for small, simple projects; pick RTOS for multitasking and timing needs.

Practice

1. Which statement best describes the bare-metal execution model in embedded C?

easy

A. Multiple tasks run concurrently with a scheduler.

B. It requires an operating system to manage tasks.

C. Code runs directly on hardware with a single main loop.

D. It uses virtual machines to isolate processes.

Solution

1. Step 1: Understand bare-metal execution

   Bare-metal means the program runs directly on the hardware without an operating system.

2. Step 2: Identify the execution style

   Bare-metal typically uses a single main loop to control the program flow.

3. Final Answer:

   Code runs directly on hardware with a single main loop. -> Option C

4. Quick Check:

   Bare-metal = single main loop [OK]

Hint: Bare-metal means one main loop, no OS multitasking [OK]

Common Mistakes:

• Confusing bare-metal with RTOS multitasking
• Thinking bare-metal requires an OS
• Assuming bare-metal uses task scheduling

2. Which of the following is the correct way to start a task in an RTOS environment in embedded C?

easy

A. void startTask() { while(1) { /* task code */ } }

B. xTaskCreate(taskFunction, "Task", 1000, NULL, 1, NULL);

C. main() { runTask(); }

D. createThread(taskFunction);

Solution

1. Step 1: Recognize RTOS task creation syntax

   In embedded C with RTOS like FreeRTOS, tasks are created using xTaskCreate().

2. Step 2: Match the correct function call

   xTaskCreate(taskFunction, "Task", 1000, NULL, 1, NULL); uses xTaskCreate() with proper parameters to start a task.

3. Final Answer:

   xTaskCreate(taskFunction, "Task", 1000, NULL, 1, NULL); -> Option B

4. Quick Check:

   RTOS task start = xTaskCreate() [OK]

Hint: RTOS tasks start with xTaskCreate() function [OK]

Common Mistakes:

• Using infinite loops without RTOS task creation
• Calling non-existent functions like createThread()
• Starting tasks directly in main() without scheduler

3. Given the following code snippet in a bare-metal system:

int main() {
  while(1) {
    toggleLED();
  }
  return 0;
}

What will happen when this runs?

medium

A. The LED toggles continuously without stopping.

B. The program creates multiple tasks to toggle the LED.

C. The LED toggles once and the program ends.

D. The program will cause a runtime error.

Solution

1. Step 1: Analyze the infinite loop

   The while(1) loop runs forever, repeatedly calling toggleLED().

2. Step 2: Understand bare-metal behavior

   Since there is no OS, the program stays in this loop, toggling the LED continuously.

3. Final Answer:

   The LED toggles continuously without stopping. -> Option A

4. Quick Check:

   Infinite loop toggles LED forever [OK]

Hint: Infinite loop means continuous action in bare-metal [OK]

Common Mistakes:

• Thinking tasks are created automatically
• Assuming program ends after one toggle
• Expecting runtime errors without cause

4. In an RTOS program, the following code snippet causes the LED to toggle only once:

void taskLED(void *params) {
  toggleLED();
}

int main() {
  xTaskCreate(taskLED, "LED", 1000, NULL, 1, NULL);
  vTaskStartScheduler();
  while(1) {}
}

What is the main problem?

medium

A. The task function lacks an infinite loop to keep running.

B. The scheduler is not started properly.

C. The task priority is too low to run.

D. The LED toggle function is incorrect.

Solution

1. Step 1: Check the task function structure

   The task function runs toggleLED() once and then returns, ending the task immediately.

2. Step 2: Understand RTOS task lifetime

   RTOS tasks must have an infinite loop to keep running and performing actions repeatedly.

3. Final Answer:

   The task function lacks an infinite loop to keep running. -> Option A

4. Quick Check:

   RTOS tasks need infinite loops [OK]

Hint: RTOS tasks must loop forever to keep running [OK]

Common Mistakes:

• Forgetting infinite loop in task function
• Assuming scheduler auto-repeats tasks
• Blaming LED function without checking task code

5. You have a project that needs to read sensor data, control motors, and communicate over UART simultaneously. Which execution model is best and why?

hard

A. Bare-metal, because it is simpler and uses one main loop.

B. Bare-metal, because multitasking is not possible in RTOS.

C. RTOS, but only if the hardware supports virtual machines.

D. RTOS, because it can run multiple tasks concurrently with scheduling.

Solution

1. Step 1: Analyze project requirements

   The project needs to handle sensor reading, motor control, and UART communication at the same time.

2. Step 2: Match execution model to multitasking needs

   RTOS supports multiple tasks running concurrently with a scheduler, ideal for complex multitasking.

3. Final Answer:

   RTOS, because it can run multiple tasks concurrently with scheduling. -> Option D

4. Quick Check:

   Multitasking needs = RTOS [OK]

Hint: Use RTOS for multitasking, bare-metal for simple loops [OK]

Common Mistakes:

• Choosing bare-metal for complex multitasking
• Thinking RTOS can't multitask
• Confusing virtual machines with RTOS requirements