• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 1658 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

USB devices on host OTG port in OMAP4430/4460

michelle villegas
Intellectual 640 points
Other Parts Discussed in Thread: 4460

Hi, i am trying to get data from USB device by plugging the device at the OTG port of my OMAP4430/4460 based board, i configured the kernel and disabled the android gadget driver, and enabled the port as host, and i get the following:

[ 0.529846] musb-hdrc: version 6.0, musb-dma, host
[ 0.530151] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)
[ 0.530151] musb-hdrc: MHDRC RTL version 2.0
[ 0.530151] musb-hdrc: setup fifo_mode 4
[ 0.530609] musb-hdrc: 28/31 max ep, 16384/16384 memory
[ 0.530609] musb-hdrc musb-hdrc: MUSB HDRC host driver
[ 0.530975] musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 1
[ 0.530975] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.530975] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.531402] usb usb1: Product: MUSB HDRC host driver
[ 0.531494] usb usb1: Manufacturer: Linux 3.0.8-g52f4764-dirty musb-hcd
[ 0.531494] usb usb1: SerialNumber: musb-hdrc
[ 0.531494] hub 1-0:1.0: USB hub found
[ 0.532226] hub 1-0:1.0: 1 port detected
[ 0.532226] musb-hdrc musb-hdrc: USB OTG mode controller at fc0ab000 using DMA, IRQ 124
[ 0.532775] Switched to NOHz mode on CPU #0
[ 0.532775] Switched to NOHz mode on CPU #1
[ 0.533081] NET: Registered protocol family 2
[ 0.533081] IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.534423] TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.534423] TCP bind hash table entries: 65536 (order: 8, 1572864 bytes)
[ 0.539154] TCP: Hash tables configured (established 131072 bind 65536)
[ 0.539154] TCP reno registered

apparently the OTG port is configured as HOST and the USB bus is registered, and there seems to be a device found, but i have nothing plugged on the port yet, and there is product and vendor of a device but i don't know what device is it refering to,  and when i execute:

$ cat /proc/bus/usb/devices

i get the follwing:

T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 1
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=1d6b ProdID=0002 Rev= 3.00
S: Manufacturer=Linux 3.0.8-g52f4764-dirty musb-hcd
S: Product=MUSB HDRC host driver
S: SerialNumber=musb-hdrc
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr= 0mA
I:* If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 4 Ivl=256ms

and when i plug any device on that port nothing happens, the device that i am using to make the tests is a touchpad, i am powering it with other source, i am not using the port to power the device, i only use the data lines of the OTG USB and ground the power source that i am using to ground of my board, but when i plug it, i dont get anything on the kernel, it seems like if it wouldn't be recognized, so i dont know what could it be, because the port seems to be configured as Host.

I am using a Pandaboard, with Android ICS and kernel 3.0.8 running on it.

Best Regards.

  • 0
    TI__Expert 8055 points

    Michelle,

    Please contact the Pandaboard Google Group to see if/how USB host support is included.  On Blaze and Blaze Tablet, this should work.

    Regards,
    Gina 

  • 0 in reply to Gina Glaser
    Intellectual 640 points

    Hi, i got it working now (the OTG as Host in Pandaboard unerd Android ICS), i had to ground the J15 in Pandaboard (the ID pin of the OTG), also i selected the Host in the kernel for the inventra controller and disable the gadged driver for the OTG, and i connected the touchpad with an OTG cable and it worked perfectly (connecting only that device), though, when i connect a HUB in that port (a HUB powered by an external source) i get the following error:

    [ 170.161193] usb 1-1: new high speed USB device number 10 using musb-hdrc 
    [ 185.289184] usb 1-1: device descriptor read/64, error -110 
    [ 200.525543] usb 1-1: device descriptor read/64, error -110 
    [ 200.764892] usb 1-1: new high speed USB device number 11 using musb-hdrc 
    [ 215.897552] usb 1-1: device descriptor read/64, error -110 
    [ 231.133850] usb 1-1: device descriptor read/64, error -110 
    [ 231.373138] usb 1-1: new high speed USB device number 12 using musb-hdrc 
    [ 241.802825] usb 1-1: device not accepting address 12, error -110

    and it keeps enumerating and the device is never accepted, i dont know what could it be, because i am powering the HUB externally, so i dont think there could be a problem of power.

    Best Regards.