Mark, Like you, I also had to scour the internet for information on installing DSPLink. In hindsight, the DSPLink User Guide is probably the resource I should have started with and used the most. I also found pixhawk's guides to be fairly helpful even though there may be some broken information. I should really list pixhawk.ethz.ch as a resource in the wiki.
Therefore, the wiki is a collection of information I have found in order to install DSPLink on a Beagle. I imagine that the process to install would be fairly similar to other comparable embedded platforms such as the Overo. About the cross compilers, I don't use the ARM Toolchain for that purpose. I do in fact use the cross compilers from OpenEmbedded build. The only reason I linked to CodeSourcery was for the line in the DSPLink make file that states: OSINC_TARGET := $(BASE_TOOLCHAIN)/arm-none-linux-gnueabi/libc/usr/include I couldn't find anything in the OpenEmbedded directory that had similar contents to this folder in CodeSourcery's toolchain. Other than this folder, nothing else in the build process uses files from CodeSourcery. Does anyone know of a comparable folder that could be used so I can remove CodeSourcery altogether from the wiki. Thanks, Ravi On Wed, Jul 8, 2009 at 9:19 AM, Mark Porter <markporter...@gmail.com> wrote: > Hi Ravi, > > First let me thank you for writing a procedure to get DSPLink running on > the Beagle. To install DSPLink on my Beagle I followed instructions from all > over the place, but mostly from the pixhawk tutorial at > > http://www.pixhawk.ethz.ch/wiki/tutorials/omap/dsplink > > but they now claim it is broken. I think it is better to use the toolchain > that comes with oe (situated in $OE_HOME/tmp/cross), since people claim on > the Beagleboard group that CodeSourcery is broken. > > Anyways, I have gotten DSPLink to work on the Beagle by installing the > proper environment on my development host and compiling the two sides of > each example (DSP and GPP) and running them. It is not easy to get started > but I think once you have that setup, it becomes rather trivial to modify > the examples they have given (one for each essential DSP-GPP link function > IIRC). > > It is strange that DSPLink for the Beagle is not documented more than it > is. I think it has to do with the fact that a lot of people using DSP on the > Beagle only need it for audio/video, therefore the codec engine approach > works better for them I guess and they document it as such. For custom > applications like SDR I think the better way is DSPLink. > > Cheers, > > Mark > > On Tue, Jul 7, 2009 at 12:19 PM, Ravi Mehra <ravish...@gmail.com> wrote: > >> Hi João, >> >> I am also pretty new to this list. Thanks for the information and the >> links. I did look into DSP Bridge earlier and was having trouble following >> some outdated instructions so I moved onto DSPLink. From my experience, I >> do not know enough about the two to tell you which is better. DSP Bridge >> looks like a viable solution and I found this site to describe some >> differences. >> http://elinux.org/BeagleBoard/DSP_Clarification >> >> Just for clarification though, the instructions on the wiki do not use the >> Codec Engine at all. The DSP and GPP applications run natively and do not >> require the Codec Engine. >> >> I'd also be interested if someone has some thoughts on the pros/cons of >> DSPLink and DSP Bridge. >> >> Ravi Mehra >> >> >> 2009/7/6 João Felipe Santos <joao....@gmail.com> >> >> Hello, I'm new on this list! My name is João Felipe and I am also >>> working with the Beagleboard for SDR applications. >>> >>> We are using another method to run code on the DSP. We use the >>> dspbridge module on Linux and libdspbridge to make GPP applications >>> communicate with the DSP. This method is described here [1] (the >>> "simplified" method). I wonder if anybody here used this method and >>> has comments or pros/cons on using it. For me, it looked easier than >>> having to adapt your DSP application to CodecEngine. A dummy >>> application is available here [2]. >>> >>> [1] http://elinux.org/BeagleBoard/DSP_Howto#Simplified >>> [2] http://github.com/felipec/dsp-dummy/tree/master >>> >>> -- João >>> >>> On Mon, Jul 6, 2009 at 6:51 PM, Ravi Mehra<ravi...@vt.edu> wrote: >>> > Srujan and I at MPRG have made some headway with using the DSP on the >>> > BeagleBoard. The two predominant methods of using the DSP is either >>> > bitbaking Codec Engine which will install DSPLink or to install DSPLink >>> from >>> > source. The codec engine installation includes video and audio >>> processing >>> > applications which are not needed for SDR work. Additionally, the >>> codec >>> > engine does not provide the tools needed to compile user applications. >>> > Therefore, installing DSPLink from source is the most efficient method. >>> > >>> > I have created a wiki which may be useful to anyone who wants to get >>> started >>> > using the DSP. The wiki shows how to install DSPLink, run it, and run >>> some >>> > sample applications. Once finished, the host system will have all the >>> tools >>> > necessary to compile your own GPP/DSP applications. >>> > >>> > http://ossie.wireless.vt.edu/trac/wiki/BeagleBoard_DSPLink >>> > >>> > Please contact me if you have any questions or comments on the wiki. >>> > >>> > Ravi Mehra >>> > >>> >> >> > > > -- > Mark >
