Waiting for event bits (AND/OR) in FreeRTOS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What does waiting for event bits with AND condition mean in FreeRTOS?

It means the task waits until all specified event bits are set before continuing. The task blocks until every bit in the mask is set.

beginner

What happens when you wait for event bits with OR condition in FreeRTOS?

The task unblocks as soon as any one of the specified event bits is set. It does not wait for all bits, just one or more.

beginner

Which FreeRTOS API function is used to wait for event bits?

xEventGroupWaitBits() is used to wait for event bits with options for AND/OR conditions and timeout.

intermediate

What does the parameter 'xWaitForAllBits' control in xEventGroupWaitBits()?

It controls whether the task waits for all bits (pdTRUE) or any bit (pdFALSE) in the bitmask before unblocking.

intermediate

Why is it important to clear event bits after waiting in FreeRTOS?

Clearing event bits prevents the task from immediately unblocking again on the same bits, ensuring correct synchronization.

In FreeRTOS, if you want a task to wait until all bits 0x03 are set, which parameter should you use in xEventGroupWaitBits()?

A Set xWaitForAllBits to true

B Set xWaitForAllBits to false

C Set the timeout to zero

D Use a different API function

Setting xWaitForAllBits to true makes the task wait until all bits in the mask (0x03) are set.

What does xEventGroupWaitBits() return when the timeout expires without the bits being set?

A The function blocks forever

B An error code

C The bits that were set at timeout (possibly zero)

D Always zero

It returns the bits that were set at the time of timeout, which may be zero if none were set.

If you want a task to unblock when any one bit of 0x0F is set, what should xWaitForAllBits be?

A False

B True

C Ignored

D Set to the bitmask value

Setting xWaitForAllBits to false makes the task unblock when any bit in the mask is set.

Which of these is NOT a reason to clear event bits after waiting?

A To reset synchronization state

B To save memory

C To avoid immediate re-unblocking

D To ensure correct task sequencing

Clearing bits is about synchronization, not memory saving.

What type of synchronization primitive are event groups in FreeRTOS?

A Binary semaphore

B Counting semaphore

C Mutex

D Bitwise event flags

Event groups use bitwise event flags to synchronize tasks based on bits.

Explain how waiting for event bits with AND and OR conditions works in FreeRTOS.

Think about how tasks wait for multiple signals at once.

Describe why and how you should clear event bits after a task unblocks in FreeRTOS.

Consider what happens if bits stay set.

Practice

1. What does waiting for event bits in FreeRTOS allow a task to do?

easy

A. Pause execution until specific event bits are set

B. Run continuously without interruption

C. Automatically clear all event bits on start

D. Create new event bits dynamically

Solution

1. Step 1: Understand event bits purpose

   Event bits are signals that tasks can wait for to synchronize actions.

2. Step 2: Identify what waiting means

   Waiting means the task pauses until the required bits are set.

3. Final Answer:

   Pause execution until specific event bits are set -> Option A

4. Quick Check:

   Waiting for event bits = pause task until bits set [OK]

Hint: Waiting means pausing until bits signal event [OK]

Common Mistakes:

• Thinking waiting means running continuously
• Confusing event bits with task creation
• Assuming bits clear automatically on start

2. Which of the following is the correct syntax to wait for event bits using AND mode in FreeRTOS?

easy

A. xEventGroupClearBits(eventGroup, bitsToWaitFor);

B. xEventGroupWaitBits(eventGroup, bitsToWaitFor, clearOnExit, pdFALSE, timeout);

C. xEventGroupWaitBits(eventGroup, bitsToWaitFor, clearOnExit, pdTRUE, timeout);

D. xEventGroupSetBits(eventGroup, bitsToWaitFor);

Solution

1. Step 1: Identify the AND mode parameter

   The fourth parameter is pdTRUE to wait for all bits (AND mode).

2. Step 2: Confirm function usage

   xEventGroupWaitBits waits for bits with parameters: event group, bits, clear flag, wait mode, timeout.

3. Final Answer:

   xEventGroupWaitBits(eventGroup, bitsToWaitFor, clearOnExit, pdTRUE, timeout); -> Option C

4. Quick Check:

   pdTRUE means AND mode in wait bits [OK]

Hint: pdTRUE means wait for all bits (AND) [OK]

Common Mistakes:

• Using pdFALSE for AND mode
• Confusing SetBits with WaitBits
• Mixing up clearOnExit parameter

3. Given the code snippet:

EventBits_t bits = xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdTRUE, pdFALSE, 1000);

What does bits contain if only BIT_1 is set in the event group before the call?

medium

A. Only BIT_1 set in bits

B. Both BIT_1 and BIT_2 set in bits

C. Zero (no bits set)

D. Function blocks indefinitely

Solution

1. Step 1: Understand wait mode pdFALSE

   pdFALSE means OR mode: wait for any bit set.

2. Step 2: Check which bits are set before call

   Only BIT_1 is set, but the third parameter is pdTRUE (clearOnExit), and the fourth parameter is pdFALSE (waitForAll = false), so the function waits for any bit set.

3. Step 3: Analyze the code

   However, the third parameter is pdTRUE (clearOnExit), so bits are cleared on exit. But since waitForAll is pdFALSE, the function returns when any bit is set.

4. Step 4: But the question is what bits contains if only BIT_1 is set before call

   Since waitForAll is false, the function returns immediately with bits containing BIT_1 set.

5. Final Answer:

   Only BIT_1 set in bits -> Option A

6. Quick Check:

   OR mode returns bits set among requested [OK]

Hint: pdFALSE means OR mode, returns any set bits [OK]

Common Mistakes:

• Assuming both bits must be set for return
• Thinking function blocks if not all bits set
• Confusing pdTRUE and pdFALSE meanings

4. Identify the error in this code snippet:

EventBits_t bits = xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdTRUE, pdTRUE, 500);

What is wrong?

medium

A. pdTRUE for waitForAll means wait for all bits, but clearOnExit should be false to avoid clearing

B. pdTRUE for clearOnExit clears bits on exit, which is valid; no error

C. Using pdTRUE for both clearOnExit and waitForAll bits is correct

D. pdTRUE for waitForAll is invalid; must be pdFALSE

Solution

1. Step 1: Understand clearOnExit parameter

   pdTRUE means bits are cleared when function returns.

2. Step 2: Understand waitForAll parameter

   pdTRUE means wait for all bits (AND mode), which is valid.

3. Final Answer:

   pdTRUE for clearOnExit clears bits on exit, which is valid; no error -> Option B

4. Quick Check:

   clearOnExit pdTRUE is allowed and common [OK]

Hint: clearOnExit pdTRUE clears bits on return, allowed [OK]

Common Mistakes:

• Thinking clearOnExit pdTRUE is always wrong
• Confusing waitForAll with clearOnExit
• Assuming pdTRUE for waitForAll is invalid

5. You want a task to wait until both BIT_1 and BIT_2 are set, then clear those bits automatically on exit. Which call achieves this correctly?

hard

A. xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdFALSE, pdTRUE, portMAX_DELAY);

B. xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdFALSE, pdFALSE, portMAX_DELAY);

C. xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdTRUE, pdFALSE, portMAX_DELAY);

D. xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdTRUE, pdTRUE, portMAX_DELAY);

Solution

1. Step 1: Identify wait for all bits

   Fourth parameter pdTRUE means wait for all bits (AND mode).

2. Step 2: Identify clear bits on exit

   Third parameter pdTRUE means clear bits on exit.

3. Step 3: Match parameters to options

   xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdTRUE, pdTRUE, portMAX_DELAY); uses clearOnExit = pdTRUE and waitForAll = pdTRUE, correct for requirement.

4. Final Answer:

   xEventGroupWaitBits(eventGroup, BIT_1 | BIT_2, pdTRUE, pdTRUE, portMAX_DELAY); -> Option D

5. Quick Check:

   Clear bits and wait all bits = clearOnExit pdTRUE, waitForAll pdTRUE [OK]

Hint: clearOnExit and waitForAll both pdTRUE for AND + clear [OK]

Common Mistakes:

• Mixing up clearOnExit and waitForAll parameters
• Using pdFALSE for waitForAll when AND needed
• Not setting timeout to wait indefinitely