Trouble with MHET v2.0 board and v9 and v11 hyperserialesp32 - Running HyperHDR v21 stable #137

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 v8 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