Setting and clearing event bits in FreeRTOS - Time & Space Complexity

Time Complexity: Setting and clearing event bits

O(1)

Understanding Time Complexity

When working with FreeRTOS event bits, it's important to understand how the time to set or clear bits changes as the number of bits grows.

We want to know how the cost of these operations grows when more event bits are involved.

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

// Set and clear event bits example
EventGroupHandle_t eventGroup = xEventGroupCreate();

// Set bits 0 and 1
xEventGroupSetBits(eventGroup, (1 << 0) | (1 << 1));

// Clear bit 0
xEventGroupClearBits(eventGroup, (1 << 0));
    

This code creates an event group, sets two bits, and then clears one bit in the group.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Checking and updating bits inside the event group's bit field.
• How many times: The operation runs once per call, processing all bits in a fixed-size integer (usually 32 bits).

How Execution Grows With Input

The time to set or clear bits depends on the number of bits in the event group, which is fixed (commonly 32 bits).

Input Size (number of bits)	Approx. Operations
10	10 checks and updates
32	32 checks and updates
64	64 checks and updates (if supported)

Pattern observation: The operations grow linearly with the number of bits, but since the bit count is fixed and small, the time stays constant in practice.

Final Time Complexity

Time Complexity: O(1)

This means setting or clearing event bits takes about the same time regardless of how many bits are set, because the bit field size is fixed.

Common Mistake

[X] Wrong: "Setting multiple bits takes longer for each bit set, so time grows with the number of bits set."

[OK] Correct: The operation checks all bits in a fixed-size field each time, so time depends on the total bit field size, not how many bits are set.

Interview Connect

Understanding how fixed-size bit operations work helps you reason about efficient signaling and synchronization in embedded systems.

Self-Check

"What if the event group supported a variable number of bits instead of a fixed size? How would the time complexity change?"

Practice

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

easy

A. To create a new event group

B. To clear (reset) specific bits in an event group

C. To set (signal) specific bits in an event group

D. To delete an existing event group

Solution

1. Step 1: Understand the function name

   xEventGroupSetBits() suggests setting bits, which means signaling events.

2. Step 2: Compare with other functions

   xEventGroupClearBits() is used to clear bits, so setting bits is done by xEventGroupSetBits().

3. Final Answer:

   To set (signal) specific bits in an event group -> Option C

4. Quick Check:

   Set bits = signal events [OK]

Hint: Set bits means signal events, clear bits means reset [OK]

Common Mistakes:

• Confusing setting bits with clearing bits
• Thinking it creates or deletes event groups
• Mixing up function names

2. Which of the following is the correct syntax to clear bits 0x03 in an event group named myEventGroup?

easy

A. xEventGroupClear(myEventGroup, 0x03);

B. xEventGroupSetBits(myEventGroup, 0x03);

C. xClearEventBits(myEventGroup, 0x03);

D. xEventGroupClearBits(myEventGroup, 0x03);

Solution

1. Step 1: Identify the correct function for clearing bits

   The function to clear bits is xEventGroupClearBits().

2. Step 2: Check the syntax

   The correct syntax is xEventGroupClearBits(eventGroupHandle, bitsToClear);. xEventGroupClearBits(myEventGroup, 0x03); matches this exactly.

3. Final Answer:

   xEventGroupClearBits(myEventGroup, 0x03); -> Option D

4. Quick Check:

   Clear bits syntax = xEventGroupClearBits(handle, bits) [OK]

Hint: Clear bits uses xEventGroupClearBits with group and bit mask [OK]

Common Mistakes:

• Using xEventGroupSetBits to clear bits
• Using incorrect function names
• Missing parameters or wrong order

3. Given the code snippet:

EventBits_t bits;
bits = xEventGroupSetBits(myEventGroup, 0x05);
bits = xEventGroupClearBits(myEventGroup, 0x01);

What is the value of bits after these calls if the initial bits were 0x00?

medium

A. 0x00

B. 0x05

C. 0x04

D. 0x01

Solution

1. Step 1: First call - xEventGroupSetBits(myEventGroup, 0x05)

   Initial event group: 0x00. Returns bits BEFORE setting: 0x00 (event group becomes 0x05). bits = 0x00.

2. Step 2: Second call - xEventGroupClearBits(myEventGroup, 0x01)

   Event group now: 0x05. Returns bits BEFORE clearing: 0x05 (event group becomes 0x04). bits = 0x05.

3. Final Answer:

   0x00 -> Option A

4. Quick Check:

   Return value = pre-operation bits [OK]

Hint: xEventGroupSetBits/ClearBits return bits BEFORE operation [OK]

Common Mistakes:

• Confusing return value (pre-op) with post-op event group state
• Miscalculating bitwise operations on event group
• Forgetting return value overwrites 'bits' each call

4. Identify the error in this code snippet:

EventGroupHandle_t myEventGroup;
myEventGroup = xEventGroupCreate();
xEventGroupClearBits(0x01, myEventGroup);

medium

A. Arguments to xEventGroupClearBits are reversed

B. xEventGroupCreate() returns void, not a handle

C. xEventGroupClearBits requires a pointer, not a value

D. Missing include for FreeRTOS headers

Solution

1. Step 1: Check function parameter order

   xEventGroupClearBits() expects (EventGroupHandle_t, EventBits_t). The code passes (0x01, myEventGroup), which is reversed.

2. Step 2: Confirm return type of xEventGroupCreate()

   xEventGroupCreate() returns an EventGroupHandle_t, so assignment is correct.

3. Final Answer:

   Arguments to xEventGroupClearBits are reversed -> Option A

4. Quick Check:

   Function parameters order matters [OK]

Hint: Check parameter order carefully for FreeRTOS API calls [OK]

Common Mistakes:

• Swapping parameters in API calls
• Assuming wrong return types
• Ignoring compiler warnings

5. You want to signal two events represented by bits 0x01 and 0x04, then immediately clear bit 0x01 without affecting others. Which sequence correctly achieves this?

hard

A. xEventGroupClearBits(myEventGroup, 0x05); xEventGroupSetBits(myEventGroup, 0x01);

B. xEventGroupSetBits(myEventGroup, 0x05); xEventGroupClearBits(myEventGroup, 0x01);

C. xEventGroupSetBits(myEventGroup, 0x01); xEventGroupClearBits(myEventGroup, 0x04);

D. xEventGroupClearBits(myEventGroup, 0x01); xEventGroupSetBits(myEventGroup, 0x05);

Solution

1. Step 1: Set bits 0x01 and 0x04 together

   Setting bits 0x05 (binary 0101) signals both events at once.

2. Step 2: Clear only bit 0x01

   Clearing bit 0x01 removes that event signal but leaves 0x04 set.

3. Final Answer:

   xEventGroupSetBits(myEventGroup, 0x05); xEventGroupClearBits(myEventGroup, 0x01); -> Option B

4. Quick Check:

   Set both bits then clear one bit [OK]

Hint: Set all bits first, then clear only the unwanted bit [OK]

Common Mistakes:

• Clearing bits before setting them
• Clearing wrong bits
• Not combining bits correctly