Bare-metal vs RTOS execution model in Embedded C - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define the main loop in a bare-metal system.

Embedded C

int main() {
    while([1]) {
        // main loop code
    }
    return 0;
}

Drag options to blanks, or click blank then click option'

A1

B0

Ctrue

Dfalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 or false causes the loop to never run.

Using variables that might change and stop the loop.

In bare-metal programming, the main loop runs indefinitely, so the condition should always be true. Using 1 ensures the loop never ends.

2fill in blank

medium

Complete the code to create a task function prototype for an RTOS.

Embedded C

void [1](void *params) {
    while(1) {
        // task code
    }
}

Drag options to blanks, or click blank then click option'

Atask_function

BTaskFunction

CTask1

Dmain

Attempts:

3 left

💡 Hint

Common Mistakes

Using main as a task function name.

Using names with uppercase letters that don't match style.

Task functions in RTOS often use lowercase and underscore naming. task_function is a clear, valid prototype name.

3fill in blank

hard

Fix the error in the RTOS task creation code by filling the blank.

Embedded C

xTaskCreate([1], "Task1", 100, NULL, 1, NULL);

Drag options to blanks, or click blank then click option'

ATask1

Btask_function

Cmain

Dvoid

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the task name string instead of the function.

Passing void which is not a function.

The first argument to xTaskCreate must be the task function name. task_function is the correct function to run.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps task names to their priorities if priority is greater than 2.

Embedded C

task_priorities = {name: [1] for name, [2] in tasks.items() if priority > 2}

Drag options to blanks, or click blank then click option'

Apriority

Cprio

Dtask

Attempts:

3 left

💡 Hint

Common Mistakes

Using inconsistent variable names for priority.

Using undefined variables like prio or task.

The dictionary comprehension maps each task name to its priority. The variable priority is used both in the value and in the loop unpacking.

5fill in blank

hard

Fill all three blanks to filter and map tasks with priority above 3 to their uppercase names and priorities.

Embedded C

filtered_tasks = [1]([2].upper(): [3] for [2], priority in tasks.items() if priority > 3)

Drag options to blanks, or click blank then click option'

Adict

Bname

Cpriority

Dtasks

Attempts:

3 left

💡 Hint

Common Mistakes

Using tasks instead of dict.

Mixing variable names in keys and values.

The code creates a dictionary from a comprehension. It uses name for keys (converted to uppercase) and priority for values.

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