HyperSerialESP32 Fails to Control SK6812 LEDs in HyperHDR Setup on Debian 12, also 0 Frames from MS2310

[J-Houghton]

I’m having trouble getting my SK6812 LEDs to work with an ESP32 running HyperSerialESP32 firmware in my HyperHDR setup on Debian 12. While the LEDs function perfectly with a WLED controller, they don’t turn on at all with HyperSerialESP32, despite testing with two different ESP32 boards. I’m using an EZCoo 1x2 HDMI splitter and have tried various baud rates (1MB, 2MB, 4MB), but the issue persists. I’d like some help troubleshooting this. Below are the specific details of my setup.

---

Setup Details:

• HyperHDR Version: Initially 21 beta2, now on 21 beta1 (due to beta2 being released recently)

• Operating System: Debian 12

• LED Type: SK6812 (300 LEDs, 5 meters)

• ESP32 Controller: Classic ESP32 (ESP32-WROOM-32) with the latest HyperSerialESP32 firmware. Also got this Mini ESP32, but didn't realize I bought the one with the slow baud rate

• Data Pin: GPIO2 (pin 2) connected to the SK6812 LED strip

• HDMI Splitter: EZCoo 1x2

• USB Grabbed: MS2310 Amazon

• Connection: ESP32 connected via USB to Debian server at /dev/ttyUSB0

---

ESP32 Observations:

The SK6812 LEDs do not turn on when controlled by the ESP32 with HyperSerialESP32 firmware in HyperHDR. Here’s what I’ve observed:

• The LEDs work perfectly when connected to a WLED controller, confirming the LEDs and wiring are functional.
• With HyperSerialESP32, the LEDs remain off, and I’m unsure if HyperHDR is communicating with the ESP32 correctly.
• I’ve tried baud rates of 1,000,000 bps, 2,000,000 bps, and 4,000,000 bps in HypderHDR, but the issue persists.
• I’ve tested with two different ESP32 boards, and both exhibit the same behavior, suggesting it’s not a hardware defect.
• Without handshake, no errors, but LEDs still don’t turn on.

Steps Taken:

• Verified the ESP32 is detected at /dev/ttyUSB0.
• Checked wiring between the ESP32 (GPIO2) and SK6812 LEDs.
• Tested with WLED on the same ESP32 to confirm hardware functionality—LEDs turned on as expected.
• Plan to test with a Raspberry Pi Pico RP2040 W tomorrow to see if the issue is specific to the ESP32.

---

I also been dealing with a weird issue with ms2310 usb capture, initial set up last night had frame too small 0 != xxxx error, but I was able to see live video, and addressed the dark HDR issue with SDR to HDR button. But today I have the same error with a black screen for live video with a split second of no signal.

I'm not sure if my esp32 hardware is the issue, but I can pick up a pico r2040 W tomorrow for pretty cheap to test. I am more concerned about the USB grabbed, should I just get the ms2109 instead for less headache?

---

[awawa-dev]

Hi
For these slower uarts first you need to compile&flash the firmware for slower baud-rate, then to set it up in HyperHDR also.

[J-Houghton]

Hi,
I see, if that is the case I plan to get a Pico R2040 W today to address the LED controller issue.

Do you have any ideas on the USB grabber(MS2310), is it an issue related to LED hardware-esp32, or a separate USB Video Capture issue?

[awawa-dev]

frame too small 0 != xxxx error, but I was able to see live video, 

Such error is quite usual when the grabber starts the stream but later it should not appear.

[J-Houghton]

Hi, you were right about my initial issue! After I got a pico w yesterday everything was working when I hooked it up on the bread board. (For the grabber, I had to turn on scaler on splitter to USB grabber, then live video was working perfectly. )

Today however, I mounted the TV and put the pico and logic shifter on a perf board, the LED didn't turn on. I saw an old post regarding a connection issue, and putting everything on the breadboard worked to turn on the LEDs. However, instead of video effects, I have this super fast rainbow effect.

During initial start, the rainbow effect doesn't have white then it does after a few seconds. I tried to unplug and plug back in splitter, when the splitter was unplugged, the rainbow effect continued but without white light. But white came back after splitter had power back.

I thought it might be something with the effects, so I changed to static color red. It didn't do anything initially, white with rainbow effect super fast, but when I restarted hypderHDR, I saw static red for a few seconds then rainbow with white effect again.

I'm not sure if it's an setting I've accidentally turned on or an actual issue. There are some changes on how I hooked up the power from the power supply terminal and now using 16awg wires instead of 22awg, but besides that it is the identical set up as I had yesterday with everything working. After the intial configs, I've downloaded LUT for ms2310, did HDR LUT Calibration following the guide, and compressed .3d to .zst. And flashed ms2310 using F3 file.

[awawa-dev]

Hi first you need to have stable output using effects. Such disco reaction from led is usually related to missing common ground. So if you have a multimeter check if there is a continuity between LED strip ground and Pico ground. Btw which level shifter do you use? Hopefully is not the i2c type.

[J-Houghton]

Hi, the logic shifter I have is the SN74AHCT125N. Thank you for the tip, I will check on the ground when I have time later today.

Here is my current connection
Debian PC -> controller (Pico W) via micro usb

Power supply (top results from amazon 5V, metal box) 2 sets of V+, V- but from my understanding they are still connected internally.
V+, V- (1) -> led strip

V+, V- (2) -> perf board (bread board)
- Board V+(2) -> SN74AHCT125N
- Board V-(2) -> Pico W Gnd (pin 3, above GPIO2)
- Pico W Gnd -> SN74AHCT125N pin 1 -> from pin 1 to pin 7 for gnd
- Pico W Pin 4 (GPIO2) -> SN74AHCT125N pin 2
- SN74AHCT125N pin 3 -> Data In SK6812

The connection's fairly simple and the above text is mainly for my own preparation when taking another look at it tonight.

[awawa-dev]

Another possibility is that the ground created a loop. Maybe simplified ground connection and connecting it directly to the level shifter(board) from the same line as for led strip could help. But first check if you have continuity between LED and Pico/bread board.

[J-Houghton]

Thank you @awawa-dev for the help, my questions came from my inexperience but you were still nice enough to help! After setting up the connections properly HyperHDR is working great

I'll leave my set up here in case anyone faces similar issues

---

Setup Details:

• HyperHDR Version: 21 beta1

• HyperHDR OS: Debian 12

• LED: SK6812 (300 LEDs, 5 meters)

• LED Controller: Pico W using SN74AHCT125N Classic ESP32 (ESP32-WROOM-32) with the latest HyperSerialESP32 firmware. Also got this Mini ESP32, but didn't realize I bought the one with the slow baud rate
  - Followed HyperSerialPico

• HDMI Splitter: EZCoo 1x2

• USB Grabber: MS2310 Amazon

Issue 1, using slower classic ESP32

• My first issue was the ESP32 above from amazon, one was the classic esp32 and the other was one that looked like what's recommended in the guide but had same speed as classic esp32. In HyperHDR, it was never detected when using handshake option. When not using handshake option, everything seems fine in the logs to me, but the LED would not work. All my issue was resolved by using Pico W instead of my classic esp32s.

Issue 2, Black Screen or No Signal from MS2310

• This was resolved by turning on scaler for HDMI out to USB Grabber.

Issue 3, Disco Effect on LED strip when everything is connected

• This came from in proper wiring, after I redid my wiring to a previous working state, HypderHDR was working as expected.

---

After these 2 issues resolved, it was working very smoothly, I was able to download LUT file, calibrate LUT, compress LUT.3d file. Smoothing and black bar detection also worked well for me with the default settings.