[Solved] What is wrong with this event-driven task code?void vTask(void... What is wrong with this event-driven task code?void vTask(void *pvParameters) { EventGroupHandle_t xEventGroup = xEventGroupCreate(); | FreeRTOS

FreeRTOS - Design Patterns for RTOS

What is wrong with this event-driven task code?

void vTask(void *pvParameters) {
  EventGroupHandle_t xEventGroup = xEventGroupCreate();
  xEventGroupWaitBits(xEventGroup, 0x01, pdTRUE, pdFALSE, portMAX_DELAY);
}

AxEventGroupWaitBits() cannot be called with portMAX_DELAY

BThe task does not delete itself after waiting

CThe bit mask 0x01 is invalid

DThe event group is created inside the task and not shared

Step-by-Step Solution

Solution:

Step 1: Analyze event group creation location
The event group is created inside the task, so other tasks cannot share it.
Step 2: Understand sharing requirement in event-driven design
Event groups should be created outside tasks and shared for synchronization.
Final Answer:
The event group is created inside the task and not shared -> Option D
Quick Check:
Event groups must be shared for inter-task sync [OK]

Quick Trick: Create event groups outside tasks for sharing [OK]

Common Mistakes:

Creating event groups inside tasks
Misunderstanding portMAX_DELAY usage
Assuming bit mask 0x01 is invalid

Master "Design Patterns for RTOS" in FreeRTOS

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

More FreeRTOS Quizzes

What is wrong with this event-driven task code?

Step 1: Analyze event group creation location

Step 2: Understand sharing requirement in event-driven design

Final Answer:

Quick Check:

Want More Practice?