Why mutexes protect shared resources in FreeRTOS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a mutex in FreeRTOS.

FreeRTOS

SemaphoreHandle_t xMutex = [1]();

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

AxSemaphoreCreateMutex

BxTaskCreate

CvTaskDelay

DxQueueCreate

Attempts:

3 left

💡 Hint

Common Mistakes

Using xQueueCreate instead of xSemaphoreCreateMutex.

The function xSemaphoreCreateMutex() creates a mutex in FreeRTOS.

2fill in blank

medium

Complete the code to take (lock) the mutex before accessing a shared resource.

FreeRTOS

if(xSemaphoreTake(xMutex, [1]) == pdTRUE) {
    // Access shared resource
}

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

A0

BpdFALSE

CportMAX_DELAY

DpdPASS

Attempts:

3 left

💡 Hint

Common Mistakes

Using 0 causes the task to not wait for the mutex.

Using portMAX_DELAY makes the task wait indefinitely until the mutex is available.

3fill in blank

hard

Fix the error in releasing the mutex after using the shared resource.

FreeRTOS

xSemaphore[1](xMutex);

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

ADelete

BGive

CCreate

DTake

Attempts:

3 left

💡 Hint

Common Mistakes

Using xSemaphoreTake instead of xSemaphoreGive to release the mutex.

To release the mutex, use xSemaphoreGive().

4fill in blank

hard

Fill both blanks to correctly protect a shared variable with a mutex.

FreeRTOS

if(xSemaphore[1](xMutex, portMAX_DELAY) == pdTRUE) {
    sharedVar [2] 10;
    xSemaphoreGive(xMutex);
}

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

ATake

B+=

C=

DGive

Attempts:

3 left

💡 Hint

Common Mistakes

Using '=' instead of '+=' to update the variable.

Use xSemaphoreTake to lock the mutex and += to update the shared variable safely.

5fill in blank

hard

Fill all three blanks to create, take, and give a mutex protecting a shared counter.

FreeRTOS

SemaphoreHandle_t [1] = [2]();

if(xSemaphoreTake([1], portMAX_DELAY) == pdTRUE) {
    counter++;
    xSemaphoreGive([1]);
}

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

AxMutex

BxSemaphoreCreateMutex

DxSemaphoreCreateBinary

Attempts:

3 left

💡 Hint

Common Mistakes

Using xSemaphoreCreateBinary() instead of xSemaphoreCreateMutex().

Create the mutex with xSemaphoreCreateMutex(), store it in xMutex, then take and give it to protect the counter.

Practice

1. Why do we use mutexes in FreeRTOS when accessing shared resources?

easy

A. To allow only one task to access the resource at a time

B. To speed up the execution of all tasks simultaneously

C. To permanently lock the resource so no task can use it

D. To create multiple copies of the resource for each task

Solution

1. Step 1: Understand what a shared resource is

   A shared resource is something multiple tasks want to use, like a variable or hardware.

2. Step 2: Understand mutex purpose in FreeRTOS

   Mutexes ensure only one task uses the resource at a time to avoid conflicts or errors.

3. Final Answer:

   To allow only one task to access the resource at a time -> Option A

4. Quick Check:

   Mutex = single task access [OK]

Hint: Mutex means one task at a time [OK]

Common Mistakes:

• Thinking mutex speeds up all tasks
• Believing mutex locks resource forever
• Assuming mutex duplicates resources

2. Which FreeRTOS function is used to lock a mutex before accessing a shared resource?

easy

A. xSemaphoreGive()

B. vTaskDelay()

C. xSemaphoreTake()

D. xQueueSend()

Solution

1. Step 1: Identify the function to lock a mutex

   In FreeRTOS, xSemaphoreTake() is used to take or lock a mutex.

2. Step 2: Confirm other functions' purposes

   xSemaphoreGive() releases the mutex, vTaskDelay() delays a task, and xQueueSend() sends data to a queue.

3. Final Answer:

   xSemaphoreTake() -> Option C

4. Quick Check:

   Lock mutex = xSemaphoreTake() [OK]

Hint: Take locks, Give unlocks mutex [OK]

Common Mistakes:

• Confusing xSemaphoreGive() as lock
• Using vTaskDelay() to lock mutex
• Mixing queue functions with mutex

3. What will happen if two tasks try to access a shared variable without using a mutex in FreeRTOS?

medium

A. Data corruption or unexpected behavior may occur

B. Both tasks access safely without issues

C. The system automatically locks the variable

D. The second task waits automatically until the first finishes

Solution

1. Step 1: Understand shared resource risks without mutex

   Without mutex, tasks can change the variable at the same time, causing data corruption.

2. Step 2: Check FreeRTOS behavior without explicit locking

   FreeRTOS does not automatically lock variables; tasks run concurrently unless synchronized.

3. Final Answer:

   Data corruption or unexpected behavior may occur -> Option A

4. Quick Check:

   No mutex = risk of data corruption [OK]

Hint: No mutex means unsafe shared access [OK]

Common Mistakes:

• Assuming FreeRTOS auto-locks variables
• Thinking tasks wait automatically
• Believing no issues happen without mutex

4. Given this code snippet, what is the error related to mutex usage?

if(xSemaphoreTake(mutex, 0) == pdTRUE) {
  sharedVar++;
}
// Missing xSemaphoreGive(mutex) here

medium

A. The mutex is taken twice without giving

B. The mutex is given before taking

C. The shared variable is not incremented

D. The mutex is never released, causing a deadlock

Solution

1. Step 1: Check mutex take and give usage

   The code takes the mutex but never calls xSemaphoreGive() to release it.

2. Step 2: Understand consequences of not releasing mutex

   Not releasing the mutex causes other tasks to wait forever, leading to deadlock.

3. Final Answer:

   The mutex is never released, causing a deadlock -> Option D

4. Quick Check:

   Missing give = deadlock risk [OK]

Hint: Always give mutex after take [OK]

Common Mistakes:

• Forgetting to release mutex
• Assuming increment fails without mutex
• Confusing order of take/give

5. You have two tasks that both update a shared sensor reading variable. How should you use a mutex to ensure safe updates and avoid blocking tasks too long?

hard

A. Take the mutex once at system start and never release it

B. Take the mutex, update the variable quickly, then give the mutex immediately

C. Update the variable without mutex and rely on task priorities

D. Use two separate mutexes for the same variable

Solution

1. Step 1: Understand mutex best practice for shared data

   Mutex should be held only briefly to protect the critical section (variable update).

2. Step 2: Evaluate options for safe and efficient updates

   Taking and giving mutex immediately around update prevents blocking other tasks too long.

3. Final Answer:

   Take the mutex, update the variable quickly, then give the mutex immediately -> Option B

4. Quick Check:

   Short mutex hold = safe and efficient [OK]

Hint: Lock only during update, then unlock fast [OK]

Common Mistakes:

• Holding mutex too long blocking tasks
• Never releasing mutex causing deadlock
• Ignoring mutex and risking data errors