On 11 February 2008 17:27, Joel Sherrill wrote:
> Starting with what I know. This is for the SPARC/SIS
> BSP for RTEMS.
>
> To compile:
> sparc-rtems4.9-gcc -B${RTEMSBSP_prefix} \
> -specs bsp_specs -qrtems -g -O2 -mcpu=cypress \
> -c FILE.c
>
> To Link:
> sparc-rtems4.9-gcc -B${RTEMSBSP_prefix} \
> -specs bsp_specs -qrtems -g -mcpu=cypress \
> -o TEST_EXECUTABLE OBJECTS HARNESS.o
>
> To Run:
>
> sis-4.9 TEST_EXECUTABLE
>
> RTEMS programs start with a "Init" thread. So
> we will have build "HARNESS.c" and link with it
> in each test executable.
>
> RTEMS applications do not return the exit status
> to the environment. So it will have to print
> pass/fail based on the exit value. I vaguely
> remember this not being a big deal for DejaGNU.
>
> If I can get one worked out, I can make it happen
> for the others but I can't unravel the magic yet. :(
Basically, you add a new baseboard file in $prefix/share/dejagnu/baseboards,
the example in the docs is a reasonable starting point. The new baseboard
file includes a line somewhere like 'load_generic_config "sim"', which pulls
in all the support routines from $prefix/share/dejagnu/config/sim.exp. These
handle the basic interfacing of the test framework to a locally-run simulator,
and hopefully you shouldn't need to do too much more than tinker with config
variables in the board.exp file.
> + an extra object file to link with.
set_board_info ldflags
> + target CFLAGS and LDFLAGS
set_board_info cflags
set_board_info ldflags
> + command to run simulator
set_board_info sim
So, how far are you at? Have you got a baseboard script written yet? Have
you read the "Extending DejaGnu" chapter of the manual, specifically the
"Adding a new board" section?
cheers,
DaveK
--
Can't think of a witty .sigline today....
_______________________________________________
DejaGnu mailing list
DejaGnu@gnu.org
http://lists.gnu.org/mailman/listinfo/dejagnu
