From 7436e049db8b89ad3e9f630510bf62ef95164cef Mon Sep 17 00:00:00 2001 From: Anne Jan Brouwer Date: Fri, 14 Aug 2026 23:34:12 +0200 Subject: [PATCH] docs(mch2022): say which firmware the RGBW fix needs The warning said RGBW was broken and would be fixed upstream. It is fixed now, in mch2022-firmware-rp2040 pull request 22, but no release carries it: 0x0C is still the latest, so any badge running a released firmware still goes dark on mode 2. Say that, and link the fix. Co-Authored-By: Claude Opus 5 Claude-Session: https://claude.ai/code/session_0142DuVFXpWnjeQhZzT3N3nC --- .../MCH2022/software-development/api/ws2812.md | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/content/en/docs/Badges/MCH2022/software-development/api/ws2812.md b/content/en/docs/Badges/MCH2022/software-development/api/ws2812.md index 34f08a1..c38ea57 100755 --- a/content/en/docs/Badges/MCH2022/software-development/api/ws2812.md +++ b/content/en/docs/Badges/MCH2022/software-development/api/ws2812.md @@ -99,9 +99,13 @@ the five LEDs of the tilde add-on, then fades each color up and down, first across all five LEDs together and then one LED at a time. It is a short read and a good starting point for your own add-on. -{{% alert title="RGBW mode does not work yet" color="warning" %}} -Mode `2` is meant to select 32-bit RGBW output, but the RP2040 firmware -falls through from that case straight into disabling the output, so the -LEDs go dark instead. Use mode `1` until that is fixed upstream. +{{% alert title="RGBW mode needs a firmware newer than 0x0C" color="warning" %}} +Mode `2` selects 32-bit RGBW output. On every released RP2040 firmware up +to and including `0x0C` it turns the LEDs off instead: the switch enables +the output and then falls through into the disable case. + +[The fix](https://github.com/badgeteam/mch2022-firmware-rp2040/pull/22) is +on `master` and is not in a release yet, so a badge you did not build the +firmware for yourself still has this. Use mode `1` there. {{% /alert %}}