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