Hi,
My testing has been delayed because I blew up the ZeroW. I've now received a new ZeroW and a Zero2W. My problem is that if I try to connect a mobile phone (can be selected to appear as either mass-storage or ethernet) to the ZeroW I get some errors reported in syslog and from that pont on the USB connection will not detect any subsequent devices (even USB sticks that were detected prior to trying to use the mobile phone).
lsusb still reports the root hub on the USB bus but never any more.
Here is syslog showing plugging/unplugging a USB stick (works fine) and then what happens when I try to connect the phone as mass-storage.The only way I've found of correcting this issue is to reboot the ZeroW with the phone still connected. Because there is no power glitch on the reboot the phone stays in storage/ethernet mode and is detected properly when the ZeroW restarts. This problem occurs with all three phones I have for testing (2 dumbphones and 1 smartphone) so I don't think it is a phone-specific issue. The Zero2W has exactly the same problem. I've also tested using the latest RPi official full-release (kernel 6.6.30) as well as my custom kernels (6.6.42). I'm using -v6 in the ZeroW and -v7 in the Zero2W.
If I connect a non-powered USB hub to the ZeroW and then plug these phones to that hub everything works properly. It's when I try to connect directly that things go wrong.
I presume the kernel (bcm2708-usb module ?) stops polling the bus when this error occurs. But it seems to be a driver fault here because these devices work properly on all other RPi models as well as PCs and whatever else I have for testing.
Can anybody suggest what I can try here to re-activate the USB bus after the erroneous error event here ? I can't see anything in /sys/class or /proc that shows any disabled state or any way I can tell the driver to try again. But I hope I'm missing something important here and can develop a recovery strategy.
Thanks,
Steven
My testing has been delayed because I blew up the ZeroW. I've now received a new ZeroW and a Zero2W. My problem is that if I try to connect a mobile phone (can be selected to appear as either mass-storage or ethernet) to the ZeroW I get some errors reported in syslog and from that pont on the USB connection will not detect any subsequent devices (even USB sticks that were detected prior to trying to use the mobile phone).
lsusb still reports the root hub on the USB bus but never any more.
Here is syslog showing plugging/unplugging a USB stick (works fine) and then what happens when I try to connect the phone as mass-storage.
Code:
Aug 12 03:15:39 RP234 kernel: [ 33.993179] Indeed it is in host mode hprt0 = 00021501Aug 12 03:15:39 RP234 kernel: [ 34.203128] usb 1-1: new high-speed USB device number 2 using dwc_otgAug 12 03:15:39 RP234 kernel: [ 34.203559] Indeed it is in host mode hprt0 = 00001101Aug 12 03:15:39 RP234 kernel: [ 34.446549] usb 1-1: New USB device found, idVendor=0951, idProduct=1666, bcdDevice= 2.00Aug 12 03:15:39 RP234 kernel: [ 34.446573] usb 1-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4Aug 12 03:15:39 RP234 kernel: [ 34.446591] usb 1-1: Product: DataTraveler 3.0Aug 12 03:15:39 RP234 kernel: [ 34.446605] usb 1-1: Manufacturer: KingstonAug 12 03:15:39 RP234 kernel: [ 34.446618] usb 1-1: SerialNumber: E0D55E6C09F91680A92C03F0Aug 12 03:15:39 RP234 kernel: [ 34.447443] usb-storage 1-1:1.0: USB Mass Storage device detectedAug 12 03:15:39 RP234 kernel: [ 34.453457] scsi host0: usb-storage 1-1:1.0Aug 12 03:15:39 RP234 mtp-probe: checking bus 1, device 2: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1"Aug 12 03:15:39 RP234 mtp-probe: bus: 1, device: 2 was not an MTP deviceAug 12 03:15:40 RP234 mtp-probe: checking bus 1, device 2: "/sys/devices/platform/soc/3f980000.usb/usb1/1-1"Aug 12 03:15:40 RP234 mtp-probe: bus: 1, device: 2 was not an MTP deviceAug 12 03:15:40 RP234 kernel: [ 35.513979] scsi 0:0:0:0: Direct-Access Kingston DataTraveler 3.0 0000 PQ: 0 ANSI: 4Aug 12 03:15:40 RP234 kernel: [ 35.514971] sd 0:0:0:0: Attached scsi generic sg0 type 0Aug 12 03:15:40 RP234 kernel: [ 35.516521] sd 0:0:0:0: [sda] 60538881 512-byte logical blocks: (31.0 GB/28.9 GiB)Aug 12 03:15:40 RP234 kernel: [ 35.516958] sd 0:0:0:0: [sda] Write Protect is offAug 12 03:15:40 RP234 kernel: [ 35.516978] sd 0:0:0:0: [sda] Mode Sense: 23 00 00 00Aug 12 03:15:40 RP234 kernel: [ 35.517211] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUAAug 12 03:15:40 RP234 kernel: [ 35.522270] sda: sda1Aug 12 03:15:40 RP234 kernel: [ 35.522744] sd 0:0:0:0: [sda] Attached SCSI removable diskAug 12 03:18:00 RP234 kernel: [ 175.033161] Aug 12 03:18:00 RP234 kernel: [ 175.033176] ERROR::dwc_otg_hcd_urb_enqueue:502: Not connectedAug 12 03:18:00 RP234 kernel: [ 175.033176] Aug 12 03:18:01 RP234 kernel: [ 175.853357] usb 1-1: USB disconnect, device number 2Aug 12 03:18:18 RP234 kernel: [ 193.493189] Indeed it is in host mode hprt0 = 00021501Aug 12 03:18:19 RP234 kernel: [ 193.703131] usb 1-1: new high-speed USB device number 3 using dwc_otgAug 12 03:18:19 RP234 kernel: [ 193.703590] Indeed it is in host mode hprt0 = 00001101Aug 12 03:18:19 RP234 kernel: [ 193.913124] usb 1-1: device descriptor read/64, error -71Aug 12 03:18:19 RP234 kernel: [ 194.033396] NYET/NAK/ACK/other in non-error case, 0x00000002Aug 12 03:18:19 RP234 kernel: [ 194.033439] Indeed it is in host mode hprt0 = 00001101Aug 12 03:18:19 RP234 kernel: [ 194.243127] usb 1-1: device descriptor read/64, error -71Aug 12 03:18:19 RP234 kernel: [ 194.363179] Indeed it is in host mode hprt0 = 00001101Aug 12 03:18:20 RP234 kernel: [ 194.573128] usb 1-1: new high-speed USB device number 4 using dwc_otgAug 12 03:18:20 RP234 kernel: [ 194.573376] NYET/NAK/ACK/other in non-error case, 0x00000002Aug 12 03:18:20 RP234 kernel: [ 194.573400] NYET/NAK/ACK/other in non-error case, 0x00000002Aug 12 03:18:20 RP234 kernel: [ 194.573421] NYET/NAK/ACK/other in non-error case, 0x00000002Aug 12 03:18:20 RP234 kernel: [ 194.573452] Indeed it is in host mode hprt0 = 00001101Aug 12 03:18:20 RP234 kernel: [ 194.783129] usb 1-1: device descriptor read/64, error -71Aug 12 03:18:20 RP234 kernel: [ 194.903463] Indeed it is in host mode hprt0 = 00001101Aug 12 03:18:20 RP234 kernel: [ 195.113136] usb 1-1: device descriptor read/64, error -71Aug 12 03:18:20 RP234 kernel: [ 195.233168] usb usb1-port1: attempt power cycleIf I connect a non-powered USB hub to the ZeroW and then plug these phones to that hub everything works properly. It's when I try to connect directly that things go wrong.
I presume the kernel (bcm2708-usb module ?) stops polling the bus when this error occurs. But it seems to be a driver fault here because these devices work properly on all other RPi models as well as PCs and whatever else I have for testing.
Can anybody suggest what I can try here to re-activate the USB bus after the erroneous error event here ? I can't see anything in /sys/class or /proc that shows any disabled state or any way I can tell the driver to try again. But I hope I'm missing something important here and can develop a recovery strategy.
Thanks,
Steven
Statistics: Posted by phelum — Sun Aug 11, 2024 6:03 pm