Sure, I did start to write about using the HackRF at http://blog.stephenpape.net/
I've actually completed that whole project (I can generate a signal to control a ceiling fan), but I've only written the first blog post about decoding the signal so far. I'll cover generating the packet and synthesizing the signal when I get around to writing more. -Stephen On Fri, Sep 25, 2015 at 12:01 PM, William Hermans <yyrk...@gmail.com> wrote: > Stephen, > > Somewhat off topic. But if you plan on blogging, or just sharing your > experiences, and / or project notes on that hackRF. Id be interesting in > reading . . . > > My buddy here has been an EE for a long time, and a professional radio > station engineer. But as far as I know hes not worked with SDRs in this > context so much. Anyway, we both have interest in that device of yours . . . > > On Fri, Sep 25, 2015 at 8:56 AM, Stephen P <srp...@gmail.com> wrote: > >> Alright, thanks for the help! I think I'll order one of those. >> >> On Fri, Sep 25, 2015 at 11:52 AM, William Hermans <yyrk...@gmail.com> >> wrote: >> >>> *I might try a raspberry pi, but I'm kind of worried that it'll use the >>>> same USB stack and have the same issue. Might be worth a shot though.* >>>> >>> >>> It shouldn't. But if you want flexibility in which distro you install >>> I'd go with the rPI-2. >>> >>> On Fri, Sep 25, 2015 at 8:50 AM, Stephen P <srp...@gmail.com> wrote: >>> >>>> Ah, I see. I've tried it with and without the hub. I actually bought >>>> the hub because I at first assumed that the HackRF wasn't getting enough >>>> power, but I saw the same behavior. >>>> >>>> I might try a raspberry pi, but I'm kind of worried that it'll use the >>>> same USB stack and have the same issue. Might be worth a shot though. >>>> >>>> On Fri, Sep 25, 2015 at 11:45 AM, William Hermans <yyrk...@gmail.com> >>>> wrote: >>>> >>>>> No, just making sure you were not using the mini - heh. >>>>> >>>>> Anyway, I do not really know where to start in fixing this, well >>>>> actually I do. . . libusb, but after that . . . no idea. >>>>> >>>>> Hubs can also sometimes cause problems, but you're already able to >>>>> receive it seems. Which I guess as long as you're not trying receive and >>>>> send at the same time. You're good. >>>>> >>>>> On Fri, Sep 25, 2015 at 8:38 AM, Stephen P <srp...@gmail.com> wrote: >>>>> >>>>>> The full sized. Why would I use the mini? I'd have to get an adapter, >>>>>> but I could try it I guess. I have a powered USB hub connected to the >>>>>> full >>>>>> sized USB port. Then a HackRF connected to the hub. >>>>>> >>>>>> On Fri, Sep 25, 2015 at 11:36 AM, William Hermans <yyrk...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> What a minute. Which port are you using to attempt to connect to >>>>>>> your hackRF ? the mini, or full sized port ? >>>>>>> >>>>>>> On Fri, Sep 25, 2015 at 8:34 AM, Stephen P <srp...@gmail.com> wrote: >>>>>>> >>>>>>>> What do you mean? I'm giving the board 2.5A via a wall plug. If I >>>>>>>> power the board over USB, then I can only give it 500ma. >>>>>>>> >>>>>>>> On Fri, Sep 25, 2015 at 11:32 AM, William Hermans < >>>>>>>> yyrk...@gmail.com> 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 <srp...@gmail.com> >>>>>>>>> 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 < >>>>>>>>>> yyrk...@gmail.com> 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 < >>>>>>>>>>> yyrk...@gmail.com> 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 <srp...@gmail.com >>>>>>>>>>>> > 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 < >>>>>>>>>>>>>> robert...@gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Wed, Sep 23, 2015 at 9:47 AM, Stephen Pape < >>>>>>>>>>>>>>> srp...@gmail.com> 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 beagleboard...@googlegroups.com. >>>>>>>>>>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>>>>>>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>>>>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>>>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>>>>>> 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 >>>>>>> beagleboard+unsubscr...@googlegroups.com. >>>>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>>>> 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 >>>>> beagleboard+unsubscr...@googlegroups.com. >>>>> 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 beagleboard+unsubscr...@googlegroups.com. >>>> 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 >>> beagleboard+unsubscr...@googlegroups.com. >>> 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 beagleboard+unsubscr...@googlegroups.com. >> 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 > beagleboard+unsubscr...@googlegroups.com. > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
