From 2af46634a33fcd9aa89444f7279e80bdd86f862e Mon Sep 17 00:00:00 2001 From: Ralf Corsepius Date: Sat, 31 Jul 2004 03:27:44 +0000 Subject: 2004-07-31 Ralf Corsepius * FAQ/basic.texi, FAQ/bsp.texi, FAQ/build45.texi, FAQ/concepts.texi, FAQ/debug.texi, FAQ/endoftime.texi, FAQ/freesw.texi, FAQ/hwdebugaids.texi, FAQ/projects.texi, FAQ/tools.texi, FAQ/version.texi: New. --- doc/FAQ/basic.texi | 268 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 268 insertions(+) create mode 100644 doc/FAQ/basic.texi (limited to 'doc/FAQ/basic.texi') diff --git a/doc/FAQ/basic.texi b/doc/FAQ/basic.texi new file mode 100644 index 0000000000..205c8f18f5 --- /dev/null +++ b/doc/FAQ/basic.texi @@ -0,0 +1,268 @@ +@c +@c COPYRIGHT (c) 1988-2002. +@c On-Line Applications Research Corporation (OAR). +@c All rights reserved. +@c +@c $Id$ +@c + + +@node Basic Information, What does RTEMS stand for?, Top, Top + +@chapter Basic Information +@ifinfo +@menu +* What does RTEMS stand for?:: +* What is RTEMS?:: +* What standards does RTEMS support?:: +* What processors is RTEMS available for?:: +* Executive vs. Kernel vs. Operating System (RTOS):: +* Where/why was it developed?:: +* Are there no similar commercial products?:: +* How can I get RTEMS?:: +* What about support?:: +* Are there any mailing lists?:: +* Are there any license restrictions?:: +* Are there any export restrictions?:: +@end menu +@end ifinfo + +The questions in this category are basic questions about RTEMS. Where +did it come from, why is it, what is it, when should you use it, etc.? + + +@node What does RTEMS stand for?, What is RTEMS?, Basic Information, Basic Information + +@section What does RTEMS stand for? + +RTEMS is an an acronym for the Real-Time Executive for Multiprocessor +Systems. + +Initially RTEMS stood for the Real-Time Executive for Missile Systems +but as it became clear that the application domains that could use +RTEMS extended far beyond missiles, the "M" changed to mean Military. +At one point, there were both Ada and C implementations of RTEMS. The +C version changed the "M" to mean Multiprocessor while the Ada version +remained with the "M" meaning Military. + + +@node What is RTEMS?, What standards does RTEMS support?, What does RTEMS stand for?, Basic Information + +@section What is RTEMS? + +RTEMS is a real-time executive which provides a high performance +environment for embedded military applications including many +features. The following is just a short list of the features +available in RTEMS. If you are interested in something that +is not on this list, please contact the RTEMS Team. Features +are being added continuously. + +@itemize @bullet + +@item Standards Compliant +@itemize @bullet +@item POSIX 1003.1b API including threads +@item RTEID/ORKID based Classic API +@end itemize + +@item TCP/IP Stack +@itemize @bullet +@item high performance port of FreeBSD TCP/IP stack +@item UDP, TCP +@item ICMP, DHCP, RARP +@item TFTP +@item RPC +@item FTPD +@item HTTPD +@item CORBA +@end itemize + +@item Debugging +@itemize @bullet +@item GNU debugger (gdb) +@item DDD GUI interface to GDB +@item thread aware +@item debug over Ethernet +@item debug over Serial Port +@end itemize + +@item Filesystem Support +@itemize @bullet +@item In-Memory Filesystem (IMFS) +@item TFTP Client Filesystem +@end itemize + +@item Basic Kernel Features +@itemize @bullet +@item multitasking capabilities +@item homogeneous and heterogeneous multiprocessor systems +@item event-driven, priority-based, preemptive scheduling +@item optional rate monotonic scheduling +@item intertask communication and synchronization +@item priority inheritance +@item responsive interrupt management +@item dynamic memory allocation +@item high level of user configurability +@end itemize + +@end itemize + + + +@node What standards does RTEMS support?, What processors is RTEMS available for?, What is RTEMS?, Basic Information + +@section What standards does RTEMS support? + +The original "Classic" RTEMS API is based on the Real-Time Executive +Interface Definition (RTEID) and the Open Real-Time Kernel Interface +Definition (ORKID). RTEMS also includes support for POSIX threads +and real-time extensions. + +With the addition of file system infrastructure, RTEMS supports +about 70% of the POSIX 1003.1b-1996 standard. This standard +defines the programming interfaces of standard UNIX. This means +that much source code that works on UNIX, also works on RTEMS. + + +@node What processors is RTEMS available for?, Executive vs. Kernel vs. Operating System (RTOS), What standards does RTEMS support?, Basic Information + +@section What processors is RTEMS available for? + +RTEMS is available for the following processor families: + +@itemize @bullet +@item Motorola MC68xxx +@item Motorola MC683xx +@item Motorola ColdFire +@item ARM +@item Hitachi H8/300 +@item Hitachi SH +@item Intel i386 +@item Intel i960 +@item MIPS +@item PowerPC +@item SPARC +@item Texas Instruments C3x/C4x +@item OpenCores OR32 +@end itemize + +In addition, there is a port to UNIX which can be used as a prototyping +and simulation environment. + + +@node Executive vs. Kernel vs. Operating System (RTOS), Where/why was it developed?, What processors is RTEMS available for?, Basic Information + +@section Executive vs. Kernel vs. Operating System (RTOS) + +The developers of RTEMS developers use the terms executive and kernel +interchangeably. In the embedded system community, the terms executive +or kernel are generally used to refer to small operating systems. +So we consider it proper to refer to RTEMS as an executive, a kernel, +or an operating system. + + +@node Where/why was it developed?, Are there no similar commercial products?, Executive vs. Kernel vs. Operating System (RTOS), Basic Information + +@section Where/why was it developed? + +RTEMS was developed by On-Line Applications Research Corporation (OAR) +for the U.S. Army Missile Command prior to that organizations merger +with the Aviation Command that resulted in the new command, U. S. Army +Aviation and Missile command (AMCOM). The original goal of RTEMS was +to provide a portable, standards-based real-time executive for which +source code was available and royalties were paid. + +In other words, RTEMS was open source before open source was cool. + +Since the initial release to the world, the RTEMS Community has +grown enormously and contributed significantly to RTEMS. Important +additions such as the TCP/IP stack, FAT filesystem, multiple ports, +device drivers, and most BSPs have come from users like yourself. + + +@node Are there no similar commercial products?, How can I get RTEMS?, Where/why was it developed?, Basic Information + +@section Are there no similar commercial products? + +Yes, but not all are based on standards and the open source philosophy. + + +@node How can I get RTEMS?, What about support?, Are there no similar commercial products?, Basic Information + +@section How can I get RTEMS? + +RTEMS is distributed from @uref{@value{RTEMSHTTPURL},@value{RTEMSHTTPURL}}. +This is a server dedicated to the RTEMS Project which was donated by and +hosted by @uref{http://www.oarcorp.com,OAR Corporation} to provide +a focal point for all RTEMS activities. Point your +favorite browser at the following URL and following the link: + +@uref{@value{RTEMSHTTPURL},@value{RTEMSHTTPURL}} + +But if you are already reading this, you probably already found it. :) + + +@node What about support?, Are there any mailing lists?, How can I get RTEMS?, Basic Information + +@section What about support? + +RTEMS development and support services are available from a number +of firms. See +@uref{@value{RTEMSHTTPURL}/support.html,@value{RTEMSHTTPURL}/support.html} +for the current list of RTEMS service providers. + +Remember that RTEMS maintenance is funded by users. If you are +using RTEMS on a commercial project, please get support. + + +@node Are there any mailing lists?, Are there any license restrictions?, What about support?, Basic Information + +@section Are there any mailing lists? + +The primary RTEMS mailing list is @code{@value{RTEMSUSERS}}. This +list is for general RTEMS discussions, questions, design help, advice, +etc.. Subscribe by sending an empty mail +message to @code{@value{RTEMSUSERSSUBSCRIBE}}. This +mailing list is archived at: + +@example +http://www.rtems.com/ml/rtems-users +@end example + +The @code{@value{RTEMSSNAPSHOTS}} mailing list is for those +interested in taking a more active role in the design, development, +and maintenance of RTEMS. Discussions on this list tend to focus +on problems in the development source, design of new features, problem +reports, etc.. Subscribe by sending an empty mail +message to @code{@value{RTEMSSNAPSHOTSSUBSCRIBE}}. +mailing list is archived at: + +@example +http://www.rtems.com/ml/rtems-snapshots +@end example + +The archives for both mailing lists include discussions back +to 1997. + + +@node Are there any license restrictions?, Are there any export restrictions?, Are there any mailing lists?, Basic Information + +@section Are there any license restrictions? + +RTEMS is licensed under a modified version of the GNU General Public License +(GPL). The modification places no restrictions on the applications which +use RTEMS but protects the interests of those who work on RTEMS. + +The TCP/IP network stack included with RTEMS is a port of the FreeBSD +network stack and is licensed under different terms that also do not +place restrictions on the application. + + +@node Are there any export restrictions?, , Are there any license restrictions?, Basic Information + +@section Are there any export restrictions? + +No. + + + -- cgit v1.2.3