Bug 9472 - [NO USB support ] Beaglebone black latest yocto
Summary: [NO USB support ] Beaglebone black latest yocto
Status: RESOLVED FIXED
Alias: None
Product: General Runtime
Classification: Runtime
Component: General Runtime (show other bugs)
Version: unspecified
Hardware: BeagleBone Multiple
: Medium+ major
Target Milestone: 2.1.1
Assignee: Kevin Hao
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2016-04-17 21:04 UTC by hiims
Modified: 2016-06-01 10:49 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: New (Never tested)
Verified:
Documentation change: Don't know


Attachments
boot dmesg log (10.02 KB, text/plain)
2016-04-21 19:08 UTC, hiims
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description hiims 2016-04-17 21:04:44 UTC
After installing yocto minimal on beaglebone black there is no USB device.

ll /sys/bus/usb/devices/
   3707 drwxr-xr-x    2 root     root             0 Jan  1  2000 .
   3705 drwxr-xr-x    4 root     root             0 Jan  1  2000 ..


plug and play USB - DMESG not respond to changes.

lsusb return
"unable to initialize libusb: -99 "


--------------------------
step to reproduce:
install yocto core-image-minimal

software version
kernel 4.1.6-yocto-standard and 4.1.15-yocto-standard

--------------------------
please note:
tested on 3 different beaglebones
Comment 1 Saul Wold 2016-04-21 18:38:22 UTC
This is likely because you are building core-image-minimal which does not contain kernel-modules, is it possible that there is missing modules.  If you build core-image-full-cmdline for example does it display USB correctly?

Also, can you please provide your dmesg output.
Comment 2 hiims 2016-04-21 19:08:51 UTC
Created attachment 3147 [details]
boot dmesg log
Comment 3 hiims 2016-04-21 19:19:01 UTC
hi Saul,
thanks for your help.
attaching the boot dmesg.

you can see that USB needed modules are loaded but there is no USB device at all.
also i'll build the other images for test.
IMHO this is related to the firmware, because the HW is not exists on /dev or /sys/bus/usb
Comment 4 hiims 2016-04-22 07:37:19 UTC
tested with core-image-full-cmdline same results
Comment 5 hiims 2016-04-22 08:18:52 UTC
enabling MUSB_HDRC  in the kernel config fix the problem


DMESG partially output
----------------------------------------------------
    dmesg |grep -i usb
[    2.019340] usbcore: registered new interface driver usbfs
[    2.019415] usbcore: registered new interface driver hub
[    2.019554] usbcore: registered new device driver usb
[    2.740153] usbcore: registered new interface driver kaweth
[    2.744774] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[    2.751233] usbcore: registered new interface driver pegasus
[    2.755942] usbcore: registered new interface driver rtl8150
[    2.760586] usbcore: registered new interface driver asix
[    2.764966] usbcore: registered new interface driver ax88179_178a
[    2.770041] usbcore: registered new interface driver cdc_ether
[    2.774867] usbcore: registered new interface driver dm9601
[    2.779426] usbcore: registered new interface driver smsc75xx
[    2.784192] usbcore: registered new interface driver smsc95xx
[    2.788907] usbcore: registered new interface driver net1080
[    2.793554] usbcore: registered new interface driver cdc_subset
[    2.798446] usbcore: registered new interface driver zaurus
[    2.802999] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[    2.809486] usbcore: registered new interface driver int51x1
[    2.814164] usbcore: registered new interface driver cdc_ncm
[    2.818966] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.828770] usbcore: registered new interface driver usb-storage
[    2.834957] 47401300.usb-phy supply vcc not found, using dummy regulator
[    2.864330] musb-hdrc musb-hdrc.0.auto: Need DT for the DMA engine.
[    2.869556] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.869565] musb-hdrc: MHDRC RTL version 2.0 
[    2.869571] musb-hdrc: setup fifo_mode 4
[    2.869589] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.870621] 47401b00.usb-phy supply vcc not found, using dummy regulator
[    2.904213] musb-hdrc musb-hdrc.1.auto: Need DT for the DMA engine.
[    2.909433] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[    2.909442] musb-hdrc: MHDRC RTL version 2.0 
[    2.909448] musb-hdrc: setup fifo_mode 4
[    2.909461] musb-hdrc: 28/31 max ep, 16384/16384 memory
[    2.909573] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver
[    2.914327] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 1
[    2.922177] hub 1-0:1.0: USB hub found
[    2.966638] usb0: HOST MAC <removed>
[    2.969884] usb0: MAC <removed>
[    3.102872] usbcore: registered new interface driver usbhid
[    3.107364] usbhid: USB HID core driver
[    3.413570] usb 1-1: new high-speed USB device number 2 using musb-hdrc
[    3.554100] usb-storage 1-1:1.0: USB Mass Storage device detected
[    3.567905] scsi host0: usb-storage 1-1:1.0
[  149.023975] usb 1-1: USB disconnect, device number 2
[  154.702402] usb 1-1: new high-speed USB device number 3 using musb-hdrc
[  154.850885] usb-storage 1-1:1.0: USB Mass Storage device detected
[  154.856621] scsi host1: usb-storage 1-1:1.0

----------------------------------------------------
lsusb
Bus 001 Device 003: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

----------------------------------------------------

i did a lot of changes in the kernel config, adding multiple drivers etc,
i'll check it again in the next few days with only the MUSB_HDRC enable to see if it work, and probably it should be added to BBB defconfig.
so please don't close this bug till i check with a clean image.
Comment 6 hiims 2016-04-25 18:14:46 UTC
tested and it works on a new clean minimal image

BTW
after enabling the HDRC i got those warnings

Value requested for CONFIG_USB_MUSB_AM335X_CHILD not in final ".config"
Requested value: "CONFIG_USB_MUSB_AM335X_CHILD=m"
Actual value set: "CONFIG_USB_MUSB_AM335X_CHILD=y"

Value requested for CONFIG_USB_MUSB_DSPS not in final ".config"
Requested value: "CONFIG_USB_MUSB_DSPS=m"
Actual value set: "CONFIG_USB_MUSB_DSPS=y"

Value requested for CONFIG_USB_MUSB_HDRC not in final ".config"
Requested value: "CONFIG_USB_MUSB_HDRC=m"
Actual value set: "CONFIG_USB_MUSB_HDRC=y"

Value requested for CONFIG_USB_MUSB_OMAP2PLUS not in final ".config"
Requested value: "CONFIG_USB_MUSB_OMAP2PLUS=m"
Actual value set: "CONFIG_USB_MUSB_OMAP2PLUS=y"

thanks
Comment 7 Stephen K Jolley 2016-05-02 17:59:30 UTC
Saul,

It appears he has answered your question.  If you have more questions please place this back into NEEDINFO.