xQueueSend() and xQueueReceive() in FreeRTOS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to send an item to the queue.

FreeRTOS

xQueueSend(queueHandle, &[1], portMAX_DELAY);

Drag options to blanks, or click blank then click option'

AqueueHandle

Bitem

CportMAX_DELAY

D&item

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the queue handle instead of the item.

Passing the delay constant instead of the item.

The first argument after the queue handle is the pointer to the item to send. Here, item is the variable holding the data.

2fill in blank

medium

Complete the code to receive an item from the queue.

FreeRTOS

xQueueReceive(queueHandle, &[1], portMAX_DELAY);

Drag options to blanks, or click blank then click option'

AqueueHandle

B&item

Citem

DportMAX_DELAY

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the address of the variable when the code already has &.

Passing the queue handle instead of the variable.

The second argument to xQueueReceive is a pointer to the variable where the received data will be stored. So, &item is correct, but since the code already has &, just item is needed.

3fill in blank

hard

Fix the error in the code to send data to the queue.

FreeRTOS

xQueueSend(queueHandle, [1], portMAX_DELAY);

Drag options to blanks, or click blank then click option'

Aitem

BportMAX_DELAY

CqueueHandle

D&item

Attempts:

3 left

💡 Hint

Common Mistakes

Passing the variable directly instead of its address.

Passing the queue handle instead of the data.

The second argument must be a pointer to the data. So, &item is correct.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that stores the length of each word if the length is greater than 3.

FreeRTOS

{word: [1] for word in words if [2]

Drag options to blanks, or click blank then click option'

Alen(word)

Blen(word) > 3

Cword

Dlen(words)

Attempts:

3 left

💡 Hint

Common Mistakes

Using word instead of len(word) for the value.

Checking length of the whole list instead of each word.

The dictionary comprehension maps each word to its length using len(word). The condition filters words with length greater than 3 using len(word) > 3.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that stores uppercase keys and values only if the value is positive.

FreeRTOS

{ [1]: [2] for [3], v in data.items() if v > 0 }

Drag options to blanks, or click blank then click option'

Ak.upper()

Bv

Ck

Dv.upper()

Attempts:

3 left

💡 Hint

Common Mistakes

Using v.upper() which is invalid if values are not strings.

Using k as value or v as key.

The keys are converted to uppercase with k.upper(). The values are kept as v. The loop variable is k for keys.

Practice

1. What is the primary purpose of the xQueueSend() function in FreeRTOS?

easy

A. To remove an item from a queue

B. To add an item to a queue for other tasks to receive

C. To create a new queue

D. To delete an existing queue

Solution

1. Step 1: Understand the role of xQueueSend()

   xQueueSend() is used to place data into a queue so that other tasks can retrieve it later.

2. Step 2: Differentiate from other queue functions

   Functions like xQueueReceive() remove data, while xQueueCreate() and xQueueDelete() manage queue lifecycle, not data transfer.

3. Final Answer:

   To add an item to a queue for other tasks to receive -> Option B

4. Quick Check:

   xQueueSend() adds data [OK]

Hint: Remember: Send puts data in, Receive takes data out [OK]

Common Mistakes:

• Confusing sending with receiving
• Thinking it creates or deletes queues
• Ignoring the function's data transfer role

2. Which of the following is the correct syntax to send data to a queue using xQueueSend()?

easy

A. xQueueSend(queueHandle, data, 0);

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

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

D. xQueueSend(queueHandle, &data);

Solution

1. Step 1: Check parameter types for xQueueSend()

   The function expects the queue handle, a pointer to the data, and a timeout value.

2. Step 2: Match the correct syntax

   xQueueSend(queueHandle, &data, portMAX_DELAY); correctly passes the queue handle, address of data, and a timeout constant portMAX_DELAY.

3. Final Answer:

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

4. Quick Check:

   Queue handle + &data + timeout = correct syntax [OK]

Hint: Always pass data by address and include timeout [OK]

Common Mistakes:

• Passing data by value instead of pointer
• Omitting the timeout parameter
• Passing queue handle by address

3. Consider the following code snippet:

int value = 10;
if (xQueueSend(queue, &value, 0) == pdPASS) {
    int receivedValue = 0;
    if (xQueueReceive(queue, &receivedValue, 0) == pdPASS) {
        printf("%d", receivedValue);
    }
}

What will be printed when this code runs?

medium

A. 10

B. 0

C. No output (queue empty)

D. Compilation error

Solution

1. Step 1: Analyze xQueueSend() call

   The value 10 is sent to the queue with zero wait time. If the queue is not full, it returns pdPASS.

2. Step 2: Analyze xQueueReceive() call

   The code tries to receive from the queue immediately. Since the value was just sent, it will receive 10 and print it.

3. Final Answer:

   10 -> Option A

4. Quick Check:

   Send 10, receive 10, print 10 [OK]

Hint: Send then receive immediately prints sent value [OK]

Common Mistakes:

• Assuming queue is empty at receive
• Confusing return values with data
• Ignoring zero timeout behavior

4. What is wrong with this code snippet?

int data = 5;
if (xQueueSend(queue, data, 10) != pdPASS) {
    // handle error
}

medium

A. Data should be passed by pointer, not by value

B. Timeout value 10 is invalid

C. Return value should not be compared to pdPASS

D. Queue handle is missing

Solution

1. Step 1: Check parameter types in xQueueSend()

   The second parameter must be a pointer to the data, but here data is passed by value.

2. Step 2: Identify the error cause

   Passing data by value causes a type mismatch and likely a compilation error or incorrect behavior.

3. Final Answer:

   Data should be passed by pointer, not by value -> Option A

4. Quick Check:

   Pass &data, not data [OK]

Hint: Always pass address of data to queue functions [OK]

Common Mistakes:

• Passing data directly instead of pointer
• Misunderstanding timeout parameter
• Ignoring return value check

5. You want to send multiple integers to a queue and then receive them in order. Which approach correctly uses xQueueSend() and xQueueReceive() to achieve this without losing data?

hard

A. Use xQueueReceive() to send data and xQueueSend() to receive data

B. Send all integers at once by passing an array pointer to xQueueSend(), then receive with one xQueueReceive()

C. Send integers without checking return values, then receive once expecting all data

D. Send each integer with xQueueSend() using a timeout, then receive each with xQueueReceive() using a timeout, checking return values each time

Solution

1. Step 1: Understand queue data handling

   Queues handle one item at a time, so each integer must be sent individually with xQueueSend().

2. Step 2: Properly receive data

   Each item must be received individually with xQueueReceive(), checking return values to avoid errors or data loss.

3. Step 3: Eliminate incorrect options

   Send all integers at once by passing an array pointer to xQueueSend(), then receive with one xQueueReceive() is wrong because queues do not send arrays as single items. Send integers without checking return values, then receive once expecting all data risks data loss by ignoring return values. Use xQueueReceive() to send data and xQueueSend() to receive data reverses function roles.

4. Final Answer:

   Send each integer with xQueueSend() using a timeout, then receive each with xQueueReceive() using a timeout, checking return values each time -> Option D

5. Quick Check:

   Send and receive items one by one, check returns [OK]

Hint: Send and receive items individually, always check returns [OK]

Common Mistakes:

• Trying to send multiple items at once
• Ignoring return values causing lost data
• Mixing up send and receive functions