USB A port not useable on recent BBB image (Bug #151)


Added by First name Last name almost 2 years ago. Updated almost 2 years ago.


Status:New Start date:10/09/2015
Priority:Normal Due date:
Assignee:Robert Nelson % Done:

0%

Category:-
Target version:-

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
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

The installed image is:
BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf-2015-09-13-4gb.img.xz

updated and upgraded
and then
apt-get install linux-image-4.2.3-bone2

I did try installing more recent images:
BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf-2015-09-27-4gb.img.xz
BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf-2015-10-04-4gb.img.xz

but could not get them to work.

Here is relevant snip from dmesg:

[ 3.593990] PM: Hibernation image not present or could not be loaded.
[ 3.594846] Freeing unused kernel memory: 444K (c09a5000 - c0a14000)
[ 3.638953] systemd-udevd99: starting version 215
[ 3.641000] random: systemd-udevd urandom read with 9 bits of entropy available
[ 3.897905] usb 1-1: unable to read config index 0 descriptor/all
[ 3.904110] usb 1-1: can't read configurations, error -71
[ 4.033363] usb 1-1: new low-speed USB device number 3 using musb-hdrc
[ 4.175238] usb 1-1: device descriptor read/all, error -71
[ 4.293287] usb 1-1: new low-speed USB device number 4 using musb-hdrc
[ 4.713281] usb 1-1: device not accepting address 4, error -71
[ 4.833283] usb 1-1: new low-speed USB device number 5 using musb-hdrc
[ 5.253287] usb 1-1: device not accepting address 5, error -71
[ 5.259166] usb usb1-port1: unable to enumerate USB device
[ 5.414331] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 5.936435] systemd1: Found ordering cycle on basic.target/start
[ 5.936474] systemd1: Found dependency on sysinit.target/start
[ 5.936492] systemd1: Found dependency on console-setup.service/start
[ 5.936509] systemd1: Found dependency on remote-fs.target/start
[ 5.936523] systemd1: Found dependency on remote-fs-pre.target/start
[ 5.936537] systemd1: Found dependency on connman.service/start
[ 5.936551] systemd1: Found dependency on dbus.service/start
[ 5.936564] systemd1: Found dependency on basic.target/start
[ 5.936579] systemd1: Breaking ordering cycle by deleting job console-setup.service/start
[ 5.936595] systemd1: Job console-setup.service/start deleted to break ordering cycle starting with basic.target/start
[ 6.113682] NET: Registered protocol family 38
[ 6.159427] systemd1: systemd-modules-load.service: main process exited, code=exited, status=1/FAILURE
[ 6.213471] systemd1: Failed to start Load Kernel Modules.
[ 6.219334] systemd1: Unit systemd-modules-load.service entered failed state.
[ 6.746281] systemd-udevd180: starting version 215
[ 7.031479] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro
[ 8.307184] omap_rng 48310000.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-2015-09-20-4gb.img.xz
and
BBB-eMMC-flasher-debian-8.2-lxqt-4gb-armhf-2015-09-13-4gb.img.xz

my workaround for that issue was
apt-get install --reinstall linux-image-4.1.6-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.
:-)


History

Updated by Robert Nelson almost 2 years ago

odd, it looks like your dealing with a bad usb cable/hub:

usb 1-1: unable to read config index 0 descriptor/all

How are you powering the device?

debian@beaglebone:~$ uname -r
4.2.3-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
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
debian@beaglebone:~$ dmesg | grep musb
[    3.089778] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    3.089794] musb-hdrc: MHDRC RTL version 2.0 
[    3.089801] musb-hdrc: setup fifo_mode 4
[    3.089817] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    3.092451] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    3.092464] musb-hdrc: MHDRC RTL version 2.0 
[    3.092471] musb-hdrc: setup fifo_mode 4
[    3.092483] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    3.092570] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    3.092796] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    3.092982] usb usb1: Manufacturer: Linux 4.2.3-bone2 musb-hcd
[    3.092989] usb usb1: SerialNumber: musb-hdrc.1.auto
[    3.493411] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[    3.913501] usb 1-1.4: new full-speed USB device number 3 using musb-hdrc
[    4.024248] 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
[    4.158141] input: Logitech M215 as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:1020.0004/input/input0
[    4.158570] logitech-hidpp-device 0003:046D:1020.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech M215] on usb-musb-hdrc.1.auto-1.4:1
[    4.166565] input: Logitech K360 as /devices/platform/ocp/47400000.usb/47401c00.usb/musb-hdrc.1.auto/usb1/1-1/1-1.4/1-1.4:1.2/0003:046D:C52B.0003/0003:046D:4004.0005/input/input1
[    4.167484] logitech-hidpp-device 0003:046D:4004.0005: input,hidraw2: USB HID v1.11 Keyboard [Logitech K360] on usb-musb-hdrc.1.auto-1.4:2

  • Assignee set to Robert Nelson

Updated by First name Last name almost 2 years ago

odd, it looks like your dealing with a bad usb cable/hub:

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
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
debian@beaglebone:~$

2) unplugging the powered hub (powered only by barrel connector) :-(

debian@beaglebone:~$ [ 494.559183] usb 1-1: device descriptor read/64, error -71
[ 495.209461] usb 1-1: device not accepting address 18, error -71
[ 495.449563] usb 1-1: device descriptor read/64, error -71
[ 495.679614] usb 1-1: device descriptor read/64, error -71
[ 496.329878] usb 1-1: device not accepting address 20, error -71
[ 496.870126] usb 1-1: device not accepting address 21, error -71
[ 496.876237] usb usb1-port1: unable to enumerate USB device

debian@beaglebone:~$ sudo lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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' :-)

So another Big Thankyou for all your good work providing the excellent test images.
:-)

Also available in: Atom PDF