For now I'd say there are two main approaches that can be taken for DSP 
development on the omap/davinci ... at least to the best of my knowledge.  
There is the DSPLink approach and the Codec Engine approach.  DSPLink provides 
the barebones mechanisms to enable inter-processor communication, setup, and 
data exchange.  I've steered away from Codec Engine because it seems more 
complicated and because from what I gather it's targeted more for situations 
where you might purchase a codec and only have access to the binary and you 
would need a mechanism to select and run between multiple codecs that might be 
available and for that Codec Engine would provide a framework to handle this 
situation.

If you're taking the DSPLink approach then the following are the set of tools 
you would need:

1- TI Code Generation Tools (CGT) C6000
    the DSP Compiler
2- TI DSPLink
   to handle inter processor communication
3- TI Codec Engine
    even if you're not using it you have install it because of dependency
4- TI DSP/BIOS
    DSP RTOS
5- TI Local Power Manager (LPM)
    The OMAP processor has a bug where you have to reset the DSP if you plan on 
loading different executables and the LPM modules provides an executable to do 
just that

You would need to setup the Makefiles for DSPLink before using it to point it 
to your kernel directory, compile tools, ... etc

al
-----Original Message-----
From: Alexander Chemeris <[email protected]>
To: Philip Balister <[email protected]>
Cc: discuss-gnuradio <[email protected]>
Sent: Fri, May 6, 2011 4:52 pm
Subject: Re: [Discuss-gnuradio] Questions about E100


On Fri, May 6, 2011 at 16:29, Philip Balister <[email protected]> wrote:
 On 05/05/2011 05:42 PM, Scott Johnston wrote:
>
> Hi,
>
> Has anybody out there done any development on the DSP? What tools are
> available to program it? I have used TI's code composer in the past to
> program DSPs, is there something comparable to that included with E100,
> or is it easy to get it? What I would like to be able to do is obtain
> common C libraries and compile C code to run on the DSP.

 You can build an image with dsp support by following the notes at:

 
http://ettus-apps.sourcerepo.com/redmine/ettus/projects/usrpe1xx/wiki/Install_OpenEmbedded

 I'll post a copy of the image next week.

 To run the demos, you'll need to modify the kernel boot args to create a
 memory hole. This is (barely) documented on the interwebs. Next time I
 update u-boot, I'll include an extra variable to make it easier to create
 the memory hole.
On a related question - have anyone tried SysLink on Gumstix/E100?
I'm just getting into this staff and trying to understand what tools
re the best to use for DSP on OMAP/DaVinci/Integra.
-- 
egards,
lexander Chemeris.
_______________________________________________
iscuss-gnuradio mailing list
[email protected]
ttps://lists.gnu.org/mailman/listinfo/discuss-gnuradio

_______________________________________________
Discuss-gnuradio mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio

Reply via email to