What is an RTOS in FreeRTOS - Practice Questions & Exercises

Challenge - 5 Problems

🧠 Conceptual

intermediate

Understanding RTOS Basics

Which statement best describes what an RTOS (Real-Time Operating System) is?

A A software that delays all tasks to run them sequentially after a fixed time.

B An operating system designed to handle tasks within strict timing constraints.

C A system that only runs one task at a time without multitasking.

D An operating system mainly used for desktop computers and laptops.

💡 Hint

Think about systems that need to respond quickly and predictably.

An RTOS is built to manage tasks so they complete within specific time limits, ensuring predictable behavior.

❓ Predict Output

intermediate

RTOS Task Scheduling Output

Consider this FreeRTOS code snippet that creates two tasks with different priorities. What will be the output?

FreeRTOS

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

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

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

A No output because tasks do not run without an infinite loop.

B Task1 running\nTask1 running\nTask2 running\nTask1 running\nTask2 running\nTask1 running\n...

C Task1 running\nTask2 running\nTask1 running\nTask2 running\nTask1 running\nTask2 running\n...

D Task2 running\nTask2 running\nTask1 running\nTask2 running\nTask2 running\nTask1 running\n...

💡 Hint

Higher priority tasks run more often and can preempt lower priority tasks.

Task2 has higher priority and runs more frequently, so its messages appear more often than Task1's.

🔧 Debug

advanced

Identifying RTOS Deadlock Scenario

What error will this FreeRTOS code cause?

SemaphoreHandle_t xSemaphore;

void TaskA(void *pvParameters) {
  xSemaphoreTake(xSemaphore, portMAX_DELAY);
  // Critical section
  xSemaphoreTake(xSemaphore, portMAX_DELAY);
  xSemaphoreGive(xSemaphore);
  xSemaphoreGive(xSemaphore);
  vTaskDelete(NULL);
}

void TaskB(void *pvParameters) {
  xSemaphoreTake(xSemaphore, portMAX_DELAY);
  // Critical section
  xSemaphoreGive(xSemaphore);
  vTaskDelete(NULL);
}

int main() {
  xSemaphore = xSemaphoreCreateMutex();
  xTaskCreate(TaskA, "TaskA", 1000, NULL, 1, NULL);
  xTaskCreate(TaskB, "TaskB", 1000, NULL, 1, NULL);
  vTaskStartScheduler();
  return 0;
}

A Deadlock because TaskA tries to take the same mutex twice without giving it back.

B Stack overflow due to infinite recursion in TaskA.

C No error; tasks run normally and release the semaphore correctly.

D Memory leak because semaphore is never deleted.

💡 Hint

Think about what happens when a task tries to take a mutex it already holds.

TaskA tries to take the mutex twice without releasing it first, causing a deadlock waiting on itself.

📝 Syntax

advanced

Correct FreeRTOS Task Creation Syntax

Which option shows the correct syntax to create a FreeRTOS task that runs a function named MyTask?

A xTaskCreate(MyTask, "MyTask", 512, NULL, 2, NULL);

B xTaskCreate("MyTask", MyTask, 512, NULL, 2, NULL);

C xTaskCreate(MyTask(), "MyTask", 512, NULL, 2, NULL);

D xTaskCreate(&MyTask, "MyTask", 512, NULL, 2, NULL);

💡 Hint

Remember that the task function name is passed as a pointer without parentheses.

The function name is passed directly without parentheses or address operator. Option A is correct.

🚀 Application

expert

Choosing the Best RTOS Feature for a Time-Critical Application

You are designing a system that must respond to sensor input within 5 milliseconds consistently. Which RTOS feature is most important to ensure this?

A Round-robin scheduling to give equal CPU time to all tasks.

B Idle task to save power when no tasks are running.

C Priority-based preemptive scheduling to guarantee high-priority task execution.

D Dynamic memory allocation for flexible task creation.

💡 Hint

Think about how to make sure the most important task runs immediately when needed.

Priority-based preemptive scheduling allows the RTOS to run high-priority tasks immediately, meeting strict timing needs.

Practice

1. What does RTOS stand for in embedded systems?

easy

A. Random Task Operating System

B. Real-Time Operating System

C. Rapid Transfer Operating Software

D. Reliable Time Output System

Solution

1. Step 1: Understand the acronym RTOS

   RTOS is a common term in embedded systems referring to a type of operating system.

2. Step 2: Match the correct full form

   RTOS stands for Real-Time Operating System, which manages tasks with timing constraints.

3. Final Answer:

   Real-Time Operating System -> Option B

4. Quick Check:

   RTOS = Real-Time Operating System [OK]

Hint: Remember RTOS means system for real-time tasks [OK]

Common Mistakes:

• Confusing RTOS with general operating systems
• Thinking RTOS stands for random or rapid terms
• Mixing up the order of words in the acronym

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, "TaskName", StackSize, Priority);

C. TaskCreate(TaskFunction, StackSize, Priority);

D. xCreateTask(TaskFunction, "TaskName", Priority);

Solution

1. Step 1: Recall FreeRTOS task creation syntax

   FreeRTOS uses the function xTaskCreate with specific parameters including function, name, stack size, parameters, priority, and task handle.

2. Step 2: Identify the correct function call

   xTaskCreate(TaskFunction, "TaskName", StackSize, NULL, Priority, NULL); matches the correct syntax with all required parameters and correct function name.

3. Final Answer:

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

4. Quick Check:

   FreeRTOS task creation uses xTaskCreate [OK]

Hint: Look for xTaskCreate with all parameters included [OK]

Common Mistakes:

• Using incorrect function names like createTask
• Omitting required parameters
• Wrong order of parameters

3. Consider this FreeRTOS code snippet:

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

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

What will be the output when this program runs?

medium

A. Compilation error due to missing parameters

B. Task1 running printed once then program ends

C. Task1 running printed every 1 second repeatedly

D. No output because scheduler is not started

Solution

1. Step 1: Analyze the task loop and delay

   The task runs an infinite loop with vTaskDelay of 1000 milliseconds, so it prints "Task1 running" every second.

2. Step 2: Check scheduler start and task creation

   The task is created and scheduler started, so the task runs indefinitely printing the message repeatedly.

3. Final Answer:

   Task1 running printed every 1 second repeatedly -> Option C

4. Quick Check:

   Infinite loop with delay prints repeatedly [OK]

Hint: Infinite loop with delay prints repeatedly [OK]

Common Mistakes:

• Thinking the program ends after one print
• Assuming scheduler is not started
• Confusing delay units or missing infinite loop

4. Identify the error in this FreeRTOS task creation code:

void Task2(void *pvParameters) {
  // Task code
}

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

medium

A. Missing last parameter (task handle) in xTaskCreate call

B. Task function should not have parameters

C. Stack size is too small

D. Scheduler should be started before creating tasks

Solution

1. Step 1: Review xTaskCreate function parameters

   xTaskCreate requires six parameters: function, name, stack size, parameters, priority, and task handle pointer.

2. Step 2: Check the code for missing parameters

   The code provides only five parameters, missing the last one (task handle), causing a compile error.

3. Final Answer:

   Missing last parameter (task handle) in xTaskCreate call -> Option A

4. Quick Check:

   xTaskCreate needs 6 parameters [OK]

Hint: Count parameters in xTaskCreate; must be six [OK]

Common Mistakes:

• Omitting the task handle parameter
• Thinking task functions cannot have parameters
• Starting scheduler before task creation

5. You want to run two tasks in FreeRTOS: one blinking an LED every 500ms and another reading a sensor every 1000ms. Which feature of an RTOS helps you achieve this reliably?

hard

A. Static memory allocation only

B. Single-threaded execution without interrupts

C. Manual delay loops in main program

D. Task scheduling with priorities and time slicing

Solution

1. Step 1: Understand multitasking needs

   Running two tasks with different timing requires the system to switch between tasks efficiently and predictably.

2. Step 2: Identify RTOS feature for multitasking

   RTOS uses task scheduling with priorities and time slicing to manage multiple tasks reliably.

3. Final Answer:

   Task scheduling with priorities and time slicing -> Option D

4. Quick Check:

   RTOS scheduling enables reliable multitasking [OK]

Hint: RTOS scheduling manages multiple timed tasks [OK]

Common Mistakes:

• Thinking single-threaded code can handle multitasking well
• Using manual delays instead of scheduler
• Confusing memory allocation with task management