Trouble with MHET v2.0 board and v9 and v11 hyperserialesp32 - Running HyperHDR v21 stable #138
Replies: 16 comments 1 reply
-
|
Hi |
Beta Was this translation helpful? Give feedback.
-
|
Unfortunately after doing that the LED's are not turned on. 23:28:57.305 LEDDEVICE0_ADALIGHT : DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (Welcome! Awa driver 9. NeoPixelBus SK6812 cold GRBW. RGBW => Gain: 255/255, red: 160, green: 160, blue: 160) at 66 msec |
Beta Was this translation helpful? Give feedback.
-
|
It's about logs not LED rendering at this point. Are you sure you followed the guide exactly as described? |
Beta Was this translation helpful? Give feedback.
-
|
Pretty sure... I flash hyperserialesp32.bin version 7 to MHET board and it works fine. I flash hyperserialesp32.bin version 9 or version 11 to MHET board and it does not work. No LED control even though hyperhdr says it's detected in the logs... |
Beta Was this translation helpful? Give feedback.
-
|
Im not talking about that part right now. You need to proceed with the test procedure described in the link I gave you earlier. |
Beta Was this translation helpful? Give feedback.
-
|
I went through the testing procedure from the link you provided above and pasted the logs whilst doing so. But why go through the test procedure with the MHET board does not control the LED strip? What am I missing? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
You need to read statistics described in the test procedure to make sure the board is receiving colors from HyperHDR. If it's receiving them, it's most likely an electrical/connection issue. |
Beta Was this translation helpful? Give feedback.
-
|
Guaranteed it's not a electrical issue. I have multiple mhet live boards that have different hyperserialesp32 versions on and I just rip them off the headers that are soldered on the pcb. All versions above 7 do not work. I plonk a v7 board in whilst it's all powered on and the leds start doing there thing... Dunno. Here's logs of me doing that. Maybe I've missed somthing. I recompiled one of the v11 SK6812 firmwares with the actual board name itself and serial baud of 4000000 but no joy. 2026-06-28T03:17:09.168Z [CORE] TTY is not attached to the log output Thanks anyways. |
Beta Was this translation helpful? Give feedback.
-
|
I think I asked you about different thing but feel free to perform the diagnostic in your own way but without me. These boards from Ali come in different UART configurations so some things must be tested first. |
Beta Was this translation helpful? Give feedback.
-
|
oh not at all. Sorry didn't mean it that way. I understand you don't have access to my equipment and can only see what logs I provide. I'm pretty sure I've wired it correctly with a level shifter as it's worked for years as a single strip. I should just be able to flash a newer version of hyperserialesp32 right? I wouldn't be surprised if I'm flashing the board wrong... I just don't understand why I flash with version 7 and push the board in to my pre-wired pcb with headers and it all works but I flash with any higher version and nothing happens. Tried multiple boards. I can't get a solid colour to calibrate even though it detects the mhet board with the awa 11 driver in the logs. I don't want to use a rpi as they are very expensive here and the mhet live board was the goto in the day and have a few of them. Can you recommend another board if this one is not great anymore please? |
Beta Was this translation helpful? Give feedback.
-
|
If in the statistics from this test you can see that the board received frames from HyperHDR, then the problem appears somewhere on the output side. If you're using recommended type of the level shifter, it's hard for me to clearly identify the cause. v7 uses the same I2S timings as v11 when emulating Neopixel. |
Beta Was this translation helpful? Give feedback.
-
|
I'm also thinking of trying Hyperk. If it works, it should at least rule out a hardware problem. Plus, it will soon have HyperSerial support as well. |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the delay, life got in the way. I've installed hyperk on the mhet v2.0 board. I've confirmed this board is using a ch9102f usb to uart bridge chipset Logs from the mhet are flashing hyperk: Hyperhdr information: Platform: V21 doesn't appear to have hyperk as a controller type. I can't run any newer version than hypderhdr v21 due to missing libraries on the intel nuc with Libreelec 12.2.1. |
Beta Was this translation helpful? Give feedback.
-
|
Is there any point? Hyperk and specifically WLED is for network connections right? They don't have serial support? my setup uses serial uart_bridge_usb for communication for low latency. It's bizarre, I have v1 and v2 of the mhet live wemos mini d1. Neither work past hyperserialesp32.v7. Something is funky here, I'd like to know why but I don't know enough to troubleshoot further. I'm happy if someone wants to guide, to flash other firmwares and/or test. Moving forward, I ordered 6 x esp-s2mini - lolin boards from aliexpress. Maybe I'll see some difference with the newer firmware versions. |
Beta Was this translation helpful? Give feedback.
-
You're missing that point again... I've already told you that Hyperk will receive HyperSerial as well soon so the LED renderer can be tested even now - so why even you've installed it?. BTW esp32s2 is rather poor choice these days compared to classic esp32 (performance, HyperSerialESP32 support) or esp32-c6 (Wifi6, Parlio, price tag, also CDC for Hyperk HyperSerial). |
Beta Was this translation helpful? Give feedback.
-
Doh!@ I have a bunch of esp32-s3 mini but I can't use them with hyperserialesp32.
I probably am. Sorry. So you mean I should've just swapped out the mhet v2 board with another mhet v2 flashed with hyperk and it should work? I'll go test that. Sorry for the confusion. Next time I'll add photos as telepathy is not helpful for troubleshooting... ;-) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
Hope you are well.
I've been running hyper hdr v18 and hyperserialesp32 v7 for a while now. I got a new TV and decided to upgrade hyper software.
I'm running libreelec 12.2.1 on intel nuc i511. I know there's an addon but I'd prefer just to use the linux tarball with static libs for testing purposes. I had no joy with the addon.
To get v21.0 hyperhdr stable working I had to copy some libraries from "elsewhere" (previous hyperhdr version) to ~/hyperhdr/share/hyperhdr/lib/
And it started up fine with no errors afterwards. Happy days.
I have a lot of mhet v1 and v2 boards from other things and these work fine as the LED controller when using v7 and v7 of hyperserialesp32.bin but when I flash(successfully) v9 or v11 there is no LED response.
The serial port is opened according to the logs in HyperHDR and the board and flashed version are detected OK:
22:41:07.935 LEDDEVICE0_ADALIGHT : Serial port auto-discovery. Found serial port device: USB Single Serial (/dev/ttyACM0 => ttyACM0)
22:41:07.935 LEDDEVICE0_ADALIGHT : Opening UART: ttyACM0
22:41:07.935 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:209:tryOpen() | _serialPort.open(QIODevice::ReadWrite): ttyACM0, Baud rate [2000000]bps
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:214:tryOpen() | portName: ttyACM0
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:215:tryOpen() | systemLocation: /dev/ttyACM0
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:216:tryOpen() | description: USB Single Serial
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:217:tryOpen() | manufacturer: 1a86
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:218:tryOpen() | productIdentifier: 0x55d4
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:219:tryOpen() | vendorIdentifier: 0x1a86
22:41:07.946 LEDDEVICE0_ADALIGHT : ProviderSerial.cpp:220:tryOpen() | serialNumber: 567E050638
22:41:08.250 LEDDEVICE0_ADALIGHT : ESP sent: ''
22:41:08.316 LEDDEVICE0_ADALIGHT : DETECTED DEVICE USING HyperSerialEsp8266/HyperSerialESP32/HyperSerialPico FIRMWARE (Welcome! Awa driver 9. NeoPixelBus SK6812 cold GRBW. RGBW => Gain: 255/255, red: 160, green: 160, blue: 160) at 66 msec
I am using the latest version (5.8) of esptool to flash the factory firmwares at offset 0x0
I've also tried to flash the factory.bin then the base binary afterwards to offset 0x10000
The only thing I've noticed is when I connect to the serial port to check for v7 & v8, I get the response:
python3 -m serial.tools.miniterm /dev/ttyACM0 2000000
--- Miniterm on /dev/ttyACM0 2000000,8,N,1 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
Welcome!
Awa driver 8.
NeoPixelBus SK6812 cold GRBW.
RGBW => Gain: 255/255, red: 160 , green: 160 , blue: 160
HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem: 3568, heap: 365572
RGBW => Gain: 255/255, red: 160 , green: 160 , blue: 160
HyperHDR frames: 0 (FPS), receiv.: 0, good: 0, incompl.: 0, mem: 3536, heap: 365572
RGBW => Gain: 255/255, red: 160 , green: 160 , blue: 160
-----------------and it keeps going forever until handshake
HOWEVER, when I connect to the serial port for v9 and v11 it only displays an output ONCE:
root@opc01:/home/user/Downloads/HyperHDR/esptool/esptool-linux-amd64# python3 -m serial.tools.miniterm /dev/ttyACM0 2000000
--- Miniterm on /dev/ttyACM0 2000000,8,N,1 ---
--- Quit: Ctrl+] | Menu: Ctrl+T | Help: Ctrl+T followed by Ctrl+H ---
<␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀␀ crap omitted>
Welcome!
Awa driver 9.
NeoPixelBus SK6812 cold GRBW.
RGBW => Gain: 255/255, red: 160, green: 160, blue: 160
Then that's it.
I'm pretty stuck at this point . Should v9 & v11 hyperserialesp work with hyperHDR 21.0+ ?
I've also noted that once flashed with v9 and v11 they do not work hyperhdr18 but this part is documented, iirc to require v19.2beta at least.
At this point I have 2 working setups with hyperserialesp32 v8 and hyperhdr v21. It's working fine but latest software improvements and all that.
Please help before I go more crazy.
Thank you
Beta Was this translation helpful? Give feedback.
All reactions