Hi,
I'm trying to connect a mobile phone to my Zero-W so I can access its SD-card and also activate tethering. But when I connect the phone syslog reports read errors on the USB device and the connect fails and after this nothing else (e.g. USB stick) is recognised. The only way to recover I've found is to reboot the RPi with the device connected and then all is fine and the device (stick or phone) is recognised and accessible.
I'm suspecting that maybe chargeable devices (e.g. the phone) might cause a current surge on the port when first connected and this causes the read failures. The syslog does also report a power cycle attempt on the USB port so it looks like the driver is attempting a recovery but this doesn't help.
The phone only wants 100ma so it's way within the USB spec I believe. But maybe the RPi has a polyfuse or suchlike and this is tripping.
Is there any software solution to this ? Or sufficient hardware detail so I could connect input 5V (hopefully after a master polyfuse) to the USB port 5V ? Obviously I'd much rather not try to hack the board. I'm guessing my software alternative would be to fiddle with /proc variables to get the driver to retry.
Thanks,
Steven
I'm trying to connect a mobile phone to my Zero-W so I can access its SD-card and also activate tethering. But when I connect the phone syslog reports read errors on the USB device and the connect fails and after this nothing else (e.g. USB stick) is recognised. The only way to recover I've found is to reboot the RPi with the device connected and then all is fine and the device (stick or phone) is recognised and accessible.
I'm suspecting that maybe chargeable devices (e.g. the phone) might cause a current surge on the port when first connected and this causes the read failures. The syslog does also report a power cycle attempt on the USB port so it looks like the driver is attempting a recovery but this doesn't help.
The phone only wants 100ma so it's way within the USB spec I believe. But maybe the RPi has a polyfuse or suchlike and this is tripping.
Is there any software solution to this ? Or sufficient hardware detail so I could connect input 5V (hopefully after a master polyfuse) to the USB port 5V ? Obviously I'd much rather not try to hack the board. I'm guessing my software alternative would be to fiddle with /proc variables to get the driver to retry.
Thanks,
Steven
Statistics: Posted by phelum — Sun Aug 04, 2024 8:35 pm