RTEMS 4.7.2 On-Line Library

Sample Applications Introduction

RTEMS Development Environment Guide

3.1: Introduction

The RTEMS source distribution includes a set of sample applications that are located in the ${RTEMS_ROOT}/testsuites/samples/ directory. These applications are intended to illustrate the basic format of RTEMS single and multiple processor applications and the use of some features. In addition, these relatively simple applications can be used to test locally developed board support packages and device drivers as they exercise a critical subset of RTEMS functionality that is often broken in new BSPs.

Some of the following sample applications will be covered in more detail in subsequent sections:

Hello World: The RTEMS Hello World test is provided in the subdirectory ${RTEMS_ROOT}/testsuites/samples/hello/. This test is helpful when testing new RTEMS development environment.
Clock Tick: The ${RTEMS_ROOT}/testsuites/samples/ticker/ subdirectory provides a test for verification of clock chip device drivers of BSPs.
Base Single Processor: A simple single processor test similar to those in the single processor test suite is provided in ${RTEMS_ROOT}/testsuites/samples/base_sp/.
Base Multiple Processor: A simple two node multiprocessor test capable of testing an newly developed MPCI layer is provided in ${RTEMS_ROOT}/testsuites/samples/base_mp/.
Constructor/Destructor C++ Test: The ${RTEMS_ROOT}/testsuites/samples/cdtest/ subdirectory provides a simple C++ application using constructors and destructors. It is only built when C++ is enabled and its primary purpose is to demonstrate that global constructors and destructors work. Since this requires that the linker script for your BSP be correct, this is an important test.
File IO: The RTEMS File IO test is provided in the subdirectory ${RTEMS_ROOT}/testsuites/samples/fileio/. This is an interactive test which allows the user to interact with an ATA/IDE device. It will read the partition table and allow the user to dynamically mount one of the FAT32 partitions it finds. Commands are also provided to write and read files on the disk.
IO Stream: The RTEMS IO Stream test is provided in the subdirectory ${RTEMS_ROOT}/testsuites/samples/iostream/. This test is a simple C++ application which demonstrates that C++ iostreams are functional. This requires that the RTEMS C++ run-time support is functioning properly. This test is only build when C++ is enabled.
Network Loopback Test: The ${RTEMS_ROOT}/testsuites/samples/loopback/ directory contains a sample test that demonstrates the use of sockets and the loopback network device. It does not require the presence of network hardware in order to run. It is only built if RTEMS was configured with networking enabled.
Minimum Size Test: The directory ${RTEMS_ROOT}/testsuites/samples/minimum/ contains a simple RTEMS program that results in a non-functional executable. It is intended to show the size of a minimum footprint application based upon the current RTEMS configuration.
Paranoia Floating Point Test: The directory ${RTEMS_ROOT}/testsuites/samples/paranoia/ contains the public domain floating point and math library test.
Point-to-Point Protocol Daemon: The RTEMS Point-to-Point Protocol Daemon test is provided in the subdirectory ${RTEMS_ROOT}/testsuites/samples/pppd/. This test primarily serves as the baseline for a user application using the PPP protocol.
Unlimited Object Allocation: The ${RTEMS_ROOT}/testsuites/samples/unlimited/ directory contains a sample test that demonstrates the use of the unlimited object allocation configuration option to RTEMS.

The sample tests are written using the Classic API so the reader should be familiar with the terms used and material presented in the RTEMS Applications Users Guide.

RTEMS Development Environment Guide