Mutex vs binary semaphore difference in FreeRTOS - Quick Revision & Key Differences

Recall & Review

beginner

What is a mutex in FreeRTOS?

A mutex is a special type of semaphore used to protect shared resources by allowing only one task to access the resource at a time. It includes priority inheritance to avoid priority inversion.

beginner

What is a binary semaphore in FreeRTOS?

A binary semaphore is a synchronization tool that can take only two values: 0 or 1. It is used to signal events or synchronize tasks but does not support priority inheritance.

intermediate

How does priority inheritance differ between mutex and binary semaphore?

Mutexes support priority inheritance to prevent priority inversion, temporarily boosting the priority of the task holding the mutex. Binary semaphores do not support priority inheritance.

intermediate

Can a binary semaphore be used for mutual exclusion like a mutex?

While a binary semaphore can be used for mutual exclusion, it lacks priority inheritance and is generally better suited for signaling events rather than protecting shared resources.

intermediate

Why is a mutex preferred over a binary semaphore for resource protection?

A mutex is preferred because it includes priority inheritance, which helps avoid priority inversion problems when multiple tasks with different priorities access the same resource.

Which synchronization tool in FreeRTOS supports priority inheritance?

A Counting semaphore

B Binary semaphore

C Event group

D Mutex

Mutexes support priority inheritance to prevent priority inversion, while binary semaphores do not.

What is the main use of a binary semaphore in FreeRTOS?

A Protecting shared resources with priority inheritance

B Counting multiple resources

C Signaling events between tasks

D Scheduling tasks

Binary semaphores are mainly used for signaling events or synchronizing tasks.

Which of the following is true about mutexes?

A They are used only for signaling events

B They include priority inheritance to avoid priority inversion

C They can only take values 0 or 1 and do not support priority inheritance

D They are not suitable for resource protection

Mutexes include priority inheritance, making them suitable for protecting shared resources.

Can a binary semaphore be used to protect a shared resource?

A Yes, but it lacks priority inheritance

B No, it cannot be used for resource protection

C Yes, and it supports priority inheritance

D No, it is only for counting resources

Binary semaphores can be used for mutual exclusion but do not support priority inheritance.

What problem does priority inheritance in mutexes help to solve?

A Priority inversion

B Deadlock

C Race conditions

D Memory leaks

Priority inheritance helps prevent priority inversion, where a low-priority task blocks a higher-priority task.

Explain the key differences between a mutex and a binary semaphore in FreeRTOS.

Think about how each handles task priorities and their main use cases.

Describe a scenario where you would choose a binary semaphore over a mutex in FreeRTOS.

Consider event signaling versus resource locking.

Practice

1. Which of the following best describes the main difference between a mutex and a binary semaphore in FreeRTOS?

easy

A. Binary semaphores have ownership; mutexes do not.

B. Mutexes have ownership and priority inheritance; binary semaphores do not.

C. Mutexes are used only for signaling; binary semaphores are for exclusive access.

D. There is no difference; both behave exactly the same.

Solution

1. Step 1: Understand ownership concept

   Mutexes have ownership, meaning the task that locks it must unlock it. Binary semaphores do not have ownership.

2. Step 2: Understand priority inheritance

   Mutexes support priority inheritance to avoid priority inversion; binary semaphores do not.

3. Final Answer:

   Mutexes have ownership and priority inheritance; binary semaphores do not. -> Option B

4. Quick Check:

   Ownership + priority inheritance = Mutex [OK]

Hint: Mutex = ownership + priority; binary semaphore = simple flag [OK]

Common Mistakes:

• Thinking binary semaphores have ownership
• Confusing signaling role of binary semaphores
• Assuming mutexes do not support priority inheritance

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

easy

A. xSemaphoreCreateMutex()

B. xQueueCreateMutex()

C. xSemaphoreCreateBinary()

D. xMutexCreateSemaphore()

Solution

1. Step 1: Recall FreeRTOS API for mutex creation

   The function to create a mutex is xSemaphoreCreateMutex().

2. Step 2: Verify other options

   xSemaphoreCreateBinary() creates a binary semaphore, not a mutex. The other options are invalid API calls.

3. Final Answer:

   xSemaphoreCreateMutex() -> Option A

4. Quick Check:

   Mutex creation function = xSemaphoreCreateMutex() [OK]

Hint: Mutex creation always uses xSemaphoreCreateMutex() [OK]

Common Mistakes:

• Using xSemaphoreCreateBinary() for mutex
• Confusing queue creation functions with mutex
• Inventing non-existent API functions

3. Consider the following FreeRTOS code snippet:

SemaphoreHandle_t xMutex = xSemaphoreCreateMutex();
if (xSemaphoreTake(xMutex, 0) == pdTRUE) {
    // Critical section
    xSemaphoreGive(xMutex);
    printf("Mutex taken and released\n");
} else {
    printf("Failed to take mutex\n");
}

What will be the output when this code runs?

medium

A. Mutex taken and released

B. Failed to take mutex

C. Compilation error

D. No output

Solution

1. Step 1: Analyze mutex creation and take

   The mutex is created successfully. The call to xSemaphoreTake with zero block time tries to take the mutex immediately. Since it is free, it succeeds.

2. Step 2: Check critical section and release

   The mutex is given back with xSemaphoreGive, and the message "Mutex taken and released" is printed.

3. Final Answer:

   Mutex taken and released -> Option A

4. Quick Check:

   Mutex free at start, take succeeds, prints message [OK]

Hint: Mutex initially free, immediate take succeeds [OK]

Common Mistakes:

• Assuming take fails with zero block time
• Confusing mutex with binary semaphore behavior
• Expecting compilation errors from correct API usage

4. Identify the error in the following FreeRTOS code using a binary semaphore:

SemaphoreHandle_t xBinarySemaphore = xSemaphoreCreateBinary();
xSemaphoreGive(xBinarySemaphore);
if (xSemaphoreTake(xBinarySemaphore, portMAX_DELAY) == pdTRUE) {
    // Critical section
    xSemaphoreGive(xBinarySemaphore);
    xSemaphoreGive(xBinarySemaphore);
}

medium

A. Semaphore handle is not initialized.

B. Taking the semaphore with portMAX_DELAY is invalid.

C. Binary semaphore must be created with xSemaphoreCreateMutex().

D. Giving the semaphore twice causes incorrect behavior.

Solution

1. Step 1: Understand binary semaphore usage

   Binary semaphores act like flags with max count 1. Giving twice without taking in between can cause logic errors.

2. Step 2: Analyze the code's semaphore give calls

   The code gives the semaphore twice without an intervening take, which can lead to unexpected behavior or overflow.

3. Final Answer:

   Giving the semaphore twice causes incorrect behavior. -> Option D

4. Quick Check:

   Binary semaphore max count = 1, double give is wrong [OK]

Hint: Binary semaphore max count 1, don't give twice without take [OK]

Common Mistakes:

• Thinking portMAX_DELAY is invalid
• Confusing binary semaphore with mutex creation
• Ignoring semaphore initialization

5. You have two tasks: Task A (high priority) and Task B (low priority). Both need exclusive access to a shared resource. Which synchronization method should you use to avoid priority inversion and why? A) Use a mutex because it supports priority inheritance. B) Use a binary semaphore because it is simpler. C) Use a counting semaphore to allow multiple accesses. D) Use no synchronization to improve performance.

hard

A. Use a counting semaphore to allow multiple accesses.

B. Use a binary semaphore because it is simpler.

C. Use a mutex because it supports priority inheritance.

D. Use no synchronization to improve performance.

Solution

1. Step 1: Identify need for exclusive access with priority handling

   Both tasks need exclusive access, so synchronization is required. Priority inversion can occur if a low priority task holds the resource.

2. Step 2: Choose synchronization with priority inheritance

   Mutexes provide priority inheritance, temporarily boosting the low priority task's priority to avoid blocking the high priority task.

3. Final Answer:

   Use a mutex because it supports priority inheritance. -> Option C

4. Quick Check:

   Priority inversion avoidance = mutex [OK]

Hint: Use mutex for priority inheritance and exclusive access [OK]

Common Mistakes:

• Choosing binary semaphore ignoring priority inversion
• Using counting semaphore for exclusive access
• Skipping synchronization to save time