Still stuck on the basics
Neal Tanner
tanner at stanford.edu
Thu Jan 29 02:15:45 CET 2004
1) When I run the examples under /usr/realtime/testsuite/user they
generate output telling me to use Ctrl-C to exit (preempt even
starts scrolling data) but when I press Ctrl-C, the entire machine
locks up. Do I have something configured wrong in rtai? Any
ideas?
2) I am still a little confused on what modules I do or do not need
and how they correspond to the 24.1.x modules that I have been
using. Here are the modules that I used to use and my best
guesses. Are there other modules that I will need as well? Any
clarifications would be appreciated.
rtai --> adeos & rtai_hal ???
rtai_sched --> rtai_up
rtai_shm --> rtai_shm
rtai_utils --> ???
rtai_fifos --> rtai_fifos
rtai_libm --> rtai_math
3) I am trying to go back and get my existing code running with
rtai-3.0. I made sure that the option for backwards compatibility
was enabled in the configuration menu, but "nam2num" is generating
implicit declaration warnings and unresolved symbol errors. I
think that I pulled my usage (shown below) of rtai_kmalloc
straight out of the 24.1.x programming guide. Is "nam2num" part
of rtai or have I screwed up something seperate?
state = rtai_kmalloc(nam2num(MODULE_SHMNAME), sizeof(struct
module_state));
4) I got started on this whole project because we are upgrading the
machines in our lab to Redhat 9 and I since I was going to have to
reinstall rtai, I figured the newest version would be a good idea.
Is it? Currently, we use a very small subset of the capabilities
of rtai (mainly executing a couple of servo loops at a few
kilohertz and moving some data through shared memory for display
purposes). Are we better off going back to 24.1.x since we know
how to use it (at least somewhat)? Does anyone have a feel for if
I'm anywhere close to having this working yet?
Sorry for the long barrage of questions this time around, but thanks
so much for any help you can be.
neal
More information about the Rtai
mailing list