Please describe exactly what does and doesn't work in this case? Is it only touch that doesn't work, or does it not power the Pi either?When I try to put the power in one port of the Viewsonic, and then chain the RPi from the other port of the Viewsonic using the various USB C - USB C cables (Android, Apple, Belkin TB3) I have lying around... it doesn't work.
If it won't power the Pi, then it's likely to be the CC signalling lines.
If it's the touch that won't work, then try both orientations of one plug as the monitor may not have implemented the full signalling.
I've dug my display back out. Pi5 PSU into the monitor. USB-C to USB-C cable from the monitor to a Pi4. HDMI mini to micro cable. "dtoverlay=dwc2,dr_mode=host" in config.txt.
Code:
pi@bookworm64-1:~ $ lsusb -t/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=dwc2/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 3, If 2, Class=Human Interface Device, Driver=usbhid, 12M/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480Mpi@bookworm64-1:~ $ evtestNo device specified, trying to scan all of /dev/input/event*Not running as root, no devices may be available.Available devices:/dev/input/event0:vc4-hdmi-0/dev/input/event1:vc4-hdmi-0 HDMI Jack/dev/input/event2:vc4-hdmi-1/dev/input/event3:vc4-hdmi-1 HDMI Jack/dev/input/event4:WingCool Inc. TouchScreen/dev/input/event5:WingCool Inc. TouchScreenSelect the device event number [0-5]: 4This setup would NOT power a Pi5 - it kept browning out during boot. Ethernet is the only thing I have connected to the Pi.
Statistics: Posted by 6by9 — Thu Dec 12, 2024 3:08 pm
