• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 98 subscribers
  • Views 519 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 Device Detection Problems at Boot on Blaze 4430 Development Platform

Scott Talbert
Prodigy 110 points
Other Parts Discussed in Thread: 4430

Hi,

I am working on a Blaze 4430 Development Platform running Android 4AI.1.5.  I am seeing an issue with USB device detection when I boot up the Blaze with certain USB devices attached: powered USB hubs or a USB LTE modem.

When I boot with these devices attached I am getting the below kernel messages over and over.  When the Blaze gets into this state, it seems that the USB interface is stuck and even hotplugging the device does not work.  Also, I can boot fine with certain other USB devices attached (e.g., USB flash drive) and the devices are recognized on boot.  I also can boot fine (and the devices are recognized) if I attach an unpowered USB hub.  If I connect a powered USB hub after the Blaze has booted, it works fine.

Any ideas why I'm seeing USB issues on bootup with certain devices?

Thanks, Scott

<6>[    4.146667] musb-hdrc musb-hdrc: MUSB HDRC host driver
<6>[    4.152496] musb-hdrc musb-hdrc: new USB bus registered, assigned bus number 2
<6>[    4.160736] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
<6>[    4.168304] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
<6>[    4.176422] usb usb2: Product: MUSB HDRC host driver
<6>[    4.181976] usb usb2: Manufacturer: Linux 3.0.21-0003_1bl+ musb-hcd
<6>[    4.189056] usb usb2: SerialNumber: musb-hdrc
<6>[    4.194702] hub 2-0:1.0: USB hub found
<6>[    4.952758] usb 2-1: new high speed USB device number 2 using musb-hdrc
<6>[    5.536041] usbcore: registered new interface driver usbhid
<6>[    5.542266] usbhid: USB HID core driver
<6>[    5.599395] usbcore: registered new interface driver snd-usb-audio
<3>[    9.955413] android_usb: already disabled
<3>[   20.077758] usb 2-1: device descriptor read/64, error -110
<3>[   35.312072] usb 2-1: device descriptor read/64, error -110
<6>[   35.546447] usb 2-1: new high speed USB device number 3 using musb-hdrc
<3>[   50.671539] usb 2-1: device descriptor read/64, error -110
<3>[   65.905944] usb 2-1: device descriptor read/64, error -110
<6>[   66.140289] usb 2-1: new high speed USB device number 4 using musb-hdrc
<3>[   76.562164] usb 2-1: device not accepting address 4, error -110
<6>[   76.687164] usb 2-1: new high speed USB device number 5 using musb-hdrc
<3>[   87.109008] usb 2-1: device not accepting address 5, error -110
<3>[   87.115997] hub 2-0:1.0: unable to enumerate USB device on port 1
<4>[   87.123596] musb_bus_suspend 2298: trying to suspend as a_host while active
<6>[   87.249633] usb 2-1: new high speed USB device number 6 using musb-hdrc
<3>[  102.374694] usb 2-1: device descriptor read/64, error -110
<3>[  117.609069] usb 2-1: device descriptor read/64, error -110
<6>[  117.843444] usb 2-1: new high speed USB device number 7 using musb-hdrc
<3>[  132.968444] usb 2-1: device descriptor read/64, error -110

  • 0
    TI__Expert 8055 points

    Scott,

    I will look into this.  First I want to confirm:

    - You are using a Blaze OMAP4430 ES2.3 HS platform, correct?

    - Are you using the Android pre-built binaries from here: http://www.omappedia.com/wiki/Android:_Working_with_pre-built_binaries?  Could you do a quick test with the 4AI.1.7 pre-built binaries from this site, as 4AI.1.7 is the Beta release, to confirm you see the same behavior?

    - Do you have any other Blaze or Blaze Tablet hardware you could test with to confirm you see the same behavior?

    - You mean that there are some devices that always work on bootup and some devices that always fail on bootup, correct?  (Not that the devices work sometimes)

    Thank you,
    Gina 

  • 0 in reply to Gina Glaser
    Prodigy 110 points

    Gina,

    Thanks for looking into it.

    - Yes, I believe that is correct, but is there a way I can tell for sure?  I don't see any real markings on the outside of the unit.

    - No, I am not using prebuilt binaries, but I will try the 4AI.1.7 ones to see if that helps.

    - I may have one other Blaze that I can try.

    - Correct, I have some devices that always fail and some devices that always work.  The success/failure is consistent for a given device.

    Thanks, Scott

  • 0 in reply to Scott Talbert
    TI__Expert 8055 points

    Scott,

    If you pop off the back cover of your Blaze, usually there is a sticker on the SOM that indicates, for example, "ES2.3 HS".

    Thanks,
    Gina 

  • 0 in reply to Gina Glaser
    Prodigy 110 points

    Mine reads: ES2.3 GP

    Scott

  • 0 in reply to Scott Talbert
    TI__Expert 8055 points

    Scott,

    I tested here with an OMAP4430 ES2.3 HS Blaze (sorry I don't have an ES2.3 GP easily accessible, but I really doubt that should have any effect), and the 4AI.1.7 prebuilt binaries from omappedia.  I plugged in a powered USB hub into the Blaze OTG port with a micro-A USB cable before powering on the Blaze.  It seemed to detect the hub fine, and I didn't get any of the error messages that you reported.  

    Can you please confirm if you see the same issue on your 2nd Blaze as well, using the 4AI.1.7 prebuilt binaries from omappedia?  If so, it would be helpful if you could send some details about the devices that you see the issue with and the devices you do not see the issue with.

    Thank you,
    Gina 

  • 0 in reply to Gina Glaser
    Prodigy 110 points

    Gina,

    Thanks for testing it.  We tested on the 2nd Blaze but with a different powered USB hub and it worked OK.  Unfortunately, the 2 Blazes are not in the same location and we do not have duplicate instances of the problematic USB devices.

    I will try the prebuilt 4AI.1.7 binaries and let you know the results.

    Thanks, Scott

  • 0 in reply to Scott Talbert
    Prodigy 110 points

    Gina,

    I was able to test the prebuilt 4AI.1.7 binaries on my Blaze. Unfortunately, I could not do a 100% apples-to-apples test as the prebuilt kernel does not have all of the drivers I need for one of my devices, but for the USB hubs, I am no longer seeing those error messages on bootup and the devices appear to be enumerating correctly.

    This suggests to me that there are probably some USB-related kernel fixes between 4AI.1.5 and 4AI.1.7.  I'll have to take a look to see if I can find a specific patch or two that I can pick up.

    Thanks,

    Scott

  • 0 in reply to Scott Talbert
    TI__Expert 8055 points

    Scott,

    That's good news; thanks for the update.  In case you aren't already aware, you can see the kernel patches to /drivers/usb pushed here: http://git.omapzoom.org/?p=kernel/omap.git;a=history;f=drivers/usb;hb=p-android-omap-3.0  However, have you considered moving to the 4AI.1.7 release?  That is our recommendation, since 4AI.1.7 is the Beta release for Ice Cream Sandwich, and has many bug fixes pushed since 4AI.1.5 across other subsystems as well.

    Regards,
    Gina 

  • 0 in reply to Gina Glaser
    Prodigy 110 points

    Gina,

    Thanks...unfortunately, I don't think we can move outright to 4AI.1.7 at this point in our program.  I'd feel much more comfortable if I could just cherry-pick a patch or two.  But we may look to move forward in the future.

    Thanks, Scott