Also, short term, using something else to get your project working would probably be a good idea. However, it'd be cool to get that problem resolved eventually too . . .
On Fri, Sep 25, 2015 at 8:32 AM, William Hermans <[email protected]> wrote: > *A few posts below the one you're referring to, they just disable the >> kernel config option instead. It looks like it didn't really help anyway, >> and the only thing that worked was to power the board via USB instead of >> barrel plug, but then you can only get 500ma.* >> > > > Well, no. It puts the USB into peripheral mode, instead of being in OTG > host mode. As for 500ma . . that's all you're going to get anyway, so > maybe that is your problem. > > Anyway, the idea was to get the USB port out of host mode. Still not sure > it would work, but I'm starting to wonder now if your problem is power > related. As in power provided to you hackRF. Personally, I think it is a > bit ridiculous that such a great piece of hardware is only power-able via > USB ?! > > On Fri, Sep 25, 2015 at 6:23 AM, Stephen P <[email protected]> wrote: > >> Well thanks for the help, but I guess that I'm going to have to use some >> other hardware for this project. Based on all of the other (unresolved) >> posts going back years, it seems the BBB just doesn't have stable USB >> support. >> >> A few posts below the one you're referring to, they just disable the >> kernel config option instead. It looks like it didn't really help anyway, >> and the only thing that worked was to power the board via USB instead of >> barrel plug, but then you can only get 500ma. >> >> On Wed, Sep 23, 2015 at 10:24 PM, William Hermans <[email protected]> >> wrote: >> >>> Here is the post I was talking about: >>> https://groups.google.com/forum/#!searchin/beagleboard/reboot|sort:relevance/beagleboard/2yOpE3XYJ1Y/gXB5oSuM7VAJ >>> >>> lisarden's 4th or 5th post, he talks about modifying board-am335xevm.c. >>> >>> Anyway Im not sure this will fix anything. It is only a gut feeling I >>> get when reading all the posts on the internet, and the "host" part of the >>> error message. That you, and others are getting. I've been reading about a >>> lot of musb host mode errors over the lat 2-3 years . . . >>> >>> On Wed, Sep 23, 2015 at 7:05 PM, William Hermans <[email protected]> >>> wrote: >>> >>>> I just noticed that on my image too . . >>>> >>>> william@xanbustester:~$ zcat /proc/config.gz | grep OTG >>>> # CONFIG_USB_OTG is not set >>>> # CONFIG_USB_OTG_WHITELIST is not set >>>> # CONFIG_USB_OTG_BLACKLIST_HUB is not set >>>> # CONFIG_USB_OTG_FSM is not set >>>> # CONFIG_USB_FOTG210_HCD is not set >>>> # CONFIG_USB_FOTG210_UDC is not set >>>> >>>> Although I do recall someone posting a month or two ago in relation to >>>> the auto kernel reboots, how to disable the OTG USB stuff. I think it was a >>>> kernel level fix. >>>> >>>> On Wed, Sep 23, 2015 at 7:01 PM, Stephen Pape <[email protected]> wrote: >>>> >>>>> I just checked out the code to attempt a build, and it looks like the >>>>> kernel >>>>> config >>>>> <https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/config> >>>>> already >>>>> has CONFIG_USB_OTG disabled >>>>> <https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/config#L4042>, >>>>> unless I'm looking at the wrong configuration file somehow. >>>>> >>>>> -Stephen >>>>> >>>>> On Wednesday, September 23, 2015 at 11:29:47 AM UTC-4, William Hermans >>>>> wrote: >>>>>> >>>>>> *They have pio mode set too..* >>>>>>> >>>>>>> *https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/config#L4133-L4134 >>>>>>> <https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/config#L4133-L4134>* >>>>>>> >>>>>>> * ARCH arm, sync's with our patchset, so it's almost exactly the >>>>>>> same as* >>>>>>> * linux-image-4.2.0-bone2 in our debian repo..* >>>>>>> >>>>>>> * Regards,* >>>>>> >>>>>> >>>>>> Ok, so trying a Debian image probably would not solve the problem >>>>>> then. However, I'm curious if disabling OTG on USB will fix it. Assuming >>>>>> the device Stephen is using does not require OTG USB . . . >>>>>> >>>>>> On Wed, Sep 23, 2015 at 7:55 AM, Robert Nelson <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> On Wed, Sep 23, 2015 at 9:47 AM, Stephen Pape <[email protected]> >>>>>>> wrote: >>>>>>> > I'm using Arch Linux with all packages updated (kernel >>>>>>> 4.2.0-1-ARCH). I >>>>>>> > noticed the older posts as well, but I haven't seen anyone offer a >>>>>>> solution. >>>>>>> > My guess is that the problem was just never resolved. >>>>>>> >>>>>>> They have pio mode set too.. >>>>>>> >>>>>>> >>>>>>> https://github.com/archlinuxarm/PKGBUILDs/blob/master/core/linux-am33x/config#L4133-L4134 >>>>>>> >>>>>>> ARCH arm, sync's with our patchset, so it's almost exactly the same >>>>>>> as >>>>>>> linux-image-4.2.0-bone2 in our debian repo.. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> -- >>>>>>> Robert Nelson >>>>>>> https://rcn-ee.com/ >>>>>>> >>>>>>> -- >>>>>>> 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 [email protected]. >>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>> >>>>>> >>>>>> -- >>>>> 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 [email protected]. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>> -- >>> 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/7h_cvfGexVs/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> 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 [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
