Queue full and empty handling in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What happens when you try to send an item to a full FreeRTOS queue?

The send operation will block or fail depending on the timeout specified. If the queue is full and no space becomes available within the timeout, the send function returns an error indicating the queue is full.

beginner

How does FreeRTOS handle receiving from an empty queue?

If a task tries to receive from an empty queue, it will block and wait for data to arrive until the specified timeout expires. If no data arrives, the receive function returns an error indicating the queue is empty.

beginner

What parameter controls how long a task waits when sending or receiving from a queue in FreeRTOS?

The 'TickType_t xTicksToWait' parameter controls the maximum time a task will block waiting for space (when sending) or data (when receiving) in the queue.

intermediate

What is the difference between xQueueSend and xQueueSendFromISR in FreeRTOS?

xQueueSend is used in normal task context and can block if the queue is full. xQueueSendFromISR is used inside interrupt service routines and cannot block; it returns immediately if the queue is full.

intermediate

Why is it important to handle queue full and empty conditions properly in FreeRTOS?

Proper handling prevents tasks from blocking indefinitely or losing data. It ensures system responsiveness and stability by managing resource limits and synchronization correctly.

What does FreeRTOS do if you try to receive from an empty queue with a zero timeout?

A Returns immediately with an error indicating the queue is empty

B Blocks until data arrives

C Fills the queue with default data

D Resets the queue

With zero timeout, the receive function returns immediately if the queue is empty.

Which function should you use to send data to a queue from an interrupt service routine?

A xQueueSendFromISR

B xQueueSend

C xQueueReceive

D vTaskDelay

xQueueSendFromISR is designed for use inside ISRs and does not block.

What happens if you call xQueueSend with a non-zero timeout and the queue is full?

A The function returns immediately with success

B The task blocks until space is available or timeout expires

C The queue is cleared automatically

D The system crashes

The task waits up to the timeout for space to become available.

Which parameter controls how long a task waits when sending or receiving from a queue?

A pvItemToQueue

B uxQueueLength

C xTicksToWait

D xQueueHandle

xTicksToWait specifies the maximum block time for queue operations.

Why should you avoid blocking indefinitely when sending to a full queue?

A To reset the queue automatically

B To fill the queue faster

C To increase CPU usage

D To prevent task deadlock and keep system responsive

Blocking indefinitely can cause deadlocks and reduce system responsiveness.

Explain how FreeRTOS handles sending data to a full queue and receiving data from an empty queue.

Think about what happens when the queue has no space or no data.

Describe why proper handling of queue full and empty conditions is important in FreeRTOS applications.

Consider what could go wrong if these conditions are ignored.

Practice

1. In FreeRTOS, what happens if you try to send an item to a queue that is already full without waiting?

easy

A. The send operation fails immediately and returns an error.

B. The queue automatically expands to fit the new item.

C. The oldest item in the queue is overwritten.

D. The task sending the item is suspended indefinitely.

Solution

1. Step 1: Understand queue full behavior

   When a queue is full, FreeRTOS does not allow new items to be added without waiting or handling the error.

2. Step 2: Check send operation without wait

   If the send function is called with zero wait time and the queue is full, it returns immediately with an error indicating failure.

3. Final Answer:

   The send operation fails immediately and returns an error. -> Option A

4. Quick Check:

   Queue full + no wait = send fails [OK]

Hint: Send with zero wait fails if queue is full [OK]

Common Mistakes:

• Assuming queue grows automatically
• Thinking oldest data is overwritten
• Believing task suspends indefinitely

2. Which of the following is the correct way to receive an item from a FreeRTOS queue with a block time of 10 ticks?

easy

A. xQueueReceive(queue, &item, 10);

B. xQueueReceive(queue, item, 10);

C. xQueueReceive(queue, &item, 0);

D. xQueueReceive(queue, &item, -1);

Solution

1. Step 1: Understand xQueueReceive parameters

   The function takes the queue handle, a pointer to the variable to store the item, and the block time in ticks.

2. Step 2: Identify correct syntax

   Passing &item as the second argument is correct to provide the address. Block time 10 means wait up to 10 ticks.

3. Final Answer:

   xQueueReceive(queue, &item, 10); -> Option A

4. Quick Check:

   Pointer + block time 10 = correct receive call [OK]

Hint: Use &item and positive ticks for blocking receive [OK]

Common Mistakes:

• Passing item instead of &item
• Using zero or negative block time incorrectly
• Confusing send and receive parameters

3. Consider the following code snippet:

QueueHandle_t queue = xQueueCreate(2, sizeof(int));
int val = 10;
xQueueSend(queue, &val, 0);
val = 20;
xQueueSend(queue, &val, 0);
val = 30;
BaseType_t result = xQueueSend(queue, &val, 0);

What is the value of result after the last send call?

medium

A. pdPASS (send succeeded)

B. errQUEUE_FULL (send failed due to full queue)

C. pdFAIL (generic failure)

D. Block indefinitely until space is available

Solution

1. Step 1: Analyze queue creation and sends

   The queue can hold 2 integers. Two sends with zero wait fill it completely.

2. Step 2: Evaluate last send with zero wait

   The third send tries to add an item when the queue is full and does not wait, so it fails returning errQUEUE_FULL.

3. Final Answer:

   errQUEUE_FULL (send failed due to full queue) -> Option B

4. Quick Check:

   Queue full + zero wait = send fails with errQUEUE_FULL [OK]

Hint: Queue size 2 + 3 sends with zero wait = last send fails [OK]

Common Mistakes:

• Assuming last send blocks
• Thinking last send overwrites data
• Confusing pdPASS and pdFAIL

4. Given this code snippet, why does xQueueReceive never return pdPASS?

QueueHandle_t queue = xQueueCreate(1, sizeof(int));
int data;

// Task A
xQueueReceive(queue, &data, 0);

// Task B
int val = 5;
xQueueSend(queue, &val, 0);

medium

A. xQueueSend is called with zero wait time, so it fails.

B. Queue size is too small to hold any data.

C. xQueueReceive is called with incorrect pointer.

D. Task A tries to receive before Task B sends, queue is empty, no wait time.

Solution

1. Step 1: Understand queue state at receive

   Task A calls receive immediately with zero wait, but queue is empty because Task B hasn't sent yet.

2. Step 2: Effect of zero wait on empty queue

   With zero wait, receive returns immediately with failure since no data is available yet.

3. Final Answer:

   Task A tries to receive before Task B sends, queue is empty, no wait time. -> Option D

4. Quick Check:

   Receive zero wait + empty queue = no pdPASS [OK]

Hint: Receive zero wait on empty queue always fails [OK]

Common Mistakes:

• Thinking queue size 1 means no data can be stored
• Assuming send fails with zero wait
• Confusing pointer usage in receive

5. You want to design a FreeRTOS task that sends sensor data to a queue but must never block if the queue is full. Which approach correctly handles the queue full condition?

hard

A. Increase the queue size dynamically when full.

B. Use xQueueSend with portMAX_DELAY to wait indefinitely until space is available.

C. Use xQueueSend with zero block time and check the return value to discard data if full.

D. Use xQueueOverwrite to replace the oldest data in the queue automatically.

Solution

1. Step 1: Understand non-blocking send requirement

   The task must never block, so waiting indefinitely or for a long time is not allowed.

2. Step 2: Choose correct send method and handling

   Using xQueueSend with zero block time returns immediately. Checking the return value lets the task discard data if the queue is full.

3. Step 3: Evaluate other options

   Use xQueueSend with portMAX_DELAY to wait indefinitely until space is available. blocks indefinitely, violating requirement. Use xQueueOverwrite to replace the oldest data in the queue automatically. overwrites data but may lose important info. Increase the queue size dynamically when full. is not supported by FreeRTOS.

4. Final Answer:

   Use xQueueSend with zero block time and check the return value to discard data if full. -> Option C

5. Quick Check:

   Non-blocking send + check return = safe discard [OK]

Hint: Send zero wait + check return to avoid blocking [OK]

Common Mistakes:

• Using blocking send when non-blocking needed
• Assuming queue size can grow dynamically
• Ignoring return value of send