Google Groups

Re: USB EHCI problems


Nuno Felicio Dec 20, 2009 6:18 AM
Posted in group: BeagleBoard
but it is high speed and i have tested with other kind of devices like
webcams and the enumeration fails also...
i think that if an usb 2.0 device that have more than one endpoit  is
connected directly to the EHCI usb host port it will fail!

Nuno


On Dec 18, 4:43 pm, Steve Sakoman <sako...@gmail.com> wrote:
> On Sat, Dec 12, 2009 at 8:25 AM, Nuno Felicio <nuno.feli...@gmail.com> wrote:
> > For a real test just do this: put an normal USB2.0 device that have
> > more than one endpoint  directly on the HOST port(ex: an usb Bluetooth
> > dongle ), no HUB (the USB hubs hide the problem!!), typically the
> > enumeration of the device fails!!
>
> Remember that the EHCI port is high speed only!
>
> If your Bluetooth dongle is not a high speed device, you *must* use a
> hub or the device will not be enumerated.
>
> Steve
>
>
>
> > I really like the OMAP3 but im shocked with the problems in the USB
> > HOST port, TI is doing a really poor job in this part...
>
> > One more thing... for the ppl that have problems with webcams,
> > typically corrupted frames... I suspect this is caused by the same
> > problem that causes problems in enumeration ...
>
> > Nuno
>
> > On Dec 11, 1:04 pm, Gerald Coley <ger...@beagleboard.org> wrote:
> >> This is a noise issue on the 1.8V IO rail and is due to the fact that the
> >> PHY does not like frequencies in the 400HZ to 4MHZ range. The switcher on
> >> the VIO_1V8 rail is 3.6MHZ. The solution is to isolate the 1.8V rail on the
> >> PHY from the main 1.8V rail.
>
> >> Oh, and I am the designer of the BeagleBoard. This issue has been fixed on
> >> the rev C4 board using the above described method.
>
> >> One additional note. I have seen cases where if the USB PHY and the
> >> BeagleBoard are not plugged into the same outlet or power strip and
> >> depending on the quality of your supplies, a ground loop can exists which
> >> can also cause additional USB issues.
>
> >> Gerald
>
> >> On Fri, Dec 11, 2009 at 6:53 AM, Stan-Dave <wizard.s...@gmail.com> wrote:
> >> > Well this is interesting.
> >> > After the fix, dd test runs fine.
> >> > After a couple of days, however, things go strange.
> >> > I've got a powered USB hub plugged into my BeagleBoard, and wireless
> >> > ethernet plugged into the hub.  Before, when the USB host would crash,
> >> > it would just die: lsusb returned just the two basic lines with no
> >> > extra devices, and plugging and removing devices made no change and
> >> > nothing appeared in dmesg.
> >> > Now my ethernet dies, but lsusb still says everything is there.  If I
> >> > attempt to bring up the network, it fails with a bunch of errors.
> >> > Here's the strange part: I can plug in a thumb drive and run the dd
> >> > test just fine still; unplug, replug, dd, back and forth, no problems.
> >> > But if I unplug my ethernet, then the whole thing becomes unstable
> >> > again: plugging anything else in after removing the ethernet causes
> >> > the EHCI to crash in the same way it used to; no disconnect/reconnect
> >> > notice, nothing reported in lsusb, just dead.  Only way to recover is
> >> > a complete reboot.
> >> > I believe I may actually have had two problems, one exacerbated by the
> >> > other.  Now that I think about it, even back before the fix, it would
> >> > die in this manner every 2 days or so.  Since the dd test consistently
> >> > caused it to crash, I just chalked it off to the USB problem.  Now,
> >> > I'm suspecting I had a different problem with my ethernet which may
> >> > have looked like or triggered this other USB error.  The fact that,
> >> > once it starts having problems, I can make the USB crash again
> >> > suggests a rather close tie in.
> >> > I need to do some more tests, but since I only get one shot to test
> >> > something every 2 days, it could take a while to figure out exactly
> >> > what's going on, unless someone smarter than I am has a suggestion.
> >> > The error log when I try to bring up my ethernet is at
> >> >http://www.rebirthofxeen.com/dmesg.log
> >> > Anywho, I just wanted to say that the fix does seem to have mostly
> >> > worked; hitting the USB hard with dd seems to work, but there may be
> >> > other problems which can trigger it.  I should know more in couple of
> >> > days.
>
> >> > --
>
> >> > You received this message because you are subscribed to the Google Groups
> >> > "Beagle Board" group.
> >> > To post to this group, send email to beagl...@googlegroups.com.
> >> > To unsubscribe from this group, send email to
> >> > beagleboard...@googlegroups.com<beagleboard%2Bunsubscribe@googlegr oups.com>
> >> > .
> >> > For more options, visit this group at
> >> >http://groups.google.com/group/beagleboard?hl=en.
>
> > --
>
> > You received this message because you are subscribed to the Google Groups "Beagle Board" group.
> > To post to this group, send email to beagl...@googlegroups.com.
> > To unsubscribe from this group, send email to beagleboard...@googlegroups.com.
> > For more options, visit this group athttp://groups.google.com/group/beagleboard?hl=en.