freertos-patterns

FreeRTOS dual-core coordination on ESP32 uses core pinning to assign tasks to Core0 or Core1 and leverages queues or task notifications for safe inter-core communication. This separation prevents WiFi operations from blocking sensor reads.

The best way to handle inter-task communication in ESP32 FreeRTOS is using queues for passing data payloads and semaphores for signaling. Binary and counting semaphores, along with task notifications, safely coordinate work without race conditions.

FreeRTOS mutexes with priority inheritance prevent deadlocks by temporarily elevating a low-priority task holding a resource to match the priority of a high-priority task waiting for it. This synchronization mechanism ensures safe resource access without indefinite blocking.

Yes, this FreeRTOS multitasking pattern library fully supports the RP2040 two-core model. It provides specific dual-core coordination examples demonstrating RP2040 setups alongside ESP32 Core0/Core1 separation for robust embedded firmware multitasking.

You should use FreeRTOS event groups instead of queues when multiple tasks must wait for multiple conditions simultaneously. Event groups facilitate multi-condition waits and broadcast signaling, whereas queues are designed for passing sequential data items between tasks.

You need software timers in FreeRTOS to execute periodic or predictable timing functions without blocking tasks with delay loops. They affect multitasking by offloading timed events to the timer service task, keeping main application threads responsive.