Open s-dinda opened 6 months ago
I'm using the official 27W Power Supply
The other devices are a printer, a DSLR and a mouse:
$ lsusb -tv
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Printer, Driver=, 480M
ID 06d3:3b36 Mitsubishi Electric Corp. CP-D80DW
|__ Port 2: Dev 3, If 0, Class=Imaging, Driver=, 480M
ID 04a9:32b4 Canon, Inc. EOS Rebel T6
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/1p, 5000M
ID 1d6b:0003 Linux Foundation 3.0 root hub
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci-hcd/2p, 480M
ID 1d6b:0002 Linux Foundation 2.0 root hub
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
ID 046a:b091 CHERRY Mouse
The touchscreen and all of them (except the mouse) are independently powered.
Same problem here, with the Canakit 45W usb-c PD power supply. the usb sees mtouch, then destroys the all USBs. Another touch driver (I have a 2nd screen) using the elecrow. ads7846. has issues as well, it sees SOME touch inputs, once every 20 seconds or so. If I set the exact same OS (raspbian) with same settings, same literal displays on the rpi4 everything works as expected. I have no idea what's happening.
ads7846 is totally unrelated as it is an I2C touchscreen. Should already be fixed via #6029.
ads7846 is totally unrelated as it is an I2C touchscreen. Should already be fixed via #6029.
I can confirm that the ads7846 display works now, thx!
Sadly the USB one still is not (mtouch one)
I'm having the same problem with Mtouch on bookworm and latest stable firmware on pi5, seems like there is no solution. I was using Ubuntu before on the same pi5 and the touchscreen was working
EDIT:
I reinstalled Ubuntu 24.04LTS server and it seems like I am now getting the same xHCI host controller not responding, assume dead
error when connecteing the touch screen. I'm pretty sure I had Ubuntu 23.10 desktop installed on the Pi5 when it was working.
So I had (a lot) of free time to play with this issue and I think I just found something interesting!
When I first got this rpi few good months ago I definitely installed Ubuntu 23.10 (luckily Ubuntu is changing its default background every release making it easy to know what version was installed even after wiping the sd card) and the mtouch screen was working wonderfully, until...
xHCI host controller not responding, assume dead
when connecteing the mtouch screen USB cable to the Pi or during boot.xHCI host controller not responding, assume dead
mesage.The eeprom!! I suspect that bookworm automatically updated my outdated 2023 bootloader to the 2024-XX-XX-XX version in which something has changed. so I went back to 2023-10-30-2712 and the touch screen was working again under Ubuntu 23.10! and I will soon test with newer OSs
What could have changed on the EEPROM side that could effect this?
https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware-2712/release-notes.md
This is possibly a duplicate of this issue although the symptoms don't sound identical
2024-04-18: Update RP1 firmware to extend PCIe L1 entry timeout to 32 us (latest)
Extend PCIe L1 entry timeout to 32us Fix xhci soft reset on link-down Set useful xhci compatibility bits in GUCTL See https://github.com/raspberrypi/firmware/issues/1877
If it is the RP1 firmware change then it should work in Ubuntu 24.04 LTS now since the rpi-eeprom-update service never automatically downgrades
It appears that you are correct, I tested and the latest working release from github releases is 2024-04-17-2712 and with the 2024-04-20 EEPROM release the touch screen no longer works. So I assume the RP1 firmware change is what broke my mtouch display. now the other folks on this thread reported this issue on March 27 so maybe it's a different issue for them?
For now I went back to 2024-04-17-2712, installed latest bookworm and disabled rpi-eeprom-update service with
sudo systemctl mask rpi-eeprom-update
and my mtouch screen works perfectly !
Describe the bug
On Pi5 Bookworm an external usb touchscreens seems to kill the xHCI controller. The same device worked fine with a previous Pi4B (Bullseye).
I am trying to connect a touchscreen via USB and HDMI, unfortunately connecting the USB device seems to kill some of the other connected USB devices - until a reboot.
Thanks in advance!
Steps to reproduce the behaviour
Device (s)
Raspberry Pi 5
System
Logs
dmesg
Additional context
No response