1 | # |
---|
2 | # COPYRIGHT (c) 1989-1999. |
---|
3 | # On-Line Applications Research Corporation (OAR). |
---|
4 | # |
---|
5 | # The license and distribution terms for this file may be |
---|
6 | # found in the file LICENSE in this distribution or at |
---|
7 | # http://www.rtems.org/license/LICENSE. |
---|
8 | |
---|
9 | This directory contains the RTEMS Sample Application Suite. |
---|
10 | The tests in this directory perform two functions: |
---|
11 | |
---|
12 | + provide simple examples of applications which can be |
---|
13 | used as a starting point for your application. |
---|
14 | |
---|
15 | + help test a new board support package |
---|
16 | |
---|
17 | The hello and ticker applications are useful when first bringing up |
---|
18 | a new board support package. The base_mp test is useful when |
---|
19 | performing initial checkout on a new MPCI layer. |
---|
20 | |
---|
21 | The following describes each of the sample applications: |
---|
22 | |
---|
23 | base_mp |
---|
24 | |
---|
25 | This is a very simple two node multiprocessor application. It consists |
---|
26 | of a single initialization task on each node which print out |
---|
27 | their respective node numbers and task IDs. This test can be |
---|
28 | used as a simple test of a new MPCI layer because it minimizes |
---|
29 | the number of packets sent by RTEMS. |
---|
30 | |
---|
31 | This is intended as a starting point for custom developed multiprocessor |
---|
32 | applications. |
---|
33 | |
---|
34 | base_sp |
---|
35 | |
---|
36 | This is a simple single processor application which consists of |
---|
37 | an initialization task which creates another task. |
---|
38 | |
---|
39 | This is intended as a starting point for custom developed single |
---|
40 | processor applications. |
---|
41 | |
---|
42 | capture |
---|
43 | |
---|
44 | This simple application starts the monitor and allows you access |
---|
45 | to the capture engine. The capture engine provides a trace of |
---|
46 | RTEMS activity and is used to debug your application. |
---|
47 | |
---|
48 | cdtest |
---|
49 | |
---|
50 | A very simple C++ application which demonstrates that it is |
---|
51 | possible to use C++ contructors and destructors in an RTEMS |
---|
52 | application. Also does a perfunctory iostream test. |
---|
53 | |
---|
54 | hello |
---|
55 | |
---|
56 | This is the RTEMS version of the classic hello world program. |
---|
57 | It consists of single initialization task which prints out |
---|
58 | a few messages. |
---|
59 | |
---|
60 | This test does not include a Clock Tick device driver and can |
---|
61 | be used to test the startup code of the board support package |
---|
62 | as well as console output. |
---|
63 | |
---|
64 | paranoia |
---|
65 | |
---|
66 | A public domain test of the floating point and math library |
---|
67 | capabilities of a toolset. It reports discrepancies between |
---|
68 | actual and expected results. It is a large test. |
---|
69 | |
---|
70 | ticker |
---|
71 | |
---|
72 | This is a simple test of the user's Clock Tick device driver. |
---|
73 | This test has an initialization task create three application |
---|
74 | tasks which sleep and periodically wake up and print the time. |
---|
75 | |
---|
76 | unlimited |
---|
77 | |
---|
78 | This is a test for the umlimited object feature of RTEMS. Here |
---|
79 | you can configure RTEMS to give as many objects as memory |
---|
80 | in the Workspace. |
---|