Why event groups coordinate tasks in FreeRTOS - Performance Analysis

Time Complexity: Why event groups coordinate tasks

O(n)

Understanding Time Complexity

When tasks wait for events in FreeRTOS, event groups help coordinate them efficiently.

We want to see how the time to handle events grows as more tasks wait.

Scenario Under Consideration

Analyze the time complexity of this event group coordination code.

EventBits_t uxBits;

// Task waits for bits 0x03 (bit 0 and 1) to be set
uxBits = xEventGroupWaitBits(
    xEventGroup,      // The event group handle
    0x03,             // Bits to wait for
    pdTRUE,           // Clear bits on exit
    pdTRUE,           // Wait for all bits
    portMAX_DELAY);   // Wait forever

// Another task sets bits
xEventGroupSetBits(xEventGroup, 0x01);
xEventGroupSetBits(xEventGroup, 0x02);

This code shows tasks waiting for event bits and other tasks setting those bits to unblock them.

Identify Repeating Operations

Look for loops or repeated checks inside the event group handling.

• Primary operation: Checking event bits and waking waiting tasks.
• How many times: Once per event bit set and per waiting task.

How Execution Grows With Input

As more tasks wait on event bits, the system checks and wakes each one when bits match.

Input Size (n tasks waiting)	Approx. Operations
10	10 checks and possible wakes
100	100 checks and possible wakes
1000	1000 checks and possible wakes

Pattern observation: The work grows linearly as more tasks wait for events.

Final Time Complexity

Time Complexity: O(n)

This means the time to coordinate tasks grows directly with the number of waiting tasks.

Common Mistake

[X] Wrong: "Event groups wake all tasks instantly with no extra checks."

[OK] Correct: The system must check each waiting task's event bits to decide who to wake, so time grows with tasks.

Interview Connect

Understanding how event groups scale helps you explain task synchronization clearly and confidently.

Self-Check

"What if event groups used a different data structure to track waiting tasks? How would that affect time complexity?"

Practice

1. What is the main purpose of event groups in FreeRTOS?

easy

A. To handle hardware interrupts directly

B. To create new tasks dynamically

C. To let tasks wait for or signal events using bits

D. To manage memory allocation

Solution

1. Step 1: Understand event groups role

   Event groups use bits to represent events that tasks can wait for or signal.

2. Step 2: Compare with other options

   Creating tasks, managing memory, and handling interrupts are different FreeRTOS features.

3. Final Answer:

   To let tasks wait for or signal events using bits -> Option C

4. Quick Check:

   Event groups coordinate tasks by signaling bits [OK]

Hint: Event groups use bits to sync tasks quickly [OK]

Common Mistakes:

• Confusing event groups with task creation
• Thinking event groups manage memory
• Assuming event groups handle interrupts

2. Which of the following is the correct way to create an event group in FreeRTOS?

easy

A. vEventGroupCreate()

B. xEventGroupCreate()

C. xCreateEventGroup()

D. vCreateEventGroup()

Solution

1. Step 1: Recall FreeRTOS naming conventions

   Functions returning handles usually start with 'x' and create functions end with 'Create'.

2. Step 2: Identify correct function

   The correct function to create an event group is xEventGroupCreate().

3. Final Answer:

   xEventGroupCreate() -> Option B

4. Quick Check:

   Event group creation uses xEventGroupCreate() [OK]

Hint: Creation functions start with 'x' and end with 'Create' [OK]

Common Mistakes:

• Using 'v' prefix which is for void functions
• Swapping function name order
• Assuming event groups are created with task functions

3. Given the code snippet:

EventGroupHandle_t xEventGroup = xEventGroupCreate();
const EventBits_t BIT_0 = (1 << 0);
xEventGroupSetBits(xEventGroup, BIT_0);
EventBits_t uxBits = xEventGroupWaitBits(xEventGroup, BIT_0, pdTRUE, pdFALSE, portMAX_DELAY);

What will be the value of uxBits after xEventGroupWaitBits returns?

medium

A. BIT_0

B. portMAX_DELAY

C. 0

D. pdTRUE

Solution

1. Step 1: Understand bit setting and waiting

   BIT_0 is set before waiting, so the wait function will return with BIT_0 set.

2. Step 2: Analyze parameters

   pdTRUE clears the bits after return, but uxBits holds the bits that were set when the function returned.

3. Final Answer:

   BIT_0 -> Option A

4. Quick Check:

   Wait returns bits that were set, here BIT_0 [OK]

Hint: Wait returns bits set before clearing if pdTRUE used [OK]

Common Mistakes:

• Assuming bits clear before return
• Confusing return value with delay constant
• Ignoring bit mask value

4. Identify the error in this FreeRTOS event group usage:

EventGroupHandle_t xEventGroup;
xEventGroupSetBits(xEventGroup, (1 << 1));

medium

A. Event groups cannot set bits directly

B. Bit mask (1 << 1) is invalid

C. xEventGroupSetBits requires a pointer to the event group

D. xEventGroup is not initialized before use

Solution

1. Step 1: Check event group initialization

   xEventGroup is declared but never created or assigned a valid handle.

2. Step 2: Understand function requirements

   xEventGroupSetBits requires a valid event group handle, which is missing here.

3. Final Answer:

   xEventGroup is not initialized before use -> Option D

4. Quick Check:

   Event group must be created before setting bits [OK]

Hint: Always create event group before using it [OK]

Common Mistakes:

• Using uninitialized event group handle
• Misunderstanding bit mask validity
• Passing pointer instead of handle

5. You want two tasks to wait until both have signaled readiness using event groups. Which approach correctly coordinates this?

hard

A. Each task sets a unique bit; both wait for both bits set before proceeding

B. Both tasks set the same bit and wait for that bit to be set

C. Tasks use separate event groups and wait independently

D. Tasks use a global variable instead of event groups

Solution

1. Step 1: Understand event group bits for coordination

   Each task sets a unique bit representing its readiness.

2. Step 2: Wait for both bits set

   Tasks wait for the combination of both bits to be set before continuing.

3. Final Answer:

   Each task sets a unique bit; both wait for both bits set before proceeding -> Option A

4. Quick Check:

   Unique bits per task coordinate readiness [OK]

Hint: Use unique bits per task and wait for all bits [OK]

Common Mistakes:

• Using same bit for multiple tasks
• Using separate event groups losing coordination
• Ignoring event groups and using variables