Closed dieseld23 closed 9 months ago
Did you notice product id and vendor id in HyperHDR logs? It's not valid: 0 so there is also 0 chance it will work. It's not HyperHDR issue and BTW webos is also not officially supported here. Latest v20 beta has also device discovery which should find valid serial devices.
I get it, I'm just trying to get any potential ideas on what's going on. Wasn't sure where to post and where the source of the issue is. The TV's operating system recognizes the Pico, but HyperHDR isn't seeing it.
Try the latest v20 beta. The device discovery tab should find Pico if it is present. Did you connect Pico to windows pc and in the device manager it was discoved as a serial port? And for webos: or the wrong serial port was selected (their name/path could change after restart) or it's caused by a comical bug in udev package (let's change something in the latest beta just before udev 'stable' release... what can go wrong?), fixed some time ago but it's propagating across various OS distroes and causes vendor/product id to be mismatched. There is a topic in the HyperHDR discussion about it.
WebOS 4.5 - v5.30.40 HyperHDR installed onto tv directly
Log from HyperHDR:![1](https://github.com/awawa-dev/HyperSerialPico/assets/5695864/bcfe2d33-f3c0-45f5-9230-9e236cc44d89)
dmesg log on TV:
lsusb:
Tried two different RP2040s with no change (one is an RP2040W original, the other is a Pimoroni Plasma 2040W). Using the latest HyperHDR v20beta and HyperSerialPico
HyperHDR set with rp2040 handshake, and to ttyACM0.
The only thing I can see is that ttyACM0 is linked to cdc_acm 7-1:1.0. But based on lsusb, it should be 7-1:1.2?