The eCos kernel and other packages have test suites which rigorously exercise the available features and confirm correct execution. The tests are run on many different possible configurations — the total number of permutations makes it impossible to test them all. The use of test suites is particularly important for embedded systems, where software robustness is a priority. All eCos software is tested prior to shipping, but if you define your own configuration, you will probably want to verify that the test cases work for it.
This release includes test suites for the eCos kernel, kernel C API, C library, µITRON compatibility, and device driver packages. The use of the test suites is similar for all packages. The tests are supplied both as prebuilt images (if you have the CD distribution of the eCos Developer's Kit) and as source code for building with specific eCos configurations.
Each test suite consists of a number of test cases which must be executed individually by following these steps:
Compile and link the test cases with the appropriately configured eCos packages, using the Configuration Tool's Build menu and choosing the Tests item, or by typing make tests (further details in Chapter 14).
Start GDB.
Set up the baud rate, usually with (gdb) set remotebaud 38400.
Select the target board, usually with (gdb) target remote com1 on Windows or (gdb) target remote ttyS0 on Linux.
Download the test program, usually with (gdb) load. This can take some time.
Execute the test program, usually with (gdb) continue.
Each test case runs without further intervention. A test case may involve one or more individual tests. Successful completion of each test within the test case is reported as a line of text which is sent to the diagnostic channel (usually the serial port) for display on a terminal or terminal emulator.
Each test case runs only once and usually requires the target hardware to be reset on completion. Note that certain test cases may not terminate immediately, especially if they involve delays and run on the target simulators.
In the CD distribution of the eCos Developer's Kit, the test cases are located in the following directories:
one prebuilt test compiled for RAM startup (needs CygMon, and will only run on real hardware): BASE_DIR/prebuilt/v1_1/mn10300-stdeval-ram for the MN10300, BASE_DIR/prebuilt/v1_1/tx39-jmr3904-ram for the TX39, and BASE_DIR/prebuilt/v1_1/powerpccogent-ram for the PowerPC.
one prebuilt test compiled for ROM startup (will work in real hardware and in the simulator): BASE_DIR/prebuilt/v1_1/mn10300-stdeval-rom for the MN10300, BASE_DIR/prebuilt/v1_1/tx39-jmr3904-rom for the TX39, and BASE_DIR/prebuilt/v1_1/powerpc-cogent-rom for the PowerPC.
Note: The PowerPC ROM test does not work with the PowerPC simulator, but it does work with a PROM emulator.
test case source code is under the base source directory BASE_DIR/packages/:
compat/uitron/v1_1/tests
devs/serial/rs232/common/v1_1/tests
devs/serial/rs232/mn10300/v1_1/tests (for the MN10300)
devs/serial/rs232/tx39/v1_1/tests (for the TX39)
devs/wallclock/v1_1/tests
devs/watchdog/v1_1/tests
kernel/v1_1/tests
language/c/libc/v1_1/tests
language/c/libm/v1_1/tests
In the section called Verification in Chapter 12 you will find detailed instructions on running a test case to verify that your hardware board is working with the supplied software.