Difference between revisions of "BeagleBoard/GSoC/2010 Projects/C6Run"

From eLinux.org
Jump to: navigation, search
(Project: RPC layer and POSIX wrappers for C6Run (formerly known as DSPEasy))
(Added to category BeagleBoard and GSOC)
(One intermediate revision by one other user not shown)
Line 36: Line 36:
Since the RPC layer builds on top of the existing C6Run build system, nothing else is necessary for the build.
See the documentation above for more details.

Revision as of 22:27, 12 April 2011

Project: RPC layer and POSIX wrappers for C6Run (formerly known as DSPEasy)

Student: Yaman Umuroglu

Mentors: Katie Roberts-Hoffman, Laine Walker-Avina, Frank Walzer

Documentation: BeagleBoard/GSoC/2010_Projects/C6Run/Documentation

Repository at: http://gforge.ti.com/svn/dspeasy/C6RunApp/branches/dsp-rpc-posix

Blog at: http://maltanar.blogspot.com

Latest blog entries: Extension:RSS -- Error: "http://maltanar.blogspot.com/feeds/posts/default%7Ccharset=UTF-8%7Cmax=3" is not in the whitelist of allowed feeds. http://linuxgizmos.com/feed is the only allowed feed.


The C6Run project offers a suite of tools to make life easier for DSP-side development (targeting the TI C6 series DSPs, including the C64x+ on the BeagleBoard's OMAP3530). Among the offered tools are C6RunApp (which enables the developer to prototype code on the DSP using a simple cross-compilation script and running the resulting executable, with file system/console access) and C6RunLib (wrap DSP-side code into ARM libraries for easy access).

DSP-RPC-POSIX is a component of C6RunApp which allows you to do DSP->GPP remote procedure calls - that is, you can invoke functions/code residing somewhere on the GPP side directly from the DSP as if you were accessing a local function (there are, of course, certain requirements and restrictions).


The project documentation has its own wiki page at BeagleBoard/GSoC/2010_Projects/C6Run/Documentation

Build Instructions

1. Checkout the sources from SVN

2. Change into the sources directory and issue make beagleboard_config

3. Set up dependency paths in the top-level Rules.mak and in platforms/beagleboard/Platform.mak

4. Issue make build

5. That's all! You can simply add the bin directory to your path and start doing things like c6runapp-cc hello_world.c -o hello_world

See the documentation above for more details.