Producer-consumer pattern in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Producer-Consumer pattern in FreeRTOS?

It is a design where one task (producer) creates data and another task (consumer) processes it, using synchronization tools like queues to safely share data.

beginner

How does a queue help in the Producer-Consumer pattern?

A queue acts like a safe mailbox where the producer puts data and the consumer takes data, ensuring no data is lost or corrupted.

intermediate

What happens if the queue is full when the producer tries to add data?

The producer task can block (wait) until space is available or handle the full queue by discarding data or retrying later.

intermediate

Why is it important to avoid busy waiting in the Producer-Consumer pattern?

Busy waiting wastes CPU time by constantly checking for data. Using blocking calls lets the CPU sleep or do other work until data is ready.

beginner

Name two FreeRTOS functions commonly used in the Producer-Consumer pattern.

xQueueSend() for the producer to add data, and xQueueReceive() for the consumer to get data from the queue.

In FreeRTOS, what does the producer task do in the Producer-Consumer pattern?

A Processes data from the queue

B Blocks the queue permanently

C Deletes the consumer task

D Creates data and sends it to a queue

The producer creates data and sends it to the queue for the consumer to process.

Which FreeRTOS function does the consumer task use to receive data?

A xQueueReceive()

B vTaskDelay()

C xQueueSend()

D xTaskCreate()

xQueueReceive() is used by the consumer to get data from the queue.

What happens if the consumer tries to receive data from an empty queue with blocking enabled?

A The consumer task waits until data is available

B The consumer task crashes

C The queue deletes itself

D The producer task stops

With blocking enabled, the consumer waits (blocks) until data arrives in the queue.

Why is using a queue better than sharing a variable directly between producer and consumer?

A Queues allow tasks to run without synchronization

B Queues are slower but easier to code

C Queues prevent data corruption by managing access safely

D Queues use more memory but are less reliable

Queues handle synchronization and prevent data corruption when sharing data between tasks.

Which of these is NOT a benefit of the Producer-Consumer pattern?

A Improves task synchronization

B Eliminates the need for queues

C Decouples data production and consumption timing

D Allows tasks to run independently

Queues are essential in this pattern to safely pass data; the pattern does not eliminate their need.

Explain how the Producer-Consumer pattern works in FreeRTOS using queues.

Think about how two friends pass notes safely without losing them.

Describe what happens when the queue is full or empty in the Producer-Consumer pattern.

Imagine a mailbox that can be full or empty and how people wait or act accordingly.

Practice

1.

In FreeRTOS, what is the main role of the queue in the producer-consumer pattern?

easy

A. To create new tasks dynamically

B. To handle interrupts directly

C. To manage memory allocation for tasks

D. To safely transfer data between producer and consumer tasks

Solution

1. Step 1: Understand the producer-consumer pattern

   The pattern involves one task producing data and another consuming it, requiring safe data sharing.

2. Step 2: Identify the role of the queue in FreeRTOS

   The queue acts as a safe buffer that holds data items, ensuring tasks do not access the same data simultaneously.

3. Final Answer:

   To safely transfer data between producer and consumer tasks -> Option D

4. Quick Check:

   Queue = Safe data transfer [OK]

Hint: Queues safely pass data between tasks without conflicts [OK]

Common Mistakes:

• Thinking queues create tasks
• Confusing queues with memory management
• Assuming queues handle interrupts

2.

Which of the following is the correct FreeRTOS API call for a producer task to send data to a queue?

void producerTask(void *params) {
    int data = 10;
    // Send data to queue here
}

easy

A. xQueueSend(queueHandle, &data, portMAX_DELAY);

B. xQueueReceive(queueHandle, &data, portMAX_DELAY);

C. xTaskCreate(queueHandle, &data, portMAX_DELAY);

D. vTaskDelay(queueHandle);

Solution

1. Step 1: Identify the correct API for sending data to a queue

   FreeRTOS uses xQueueSend() to send data from a producer to a queue.

2. Step 2: Check other options for correctness

   xQueueReceive() is for receiving data, xTaskCreate() creates tasks, and vTaskDelay() delays tasks, so they are incorrect here.

3. Final Answer:

   xQueueSend(queueHandle, &data, portMAX_DELAY); -> Option A

4. Quick Check:

   Send data = xQueueSend [OK]

Hint: Use xQueueSend to put data into the queue [OK]

Common Mistakes:

• Using xQueueReceive to send data
• Confusing task creation with queue operations
• Using delay functions instead of queue functions

3.

Consider this FreeRTOS code snippet where a producer sends integers 1 to 3 to a queue and a consumer receives them:

int data;
for (int i = 1; i <= 3; i++) {
    xQueueSend(queueHandle, &i, 0);
}
for (int j = 0; j < 3; j++) {
    xQueueReceive(queueHandle, &data, 0);
    printf("%d ", data);
}

What will be the output?

medium

A. 1 2 3

B. 3 2 1

C. 0 0 0

D. Compilation error

Solution

1. Step 1: Analyze the producer loop

   The producer sends values 1, 2, and 3 in order to the queue without delay.

2. Step 2: Analyze the consumer loop

   The consumer receives three values from the queue and prints them in the order received.

3. Final Answer:

   1 2 3 -> Option A

4. Quick Check:

   Queue preserves order = 1 2 3 [OK]

Hint: Queue keeps order; output matches sent sequence [OK]

Common Mistakes:

• Assuming queue reverses order
• Expecting zeros due to uninitialized data
• Thinking code won't compile

4.

Identify the bug in this FreeRTOS consumer task code that causes it to never receive data:

void consumerTask(void *params) {
    int receivedData;
    while(1) {
        if(xQueueReceive(queueHandle, &receivedData, 0) == pdFALSE) {
            // No data received
            continue;
        }
        processData(receivedData);
    }
}

medium

A. The loop should use vTaskDelay instead of continue

B. The receive timeout is zero, causing missed data

C. The processData function is missing

D. The queue handle is not initialized

Solution

1. Step 1: Understand xQueueReceive timeout parameter

   A zero timeout means the call returns immediately if no data is available, possibly missing data if producer is slower.

2. Step 2: Identify why data is never received

   Because the consumer never waits, it may loop too fast and miss data arriving slightly later.

3. Final Answer:

   The receive timeout is zero, causing missed data -> Option B

4. Quick Check:

   Timeout 0 means no wait = missed data [OK]

Hint: Use non-zero timeout to wait for data [OK]

Common Mistakes:

• Ignoring timeout effect on receive
• Assuming missing queue handle causes this
• Thinking processData absence causes no receive

5.

You want to implement a producer-consumer system where the producer sends sensor readings every 100ms, and the consumer processes them. Which FreeRTOS queue configuration and task design is best to avoid data loss and ensure timely processing?

hard

A. Use a queue with length 5 and consumer uses zero timeout on receive

B. Use a queue with length 1 and zero receive timeout in consumer

C. Use a queue with length 10 and consumer waits with portMAX_DELAY on receive

D. Use no queue and share a global variable with no synchronization

Solution

1. Step 1: Consider queue length for buffering

   A queue length of 10 allows buffering multiple sensor readings if consumer is busy, preventing data loss.

2. Step 2: Consider consumer receive timeout

   Using portMAX_DELAY makes consumer wait indefinitely for data, ensuring it processes every reading.

3. Final Answer:

   Use a queue with length 10 and consumer waits with portMAX_DELAY on receive -> Option C

4. Quick Check:

   Buffer + wait = no data loss [OK]

Hint: Use bigger queue and wait on receive to avoid loss [OK]

Common Mistakes:

• Using too small queue causing data overwrite
• Using zero timeout causing missed data
• Sharing data without synchronization