xSemaphoreCreateMutex() function in FreeRTOS - Time & Space Complexity

Time Complexity: xSemaphoreCreateMutex() function

O(1)

Understanding Time Complexity

We want to understand how the time cost changes when creating a mutex in FreeRTOS.

Specifically, how the function xSemaphoreCreateMutex() behaves as the system scales.

Scenario Under Consideration

Analyze the time complexity of this code snippet.

SemaphoreHandle_t xMutex;
xMutex = xSemaphoreCreateMutex();
if (xMutex == NULL) {
    // Mutex creation failed
}
// Mutex is now ready to use
    

This code creates a mutex semaphore to control access to shared resources.

Identify Repeating Operations

Look for loops or repeated steps inside the function.

• Primary operation: The function allocates memory and initializes a mutex structure.
• How many times: This happens once per call; no loops or recursion inside.

How Execution Grows With Input

The time to create a mutex stays about the same no matter how many mutexes exist.

Input Size (n)	Approx. Operations
1	Small fixed steps
10	Same small fixed steps per call
100	Same small fixed steps per call

Pattern observation: The work does not grow with input size; it stays constant.

Final Time Complexity

Time Complexity: O(1)

This means creating a mutex takes about the same time every time, no matter how many mutexes exist.

Common Mistake

[X] Wrong: "Creating a mutex takes longer if many mutexes already exist."

[OK] Correct: The function only sets up one mutex at a time and does not loop over existing mutexes, so time does not increase with count.

Interview Connect

Knowing that resource creation functions like this run in constant time helps you reason about system responsiveness and design.

Self-Check

"What if the function had to search a list of existing mutexes before creating a new one? How would the time complexity change?"

Practice

1.

What is the primary purpose of the xSemaphoreCreateMutex() function in FreeRTOS?

easy

A. To delete an existing semaphore

B. To create a counting semaphore for task synchronization

C. To create a mutex for safe access to shared resources

D. To start a new task in the system

Solution

1. Step 1: Understand the function purpose

   xSemaphoreCreateMutex() is designed to create a mutex, which is a special type of semaphore used to protect shared resources.

2. Step 2: Compare with other options

   Options A, B, and C describe different FreeRTOS functions or concepts unrelated to mutex creation.

3. Final Answer:

   To create a mutex for safe access to shared resources -> Option C

4. Quick Check:

   Mutex creation = safe resource sharing [OK]

Hint: Mutexes protect shared resources safely [OK]

Common Mistakes:

• Confusing mutex with counting semaphore
• Thinking it creates a task
• Assuming it deletes semaphores

2.

Which of the following is the correct way to create a mutex using xSemaphoreCreateMutex() in FreeRTOS?

SemaphoreHandle_t mutex = ?;

easy

A. xSemaphoreCreateMutex();

B. xSemaphoreCreateCounting(1, 0);

C. xTaskCreateMutex();

D. xSemaphoreCreateBinary();

Solution

1. Step 1: Identify correct function call

   The function to create a mutex is exactly xSemaphoreCreateMutex(), which returns a handle.

2. Step 2: Eliminate incorrect options

   Options B, C, and D are either different semaphore types or invalid functions.

3. Final Answer:

   xSemaphoreCreateMutex(); -> Option A

4. Quick Check:

   Correct mutex creation syntax = xSemaphoreCreateMutex(); [OK]

Hint: Use exact function name xSemaphoreCreateMutex() [OK]

Common Mistakes:

• Using counting or binary semaphore functions
• Mistyping function name
• Confusing task creation with mutex creation

3.

Consider the following code snippet:

SemaphoreHandle_t mutex = xSemaphoreCreateMutex();
if (mutex == NULL) {
    printf("Mutex creation failed\n");
} else {
    printf("Mutex created successfully\n");
}

What will be the output if the mutex is created successfully?

medium

A. Mutex creation failed

B. Compilation error

C. No output

D. Mutex created successfully

Solution

1. Step 1: Check the return value of xSemaphoreCreateMutex()

   If the mutex is created successfully, the returned handle is not NULL.

2. Step 2: Follow the if-else logic

   Since mutex != NULL, the else block runs, printing "Mutex created successfully".

3. Final Answer:

   Mutex created successfully -> Option D

4. Quick Check:

   Non-NULL handle means success message [OK]

Hint: Check for NULL to confirm creation success [OK]

Common Mistakes:

• Assuming NULL means success
• Ignoring the if-else structure
• Expecting compilation errors

4.

Identify the error in the following code snippet that uses xSemaphoreCreateMutex():

SemaphoreHandle_t mutex;
mutex = xSemaphoreCreateMutex();
if (mutex != NULL) {
    xSemaphoreTake(mutex, 0);
}
// Use shared resource
xSemaphoreGive(mutex);

medium

A. Using zero block time in xSemaphoreTake() may cause immediate failure

B. Mutex handle is not initialized before use

C. xSemaphoreGive() should be called before xSemaphoreTake()

D. xSemaphoreCreateMutex() does not return a handle

Solution

1. Step 1: Analyze xSemaphoreTake() call with zero block time

   Using 0 as block time means the call will not wait and may fail if mutex is not available immediately.

2. Step 2: Understand implications for resource use

   If xSemaphoreTake() fails, the shared resource is accessed without protection, causing potential issues.

3. Final Answer:

   Using zero block time in xSemaphoreTake() may cause immediate failure -> Option A

4. Quick Check:

   Zero block time risks immediate take failure [OK]

Hint: Avoid zero block time unless sure mutex is free [OK]

Common Mistakes:

• Assuming zero block time always succeeds
• Ignoring mutex initialization
• Misordering take and give calls

5.

You want to protect a shared resource in a FreeRTOS application using a mutex created by xSemaphoreCreateMutex(). Which of the following sequences correctly shows how to use the mutex to safely access the resource?

1. xSemaphoreTake(mutex, portMAX_DELAY);
2. Access shared resource
3. xSemaphoreGive(mutex);
4. Create mutex with xSemaphoreCreateMutex()

hard

A. 1, 4, 2, 3

B. 4, 1, 2, 3

C. 4, 2, 1, 3

D. 1, 2, 3, 4

Solution

1. Step 1: Identify correct order of operations

   First, create the mutex (step 4), then take it before accessing the resource (step 1), access the resource (step 2), and finally give the mutex back (step 3).

2. Step 2: Verify sequence correctness

   Only 4, 1, 2, 3 follows the logical order: create, take, access, give.

3. Final Answer:

   4, 1, 2, 3 -> Option B

4. Quick Check:

   Create before take, then access, then give [OK]

Hint: Always create mutex before taking it [OK]

Common Mistakes:

• Taking mutex before creation
• Accessing resource without taking mutex
• Giving mutex before accessing resource