The generated binaries

The RTEMS kernel images

Bootable kernel images are created in directory “kernel”. Here are for example the files for RTEMS 4.9 and BSPs (board supports) mvme2100 und mvme5500:

  • rtems-mvme2100.bin

  • rtems-mvme5500.bin

Test programs

If variable “RTEMS_TESTS” in file CONFIG.COMMON is set to “yes”, RTEMS test code will also be built.

Test programs can then be found in directory $RTEMS_TARGET/[BSP]/lib/rtems-$RTEMS_VERSION/tests.

where variables $RTEMS… are defined in files CONFIG.COMMON and CONFIG-RTEMS-NN and “BSP” is the name of the board support package. Here is an example for the simple “hello, world” test for RTEMS 4.9 and the mvme2100 board support:

  • powerpc-rtems4.9/mvme2100/lib/rtems-4.9/tests/hello.exe

Converters for boot images

The kernel boot images can always be loaded directly by the CPU. For the test programs however, this is different.

For the mvme2100 and mvme2500 CPU, these RTEMS test programs cannot be loaded directly. They first have to be converted to a bootable image format. We have the scripts [BSP]-exe2boot.sh for this, where “BSP” is the name of the board support.

For example, to create a bootable image for the “hello world” test, you have to enter this command:

./mvme2100-exe2boot.sh powerpc-rtems4.9/mvme2100/lib/rtems-4.9/tests/hello.exe

The script then generates a bootable image, in this case file “hello.ralf”.