We are using the RCE platform to preform readout of Pixel module(s).
Getting accounts, etc.
You need an account on lab1 machines, and access to the NPA area on AFS. Contact:
Mike Huffer <mehsys@slac.stanford.edu>, Amedeo Perazzo <perazzo@slac.stanford.edu>
Some links to more RCE info:
To develop RCE code:
...
- .
...
If you don't already have a release area setup, you need to make one:
Code Block |
---|
cvs co -d <mydir> release
cd <mydir>
cvs co rce
cvs co rceusr
cvs co rceapp
#for example see ~ahaas/myrelease_new
|
Then build:
Code Block |
---|
gmake ppc-rtems-rce405-dbg #builds rce apps
#gmake i386-linux-dbg #if you want to build linux apps
|
To run netbeans:
...
- .
...
- .
...
Import your release area via:
"File->New Project..."
"C/C++ Project From Existing Code"
"Existing Makefile:" enter the "<release directory>/Makefile"
Change "Build Command:" to "gmake ppc-rtems-rce405-dbg"
Next, Next, Finish, then build the project.
To run RCE code:
Code Block |
---|
telnet rce22
root (nopass)
mount -t nfs 172.21.5.150:/nfsexport/home /nfs #got ip address from "mount" on rddev102
cd /nfs/ahaas/myrelease_new/build/rceapp/mod/ppc-rtems-rce405
runtask -N test ./hellomod.1.0.test.so
|
Other handy RCE commands:
Code Block |
---|
task
cpuuse
stackuse
stoptask -N test
syslog
syslog -l 10 #just last ten lines
syslog -c #clear (see myrelease_new/rce/shell/src/syslog.cc)
|
Working on STcontrol / PixLib / unixdaq
Under construction...
To compile/run:
...