Hi Sword, I haven't got time to touch BBB recently. Most of my time devote to testing of some other device. Frankly speaking BBB more or less having the least stable USB with 3.8 kernel. There was a patch in this thread indeed helped somehow but still it gives trouble when it want.
>From the first day we understand the USB is quite sensitive to current draw or whatever, we have been using separate power from day 1 and have tested using extension cord of more than 10m which didn't really cause much difference IMHO. Sorry not able to provide much useful information, will definitely revisit here when I got time to play with BBB again. Meanwhile set mpurate indeed helped quite much with the old kernel. But since the USB patch from kernel, I don't feel any substential difference by applying it and what's more it seems sometimes ignore my setting >_<. Regards, Bai Shi On Fri, Nov 8, 2013 at 1:20 PM, <sword.l.dra...@gmail.com> wrote: > Hi，I have the same issue with musb babble interupt. some low speed mouse > can enumerate > normally on my box, some mouse will always fail. > For the failed mouse, there is always a babble interrupt, and the host > mode lost(DEVCTL is 0x98). > But I can work around with a externsion cord(about 1.5m), all the failed > mouse can work in > this case. > Could you give me some hint for debugging this problem? I think it may be > the bug with mentor's > USB ip. > > On Monday, October 28, 2013 11:27:09 PM UTC+8, Shi Bai wrote: > >> Erm, ok. I'll look for a good shielded cable.. >> >> >> On Mon, Oct 28, 2013 at 10:42 PM, Paulo Ferreira <p...@keeh.net> wrote: >> >>> You issue may be there (or not). >>> >>> To really really know, you can use some wide bandwidth digital >>> oscilloscopes to see how the USB signals are behaving. >>> Or try to use a good shielded USB cable. >>> >>> Guess what is the cheapest option, try it, and after that please tell us >>> what did you find. >>> >>> Best regards >>> Paulo Ferreira >>> >>> >>> >>> >>> >>> >>> >>> On 28/10/2013, at 14:22, Bai Shi <bais...@gmail.com> wrote: >>> >>> > Erm.. very good question. It indeed is the same external power supply >>> connected to the Beagle Board. Or I would say all the power come from the >>> same ATX power supply though it might (tiny little chance) be in different >>> rails. >>> > >>> > Frankly speaking the line was rather short (less than 5cm) so I didn't >>> bother to do shielding at all. The D+ and D- is using Cat5 ethernet cable. >>> > >>> > Does it make any significance? >>> > >>> > Regards, >>> > Bai Shi >>> > >>> > >>> > On Mon, Oct 28, 2013 at 9:56 PM, Paulo Ferreira <p...@keeh.net> wrote: >>> >>> > >>> > On 28/10/2013, at 13:27, Bai Shi <bais...@gmail.com> wrote: >>> > >>> > > My usb device draws power from external power supply, only D+ and D- >>> is connected to BBB. It works 90% of time but when I mess around too much >>> (on/off too frequently maybe, not confirmed), it will reset the USB of BBB >>> and then it will behave very strangely. Every access to /sys/bus/usb take >>> more than 15 seconds and timeout eventually. >>> > > >>> > > Hope my experience gives some hint... >>> > >>> > Is the same external power supply connected to the Beagle Board? >>> > >>> > So, the ground shield of the USB cable is connect only on one side >>> (the device) or is it completely "floating"? >>> > >>> > Best regards >>> > >>> > Paulo Ferreira >>> > >>> > -- >>> > For more options, visit http://beagleboard.org/discuss >>> > --- >>> > You received this message because you are subscribed to a topic in the >>> Google Groups "BeagleBoard" group. >>> > To unsubscribe from this topic, visit https://groups.google.com/d/ >>> topic/beagleboard/nuyyVDhU6bw/unsubscribe. >>> > To unsubscribe from this group and all its topics, send an email to >>> beagleboard...@googlegroups.com. >>> >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> > >>> > >>> > -- >>> > For more options, visit http://beagleboard.org/discuss >>> > --- >>> > You received this message because you are subscribed to the Google >>> Groups "BeagleBoard" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an email to beagleboard...@googlegroups.com. >>> > For more options, visit https://groups.google.com/groups/opt_out. >>> >>> -- >>> For more options, visit http://beagleboard.org/discuss >>> --- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "BeagleBoard" group. >>> To unsubscribe from this topic, visit https://groups.google.com/d/ >>> topic/beagleboard/nuyyVDhU6bw/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> beagleboard...@googlegroups.com. >>> >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >> >> -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/beagleboard/nuyyVDhU6bw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > beagleboard+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
