ESP32 FreeRTOS Task Scheduling & Prioritization

Introduction to FreeRTOS on ESP32

Writing deterministic firmware for complex Internet of Things (IoT) devices requires more than just a single sequential execution loop. When your ESP32 needs to scan sensors, handle Wi-Fi handshakes, run cryptographic operations, and update display units, a standard void loop() blocking architecture collapses. FreeRTOS (Real-Time Operating System) solves this by enabling multitasking via preemptive scheduling.

The ESP32 contains a dual-core Tensilica Xtensa LX6/LX7 microprocessor. Expressif's framework (ESP-IDF) automatically utilizes FreeRTOS to distribute tasks across both cores (Core 0 and Core 1). Understading how to schedule, prioritize, and communicate between these tasks is critical to building production-ready embedded systems.

Creating a FreeRTOS Task

In FreeRTOS, tasks are created using the xTaskCreatePinnedToCore() API. This function lets you specify task stack size, priorities, and anchor execution to a specific processor core.

void sensorTask(void *pvParameters) {
  for(;;) {
    // Poll sensors here
    vTaskDelay(pdMS_TO_TICKS(100)); // Non-blocking delay
  }
}

void setup() {
  xTaskCreatePinnedToCore(
    sensorTask,        // Function pointer
    "SensorTask",      // Task name debug tag
    4096,              // Stack depth in bytes
    NULL,              // Parameter payload
    2,                 // Task priority level
    NULL,              // Task handle reference
    1                  // Pin to Core 1
  );
}

Task Prioritization Guidelines

1. Core Assignment: Keep network tasks (WiFi/BLE) pinned to Core 0 (where the network stack lives). Run application and sensor logic on Core 1.
2. Priority Ranges: FreeRTOS uses priority levels from 0 (lowest) to configMAX_PRIORITIES - 1. High-priority tasks immediately pre-empt lower ones. Set network handlers and hardware interrupts to high priority, and telemetry upload to low priority.
3. Watchdog Feeds: Preemptive multitasking can starve lower-priority tasks if a high-priority task enters an infinite loop without releasing processor control. Always use non-blocking vTaskDelay() instead of blocking delay(). This allows the scheduler to shift contexts.

Conclusion

By leveraging FreeRTOS task pinning, structured priority assignments, and non-blocking scheduling, your ESP32 applications will remain highly responsive even under intense processing loads.

Working on a complex IoT product? Let's talk →