Skip to content

Files

Latest commit

d027a2a · Mar 20, 2025

History

History

led_strip

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Mar 20, 2025
Oct 26, 2024
Jan 17, 2023
Oct 26, 2024
Mar 20, 2025
Oct 25, 2024
Jul 2, 2024
Aug 11, 2022
Oct 25, 2024
Oct 25, 2024
Mar 20, 2025

LED Strip Driver

Component Registry

This driver is designed for addressable LEDs like WS2812, where each LED is controlled by a single data line.

Backend Controllers

The RMT Peripheral

This is the most economical way to drive the LEDs because it only consumes one RMT channel, leaving other channels free to use. However, the memory usage increases dramatically with the number of LEDs. If the RMT hardware can't be assist by DMA, the driver will going into interrupt very frequently, thus result in a high CPU usage. What's worse, if the RMT interrupt is delayed or not serviced in time (e.g. if Wi-Fi interrupt happens on the same CPU core), the RMT transaction will be corrupted and the LEDs will display incorrect colors. If you want to use RMT to drive a large number of LEDs, you'd better to enable the DMA feature if possible 1.

Allocate LED Strip Object with RMT Backend

#define BLINK_GPIO 0

/// LED strip common configuration
led_strip_config_t strip_config = {
    .strip_gpio_num = BLINK_GPIO,  // The GPIO that connected to the LED strip's data line
    .max_leds = 1,                 // The number of LEDs in the strip,
    .led_model = LED_MODEL_WS2812, // LED strip model, it determines the bit timing
    .color_component_format = LED_STRIP_COLOR_COMPONENT_FMT_GRB, // The color component format is G-R-B
    .flags = {
        .invert_out = false, // don't invert the output signal
    }
};

/// RMT backend specific configuration
led_strip_rmt_config_t rmt_config = {
    .clk_src = RMT_CLK_SRC_DEFAULT,    // different clock source can lead to different power consumption
    .resolution_hz = 10 * 1000 * 1000, // RMT counter clock frequency: 10MHz
    .mem_block_symbols = 64,           // the memory size of each RMT channel, in words (4 bytes)
    .flags = {
        .with_dma = false, // DMA feature is available on chips like ESP32-S3/P4
    }
};

/// Create the LED strip object
led_strip_handle_t led_strip;
ESP_ERROR_CHECK(led_strip_new_rmt_device(&strip_config, &rmt_config, &led_strip));

You can create multiple LED strip objects with different GPIOs and pixel numbers. The backend driver will automatically allocate the RMT channel for you if there is more available.

The SPI Peripheral

SPI peripheral can also be used to generate the timing required by the LED strip. However this backend is not as economical as the RMT one, because it will take up the whole bus, unlike the RMT just takes one channel. You CANT connect other devices to the same SPI bus if it's been used by the led_strip, because the led_strip doesn't have the concept of "Chip Select".

Please note, the SPI backend has a dependency of ESP-IDF >= 5.1

Allocate LED Strip Object with SPI Backend

#define BLINK_GPIO 0

/// LED strip common configuration
led_strip_config_t strip_config = {
    .strip_gpio_num = BLINK_GPIO,  // The GPIO that connected to the LED strip's data line
    .max_leds = 1,                 // The number of LEDs in the strip,
    .led_model = LED_MODEL_WS2812, // LED strip model, it determines the bit timing
    .color_component_format = LED_STRIP_COLOR_COMPONENT_FMT_GRB, // The color component format is G-R-B
    .flags = {
        .invert_out = false, // don't invert the output signal
    }
};

/// SPI backend specific configuration
led_strip_spi_config_t spi_config = {
    .clk_src = SPI_CLK_SRC_DEFAULT, // different clock source can lead to different power consumption
    .spi_bus = SPI2_HOST,           // SPI bus ID
    .flags = {
        .with_dma = true, // Using DMA can improve performance and help drive more LEDs
    }
};

/// Create the LED strip object
led_strip_handle_t led_strip;
ESP_ERROR_CHECK(led_strip_new_spi_device(&strip_config, &spi_config, &led_strip));

The number of LED strip objects can be created depends on how many free SPI buses are free to use in your project.

FAQ

  • Which led_strip backend should I choose?

    • It depends on your application requirement and target chip's ability.

      Loading
      flowchart LR
      A{Is RMT supported?}
      A --> |No| B[SPI backend]
      B --> C{Does the led strip has \n a larger number of LEDs?}
      C --> |No| D[Don't have to enable the DMA of the backend]
      C --> |Yes| E[Enable the DMA of the backend]
      A --> |Yes| F{Does the led strip has \n a larger number of LEDs?}
      F --> |Yes| G{Does RMT support DMA?}
      G --> |Yes| E
      G --> |No| B
      F --> |No| H[RMT backend] --> D
      
  • How to set the brightness of the LED strip?

    • You can tune the brightness by scaling the value of each R-G-B element with a same factor. But pay attention to the overflow of the value.

Footnotes

  1. The RMT DMA feature is not available on all ESP chips. Please check the data sheet before using it.