Semaphore timeout handling in FreeRTOS - Mini Project: Build & Apply

Semaphore timeout handling

📖 Scenario: You are writing a simple FreeRTOS program where a task waits for a semaphore to proceed. Sometimes the semaphore might not be given in time, so you want to handle the timeout properly.

🎯 Goal: Build a FreeRTOS task that waits for a semaphore with a timeout and handles the case when the semaphore is not received in time.

📋 What You'll Learn

Create a binary semaphore called xSemaphore

Create a timeout variable called xTimeout with value 1000 (milliseconds)

Use xSemaphoreTake with xTimeout to wait for the semaphore

Print "Semaphore taken!" if the semaphore is received

Print "Timeout occurred!" if the semaphore wait times out

💡 Why This Matters

🌍 Real World

Semaphore timeout handling is important in embedded systems to avoid tasks waiting forever and to handle resource availability gracefully.

💼 Career

Understanding semaphore timeout handling is essential for embedded software developers working with real-time operating systems like FreeRTOS.

1

Create the semaphore

Create a binary semaphore called xSemaphore using xSemaphoreCreateBinary().

FreeRTOS

// Create a binary semaphore called xSemaphore
// Your code here

Hint

Use xSemaphoreCreateBinary() to create a binary semaphore and assign it to xSemaphore.

2

Set the timeout value

Create a variable called xTimeout and set it to pdMS_TO_TICKS(1000) to represent 1000 milliseconds timeout.

FreeRTOS

SemaphoreHandle_t xSemaphore = xSemaphoreCreateBinary();

// Create a timeout variable xTimeout with 1000 milliseconds
// Your code here

Hint

Use pdMS_TO_TICKS(1000) to convert 1000 milliseconds to ticks and assign it to xTimeout.

3

Wait for the semaphore with timeout

Use xSemaphoreTake(xSemaphore, xTimeout) inside an if statement to check if the semaphore was taken successfully.

FreeRTOS

SemaphoreHandle_t xSemaphore = xSemaphoreCreateBinary();
TickType_t xTimeout = pdMS_TO_TICKS(1000);

// Use xSemaphoreTake with xTimeout to wait for the semaphore
// Your code here

Hint

Use xSemaphoreTake with xSemaphore and xTimeout. Check if the return value equals pdTRUE.

4

Print the result

Inside the if block, write printf("Semaphore taken!\n"). Inside the else block, write printf("Timeout occurred!\n").

FreeRTOS

SemaphoreHandle_t xSemaphore = xSemaphoreCreateBinary();
TickType_t xTimeout = pdMS_TO_TICKS(1000);

if (xSemaphoreTake(xSemaphore, xTimeout) == pdTRUE) {
    // Print semaphore taken message
    // Your code here
} else {
    // Print timeout message
    // Your code here
}

Hint

Use printf to print the messages exactly as shown.

Practice

1.

What does the timeout parameter in xSemaphoreTake() control?

easy

A. How long the task waits for the semaphore before giving up

B. The priority of the task waiting for the semaphore

C. The number of times the semaphore can be taken

D. The size of the semaphore queue

Solution

1. Step 1: Understand the role of timeout in xSemaphoreTake()

   The timeout parameter specifies the maximum time the task will wait to obtain the semaphore.

2. Step 2: Relate timeout to task blocking

   If the semaphore is not available within this time, the function returns failure, preventing indefinite blocking.

3. Final Answer:

   How long the task waits for the semaphore before giving up -> Option A

4. Quick Check:

   Timeout controls wait duration = B [OK]

Hint: Timeout limits wait time to avoid blocking forever [OK]

Common Mistakes:

• Confusing timeout with task priority
• Thinking timeout changes semaphore count
• Assuming timeout affects queue size

2.

Which of the following is the correct way to call xSemaphoreTake() with a 100 tick timeout?

SemaphoreHandle_t sem;

easy

A. xSemaphoreTake(&sem, 100);

B. xSemaphoreTake(100, sem);

C. xSemaphoreTake(sem, &100);

D. xSemaphoreTake(sem, 100);

Solution

1. Step 1: Check function signature

   xSemaphoreTake takes the semaphore handle first, then the timeout as TickType_t.

2. Step 2: Match parameters correctly

   Passing sem as first argument and 100 as timeout matches the correct syntax.

3. Final Answer:

   xSemaphoreTake(sem, 100); -> Option D

4. Quick Check:

   Semaphore handle first, timeout second = A [OK]

Hint: Semaphore handle is first argument in xSemaphoreTake [OK]

Common Mistakes:

• Swapping arguments order
• Passing address of timeout
• Passing address of semaphore handle

3.

What will be the output of this code snippet?

SemaphoreHandle_t sem = xSemaphoreCreateBinary();
if(xSemaphoreTake(sem, 10) == pdTRUE) {
    printf("Got semaphore\n");
} else {
    printf("Timeout occurred\n");
}

medium

A. Got semaphore

B. No output

C. Timeout occurred

D. Compilation error

Solution

1. Step 1: Understand semaphore initial state

   xSemaphoreCreateBinary creates a semaphore initially empty (not given).

2. Step 2: Check xSemaphoreTake behavior

   Since semaphore is empty and no give is called, xSemaphoreTake waits 10 ticks then times out.

3. Final Answer:

   Timeout occurred -> Option C

4. Quick Check:

   Empty semaphore + timeout = timeout message [OK]

Hint: Binary semaphore starts empty, so take times out if not given [OK]

Common Mistakes:

• Assuming semaphore is initially given
• Ignoring timeout effect
• Expecting compilation error

4.

Identify the error in this code snippet that uses xSemaphoreTake() with timeout:

SemaphoreHandle_t sem = xSemaphoreCreateBinary();
if(xSemaphoreTake(sem, portMAX_DELAY)) {
    // Critical section
} else {
    // Handle timeout
}

medium

A. Using portMAX_DELAY disables timeout, so else block never runs

B. Semaphore handle is not initialized

C. Missing sem give before take

D. Incorrect if condition syntax

Solution

1. Step 1: Understand portMAX_DELAY meaning

   portMAX_DELAY means wait indefinitely for the semaphore.

2. Step 2: Analyze if-else behavior

   Since wait is infinite, timeout never occurs, so else block is unreachable.

3. Final Answer:

   Using portMAX_DELAY disables timeout, so else block never runs -> Option A

4. Quick Check:

   portMAX_DELAY means infinite wait = C [OK]

Hint: portMAX_DELAY means wait forever, no timeout occurs [OK]

Common Mistakes:

• Thinking else block handles timeout with portMAX_DELAY
• Assuming semaphore uninitialized causes error here
• Confusing syntax error with logic error

5.

You want to wait for a semaphore but only up to 50 ticks. If the semaphore is not available, you want to perform a fallback task immediately. Which code snippet correctly implements this behavior?

hard

A. if(xSemaphoreTake(sem, portMAX_DELAY)) {
// Use resource
} else {
// Fallback task
}

B. if(xSemaphoreTake(sem, 50) == pdTRUE) {
// Use resource
} else {
// Fallback task
}

C. if(xSemaphoreTake(sem, 0) == pdFALSE) {
// Use resource
} else {
// Fallback task
}

D. if(xSemaphoreTake(sem, 50)) {
// Fallback task
} else {
// Use resource
}

Solution

1. Step 1: Check timeout usage

   Using 50 ticks as timeout means wait up to 50 ticks for semaphore.

2. Step 2: Verify fallback logic

   If take returns pdTRUE, resource is used; else fallback task runs immediately after timeout.

3. Final Answer:

   Correctly waits 50 ticks and runs fallback if timeout -> Option B

4. Quick Check:

   Timeout 50 ticks + fallback on failure = A [OK]

Hint: Wait with timeout, fallback in else block after failure [OK]

Common Mistakes:

• Using portMAX_DELAY disables fallback
• Swapping if-else blocks
• Using zero timeout incorrectly