Why event groups coordinate tasks in FreeRTOS

Introduction

Event groups help tasks work together by letting them wait for or signal events easily. This keeps tasks in sync without wasting time.

When multiple tasks need to wait for the same event before continuing.

When tasks must signal each other about changes or completion of work.

When you want to avoid using many separate flags or variables for task coordination.

When tasks depend on multiple conditions being true before running.

When you want a simple way to manage task synchronization in FreeRTOS.

Syntax

FreeRTOS

EventGroupHandle_t xEventGroupCreate(void);

EventBits_t xEventGroupWaitBits(
    EventGroupHandle_t xEventGroup,
    const EventBits_t uxBitsToWaitFor,
    const BaseType_t xClearOnExit,
    const BaseType_t xWaitForAllBits,
    TickType_t xTicksToWait
);

EventBits_t xEventGroupSetBits(
    EventGroupHandle_t xEventGroup,
    const EventBits_t uxBitsToSet
);

xEventGroupCreate makes a new event group.

xEventGroupWaitBits lets a task wait for specific bits (events) to be set.

Examples

This creates a new event group to use for task coordination.

FreeRTOS

EventGroupHandle_t xEventGroup = xEventGroupCreate();
// Create an event group to hold event bits.

This sets bit 0 in the event group to notify waiting tasks.

FreeRTOS

xEventGroupSetBits(xEventGroup, BIT_0);
// Set bit 0 to signal an event happened.

The task waits until either bit 0 or bit 1 is set, then clears those bits.

FreeRTOS

xEventGroupWaitBits(xEventGroup, BIT_0 | BIT_1, pdTRUE, pdFALSE, portMAX_DELAY);
// Wait for bit 0 or bit 1 to be set, then clear them.

Sample Program

This program creates two tasks. Task1 waits for BIT_0 to be set in the event group. Task2 waits 1 second, then sets BIT_0. Task1 then continues and prints a message.

FreeRTOS

#include "FreeRTOS.h"
#include "task.h"
#include "event_groups.h"
#include <stdio.h>

#define BIT_0 (1 << 0)
#define BIT_1 (1 << 1)

EventGroupHandle_t xEventGroup;

void vTask1(void *pvParameters) {
    printf("Task1: Waiting for BIT_0...\n");
    xEventGroupWaitBits(xEventGroup, BIT_0, pdTRUE, pdFALSE, portMAX_DELAY);
    printf("Task1: BIT_0 received, running task1 code.\n");
    vTaskDelete(NULL);
}

void vTask2(void *pvParameters) {
    printf("Task2: Setting BIT_0 after delay...\n");
    vTaskDelay(pdMS_TO_TICKS(1000));
    xEventGroupSetBits(xEventGroup, BIT_0);
    printf("Task2: BIT_0 set.\n");
    vTaskDelete(NULL);
}

int main(void) {
    xEventGroup = xEventGroupCreate();
    xTaskCreate(vTask1, "Task1", 1000, NULL, 1, NULL);
    xTaskCreate(vTask2, "Task2", 1000, NULL, 1, NULL);
    vTaskStartScheduler();
    for(;;) {}
    return 0;
}

Important Notes

Event groups use bits to represent events, so you can wait for multiple events at once.

Clearing bits on exit helps avoid repeated triggers for the same event.

Use event groups to reduce CPU usage by avoiding busy waiting.

Summary

Event groups let tasks wait for or signal events using bits.

They help tasks work together smoothly and efficiently.

Use event groups to coordinate multiple tasks in FreeRTOS easily.

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