1 | @c |
---|
2 | @c COPYRIGHT (c) 1988-1998. |
---|
3 | @c On-Line Applications Research Corporation (OAR). |
---|
4 | @c All rights reserved. |
---|
5 | @c |
---|
6 | @c $Id$ |
---|
7 | @c |
---|
8 | |
---|
9 | @ifinfo |
---|
10 | @node Development Environment Status, Development Environment Status RTEMS Executive Status, Installation Procedure Installing RTEMS, Top |
---|
11 | @end ifinfo |
---|
12 | @chapter Development Environment Status |
---|
13 | @ifinfo |
---|
14 | @menu |
---|
15 | * Development Environment Status RTEMS Executive Status:: |
---|
16 | * Development Environment Status Development Environment Status:: |
---|
17 | * Development Environment Status Known Problems:: |
---|
18 | @end menu |
---|
19 | @end ifinfo |
---|
20 | |
---|
21 | This chapter will describe the current status of |
---|
22 | release version @value{RELEASE} of the RTEMS Development Environment. |
---|
23 | |
---|
24 | @ifinfo |
---|
25 | @node Development Environment Status RTEMS Executive Status, Development Environment Status Development Environment Status, Development Environment Status, Development Environment Status |
---|
26 | @end ifinfo |
---|
27 | @section RTEMS Executive Status |
---|
28 | |
---|
29 | Release @value{RELEASE} of the RTEMS Executive contains support |
---|
30 | for both the classic RTEMS API based on the RTEID specification as well |
---|
31 | as support for POSIX threads and real-time extensions. |
---|
32 | |
---|
33 | The classic RTEMS API has the following managers based upon the RTEID |
---|
34 | specification: |
---|
35 | |
---|
36 | @itemize @bullet |
---|
37 | @item Task |
---|
38 | @item Initialization |
---|
39 | @item Clock |
---|
40 | @item Timer |
---|
41 | @item Interrupt |
---|
42 | @item Fatal Error |
---|
43 | @item Message |
---|
44 | @item Semaphore |
---|
45 | @item Event |
---|
46 | @item Signal |
---|
47 | @item Region |
---|
48 | @item Partition |
---|
49 | @item Dual Ported Memory |
---|
50 | @item I/O |
---|
51 | @item Multiprocessing |
---|
52 | @item Rate Monotonic |
---|
53 | @item User Extensions |
---|
54 | @end itemize |
---|
55 | |
---|
56 | RTEMS also has support for the following managers based upon the POSIX threads |
---|
57 | and real-time extensions: |
---|
58 | |
---|
59 | @itemize @bullet |
---|
60 | @item Thread |
---|
61 | @item Clock |
---|
62 | @item Key |
---|
63 | @item Condition Variable |
---|
64 | @item Mutex |
---|
65 | @item Signal |
---|
66 | @item Scheduler |
---|
67 | @end itemize |
---|
68 | |
---|
69 | This release of the C implementation supports the |
---|
70 | following processors and target boards: |
---|
71 | |
---|
72 | @itemize @bullet |
---|
73 | @item Motorola M68k family |
---|
74 | @itemize - |
---|
75 | @item DY-4 DMV152, SVME153 |
---|
76 | @item Motorola IDP |
---|
77 | @item Motorola MVME135, MVME136 |
---|
78 | @item Motorola MVME147, MVME147S |
---|
79 | @item Motorola MVME162 |
---|
80 | @item EFI 68000 and 68332 |
---|
81 | @item Generic 68302 |
---|
82 | @item Generic 68360 and 68360 in companion mode with 68040 |
---|
83 | @end itemize |
---|
84 | |
---|
85 | @item Intel i386 family |
---|
86 | @itemize - |
---|
87 | @item Force CPU386 |
---|
88 | @item Intel i386ex eval board |
---|
89 | @item PC-AT i386 and above (go32) |
---|
90 | @end itemize |
---|
91 | |
---|
92 | @item Intel i960 family |
---|
93 | @itemize - |
---|
94 | @item Cyclone CVME960, CVME961 |
---|
95 | @end itemize |
---|
96 | |
---|
97 | @item Hewlett Packard PA-RISC family |
---|
98 | @itemize - |
---|
99 | @item Processor Simulator |
---|
100 | @end itemize |
---|
101 | |
---|
102 | @item PowerPC |
---|
103 | @itemize - |
---|
104 | @item Papyrus (proprietary controller) |
---|
105 | @end itemize |
---|
106 | |
---|
107 | @item SPARC |
---|
108 | @itemize - |
---|
109 | @item ERC32 (space-hardened V7) |
---|
110 | @end itemize |
---|
111 | |
---|
112 | @item MIPS |
---|
113 | @itemize - |
---|
114 | @item P4000 with R4600 or R4650 |
---|
115 | @end itemize |
---|
116 | |
---|
117 | @item AMD 29K |
---|
118 | @itemize - |
---|
119 | @item Portsw |
---|
120 | @end itemize |
---|
121 | |
---|
122 | @item UNIX |
---|
123 | @itemize - |
---|
124 | @item Hewlett Packard HPUX (PA-RISC) |
---|
125 | @item Sun Solaris 2.x (SPARC) |
---|
126 | @item Linux (i386) |
---|
127 | @end itemize |
---|
128 | |
---|
129 | @end itemize |
---|
130 | |
---|
131 | Support for the Cygnus NEWLIB Standard C Library is |
---|
132 | provided with this release which may be used on any of the RTEMS |
---|
133 | supported targets. The BSPs only provide support for console |
---|
134 | I/O only using this library. Support for the reentrancy |
---|
135 | capabilities of newlib is provided in the RTEMS distribution. |
---|
136 | |
---|
137 | @ifinfo |
---|
138 | @node Development Environment Status Development Environment Status, Development Environment Status Known Problems, Development Environment Status RTEMS Executive Status, Development Environment Status |
---|
139 | @end ifinfo |
---|
140 | @section Development Environment Status |
---|
141 | |
---|
142 | This section details the versions of the tools used |
---|
143 | to develop and maintain RTEMS @value{RELEASE}: |
---|
144 | |
---|
145 | @itemize @bullet |
---|
146 | @item Cross Tools |
---|
147 | @itemize - |
---|
148 | @item gcc - 2.7.2.2 with rtems patch |
---|
149 | @item binutils - 2.7 with rtems patch |
---|
150 | @item zip - 1.2.4 |
---|
151 | @item make - 3.74 |
---|
152 | @end itemize |
---|
153 | @end itemize |
---|
154 | |
---|
155 | |
---|
156 | @ifinfo |
---|
157 | @node Development Environment Status Known Problems, Executive Problems, Development Environment Status Development Environment Status, Development Environment Status |
---|
158 | @end ifinfo |
---|
159 | @section Known Problems |
---|
160 | @ifinfo |
---|
161 | @menu |
---|
162 | * Executive Problems:: |
---|
163 | * Development Environment Problems:: |
---|
164 | * RTEMS Problem Reporting:: |
---|
165 | @end menu |
---|
166 | @end ifinfo |
---|
167 | |
---|
168 | Problems which are known to exist at the time of |
---|
169 | release are described in the following sections. These are |
---|
170 | provided as warnings to the user and where possible, workarounds |
---|
171 | are provided until the problem is corrected. |
---|
172 | |
---|
173 | @ifinfo |
---|
174 | @node Executive Problems, Development Environment Problems, Development Environment Status Known Problems, Development Environment Status Known Problems |
---|
175 | @end ifinfo |
---|
176 | @subsection Executive Problems |
---|
177 | |
---|
178 | There are no known bugs in the executive itself. |
---|
179 | |
---|
180 | @ifinfo |
---|
181 | @node Development Environment Problems, RTEMS Problem Reporting, Executive Problems, Development Environment Status Known Problems |
---|
182 | @end ifinfo |
---|
183 | @subsection Development Environment Problems |
---|
184 | |
---|
185 | There are no known major problems with the |
---|
186 | development environment. |
---|
187 | |
---|
188 | @ifinfo |
---|
189 | @node RTEMS Problem Reporting, RTEMS PROBLEM REPORT, Development Environment Problems, Development Environment Status Known Problems |
---|
190 | @end ifinfo |
---|
191 | @subsection RTEMS Problem Reporting |
---|
192 | |
---|
193 | A problem report is provided at the end of this |
---|
194 | document and may be copied by the RTEMS user. Please fill out |
---|
195 | the form completely to assure a speedy response to the problem. |
---|
196 | In filling out the problem report the following instructions |
---|
197 | apply: |
---|
198 | |
---|
199 | @table @code |
---|
200 | @item User Name and Address: |
---|
201 | The full name |
---|
202 | and mailing address of the customer or company where |
---|
203 | correspondence from RTEMS support personnel may be shipped. |
---|
204 | |
---|
205 | @item Contact Name: |
---|
206 | The name of the person with whom |
---|
207 | RTEMS support personnel will correspond with concerning the |
---|
208 | reported problem. |
---|
209 | |
---|
210 | @item Telephone Voice/FAX: |
---|
211 | The telephone numbers which |
---|
212 | will enable RTEMS support personnel to reach the designated |
---|
213 | contact name. |
---|
214 | |
---|
215 | @item Product/Version: |
---|
216 | The RTEMS product and the version that is currently in use. |
---|
217 | |
---|
218 | @item Target Processor/System: |
---|
219 | The processor and board type that is the target. |
---|
220 | |
---|
221 | @item Host Computer System: |
---|
222 | The manufacturer and model |
---|
223 | number of the system on which RTEMS has been installed. |
---|
224 | |
---|
225 | @item Host Operating System/Version: |
---|
226 | The operating system and version under which RTEMS has been installed. |
---|
227 | |
---|
228 | @c @item Report Type: |
---|
229 | @c Check the most appropriate description of the reported problem. |
---|
230 | |
---|
231 | @item Customer Impact: |
---|
232 | Indicate the severity of the impact of the reported problem. |
---|
233 | |
---|
234 | @item Detailed Description: |
---|
235 | A written description of the |
---|
236 | problem including the area of the RTEMS development environment |
---|
237 | where the problem is located and its behavior. Please feel free |
---|
238 | to provide source code listings, makefiles, possible solutions, |
---|
239 | and any other information describing the problem. This |
---|
240 | additional information may be submitted via email or anonymous |
---|
241 | ftp. |
---|
242 | |
---|
243 | Support, training, ports, and custom development are provided |
---|
244 | by On-Line Applications Research Corporation (OAR). Correspondence |
---|
245 | regarding any aspect of RTEMS should be addressed as follows |
---|
246 | (magnetic tapes should be marked: DO NOT X-RAY): |
---|
247 | @end table |
---|
248 | |
---|
249 | @example |
---|
250 | @group |
---|
251 | RTEMS |
---|
252 | On-Line Applications Research Corporation |
---|
253 | 4910-L Corporate Drive |
---|
254 | Huntsville, AL 35805 |
---|
255 | Voice: (205) 722-9985 |
---|
256 | FAX: (205) 722-0985 |
---|
257 | EMAIL: rtems@@OARcorp.com |
---|
258 | @end group |
---|
259 | @end example |
---|
260 | |
---|