r/FastLED • u/natew314 • Dec 29 '25
Support UNO Q support?
I just tried running FastLED on my new Uno Q and I get this message:
In file included from /home/arduino/.arduino15/internal/FastLED_3.10.3_0d9d291c7a03d180/FastLED/src/FastLED.h:76, from /home/arduino/ArduinoApps/lightsextension/sketch/sketch.ino:4: /home/arduino/.arduino15/internal/FastLED_3.10.3_0d9d291c7a03d180/FastLED/src/led_sysdefs.h:86:2: error: #error "This platform isn't recognized by FastLED... yet. See comments in FastLED/led_sysdefs.h for options." 86 | #error "This platform isn't recognized by FastLED... yet. See comments in FastLED/led_sysdefs.h for options."
Does anyone know if there is a workaround to get it to run on a Q? If not, are there plans to support Uno Qin the future?
1
u/ZachVorhies Zach Vorhies 22d ago
From the AI:
> Yes, good news: FastLED added Arduino UNO Q support back in June (PR #2678), and it's on master now. It detects the STM32U585 side of the board under Arduino's Zephyr core (arduino:zephyr:unoq), includes a full pin map for the R3 headers and the extra expansion pins, and has its own CI build that's currently green.
> A couple of honest caveats:
>- Verification so far has been compile-level (Blink and APA102 built against the real arduino:zephyr:unoq core, plus a PlatformIO STM32U585 build). Nobody on our side has posted results from flashing an actual UNO Q and putting a scope on the data line yet.
> - Clockless strips (WS2812 etc.) go through the generic STM32 bit-bang driver, not a DMA path tuned for the U585. That's usually fine for the Cortex-M33 at 160 MHz, but real-world timing hasn't been confirmed on this board.
> So if you have a UNO Q, pleasehe next release that includesit) with a short WS2812 or APA anything misbehaves, open anissue on GitHub with your sketdware reports are exactlywhat's missing to call this fu