Key findings:
- Secondary board with SYSTEK ZT5571VG MCU sits between mainboard and LEDs
- GA25 RGB_FPC_VA 5522 flat-flex cable connects to mainboard
- 3 Pogo-pins per channel (R_POGO1-3, L_POGO1-3) = WS2812B-standard pinout
- Audio path also routes through this board (no sound without it)
- Repaired WS2812B strips soldered to correct pads but don't light
- Root cause: SYSTEK chip speaks non-WS2812B protocol
- Logic analyzer ordered to identify the actual protocol
Also adds last-ditch transceive probe and logic analyzer plan from earlier.
Plan covers: hardware shopping list, pulseview setup, signal capture procedure,
analysis workflow, and three resolution paths depending on findings.
Decoder tool (superx_signal_decode.py) auto-detects LED protocol from sigrok
CSV/VCD exports — matches against WS2812B, SK6812, APA102, TM1814 and others.
Ready for use as soon as the analyzer arrives.
Summary:
- HID output/feature reports on hidraw1+2: no LED reaction
- WMI EC Method 5/6 (read+write on 0x00-0xFF): no LED reaction
- WMI CMS Method 3/4 (alt path): no LED reaction
- HID init handshake (10 variants): no LED unlock
- Electrical: MCU sends data but WS2812B strips don't decode it
Root cause: OEM LED protocol incompatible with WS2812B timing/packet format.
Software side complete. Hardware debugging (logic analyzer) needed next.
Frostbay unaffected — separate MCU with documented HID protocol.
