Hi Philip,

I also have an old Beagleboard.  In this case, I am more inclined to buy an
Overo Air which also has OMAP 3530.  Would you mind to kindly send out the
step-by-step procedure on how to get gnuradio workong in Overo?  It would be
a great help for me.

I am eager to try it out and I am begining to test out getting some sample
programs running with OE.

Thanks alot.

Anne

On Sun, May 31, 2009 at 10:41 PM, Philip Balister <[email protected]>wrote:

> anne kwong wrote:
>
>> Hi
>>
>> I want to run usrp, gnuradio using beagleboard.  In addition, I hope to
>> leverage on the TI dsp chip.
>>
>> Has anyone done that and can show me how to do that?
>>
>
> Yes :) (Well, the USRP test was done with a Gumstix Overo since I have an
> old Beagle)
>
> To use the USRP1, you will need a rev C Beagle (has working EHCI port). I
> haven't tried the musb port.
>
> To get a working build with the usrp, you will need to know your way around
> OE a bit. (I'm sure you could build GNU Radio without OE, but building the
> needed libraries might drive you crazy).
>
> The trickiest part at the moment is you need to patch OE to build libusb,
> not libusb-compat. We are sort of working on building a static version of
> libusb and using that for OE, but that is going slowly.
>
> Building the _svn recipe will apply a patch that lets the fir fff filter
> use NEON instructions. This improves performance a lot. Lot's more code
> needs optimizing for NEON. The current GCC versions do not do a good job of
> generating math code for the armv7.
>
> In summary, if you can find your way around OE a little, it is easy to get
> to where you want to be :) I want to get th 3.2 release in OE, with the
> static libusb so we have a stable gnuradio build that works with the USRP,
> but this is going to take some time (I've got several other things going on
> at the moment, and the libusb issue is holding me up)
>
> I've built and run the dsplink demos using the ti-codec engine recipe in
> OE. The examples run. Unfortunately, the examples are hard to follow in the
> source since the build system is closely coupled with the codec engine build
> system. This makes it tricky to extract a simple example we can base a GNU
> radio block on. I've heard someone is working on a simple example though.
>
> Philip
>
>
>
>
>
>
>> Thank you so much for all your help.
>>
>> Anne
>>
>> ---------- Forwarded message ----------
>> From: Philip Balister <[email protected]>
>> Date: Sat, May 16, 2009 at 11:46 PM
>> Subject: Re: gnuradio and beagleboard
>> To: [email protected]
>>
>>
>> anne kwong wrote:
>>
>> Hi Philip,
>>>
>>> That would be great.  I would like to use Beagle board to obtain AM/FM
>>> signal and play it.
>>>
>>>
>> bitbake gnuradio will produce binaries that run. The USRP binaries do not
>> run because there is a failed attempt to make the usrp work with
>> libusb-compat in there. Basically, I need to remove the patch and disable
>> the usrp build.
>>
>> If you look at the gnuradio_svn recipe, there is an example of using the
>> NEON coprocessor in one of the FIR filters. I have also built the usrp
>> code
>> by using a patch to OE that switched the build to use libusb-0.12. I'll
>> find
>> that patch and post it here.
>>
>>  Btw, are you doing anything to utilize the DSP chip in the beagleboard?
>>
>> You can build the ti-codec-engine recipe in OE (you will need to read the
>> recipe carefully to see how to install all the TI stuff). I have run the
>> dsplink examples. I haven't tried the code engine stuff.
>>
>> Basically, lots of stuff does work, but you need to be pretty motivated to
>> work with it :)
>>
>> Philip
>>
>>
>>  I would love to give it a try whenever your stuff is ready.
>>
>>> Thank you so much.
>>>
>>> Thanks,
>>> Anne
>>>
>>> On Fri, May 15, 2009 at 10:05 PM, Philip Balister <[email protected]>
>>> wrote:
>>>
>>> Anne kwong wrote:
>>>>
>>>> Hi,
>>>>>
>>>>> I am trying to have gnuradio running on beagleboard.  Does anyone know
>>>>> how to do it or is there any how-to or document out there that can
>>>>> guide me a bit?
>>>>>
>>>>> Any suggestion will be greatly appreciated.
>>>>>
>>>>> There is some very basic support in Angstrom/OE. I have some patches
>>>> that
>>>> start to exploit the NEON coprocessor also.
>>>>
>>>> I'll start posting stuff here. I also need to start moving OMAP3 support
>>>> into GNU Radio. I need to work out how to deal with the autofoo first :)
>>>>
>>>> Philip
>>>>
>>>>
>>>>
>>

Reply via email to