Changeset adee5979 in rtems


Ignore:
Timestamp:
May 4, 2000, 7:45:17 PM (21 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
104a48d
Parents:
223b64f
Message:

Numerous changes based on comments from Stephan Wilms <Stephan.Wilms@…>
including a new section in the Getting Started called "Where to
Go From Here", lots of index entries added, and more configuration
table information.

Location:
doc
Files:
31 edited

Legend:

Unmodified
Added
Removed
  • doc/FAQ/debug.t

    r223b64f radee5979  
    1010
    1111The questions in this category are hints that can ease debugging.
     12
     13@section Executable Size
     14
     15@subsection Why is my executable so big?
     16
     17There are two primary causes for this.  The most common is that
     18you are doing an @code{ls -l} and looking at the actual file
     19size -- not the size of the code in the target image.  This
     20file could be in an object format such as ELF or COFF and
     21contain debug information.  If this is the case, it could
     22be an order of magnitude larger than the required code space.
     23Use the strip command in your cross toolset to remove debugging
     24information.
     25
     26The following example was done using the i386-rtems cross toolset
     27and the pc386 BSP.  Notice that with symbolic information included
     28the file @code{hello.exe} is almost a megabyte and would barely fit
     29on a boot floppy.  But there is actually only about 93K of code
     30and initialized data.  The other 800K is symbolic information
     31which is not required to execute the application.
     32
     33@example
     34$ ls -l hello.exe
     35-rwxrwxr-x    1 joel     users      930515 May  2 09:50 hello.exe
     36$ i386-rtems-size hello.exe
     37   text    data     bss     dec     hex filename
     38  88605    3591   11980  104176   196f0 hello.exe
     39$ i386-rtems-strip hello.exe
     40$ ls -l hello.exe
     41-rwxrwxr-x    1 joel     users      106732 May  2 10:02 hello.exe
     42$ i386-rtems-size hello.exe
     43   text    data     bss     dec     hex filename
     44  88605    3591   11980  104176   196f0 hello.exe
     45@end example
     46
     47Another alternative is that the executable file is in an ASCII
     48format such as Motorola Srecords.  In this case, there is
     49no debug information in the file but each byte in the target
     50image requires two bytes to represent.  On top of that, there
     51is some overhead required to specify the addresses where the image
     52is to be placed in target memory as well as checksum information.
     53In this case, it is not uncommon to see executable files
     54that are between two and three times larger than the actual
     55space required in target memory.
     56
    1257
    1358@section Malloc
  • doc/TODO

    r223b64f radee5979  
    88General Issues
    99==============
     10Need a Roadmap
     11
     12Need a description of hello world and writing an application.
     13
    1014More automatic handling of version, date, revision, release, etc.
    1115
     
    1822====================================
    1923Produce PDF
     24
     25Classic Users Guide
     26===================
     27
     28Add Primitive Data Types Chapter
     29
     30Add descriptions for confdefs.h macros in configuring a system
     31chapter.
     32
     33Add defaults for all confdefs.h values.
     34
     35Replace example configuration
    2036
    2137POSIX User Notes
  • doc/networking/testing.t

    r223b64f radee5979  
    6262@code{sys/mbuf.h} in the network stack code.  Uncommenting
    6363these lines results in output when mbuf's are allocated
    64 and freed.  This is very useful for findind memory leaks.
     64and freed.  This is very useful for finding memory leaks.
    6565
    6666@item TX and RX queuing
  • doc/posix_users/message.t

    r223b64f radee5979  
    5757queue for the arrival of a message.
    5858
    59 The message queue descriptor mqd_t mq represents the message queue. It is
     59@findex mqd_t
     60The message queue descriptor @code{mqd_t} represents the message queue. It is
    6061passed as an argument to all of the message queue functions.
    6162
     
    6566queue.
    6667
     68@findex mq_attr
    6769@example
    6870@group
  • doc/posix_users/semaphores.t

    r223b64f radee5979  
    4343
    4444@subsection "sem_t" Structure
    45 The "sem_t" structure is used to represent semaphores. It is passed as an
     45
     46@findex sem_t
     47
     48The @code{sem_t} structure is used to represent semaphores. It is passed as an
    4649argument to the semaphore directives and is defined as follows:
    4750
    4851@example
    49 typedef int sem_t
     52typedef int sem_t;
    5053@end example
    5154
  • doc/started/Makefile.am

    r223b64f radee5979  
    1818
    1919GENERATED_FILES= binaries.texi buildc.texi buildrt.texi gdb.texi intro.texi \
    20     nt.texi require.texi sample.texi
     20    nt.texi require.texi nextstep.texi sample.texi
    2121
    2222FILES= tversions.texi
     
    3131
    3232require.texi: require.t tversions.texi
    33         $(BMENU) -c -p "EGCS Mailing List" \
     33        $(BMENU) -c -p "GCC Mailing Lists" \
    3434            -u "Top" \
    3535            -n "Prebuilt Toolset Executables" $<
     
    5858        $(BMENU) -c -p "Application Executable" \
    5959            -u "Top" \
     60            -n "Where To Go From Here" $<
     61
     62nextstep.texi: nextstep.t tversions.texi
     63        $(BMENU) -c -p "GDB for DINK32" \
     64            -u "Top" \
    6065            -n "Using MS-Windows as a Development Host" $<
    6166
    6267nt.texi: nt.t tversions.texi
    63         $(BMENU) -c -p "GDB for DINK32" \
     68        $(BMENU) -c -p "Where To Go From Here" \
    6469            -u "Top" \
    6570            -n "" $<
  • doc/started/buildc.t

    r223b64f radee5979  
    158158
    159159When the @code{bit} script is executed later in this process,
    160 it will automatically create two other subdirectories:
     160it will automatically create this subdirectory:
    161161
    162162@itemize @bullet
    163 @item src
    164163@item build-$@{CPU@}-tools
    165164@end itemize
     
    196195            @value{GCC-UNTAR}/
    197196            @value{NEWLIB-UNTAR}/
    198             @value{RTEMS-UNTAR}/
    199197            bit
    200198            bit_gdb
     
    251249It is in the reader's and tool maintainers' interest that one read the
    252250documentation before posting a problem to a mailing list or news group.
    253 
    254 @c
    255 @c  EGCS patches
    256 @c
    257 
    258 @section Apply RTEMS Patch to EGCS
     251Much of that documentation is available on-line.  The following is
     252a list of URLs where can find HTML versions of the manuals.
     253
     254@table @b
     255GCC Documentation
     256http://gcc.gnu.org/onlinedocs
     257
     258Newlib Documentation
     259Not currently online at http://sourceware.cygnus.com/newlib
     260
     261Binutils Documentation
     262Not currently online at http://sourceware.cygnus.com/binutils
     263@end table
     264
     265@c
     266@c  GCC patches
     267@c
     268
     269@section Apply RTEMS Patch to GCC
    259270
    260271@ifclear GCC-RTEMSPATCH
     
    397408
    398409@item BUILD_DOCS
    399 is set to "yes" if you want to install documentation.
     410is set to "yes" if you want to install documentation.  This requires
     411that tools supporting documentation production be installed.  This
     412currently is limited to the GNU texinfo package.
    400413For example:
    401414
     
    406419@item BUILD_OTHER_LANGUAGES
    407420is set to "yes" if you want to build languages other than C and C++.  At
    408 the current time, this enables Fortan and Objective-C.
     421the current time, the set of alternative languages includes Java, Fortran,
     422and Objective-C.  These alternative languages do not always build cross.
     423Hence this option defaults to "no".
     424
    409425For example:
    410426
     
    428444@code{configure} option @code{--enable-posix}.
    429445
     446@item ENABLE_RTEMS_ITRON
     447is set to "yes" if you want to enable the RTEMS ITRON API support.
     448At this time, this feature is not supported by the UNIX ports of RTEMS
     449and is forced to "no" for those targets.  This corresponds to the
     450@code{configure} option @code{--enable-itron}.
     451
     452@item ENABLE_RTEMS_MP
     453is set to "yes" if you want to enable the RTEMS multiprocessing
     454support.  This feature is not supported by all RTEMS BSPs and
     455is automatically forced to "no" for those BSPs.  This corresponds to the
     456@code{configure} option @code{--enable-multiprocessing}.
     457
     458@item ENABLE_RTEMS_CXX
     459is set to "yes" if you want to build the RTEMS C++ support including
     460the C++ Wrapper for the Classic API.  This corresponds to the
     461@code{configure} option @code{--enable-cxx}.
     462
    430463@item ENABLE_RTEMS_TESTS
    431464is set to "yes" if you want to build the RTEMS Test Suite.  If this
    432 is set to "no", then only the Sample Tests will be built.
     465is set to "no", then only the Sample Tests will be built.  Setting
     466this option to "yes" significantly increases the amount of disk
     467space required to build RTEMS.
    433468This corresponds to the @code{configure} option @code{--enable-tests}.
    434469
     
    439474@code{--enable-tcpip}.
    440475
    441 @item ENABLE_RTEMS_CXX
    442 is set to "yes" if you want to build the RTEMS C++ support including
    443 the C++ Wrapper for the Classic API.  This corresponds to the
    444 @code{configure} option @code{--enable-cxx}.
     476@item ENABLE_RTEMS_NONDEBUG
     477is set to "yes" if you want to build RTEMS in a fully optimized
     478state.  This corresponds to executing @code{make} after configuring
     479the source tree.
     480
     481@item ENABLE_RTEMS_DEBUG
     482is set to "yes" if you want to build RTEMS in a debug version.
     483When built for debug, RTEMS will include run-time code to
     484perform consistency checks such as heap consistency checks.
     485Although the precise compilation arguments are BSP dependent,
     486the debug version of RTEMS is usually built at a lower optimization
     487level.  This is usually done to reduce inlining which can make
     488tracing code execution difficult.  This corresponds to executing
     489@code{make VARIANT=debug} after configuring
     490the source tree.
     491
     492@item INSTALL_RTEMS
     493is set to "yes" if you want to install RTEMS after building it.
     494This corresponds to executing @code{make install} after configuring
     495and building the source tree.
     496
     497@item ENABLE_RTEMS_MAINTAINER_MODE
     498is set to "yes" if you want to enabled maintainer mode functionality
     499in the RTEMS Makefile.  This is disabled by default and it is not
     500expected that most users will want to enable this.  When this option
     501is enabled, the build process may attempt to regenerate files that
     502require tools not required when this option is disabled.
     503This corresponds to the @code{configure} option
     504@code{--enable-maintainer-mode}.
     505
    445506@end table
    446507
     
    471532@end itemize
    472533
     534The build process can take a while to complete.  Many users find it
     535handy to run the build process in the background, capture the output
     536in a file, and monitor the output.  This can be done as follows:
     537
     538@example
     539./bit_ada <target configuration> >bit.log 2>&1 &
     540tail -f bit.log
     541@end example
     542
    473543If no errors are encountered, the @code{bit} script will conclude by
    474544printing messages similar to the following:
     
    476546@example
    477547
    478 The src and build-i386-tools subdirectory may now be removed.
     548The build-i386-tools subdirectory may now be removed.
    479549
    480550Started:  Fri Apr 10 10:14:07 CDT 1998
     
    524594your PATH.
    525595
     596NOTE:  In some environments, it may be difficult remove "."
     597completely from your PATH.  In this case, make sure that "."
     598is after the system directories containing "as" and "ld".
     599
    526600@subsection Error Messages Indicating Configuration Problems
    527601
  • doc/started/buildrt.t

    r223b64f radee5979  
    103103then all supported BSPs for the selected CPU family will be built.
    104104
     105@b{NOTE:}  The POSIX API must be enabled to use GNAT/RTEMS.
     106
    105107@subsection Using the RTEMS configure Script Directly
    106108
     
    112114section "Unpack the RTEMS source", these configuration options can be found
    113115in the file tools/@value{RTEMS-UNTAR}/README.configure.
     116
     117The GNAT/RTEMS run-time implementation is based on the POSIX API.  Thus
     118the RTEMS configuration for a GNAT/RTEMS environment MUST include the
     119@code{--enable-posix} flag.
    114120
    115121The following shows the command sequence required to configure,
  • doc/started/intro.t

    r223b64f radee5979  
    150150at ftp://ftp.cygnus.com/pub/embedded/crossgcc.
    151151
    152 @subsection EGCS Mailing List
     152@subsection GCC Mailing Lists
    153153
    154 egcs@@cygnus.com
     154See http://gcc.gnu.org for details.
    155155
    156 This mailing list is dedicated to the EGCS Project which was
    157 formed to speed the development and integration of the various
    158 GNU languages.  The RTEMS and Linux communities were among those
    159 initially targetted by the EGCS Project as being important
    160 for its success.  Numerous RTEMS users have made contributions
    161 to this project.  Subscribe by sending a message with
    162 the one line "subscribe" to egcs-request@@cygnus.com.
     156The GCC Project maintains multiple mailing lists.  They
     157are described at the above web site along with subscription
     158information.
    163159
  • doc/started/nt.t

    r223b64f radee5979  
    268268
    269269@c
    270 @c  EGCS
    271 @c
    272 
    273 @section Installing EGCS AND NEWLIB
     270@c  GCC
     271@c
     272
     273@section Installing GCC AND NEWLIB
    274274
    275275@enumerate
    276 @item Unarchive and patch @value{EGCS-TAR} and @value{NEWLIB-TAR}
     276@item Unarchive and patch @value{GCC-TAR} and @value{NEWLIB-TAR}
    277277following the instructions in @ref{Unarchiving the Tools}.
    278278Apply the appropriate RTEMS specific patches as detailed in
    279 @ref{Apply RTEMS Patch to EGCS} and @ref{Apply RTEMS Patch to newlib}.
     279@ref{Apply RTEMS Patch to GCC} and @ref{Apply RTEMS Patch to newlib}.
    280280
    281281@b{NOTE}: See @ref{Bug in Patch Utility}.
     
    292292@b{NOTE}: See @ref{Bug in Patch Utility}.
    293293
    294 @item Link the following directories from Newlib to the main EGCS directory,
     294@item Link the following directories from Newlib to the main GCC directory,
    295295/source/@value{GCC-UNTAR}/ :
    296296
  • doc/started/require.t

    r223b64f radee5979  
    1717|              Component             |   Disk Space Required    |
    1818+------------------------------------+--------------------------+
    19 |        archive directory           |        30 Mbytes         |
    20 |        tools src unzipped          |       100 Mbytes         |
    21 |  each individual build directory   |  300 Mbytes worst case   |
    22 |     each installation directory    |      20-400 Mbytes       |
     19|        archive directory           |        35 Mbytes         |
     20|        tools src unarchived        |       150 Mbytes         |
     21|  each individual build directory   |       300 Mbytes         |
     22|     each installation directory    |      20-200 Mbytes       |
    2323+------------------------------------+--------------------------+
    2424@end example
    2525
    26 The disk space required for each installation directory depends
    27 primarily on the number of RTEMS BSPs which are to be installed.
    28 If a single BSP is installed, then the size of each install directory
     26It is important to understand that the above requirements only address
     27the GNU C/C++ Cross Compiler Tools themselves.  Adding additional
     28languages such as Fortran or Objective-C can increase the size
     29of the build and installation directories.  Also, the unarchived
     30source and build directories can be removed after the tools are
     31installed.
     32
     33After the tools themselves are installed, RTEMS must be built
     34and installed for each Board Support Package that you wish
     35to use.  Thus the precise amount of disk space required
     36for each installation directory depends highly on the number
     37of RTEMS BSPs which are to be installed.  If a single BSP is
     38installed, then the additional size of each install directory
    2939will tend to be in the 40-60 Mbyte range.
     40
     41There are a number of factors which must be taken into
     42account in oreder to estimate the amount of disk space required
     43to build RTEMS itself.  Attempting to build multiple BSPs in
     44a single step increases the disk space requirements.  Similarly
     45enabling optional features increases the build and install
     46space requirements.  In particular, enabling and building
     47the RTEMS tests results in a significant increase in build
     48space requirements but since the test are not installed has
     49no impact on installation requirements.
    3050
    3151The instructions in this manual should work on any computer running
  • doc/started/started.texi

    r223b64f radee5979  
    7575@include sample.texi
    7676@include gdb.texi
     77@include nextstep.texi
    7778@include nt.texi
    7879
     
    9192* Building the Sample Application::
    9293* Building the GNU Debugger::
     94* Where To Go From Here::
    9395* Using MS-Windows as a Development Host::
    9496@end menu
  • doc/started/tversions.texi

    r223b64f radee5979  
    2828@set GCC-FTPDIR      /pub/gcc/gcc-2.95.2
    2929@set GCC-HTTPDIR     /pub/gcc/releases/index.html
    30 @set GCC-RTEMSPATCH  gcc-2.95.2-rtems-20000106.diff
     30@set GCC-RTEMSPATCH  gcc-2.95.2-rtems-20000427.diff.gz
    3131
    3232@c
     
    4343
    4444@c The "official" Linux binutils
    45 @set BINUTILS-VERSION     binutils 2.9.5.0.22
    46 @set BINUTILS-TAR         binutils-2.9.5.0.22.tar.gz
    47 @set BINUTILS-UNTAR       binutils-2.9.5.0.22
     45@set BINUTILS-VERSION     binutils 2.9.5.0.24
     46@set BINUTILS-TAR         binutils-2.9.5.0.24.tar.gz
     47@set BINUTILS-UNTAR       binutils-2.9.5.0.24
    4848@set BINUTILS-FTPSITE     ftp.varesearch.com
    4949@set BINUTILS-FTPDIR      /pub/support/hjl/binutils
    50 @set BINUTILS-RTEMSPATCH  binutils-2.9.5.0.22-rtems-20000114.diff
     50@set BINUTILS-RTEMSPATCH  binutils-2.9.5.0.24-rtems-20000207.diff.gz
    5151
    5252@c When forced to use a snapshot
     
    6262@c
    6363
     64
    6465@set NEWLIB-VERSION     newlib 1.8.2
    6566@set NEWLIB-TAR         newlib-1.8.2.tar.gz
     
    6768@set NEWLIB-FTPSITE     sourceware.cygnus.com
    6869@set NEWLIB-FTPDIR      /pub/newlib
    69 @set NEWLIB-RTEMSPATCH  newlib-1.8.2-rtems-20000104.diff
     70@set NEWLIB-RTEMSPATCH  newlib-1.8.2-rtems-20000501.diff.gz
    7071
    7172@c
     
    7879@set GDB-FTPSITE     ftp.gnu.org
    7980@set GDB-FTPDIR      /pub/gnu/gdb
    80 @set GDB-RTEMSPATCH  gdb-4.18-rtems-20000107.diff
     81@set GDB-RTEMSPATCH  gdb-4.18-rtems-20000502.diff.gz
    8182
    8283@c
     
    8485@c
    8586
    86 @set RTEMS-VERSION   RTEMS 4.5.0-beta
    87 @set RTEMS-TAR       rtems-4.5.0-beta.tgz
    88 @set RTEMS-UNTAR     rtems-4.5.0-beta
     87@set RTEMS-VERSION   RTEMS 4.5.0-beta2
     88@set RTEMS-TAR       rtems-4.5.0-beta2.tgz
     89@set RTEMS-UNTAR     rtems-4.5.0-beta2
    8990@set RTEMS-FTPSITE   ftp.OARcorp.com
    90 @set RTEMS-FTPDIR    /pub/rtems/releases/4.5.0-beta
    91 @set BUILDTOOLS-TAR  c_build_scripts-20000104.tgz
     91@set RTEMS-FTPDIR    /pub/rtems/betas/4.5.0-beta
     92@set BUILDTOOLS-TAR  c_build_scripts-4.5.0-beta2.tgz
    9293
     94
  • doc/started_ada/buildada.t

    r223b64f radee5979  
    212212            @value{GNAT-UNTAR}/
    213213            @value{NEWLIB-UNTAR}/
    214             @value{RTEMS-UNTAR}/
    215214            bit_ada
    216215            bit_gdb
     
    399398@end example
    400399
     400
     401===================================================================
     402
    401403@c
    402404@c  Localizing the Configuration
     
    405407@section Localizing the Configuration
    406408
    407 Edit the @code{user.cfg} file to alter the settings of various
     409Edit the @code{user.cfg} file to alter the settings of various 
    408410variables which are used to tailor the build process.
    409411Each of the variables set in @code{user.cfg} may be modified
     
    417419was generated and for which target system the tools are to produce code for.
    418420
    419 @b{WARNING}: The @code{INSTALL_POINT} should not be a subdirectory
     421@b{WARNING}: The @code{INSTALL_POINT} should not be a subdirectory 
    420422under the build directory.  The build directory will be removed
    421423automatically upon successful completion of the build procedure.
    422424
    423425@item BINUTILS
    424 is the directory under tools that contains @value{BINUTILS-UNTAR}.
     426is the directory under tools that contains @value{BINUTILS-UNTAR}. 
    425427For example:
    426428
     
    449451
    450452@item BUILD_DOCS
    451 is set to "yes" if you want to install documentation.
     453is set to "yes" if you want to install documentation.  This requires
     454that tools supporting documentation production be installed.  This
     455currently is limited to the GNU texinfo package.
    452456For example:
    453457
     
    458462@item BUILD_OTHER_LANGUAGES
    459463is set to "yes" if you want to build languages other than C and C++.  At
    460 the current time, this enables Fortan and Objective-C.
     464the current time, the set of alternative languages includes Java, Fortran,
     465and Objective-C.  These alternative languages do not always build cross.
     466Hence this option defaults to "no".
     467
    461468For example:
    462469
     
    464471BUILD_OTHER_LANGUAGES=yes
    465472@end example
     473
     474@b{NOTE:} Based upon the version of the compiler being used, it may not
     475be possible to build languages other than C and C++ cross.  In many cases,
     476the language run-time support libraries are not "multilib'ed".  Thus the
     477executable code in these libraries will be for the default compiler settings
     478and not necessarily be correct for your CPU model.
    466479
    467480@item RTEMS
     
    476489This must be enabled to support the GNAT/RTEMS run-time.
    477490
     491@item ENABLE_RTEMS_ITRON
     492is set to "yes" if you want to enable the RTEMS ITRON API support.
     493At this time, this feature is not supported by the UNIX ports of RTEMS
     494and is forced to "no" for those targets.  This corresponds to the
     495@code{configure} option @code{--enable-itron}.
     496
     497@item ENABLE_RTEMS_MP
     498is set to "yes" if you want to enable the RTEMS multiprocessing
     499support.  This feature is not supported by all RTEMS BSPs and
     500is automatically forced to "no" for those BSPs.  This corresponds to the
     501@code{configure} option @code{--enable-multiprocessing}.
     502
     503@item ENABLE_RTEMS_CXX
     504is set to "yes" if you want to build the RTEMS C++ support including
     505the C++ Wrapper for the Classic API.  This corresponds to the
     506@code{configure} option @code{--enable-cxx}.
     507
    478508@item ENABLE_RTEMS_TESTS
    479509is set to "yes" if you want to build the RTEMS Test Suite.  If this
    480 is set to "no", then only the Sample Tests will be built.
     510is set to "no", then only the Sample Tests will be built.  Setting
     511this option to "yes" significantly increases the amount of disk
     512space required to build RTEMS.
    481513This corresponds to the @code{configure} option @code{--enable-tests}.
    482514
     
    487519@code{--enable-tcpip}.
    488520
    489 @item ENABLE_RTEMS_CXX
    490 is set to "yes" if you want to build the RTEMS C++ support including
    491 the C++ Wrapper for the Classic API.  This corresponds to the
    492 @code{configure} option @code{--enable-cxx}.
     521@item ENABLE_RTEMS_NONDEBUG
     522is set to "yes" if you want to build RTEMS in a fully optimized
     523state.  This corresponds to executing @code{make} after configuring
     524the source tree.
     525
     526@item ENABLE_RTEMS_DEBUG
     527is set to "yes" if you want to build RTEMS in a debug version.
     528When built for debug, RTEMS will include run-time code to
     529perform consistency checks such as heap consistency checks.
     530Although the precise compilation arguments are BSP dependent,
     531the debug version of RTEMS is usually built at a lower optimization
     532level.  This is usually done to reduce inlining which can make
     533tracing code execution difficult.  This corresponds to executing
     534@code{make VARIANT=debug} after configuring
     535the source tree.
     536
     537@item INSTALL_RTEMS
     538is set to "yes" if you want to install RTEMS after building it.
     539This corresponds to executing @code{make install} after configuring
     540and building the source tree.
     541
     542@item ENABLE_RTEMS_MAINTAINER_MODE
     543is set to "yes" if you want to enabled maintainer mode functionality
     544in the RTEMS Makefile.  This is disabled by default and it is not
     545expected that most users will want to enable this.  When this option
     546is enabled, the build process may attempt to regenerate files that
     547require tools not required when this option is disabled.
     548This corresponds to the @code{configure} option
     549@code{--enable-maintainer-mode}.
     550
    493551@end table
    494552
     
    523581information, contact your GNAT/RTEMS representative.
    524582
     583The build process can take a while to complete.  Many users find it
     584handy to run the build process in the background, capture the output
     585in a file, and monitor the output.  This can be done as follows:
     586
     587@example
     588./bit_ada <target configuration> >bit.log 2>&1 &
     589tail -f bit.log
     590@end example
     591
    525592If no errors are encountered, the @code{bit_ada} script will conclude by
    526593printing messages similar to the following:
  • doc/started_ada/require.t

    r223b64f radee5979  
    1717|              Component             |   Disk Space Required    |
    1818+------------------------------------+--------------------------+
    19 |        archive directory           |        30 Mbytes         |
    20 |        tools src unzipped          |       100 Mbytes         |
     19|        archive directory           |        40 Mbytes         |
     20|        tools src unarchived        |       200 Mbytes         |
    2121|  each individual build directory   |  300 Mbytes worst case   |
    22 |     each installation directory    |      20-130 Mbytes       |
     22|     each installation directory    |      20-200 Mbytes       |
    2323+------------------------------------+--------------------------+
    2424@end example
    2525
    26 The disk space required for each installation directory depends
    27 primarily on the number of RTEMS BSPs which are to be installed.
    28 If a single BSP is installed, then the size of each install directory
     26It is important to understand that the above requirements only address
     27the GNU C/C++ Cross Compiler Tools themselves.  Adding additional
     28languages such as Fortran or Objective-C can increase the size
     29of the build and installation directories.  Also, the unarchived
     30source and build directories can be removed after the tools are
     31installed. 
     32
     33After the tools themselves are installed, RTEMS must be built
     34and installed for each Board Support Package that you wish
     35to use.  Thus the precise amount of disk space required
     36for each installation directory depends highly on the number
     37of RTEMS BSPs which are to be installed.  If a single BSP is
     38installed, then the additional size of each install directory
    2939will tend to be in the 40-60 Mbyte range.
     40
     41There are a number of factors which must be taken into
     42account in oreder to estimate the amount of disk space required
     43to build RTEMS itself.  Attempting to build multiple BSPs in
     44a single step increases the disk space requirements.  Similarly
     45enabling optional features increases the build and install
     46space requirements.  In particular, enabling and building
     47the RTEMS tests results in a significant increase in build
     48space requirements but since the test are not installed has
     49no impact on installation requirements.
    3050
    3151The instructions in this manual should work on any computer running
  • doc/started_ada/tversions.texi

    r223b64f radee5979  
    2727@set GCC-FTPSITE     ftp.gnu.org
    2828@set GCC-FTPDIR      /pub/gnu
    29 @set GCC-RTEMSPATCH  gcc-2.8.1-rtems-diff-19980527.gz
     29@set GCC-RTEMSPATCH  gcc-2.8.1-rtems-gnat-3.12p-20000429.diff.gz
    3030
    3131@c
     
    3333@c
    3434
    35 @set GNAT-VERSION     gnat 3.11b
    36 @set GNAT-TAR         gnat-3.11b-src.tar.gz
    37 @set GNAT-UNTAR       gnat-3.11b-src
     35@set GNAT-VERSION     gnat 3.12p
     36@set GNAT-TAR         gnat-3.12p-src.tar.gz
     37@set GNAT-UNTAR       gnat-3.12p-src
    3838@set GNAT-FTPSITE     NONE
    3939@set GNAT-FTPDIR      NO_DIRECTORY
    40 @set GNAT-RTEMSPATCH  gnat-3.11b-rtems-diff-19981105.gz
     40@set GNAT-RTEMSPATCH  gnat-3.12p-rtems-20000429.diff.gz
    4141
    4242@c
     
    5050@set BINUTILS-FTPSITE     ftp.gnu.org
    5151@set BINUTILS-FTPDIR      /pub/gnu
    52 @set BINUTILS-RTEMSPATCH  binutils-2.9.1-rtems-diff-19981027.gz
     52@set BINUTILS-RTEMSPATCH  binutils-2.9.1-rtems-gnat-3.12p-20000429.diff.gz
    5353
    5454@c When forced to use a snapshot
     
    6464@c
    6565
    66 @set NEWLIB-VERSION     newlib 1.8.1
    67 @set NEWLIB-TAR         newlib-1.8.1.tar.gz
    68 @set NEWLIB-UNTAR       newlib-1.8.1
     66@set NEWLIB-VERSION     newlib 1.8.2
     67@set NEWLIB-TAR         newlib-1.8.2.tar.gz
     68@set NEWLIB-UNTAR       newlib-1.8.2
    6969@set NEWLIB-FTPSITE     ftp.cygnus.com
    7070@set NEWLIB-FTPDIR      /pub/newlib
    71 @set NEWLIB-RTEMSPATCH  newlib-1.8.1-rtems-diff-19980121.gz
     71@set NEWLIB-RTEMSPATCH  newlib-1.8.2-rtems-20000501.diff.gz
    7272
    7373@c
     
    8080@set GDB-FTPSITE     ftp.gnu.org
    8181@set GDB-FTPDIR      /pub/gnu
    82 @set GDB-RTEMSPATCH  gdb-4.17-rtems-diff-19981027.gz
     82@set GDB-RTEMSPATCH  gdb-4.17-rtems-gnat-3.12p-20000429.diff
    8383@c @set GDB-GNATPATCH   gdb-ada-patch-1.17.8.gz
    8484
     
    8787@c
    8888
    89 @set RTEMS-VERSION     RTEMS 4.0.0
    90 @set RTEMS-TAR         rtems-4.0.0.tgz
    91 @set RTEMS-UNTAR       rtems-4.0.0
    92 @set RTEMS-FTPSITE     ftp.OARcorp.com
    93 @set RTEMS-FTPDIR      /pub/rtems/4.0.0
    94 @set BUILDTOOLS-TAR    ada_build_scripts-4.0.0.tgz
     89@set RTEMS-VERSION   RTEMS 4.5.0-beta2
     90@set RTEMS-TAR       rtems-4.5.0-beta2.tgz
     91@set RTEMS-UNTAR     rtems-4.5.0-beta2
     92@set RTEMS-FTPSITE   ftp.OARcorp.com
     93@set RTEMS-FTPDIR    /pub/rtems/betas/4.5.0-beta
     94@set BUILDTOOLS-TAR  c_build_scripts-4.5.0-beta2.tgz
    9595
    9696
  • doc/user/clock.t

    r223b64f radee5979  
    4343and time @value{STRUCTURE} for the native time and date format:
    4444
    45 @ifset is-C
     45
     46@ifset is-C
     47@findex rtems_time_of_day
    4648@example
    4749struct rtems_tod_control @{
     
    109111@subsection Clock Tick and Timeslicing
    110112
     113@cindex timeslicing
     114
    111115Timeslicing is a task scheduling discipline in which
    112116tasks of equal priority are executed for a specific period of
     
    129133
    130134@subsection Delays
     135
     136@cindex delays
    131137
    132138A sleep timer allows a task to delay for a given
     
    140146
    141147@subsection Timeouts
     148
     149@cindex timeouts
    142150
    143151Timeouts are a special type of timer automatically
     
    191199second.  The information returned by the
    192200@code{@value{DIRPREFIX}clock_get} directive is
    193 dependent on the option selected by the caller.  The following
    194 options are available:
     201dependent on the option selected by the caller.  This
     202is specified using one of the following constants
     203associated with the enumerated type
     204@code{@value{DIRPREFIX}clock_get_options}:
     205
     206@findex rtems_clock_get_options
    195207
    196208@itemize @bullet
     
    326338@code{@value{RPREFIX}CLOCK_GET_TICKS_SINCE_BOOT}).
    327339
    328 The data type expected for time_buffer is indicated below:
    329 
     340The @code{option} argument may taken on any value of the enumerated
     341type @code{rtems_clock_get_options}.  The data type expected for
     342@code{time_buffer} is based on the value of @code{option} as
     343indicated below:
     344
     345@findex rtems_clock_get_options
    330346@ifset is-C
    331347@itemize @bullet
  • doc/user/concepts.t

    r223b64f radee5979  
    4444the executive.
    4545
     46@subsection Object Names
     47
    4648@cindex object name
     49@findex rtems_object_name
    4750
    4851An object name is an unsigned thirty-two bit entity
    49 associated with the object by the user.  Although not required
    50 by RTEMS, object names are typically composed of four ASCII
    51 characters which help identify that object.  For example, a task
    52 which causes a light to blink might be called "LITE".  Utilities
    53 are provided to build an object name from four ASCII characters
    54 and to decompose an object name into four ASCII characters.
     52associated with the object by the user.  The data type
     53@code{@value{DIRPREFIX}name} is used to store object names.
     54
     55@findex rtems_build_name
     56
     57Although not required by RTEMS, object names are often
     58composed of four ASCII characters which help identify that object.
     59For example, a task which causes a light to blink might be
     60called "LITE".  The @code{@value{DIRPREFIX}build_name} routine
     61is provided to build an object name from four ASCII characters. 
     62@ifset is-C
     63The following example illustrates this:
     64
     65@example
     66rtems_object_name my_name;
     67
     68my_name = rtems_build_name( 'L', 'I', 'T', 'E' );
     69@end example
     70@end ifset
     71
    5572However, it is not required that the application use ASCII
    5673characters to build object names.  For example, if an
     
    6077one-hundred, respectively.
    6178
     79@subsection Object IDs
     80
    6281@cindex object ID
    6382@cindex object ID composition
     83@findex rtems_id
    6484
    6585@need 3000
     
    6787An object ID is a unique unsigned thirty-two bit
    6888entity composed of three parts: object class, node, and index.
     89The data type @code{@value{DIRPREFIX}id} is used to store object IDs.
     90
    6991
    7092@ifset use-ascii
     
    260282accuracy of all interval and calendar time operations.
    261283
     284@findex rtems_interval
     285
    262286By tracking time in units of ticks, RTEMS is capable
    263287of supporting interval timing functions such as task delays,
     
    268292ticks, it is implied that the task will not execute until ten
    269293clock ticks have occurred.
     294All intervals are specified using data type
     295@code{@value{DIRPREFIX}interval}.
    270296
    271297A characteristic of interval timing is that the
     
    292318task could request to delay until midnight on New Year's Eve
    293319before lowering the ball at Times Square.
     320The data type @code{@value{DIRPREFIX}time_of_day} is used to specify
     321calendar time in RTEMS services. 
     322@xref{Clock Manager Time and Date Data Structures, , Time and Date Data Structures}.
     323@findex rtems_time_of_day
    294324
    295325Obviously, the directives which use intervals or wall
  • doc/user/conf.t

    r223b64f radee5979  
    205205
    206206@ifset is-C
     207@findex rtems_configuration_table
    207208@example
    208209@group
     
    263264When using the @code{confdefs.h} mechanism for configuring
    264265an RTEMS application, the value for this field corresponds
    265 to the setting of the macro @code{CONFIGURE_EXECUTIVE_RAM_WORK_AREA}.
     266to the setting of the macro @code{CONFIGURE_EXECUTIVE_RAM_WORK_AREA}
     267which defaults to @code{NULL}.  Normally, this field should be
     268configured as @code{NULL} as BSPs will assign memory for the
     269RTEMS RAM Workspace as part of system initialization.
    266270
    267271@item work_space_size
     
    279283an RTEMS application, the value for this field corresponds
    280284to the setting of the macro @code{CONFIGURE_MICROSECONDS_PER_TICK}.
    281 If not defined by the application, then the @code{CONFIGURE_MAXIMUM_TASKS}
    282 macro defaults to 10.
    283 XXX
     285If not defined by the application, then the
     286@code{CONFIGURE_MICROSECONDS_PER_TICK} macro defaults to 10000
     287(10 milliseconds).
    284288
    285289@item ticks_per_timeslice
     
    375379When using the @code{confdefs.h} mechanism for configuring
    376380an RTEMS application, the Multiprocessor Configuration Table
    377 is automatically generated when the @code{CONFIGURE_MPTEST}
    378 is defined.  If @code{CONFIGURE_MPTEST} is not defined, the this
     381is automatically generated when the @code{CONFIGURE_MP_APPLICATION}
     382is defined.  If @code{CONFIGURE_MP_APPLICATION} is not defined, the this
    379383entry is set to NULL.  The generated table has the name
    380384@code{Multiprocessing_configuration}.
     
    413417
    414418@ifset is-C
     419@findex rtems_api_configuration_table
    415420@example
    416421@group
     
    591596 
    592597@ifset is-C
     598@findex posix_initialization_threads_table
     599@findex posix_api_configuration_table
    593600@example
    594601@group
     
    775782
    776783@ifset is-C
     784@findex rtems_initialization_tasks_table
    777785@example
    778786typedef struct @{
     
    898906
    899907@ifset is-C
     908@findex rtems_driver_address_table
    900909@example
    901910typedef struct @{
     
    11651174
    11661175When using the @code{confdefs.h} mechanism for configuring
    1167 an RTEMS application, the macro @code{CONFIGURE_MPTEST} must
     1176an RTEMS application, the macro @code{CONFIGURE_MP_APPLICATION} must
    11681177be defined to automatically generate the Multiprocessor Configuration Table.
    1169 If @code{CONFIGURE_MPTEST}, is not defined, then a NULL pointer
     1178If @code{CONFIGURE_MP_APPLICATION}, is not defined, then a NULL pointer
    11701179is configured as the address of this table.
    11711180
  • doc/user/event.t

    r223b64f radee5979  
    2626@subsection Event Sets
    2727
     28@cindex event flag, definition
    2829@cindex event set, definition
     30@findex rtems_event_set
    2931
    3032An event flag is used by a task (or ISR) to inform
     
    3234Thirty-two event flags are associated with each task.  A
    3335collection of one or more event flags is referred to as an event
    34 set.  The application developer should remember the following
     36set.  The data type @code{@value{DIRPREFIX}event_set} is used to manage
     37event sets.
     38
     39The application developer should remember the following
    3540key characteristics of event operations when utilizing the event
    3641manager:
     
    5459An event set is posted when it is directed (or sent) to a task.  A
    5560pending event is an event that has been posted but not received.  An event
    56 condition is used to specify the events which the task desires to receive
     61condition is used to specify the event set which the task desires to receive
    5762and the algorithm which will be used to determine when the request is
    5863satisfied. An event condition is satisfied based upon one of two
  • doc/user/example.texi

    r223b64f radee5979  
    1919 *  user initialization task, and a simple task.
    2020 *
    21  *  This example assumes that a board support package exists
    22  *  and invokes the initialize_executive() directive.
     21 *  This example assumes that a board support package exists.
     22 *
     23 *  Most applications will actually use the confdefs.h method
     24 *  to generate their configuration.  This is provided primarily
     25 *  for reference.
    2326 */
    2427
     
    4144
    4245rtems_configuration_table User_Configuration_Table = @{
    43   NULL,                 /* filled in by the BSP */
     46  NULL,                 /* dynamically assigned by the BSP */
    4447  65536,                /* executive RAM size */
    4548  2,                    /* maximum tasks */
  • doc/user/fatal.t

    r223b64f radee5979  
    6666
    6767@subsection Announcing a Fatal Error
     68
     69@findex _Internal_errors_What_happened
    6870
    6971The @code{@value{DIRPREFIX}fatal_error_occurred} directive is invoked when a
  • doc/user/init.t

    r223b64f radee5979  
    8888@subsection Initialization Manager Failure
    8989
    90 The fatal_error_occurred directive will be called
     90The @code{@value{DIRPREFIX}ifatal_error_occurred} directive will be called
    9191from @code{@value{DIRPREFIX}initialize_executive}
    9292for any of the following reasons:
     
    308308initialization sequences:
    309309@code{@value{DIRPREFIX}initialize_executive} or
    310 @code{@value{DIRPREFIX}nitialize_executive_early} and
    311 @code{@value{DIRPREFIX}nitialize_executive_late}.
     310@code{@value{DIRPREFIX}initialize_executive_early} and
     311@code{@value{DIRPREFIX}initialize_executive_late}.
    312312
    313313@page
  • doc/user/intr.t

    r223b64f radee5979  
    4444if necessary, and device specific manipulation.
    4545
     46@findex rtems_vector_number
     47
    4648The @code{@value{DIRPREFIX}interrupt_catch}
    4749directive connects a procedure to
    48 an interrupt vector.  The interrupt service routine is assumed
     50an interrupt vector.  The vector number is managed using
     51the @code{@value{DIRPREFIX}vector_number} data type.
     52
     53The interrupt service routine is assumed
    4954to abide by these conventions and have a prototype similar to
    5055the following:
    5156
    5257@ifset is-C
     58@findex rtems_isr
     59
    5360@example
    5461rtems_isr user_isr(
  • doc/user/io.t

    r223b64f radee5979  
    7070commonly used to distinguish between a number of devices
    7171controlled by the same driver.
     72
     73@findex rtems_device_major_number
     74@findex rtems_device_minor_number
     75
     76The data types @code{@value{DIRPREFIX}device_major_number} and
     77@code{@value{DIRPREFIX}device_minor_number} are used to
     78manipulate device major and minor numbers, respectively.
    7279
    7380@subsection Device Names
  • doc/user/mp.t

    r223b64f radee5979  
    302302
    303303@ifset is-C
     304@findex rtems_mpci_entry
    304305@example
    305306@group
     
    466467of the packet for each node in the system.
    467468
    468 Many MPCI layers use the packet_length field of the MP_packet_prefix
     469@c XXX packet_prefix structure needs to be defined in this document
     470Many MPCI layers use the @code{packet_length} field of the
     471@code{@value{DIRPREFIX}packet_prefix} portion
    469472of the packet to avoid sending unnecessary data.  This is especially
    470473useful if the media connecting the nodes is relatively slow.
    471474
    472475The to_convert field of the MP_packet_prefix portion of the packet indicates
    473 how much of the packet (in unsigned32's) may require conversion in a
    474 heterogeneous system.
     476how much of the packet (in @code{@value{DIRPREFIX}unsigned32}'s) may require
     477conversion in a heterogeneous system.
    475478
    476479@subsection Supporting Heterogeneous Environments
  • doc/user/rtmon.t

    r223b64f radee5979  
    11381138
    11391139@ifset is-C
     1140@findex rtems_rate_monotonic_period_status
    11401141@example
    11411142typedef struct @{
    11421143  rtems_rate_monotonic_period_states  state;
    1143   unsigned32                          ticks_since_last_period;
    1144   unsigned32                          ticks_executed_since_last_period;
     1144  rtems_unsigned32                    ticks_since_last_period;
     1145  rtems_unsigned32                    ticks_executed_since_last_period;
    11451146@}  rtems_rate_monotonic_period_status;
    11461147@end example
  • doc/user/signal.t

    r223b64f radee5979  
    3838effect on the receiving task's current execution state.
    3939
     40@findex rtems_signal_set
     41
    4042A signal flag is used by a task (or ISR) to inform
    4143another task of the occurrence of a significant situation.
    4244Thirty-two signal flags are associated with each task.  A
    4345collection of one or more signals is referred to as a signal
    44 set.  A signal set is posted when it is directed (or sent) to a
     46set.  The data type @code{@value{DIRPREFIX}signal_set}
     47is used to manipulate signal sets.
     48
     49A signal set is posted when it is directed (or sent) to a
    4550task. A pending signal is a signal that has been sent to a task
    4651with a valid ASR, but has not been processed by that task's ASR.
     
    217222
    218223@ifset is-C
     224@findex rtems_asr
    219225@example
    220226rtems_asr user_routine(
  • doc/user/task.t

    r223b64f radee5979  
    121121@cindex task priority
    122122@cindex priority, task
     123@findex rtems_task_priority
    123124
    124125A task's priority determines its importance in relation to the
    125126other tasks executing on the same processor.  RTEMS supports 255
    126 levels of priority ranging from 1 to 255.  Tasks of numerically
     127levels of priority ranging from 1 to 255.  The data type
     128@code{@value{DIRPREFIX}task_priority} is used to store task
     129priorities.
     130
     131Tasks of numerically
    127132smaller priority values are more important tasks than tasks of
    128133numerically larger priority values.  For example, a task at
     
    144149
    145150@cindex task mode
    146 
    147 A task's mode is a combination of the following four components:
     151@findex rtems_task_mode
     152
     153A task's execution mode is a combination of the following
     154four components:
    148155
    149156@itemize @bullet
     
    155162
    156163It is used to modify RTEMS' scheduling process and to alter the
    157 execution environment of the task.
     164execution environment of the task.  The data type
     165@code{@value{DIRPREFIX}task_mode} is used to manage the task
     166execution mode.
    158167
    159168@cindex preemption
     
    211220
    212221@cindex task arguments
     222@cindex task prototype
    213223
    214224All RTEMS tasks are invoked with a single argument which is
     
    219229
    220230@ifset is-C
     231@findex rtems_task
     232
    221233@example
    222234rtems_task user_task(
     
    241253@cindex floating point
    242254
    243 Creating a task with the @code{@value{RPREFIX}FLOATING_POINT} flag results
     255Creating a task with the @code{@value{RPREFIX}FLOATING_POINT} attribute
     256flag results
    244257in additional memory being allocated for the TCB to store the state of the
    245258numeric coprocessor during task switches.  This additional memory is
     
    727740Valid task priorities range from a high of 1 to a low of 255.
    728741
    729 RTEMS supports a maximum of 256 interrupt levels which are
    730 mapped onto the interrupt levels actually supported by the
    731 target processor.
    732 
    733742The requested stack size should be at least
    734743@code{@value{RPREFIX}MINIMUM_STACK_SIZE}
     
    760769@item @code{@value{RPREFIX}INTERRUPT_LEVEL(n)} - execute at interrupt level n
    761770@end itemize
     771
     772The interrupt level portion of the task execution mode
     773supports a maximum of 256 interrupt levels.  These levels are
     774mapped onto the interrupt levels actually supported by the
     775target processor in a processor dependent fashion.
    762776
    763777Tasks should not be made global unless remote tasks must
  • doc/user/timer.t

    r223b64f radee5979  
    5959
    6060@ifset is-C
     61@findex rtems_timer_service_routine
    6162@example
    6263rtems_timer_service_routine user_routine(
  • doc/user/userext.t

    r223b64f radee5979  
    5757following @value{STRUCTURE}:
    5858
     59@findex rtems_extensions_table
    5960@ifset is-C
    6061@example
     
    6970  rtems_task_exitted_extension     thread_exitted;
    7071  rtems_fatal_extension            fatal;
    71 @} User_extensions_Table;
     72@} rtems_extensions_table;
    7273@end group
    7374@end example
     
    170171conventions on the user.
    171172
    172 @subsection TASK_CREATE Extension
     173@subsubsection TASK_CREATE Extension
    173174
    174175The TASK_CREATE extension directly corresponds to the
     
    179180following:
    180181
     182@findex rtems_task_create_extension
     183@findex rtems_extension
    181184@ifset is-C
    182185@example
     
    204207chain.
    205208
    206 @subsection TASK_START Extension
     209@subsubsection TASK_START Extension
    207210
    208211The TASK_START extension directly corresponds to the
     
    213216following:
    214217
     218@findex rtems_task_start_extension
    215219@ifset is-C
    216220@example
     
    238242it is placed on a ready TCB chain.
    239243
    240 @subsection TASK_RESTART Extension
     244@subsubsection TASK_RESTART Extension
    241245
    242246The TASK_RESTART extension directly corresponds to
     
    246250following:
    247251
     252@findex rtems_task_restart_extension
    248253@ifset is-C
    249254@example
     
    271276ready TCB chain.
    272277
    273 @subsection TASK_DELETE Extension
     278@subsubsection TASK_DELETE Extension
    274279
    275280The TASK_DELETE extension is associated with the
     
    280285following:
    281286
     287@findex rtems_task_delete_extension
    282288@ifset is-C
    283289@example
     
    307313task is deleting itself (current_task is equal to deleted_task).
    308314
    309 @subsection TASK_SWITCH Extension
     315@subsubsection TASK_SWITCH Extension
    310316
    311317The TASK_SWITCH extension corresponds to a task
     
    316322following:
    317323
     324@findex rtems_task_switch_extension
    318325@ifset is-C
    319326@example
     
    342349directives.
    343350
    344 @subsection TASK_BEGIN Extension
     351@subsubsection TASK_BEGIN Extension
    345352
    346353The TASK_BEGIN extension is invoked when a task
     
    349356This user extension have a prototype similar to the following:
    350357
     358@findex rtems_task_begin_extension
    351359@ifset is-C
    352360@example
     
    373381extensions, this is not a critical distinction.
    374382
    375 @subsection TASK_EXITTED Extension
     383@subsubsection TASK_EXITTED Extension
    376384
    377385The TASK_EXITTED extension is invoked when a task
     
    380388prototype similar to the following:
    381389
     390@findex rtems_task_exitted_extension
    382391@ifset is-C
    383392@example
     
    408417fatal_error_occurred with the @code{@value{RPREFIX}TASK_EXITTED} directive status.
    409418
    410 @lowersections
    411 
    412 @subsection FATAL Error Extension
     419@subsubsection FATAL Error Extension
    413420
    414421The FATAL error extension is associated with the
     
    418425This extension should have a prototype similar to the following:
    419426
     427@findex rtems_fatal_extension
    420428@ifset is-C
    421429@example
     
    445453used to pass control to a debugger when a fatal error occurs.
    446454This extension should not call any RTEMS directives.
    447 
    448 @raisesections
    449455
    450456@subsection Order of Invocation
Note: See TracChangeset for help on using the changeset viewer.