Quote:
Originally Posted by AustinSchuh
I guess you could compile your own cross compiler, but that sounds like a lot of unnecessary work and that could introduce problems in the output executable.
|
I think I did it. After installing the latest WindRiver update
on Windows, copy the entire C:\WindRiver\vxworks-6.3\target\ directory to your Ubuntu box, and put it in a directory that we'll use for the build files (~/frc/ or similar works just fine).
On your Ubuntu box,
cd to the directory you just made for the build files, then run these commands in order:
http://pastie.org/352039 (you can change
$PREFIX to change the install directory). Those instructions should be accurate for building
gcc to cross-compile to Ubuntu. Included is a patchfile for what seems to be a fix to be a small problem with the
libgcov code.
When you finish, you should have a complete cross-compiler suite in
/usr/local/powerpc-wrs-vxworks, complete with binaries, headers, and static libraries.
PLEASE tell me if you find any errors with what I've written up. (P.S. Whenever you use this compiler, you should need to have
$WIND_BASE and
$WIND_USR set; also required is a preprocessor flag
_WRS_KERNEL which you can specify on the gcc command line using the argument
-D_WRS_KERNEL.)
Now that the compiler works (well, for me, at least), it seems like it's time to try to get the
SimpleRobot kernel-module example code template to compile using this compiler. Right now I'm getting problems with case sensitivity and load path order. Can someone try to get that working? My Makefile attempt is at
http://gist.github.com/43030.
My final concern is how to upload an application to the cRIO into the RAM (not saving into flash memory). Seems like FTP is only for using the flash memory, but for code debugging, RAM is much less dangerous. Anyone figure out how to do this? Maybe we need to reverse-engineer the communications between Workbench and the cRIO.