BeagleBone Black - Bug # 151: USB A port not useable on recent BBB image

Transcription

1 BeagleBone Black - Bug # 151: USB A port not useable on recent BBB image Status: New Priority: Normal Author: First name Last name Category: Created: 10/09/2015 Assignee: Robert Nelson Updated: 10/09/2015 Due date: Description: Hi there. I have a 4Gb BBB and connect to console via minicom/serial port. HDMI,USB OTG and eth0 all seem to be working. but the Large USB A port no longer recognises peripherals. :-( debian@beaglebone:~/admin$ sudo lsusb The installed image is: BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf gb.img.xz updated and upgraded and then apt-get install linux-image bone2 I did try installing more recent images: BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf gb.img.xz BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf gb.img.xz but could not get them to work. Here is relevant snip from dmesg: [ ] PM: Hibernation image not present or could not be loaded. [ ] Freeing unused kernel memory: 444K (c09a c0a14000) [ ] systemd-udevd[99]: starting version 215 [ ] random: systemd-udevd urandom read with 9 bits of entropy available [ ] usb 1-1: unable to read config index 0 descriptor/all [ ] usb 1-1: can't read configurations, error -71 [ ] usb 1-1: new low-speed USB device number 3 using musb-hdrc [ ] usb 1-1: device descriptor read/all, error -71 [ ] usb 1-1: new low-speed USB device number 4 using musb-hdrc [ ] usb 1-1: device not accepting address 4, error -71 [ ] usb 1-1: new low-speed USB device number 5 using musb-hdrc [ ] usb 1-1: device not accepting address 5, error -71 [ ] usb usb1-port1: unable to enumerate USB device 05/13/2018 1/5

2 [ ] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ ] systemd[1]: Found ordering cycle on basic.target/start [ ] systemd[1]: Found dependency on sysinit.target/start [ ] systemd[1]: Found dependency on console-setup.service/start [ ] systemd[1]: Found dependency on remote-fs.target/start [ ] systemd[1]: Found dependency on remote-fs-pre.target/start [ ] systemd[1]: Found dependency on connman.service/start [ ] systemd[1]: Found dependency on dbus.service/start [ ] systemd[1]: Found dependency on basic.target/start [ ] systemd[1]: Breaking ordering cycle by deleting job console-setup.service/start [ ] systemd[1]: Job console-setup.service/start deleted to break ordering cycle starting with basic.target/start [ ] NET: Registered protocol family 38 [ ] systemd[1]: systemd-modules-load.service: main process exited, code=exited, status=1/failure [ ] systemd[1]: Failed to start Load Kernel Modules. [ ] systemd[1]: Unit systemd-modules-load.service entered failed state. [ ] systemd-udevd[180]: starting version 215 [ ] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro [ ] omap_rng rng: OMAP Random Number Generator ver. 20 p.s. I note the warning systemd-modules-load.service failed and am assuming this will be related to the module loading breakage that I see in images BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf gb.img.xz and BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf gb.img.xz my workaround for that issue was apt-get install --reinstall linux-image ti-r15 which allowed modules to then be found, loaded ant listed. Is there anything further that I can do to help investigate or resolve this issue? Any suggestions gladly welcomed. :-) 05/13/2018 2/5

3 History 10/09/ :15 pm - Robert Nelson - Assignee set to Robert Nelson odd, it looks like your dealing with a bad usb cable/hub: <pre> usb 1-1: unable to read config index 0 descriptor/all </pre> How are you powering the device? <pre> debian@beaglebone:~$ uname -r bone2 debian@beaglebone:~$ lsusb Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 0424:2504 Standard Microsystems Corp. USB 2.0 Hub debian@beaglebone:~$ dmesg grep musb [ ] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ ] musb-hdrc: MHDRC RTL version 2.0 [ ] musb-hdrc: setup fifo_mode 4 [ ] musb-hdrc: 28/31 max ep, 16384/16384 memory [ ] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn) [ ] musb-hdrc: MHDRC RTL version 2.0 [ ] musb-hdrc: setup fifo_mode 4 [ ] musb-hdrc: 28/31 max ep, 16384/16384 memory [ ] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ ] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1 [ ] usb usb1: Manufacturer: Linux bone2 musb-hcd [ ] usb usb1: SerialNumber: musb-hdrc.1.auto [ ] usb 1-1: new high-speed USB device number 2 using musb-hdrc [ ] usb 1-1.4: new full-speed USB device number 3 using musb-hdrc [ ] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB HID v1.11 Device [Logitech USB Receiver] on usb-musb-hdrc.1.auto-1.4/input2 [ ] input: Logitech M215 as /devices/platform/ocp/ usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1.4/1-1.4:1.2/0003:046d:c52b.0003/0003:046d: /input/inpu t0 [ ] logitech-hidpp-device 0003:046D: : input,hidraw1: USB HID v1.11 Mouse [Logitech M215] on usb-musb-hdrc.1.auto-1.4:1 [ ] input: Logitech K360 as /devices/platform/ocp/ usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1.4/1-1.4:1.2/0003:046d:c52b.0003/0003:046d: /input/inpu t1 [ ] logitech-hidpp-device 0003:046D: : input,hidraw2: USB HID v1.11 Keyboard [Logitech K360] on usb-musb-hdrc.1.auto-1.4:2 </pre> 10/09/ :02 pm - First name Last name >odd, it looks like your dealing with a bad usb cable/hub: 05/13/2018 3/5

4 Indeed, except that I have recently seen it working fine, even with an USB HDD before I upgraded emmc to Jessie. >How are you powering the device? Good point. At the moment I am powering the device from my PC via the small USB OTG port. To the best of my recollection Enumerating USB previously worked with this setup. Perhaps I am overly cautious, but by having the BBB connected to my PC by serial console and also powered by my PCs USB port, I minimise the chance of accidentally generating a damaging current flow through the serial port. However since I have the option of powering from the barrel connector, or indeed via a powered USB hub in the Big USB connector - I will experiment with each variation now. with USB OTG diconnected. Results: 1) Powered USB hub :-) debian@beaglebone:~$ sudo lsusb Bus 001 Device 017: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 016: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard Bus 001 Device 015: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB Bus 001 Device 014: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB debian@beaglebone:~$ 2) unplugging the powered hub (powered only by barrel connector) :-( debian@beaglebone:~$ [ ] usb 1-1: device descriptor read/64, error -71 [ ] usb 1-1: device not accepting address 18, error -71 [ ] usb 1-1: device descriptor read/64, error -71 [ ] usb 1-1: device descriptor read/64, error -71 [ ] usb 1-1: device not accepting address 20, error -71 [ ] usb 1-1: device not accepting address 21, error -71 [ ] usb usb1-port1: unable to enumerate USB device debian@beaglebone:~$ sudo lsusb So it does appear to power related. Furthermore experimenting with different single devices connected to the USB port I discover that a USB keyboard is detected, but its partner USB mouse is not, whereas my venerable microsoft USB mouse _is_ detected!? Anywhow thankyou for pointing me in the right direction. :-) I have been using console+serial or console+ssh or keyboard+console for sooo long now, I realise that I may not have ever actually tried to use that particular combination of GUI+mouse without the powered hub which is my USB port expander until your lxqt Jessie images which made hdmi 'just work' :-) 05/13/2018 4/5

5 So another Big Thankyou for all your good work providing the excellent test images. :-) 05/13/2018 5/5

6