diff options
Diffstat (limited to 'doc/started')
42 files changed, 0 insertions, 1781 deletions
diff --git a/doc/started/Makefile b/doc/started/Makefile deleted file mode 100644 index f5f2edf4d6..0000000000 --- a/doc/started/Makefile +++ /dev/null @@ -1,94 +0,0 @@ -# -# COPYRIGHT (c) 1988-1998. -# On-Line Applications Research Corporation (OAR). -# All rights reserved. -# -# $Id$ -# - -PROJECT=started -DISTRIBUTION_LEVEL=public - -include ../Make.config - -all: html info ps - -dirs: - $(make-dirs) - -COMMON_FILES=../common/cpright.texi ../common/setup.texi - -GENERATED_FILES= buildc.texi buildrt.texi gdb.texi intro.texi \ - nt.texi require.texi sample.texi - -FILES= $(PROJECT).texi versions.texi $(GENERATED_FILES) - -INFOFILES=$(wildcard $(PROJECT) $(PROJECT)-*) - -info: dirs $(PROJECT) - #cp $(wildcard $(PROJECT) $(PROJECT)-*) $(INFO_INSTALL) - cp $(PROJECT) $(INFO_INSTALL) - -$(PROJECT): $(FILES) - $(MAKEINFO) $(PROJECT).texi - -dvi: $(PROJECT).dvi -ps: dirs $(PROJECT).ps - -$(PROJECT).ps: $(PROJECT).dvi - dvips -o $(PROJECT).ps $(PROJECT).dvi - cp $(PROJECT).ps $(PS_INSTALL) - -# run texi2dvi twice to generate the xref's properly. -$(PROJECT).dvi: $(FILES) - $(TEXI2DVI) $(PROJECT).texi - texi2dvi $(PROJECT).texi - -intro.texi: intro.t versions.texi - $(BMENU) -c -p "Top" \ - -u "Top" \ - -n "Requirements" ${*}.t - -require.texi: require.t versions.texi - $(BMENU) -c -p "EGCS Mailing List" \ - -u "Top" \ - -n "Building the GNU C/C++ Cross Compiler Toolset" ${*}.t - -buildc.texi: buildc.t versions.texi - $(BMENU) -c -p "GNU makeinfo Version Requirements" \ - -u "Top" \ - -n "Building RTEMS" ${*}.t - -buildrt.texi: buildrt.t versions.texi - $(BMENU) -c -p "Running the bit Script" \ - -u "Top" \ - -n "Building the Sample Application" ${*}.t - -sample.texi: sample.t versions.texi - $(BMENU) -c -p "Using the RTEMS configure Script Directly" \ - -u "Top" \ - -n "Building the GNU Debugger" ${*}.t - -gdb.texi: gdb.t versions.texi - $(BMENU) -c -p "Application Executable" \ - -u "Top" \ - -n "Using MS-Windows as a Development Host" ${*}.t - -nt.texi: nt.t versions.texi - $(BMENU) -c -p "GDB for DINK32" \ - -u "Top" \ - -n "" ${*}.t - -html: dirs $(FILES) - -mkdir -p $(WWW_INSTALL)/$(PROJECT) - -cp pictures/sfile12c.jpg $(WWW_INSTALL)/$(PROJECT) - -cp pictures/bit_c.jpg $(WWW_INSTALL)/$(PROJECT) - $(TEXI2WWW) $(TEXI2WWW_ARGS) -dir $(WWW_INSTALL)/$(PROJECT) \ - $(PROJECT).texi - -clean: - rm -f *.o $(PROG) *.txt core - rm -f *.dvi *.ps *.log *.aux *.cp *.fn *.ky *.pg *.toc *.tp *.vr $(BASE) - rm -f $(PROJECT) $(PROJECT)-* $(GENERATED_FILES) - rm -f *.fixed _* - diff --git a/doc/started/buildc.t b/doc/started/buildc.t deleted file mode 100644 index fee12bf660..0000000000 --- a/doc/started/buildc.t +++ /dev/null @@ -1,485 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Building the GNU C/C++ Cross Compiler Toolset - -This chapter describes the steps required to acquire the -source code for a GNU cross compiler toolset, apply -any required RTEMS specific patches, compile that -toolset and install it. - -@section Create the Archive and Build Directories - -Start by making the @code{archive} directory to contain the downloaded -source code and the @code{tools} directory to be used as a build -directory. The command sequence to do this is shown -below: - -@example -mkdir archive -mkdir tools -@end example - -This will result in an initial directory structure similar to the -one shown in the following figure: - -@example -@group -/whatever/prefix/you/choose/ - archive/ - tools/ - -@end group -@end example - -@c @ifset use-html -@c @html -@c <IMG SRC="sfile12c.jpg" WIDTH=417 HEIGHT=178 -@c ALT="Starting Directory Organization"> -@c @end html -@c @end ifset - -@section Get All the Pieces - -This section lists the components of an RTEMS cross development system. -Included are the locations of each component as well as any required RTEMS -specific patches. - -@subheading @value{GCC-VERSION} -@example - FTP Site: @value{GCC-FTPSITE} - Directory: @value{GCC-FTPDIR} - File: @value{GCC-TAR} -@ifset use-html - URL: @href{Download @value{GCC-VERSION},,,ftp://@value{GCC-FTPSITE}@value{GCC-HTTPDIR}} -@end ifset -@end example - -@subheading @value{BINUTILS-VERSION} -@example - FTP Site: @value{BINUTILS-FTPSITE} - Directory: @value{BINUTILS-FTPDIR} - File: @value{BINUTILS-TAR} -@ifset use-html - URL: @href{Download @value{BINUTILS-VERSION},,,ftp://@value{BINUTILS-FTPSITE}@value{BINUTILS-FTPDIR}/@value{BINUTILS-TAR}} -@end ifset -@end example - -@subheading @value{NEWLIB-VERSION} -@example - FTP Site: @value{NEWLIB-FTPSITE} - Directory: @value{NEWLIB-FTPDIR} - File: @value{NEWLIB-TAR} -@ifset use-html - URL: @href{Download @value{NEWLIB-VERSION},,,ftp://@value{NEWLIB-FTPSITE}@value{NEWLIB-FTPDIR}/@value{NEWLIB-TAR}} -@end ifset -@end example - -@subheading @value{RTEMS-VERSION} -@example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR} - File: @value{RTEMS-TAR} -@ifset use-html - URL: @href{Download RTEMS components,,,ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}} -@end ifset -@end example - -@subheading RTEMS Hello World -@example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR} - File: hello_world_c.tgz -@ifset use-html - URL: @href{Download RTEMS Hello World,,,ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/hello_world_c.tgz} -@end ifset -@end example - -@subheading RTEMS Specific Tool Patches and Scripts -@example - FTP Site: @value{RTEMS-FTPSITE} - Directory: @value{RTEMS-FTPDIR}/c_tools - File: @value{BUILDTOOLS-TAR} -@ifset BINUTILS-RTEMSPATCH - File: @value{BINUTILS-RTEMSPATCH} -@end ifset -@ifset NEWLIB-RTEMSPATCH - File: @value{NEWLIB-RTEMSPATCH} -@end ifset -@ifset GCC-RTEMSPATCH - File: @value{GCC-RTEMSPATCH} -@end ifset -@ifset use-html - URL: @href{Download RTEMS Patches and Scripts,,,ftp://@value{RTEMS-FTPSITE}@value{RTEMS-FTPDIR}/c_tools} -@end ifset -@end example - -@section Unarchiving the Tools - -While in the @code{tools} directory, unpack the compressed -tar files using the following command sequence: - -@example -cd tools -tar xzf ../archive/@value{GCC-TAR} -tar xzf ../archive/@value{BINUTILS-TAR} -tar xzf ../archive/@value{NEWLIB-TAR} -tar xzf ../archive/@value{BUILDTOOLS-TAR} -@end example - -After the compressed tar files have been unpacked, the following -directories will have been created under tools. - -@itemize @bullet -@item @value{BINUTILS-UNTAR} -@item @value{GCC-UNTAR} -@item @value{NEWLIB-UNTAR} -@end itemize - -There will also be a set of scripts in the current directory -which aid in building the tools and RTEMS. They are: - -@itemize @bullet -@item bit -@item bit_gdb -@item bit_rtems -@item common.sh -@item user.cfg -@end itemize - -When the @code{bit} script is executed later in this process, -it will automatically create two other subdirectories: - -@itemize @bullet -@item src -@item build-$@{CPU@}-tools -@end itemize - -Similarly, the @code{bit_gdb} script will create the -subdirectory @code{build-$@{CPU@}-gdb} and -the @code{bit_rtems} script will create the -subdirectory @code{build-$@{CPU@}-rtems}. - -The tree should look something like the following figure: - -@example -@group -/whatever/prefix/you/choose/ - archive/ - @value{GCC-TAR} - @value{BINUTILS-TAR} - @value{NEWLIB-TAR} - @value{RTEMS-TAR} - @value{BUILDTOOLS-TAR} -@ifset GCC-RTEMSPATCH - @value{GCC-RTEMSPATCH} -@end ifset -@ifset BINUTILS-RTEMSPATCH - @value{BINUTILS-RTEMSPATCH} -@end ifset -@ifset NEWLIB-RTEMSPATCH - @value{NEWLIB-RTEMSPATCH} -@end ifset - hello_world_c.tgz - bit - tools/ - @value{BINUTILS-UNTAR}/ - @value{GCC-UNTAR}/ - @value{NEWLIB-UNTAR}/ - @value{RTEMS-UNTAR}/ - bit - bit_gdb - bit_rtems - common.sh - user.cfg -@end group -@end example - - -@c @ifset use-html -@c @html -@c <IMG SRC="bit_c.jpg" WIDTH=816 HEIGHT=267 ALT="Directory Organization"> -@c @end html -@c @end ifset - -@c -@c Host Specific Notes -@c - -@section Host Specific Notes - -@subsection Solaris 2.x - -The build scripts are written in "shell". The program @code{/bin/sh} -on Solaris 2.x is not robust enough to execute these scripts. If you -are on a Solaris 2.x host, then change the first line of the files -@code{bit}, @code{bit_gdb}, and @code{bit_rtems} to use the -@code{/bin/ksh} shell instead. - -@subsection Linux - -@subsubsection Broken install Program - -Certain versions of GNU fileutils include a version of @code{install} which -does not work properly. Please perform the following test to see if you -need to upgrade: - -@example -install -c -d /tmp/foo/bar -@end example - -If this does not create the specified directories your install -program will not install RTEMS properly. You will need to upgrade -to at least GNU fileutile version 3.16 to resolve this problem. - -@c -@c Reading the Documentation -@c - -@section Reading the Tools Documentation - -Each of the tools in the GNU development suite comes with documentation. -It is in the reader's and tool maintainers' interest that one read the -documentation before posting a problem to a mailing list or news group. - -@c -@c EGCS patches -@c - -@section Apply RTEMS Patch to EGCS - -@ifclear GCC-RTEMSPATCH -No RTEMS specific patches are required for @value{GCC-VERSION} to -support @value{RTEMS-VERSION}. -@end ifclear - -@ifset GCC-RTEMSPATCH - -Apply the patch using the following command sequence: - -@example -cd tools/@value{GCC-UNTAR} -zcat ../../archive/@value{GCC-RTEMSPATCH} | patch -p1 -@end example - -Check to see if any of these patches have been rejected using the following -sequence: - -@example -cd tools/@value{GCC-UNTAR} -find . -name "*.rej" -print -@end example - -If any files are found with the .rej extension, a patch has been rejected. -This should not happen with a good patch file which is properly applied. - -@end ifset - -@c -@c BINUTILS patches -@c - -@section Apply RTEMS Patch to binutils - -@ifclear BINUTILS-RTEMSPATCH -No RTEMS specific patches are required for @value{BINUTILS-VERSION} to -support @value{RTEMS-VERSION}. -@end ifclear - -@ifset BINUTILS-RTEMSPATCH -Apply the patch using the following command sequence: - -@example -cd tools/@value{BINUTILS-UNTAR} -zcat ../../archive/@value{BINUTILS-RTEMSPATCH} | patch -p1 -@end example - -Check to see if any of these patches have been rejected using the following -sequence: - -@example -cd tools/@value{BINUTILS-UNTAR} -find . -name "*.rej" -print -@end example - -If any files are found with the .rej extension, a patch has been rejected. -This should not happen with a good patch file which is properly applied. - -@end ifset - -@c -@c Newlib patches -@c - -@section Apply RTEMS Patch to newlib - -@ifclear NEWLIB-RTEMSPATCH -No RTEMS specific patches are required for @value{NEWLIB-VERSION} to -support @value{RTEMS-VERSION}. -@end ifclear - -@ifset NEWLIB-RTEMSPATCH - -Apply the patch using the following command sequence: - -@example -cd tools/@value{NEWLIB-UNTAR} -zcat ../../archive/@value{NEWLIB-RTEMSPATCH} | patch -p1 -@end example - -Check to see if any of these patches have been rejected using the following -sequence: - -@example -cd tools/@value{NEWLIB-UNTAR} -find . -name "*.rej" -print -@end example - -If any files are found with the .rej extension, a patch has been rejected. -This should not happen with a good patch file which is properly applied. - -@end ifset - -@c -@c Localizing the Configuration -@c - -@section Localizing the Configuration - -Edit the @code{user.cfg} file to alter the settings of various -variables which are used to tailor the build process. -Each of the variables set in @code{user.cfg} may be modified -as described below: - -@table @code -@item INSTALL_POINT -is the location where you wish the GNU C/C++ cross compilation tools for -RTEMS to be built. It is recommended that the directory chosen to receive -these tools be named so that it is clear from which egcs distribution it -was generated and for which target system the tools are to produce code for. - -@b{WARNING}: The @code{INSTALL_POINT} should not be a subdirectory -under the build directory. The build directory will be removed -automatically upon successful completion of the build procedure. - -@item BINUTILS -is the directory under tools that contains @value{BINUTILS-UNTAR}. -For example: - -@example -BINUTILS=@value{BINUTILS-UNTAR} -@end example - -@item GCC -is the directory under tools that contains @value{GCC-UNTAR}. -For example, - -@example -GCC=@value{GCC-UNTAR} -@end example - -@item NEWLIB -is the directory under tools that contains @value{NEWLIB-UNTAR}. -For example: - -@example -NEWLIB=@value{NEWLIB-UNTAR} -@end example - -@item BUILD_DOCS -is set to "yes" if you want to install documentation. -For example: - -@example -BUILD_DOCS=yes -@end example - -@item BUILD_OTHER_LANGUAGES -is set to "yes" if you want to build languages other than C and C++. At -the current time, this enables Fortan and Objective-C. -For example: - -@example -BUILD_OTHER_LANGUAGES=yes -@end example - -@b{NOTE:} Based upon the version of the compiler being used, it may not -be possible to build languages other than C and C++ cross. In many cases, -the language run-time support libraries are not "multilib'ed". Thus the -executable code in these libraries will be for the default compiler settings -and not necessarily be correct for your CPU model. - -@item RTEMS -is the directory under tools that contails @value{RTEMS-UNTAR}. - -@item ENABLE_RTEMS_POSIX -is set to "yes" if you want to enable the RTEMS POSIX API support. -At this time, this feature is not supported by the UNIX ports of RTEMS -and is forced to "no" for those targets. This corresponds to the -@code{configure} option @code{--enable-posix}. - -@item ENABLE_RTEMS_TESTS -is set to "yes" if you want to build the RTEMS Test Suite. If this -is set to "no", then only the Sample Tests will be built. -This corresponds to the @code{configure} option @code{--enable-tests}. - -@item ENABLE_RTEMS_TCPIP -is set to "yes" if you want to build the RTEMS TCP/IP Stack. If a -particular BSP does not support TCP/IP, then this feature is automatically -disabled. This corresponds to the @code{configure} option -@code{--enable-tcpip}. - -@item ENABLE_RTEMS_CXX -is set to "yes" if you want to build the RTEMS C++ support including -the C++ Wrapper for the Classic API. This corresponds to the -@code{configure} option @code{--enable-cxx}. -@end table - -@section Running the bit Script - -After the @code{bit} script has been modified to reflect the -local installation, the modified @code{bit} script is run -using the following sequence: - -@example -cd tools -./bit <target configuration> -@end example - -Where <target configuration> is one of the following: - -@itemize @bullet -@item hppa1.1 -@item i386 -@item i386-elf -@item i386-go32 -@item i960 -@item m68k -@item mips64orion -@item powerpc -@item sh -@item sparc -@end itemize - -If no errors are encountered, the @code{bit} script will conclude by -printing messages similar to the following: - -@example - -The src and build-i386-tools subdirectory may now be removed. - -Started: Fri Apr 10 10:14:07 CDT 1998 -Finished: Fri Apr 10 12:01:33 CDT 1998 -@end example - -If the @code{bit} script successfully completes, then the -GNU C/C++ cross compilation tools are installed. - -If the @code{bit} script does not successfully complete, then investigation -will be required to determine the source of the error. - diff --git a/doc/started/buildrt.t b/doc/started/buildrt.t deleted file mode 100644 index 1366bca1d4..0000000000 --- a/doc/started/buildrt.t +++ /dev/null @@ -1,137 +0,0 @@ -@c -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Building RTEMS - -@section Unpack the RTEMS Source - -Use the following command sequence to unpack the RTEMS source into the -tools directory: - -@example -cd tools -tar xzf ../archive/@value{RTEMS-TAR} -@end example - -@section Add <INSTALL_POINT>/bin to Executable PATH - -In order to compile RTEMS, you must have the cross compilation toolset -in your search patch. The following command appends the directory -where the tools were installed in the previous chapter: - -@example -export PATH=$PATH:<INSTALL_POINT>/bin -@end example - -NOTE: The above command is in Bourne shell (@code{sh}) syntax and -should work with the Korn (@code{ksh}) and GNU Bourne Again Shell -(@code{bash}). It will not work with the C Shell (@code{csh}) or -derivatives of the C Shell. - -@section Verifying the Operation of the Cross Toolset - -In order to insure that the cross-compiler is invoking the correct -subprograms (like @code{as} and @code{ld}), one can test assemble -a small program. When in verbose more, @code{gcc} prints out information -showing where it found the subprograms it invokes. Place the following -function in a file named @code{f.c}: - -@example -int f( int x ) -@{ - return x + 1; -@} -@end example - -Then assemble the file using a command similar to the following: - -@example -m68k-rtems-gcc -v -S f.c -@end example - -Where @code{m68k-rtems-gcc} should be changed to match the installed -name of your cross compiler. The result of this command will be -a sequence of output showing where the cross-compiler searched for -and found its subcomponents. Verify that these paths correspond -to your <INSTALL_POINT>. - -@b{NOTE:} One of the most common installation errors is for the -cross-compiler not to be able to find the cross assembler and default -to using the native @code{as}. This can result in very confusing -error messages. - -@section Generate RTEMS for a Specific Target and BSP - -@subsection Using the bit_rtems Script - -The simplest way to build RTEMS is to use the @code{bit_rtems} script. -This script interprets the settings in the @code{user.cfg} file to -enable or disable the various RTEMS options. - -This script is invoked as follows: - -@example -./bit_rtems CPU [BSP] -@end example - -Where CPU is one of the RTEMS supported CPU families from the following -list: - -@itemize @bullet -@item hppa1.1 -@item i386 -@item i386-elf -@item i386-go32 -@item i960 -@item m68k -@item mips64orion -@item powerpc -@item sh -@item sparc -@end itemize - -BSP is a supported BSP for the selected CPU family. The list of -supported BSPs may be found in the file -tools/@value{RTEMS-UNTAR}/README.configure -in the RTEMS source tree. If the BSP parameter is not specified, -then all supported BSPs for the selected CPU family will be built. - -@subsection Using the RTEMS configure Script Directly - -Make a build directory under tools and build the RTEMS product in this -directory. The ../@value{RTEMS-UNTAR}/configure -command has numerous command line -arguments. These arguments are discussed in detail in documentation that -comes with the RTEMS distribution. In the installation described in the -section "Unpack the RTEMS source", these configuration options can be found -in the file tools/@value{RTEMS-UNTAR}/README.configure. - -The following shows the command sequence required to configure, -compile, and install RTEMS with the POSIX API, FreeBSD TCP/IP, -and C++ support disabled. RTEMS will be built to target -the @code{BOARD_SUPPORT_PACKAGE} board. - -@example -mkdir build-rtems -cd build-rtems -../@value{RTEMS-UNTAR}/configure --target=<TARGET_CONFIGURATION> \ - --disable-posix --disable-tcpip --disable-cxx \ - --enable-rtemsbsp=<BOARD_SUPPORT_PACKAGE>\ - --prefix=<INSTALL_POINT> -gmake all install -@end example - -Where the list of currently supported of <TARGET_CONFIGURATION>'s and -<BOARD_SUPPORT_PACKAGE>'s can be found in -tools/@value{RTEMS-UNTAR}/README.configure. - -<INSTALL_POINT> is the installation point from the previous step -"Modify the bit script" in the build of the tools. - - diff --git a/doc/started/gdb.t b/doc/started/gdb.t deleted file mode 100644 index 13716ca635..0000000000 --- a/doc/started/gdb.t +++ /dev/null @@ -1,222 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Building the GNU Debugger - -GDB is not currently RTEMS aware. The following configurations have been -successfully used with RTEMS applications: - -@itemize @bullet -@item Sparc Instruction Simulator (SIS) -@item PowerPC Instruction Simulator (PSIM) -@item DINK32 -@end itemize - -Other configurations of gdb have successfully been used by RTEMS users -but are not documented here. - -@section Unarchive the gdb Distribution - -Use the following commands to unarchive the gdb distribution: - -@example -cd tools -tar xzf ../archive/@value{GDB-TAR} -@end example - -The directory @value{GDB-UNTAR} is created under the tools directory. - -@c -@c GDB Patch -@c - -@section Apply RTEMS Patch to GDB - -@ifclear GDB-RTEMSPATCH -No RTEMS specific patches are required for @value{GDB-VERSION} to -support @value{RTEMS-VERSION}. -@end ifclear - -@ifset GDB-RTEMSPATCH - -Apply the patch using the following command sequence: - -@example -cd tools/@value{GDB-UNTAR} -zcat archive/@value{GDB-RTEMSPATCH} | patch -p1 -@end example - -Check to see if any of these patches have been rejected using the following -sequence: - -@example -cd tools/@value{GDB-UNTAR} -find . -name "*.rej" -print -@end example - -If any files are found with the .rej extension, a patch has been rejected. -This should not happen with a good patch file. - -To see the files that have been modified use the sequence: - -@example -cd tools/@value{GDB-UNTAR} -find . -name "*.orig" -print -@end example - -The files that are found, have been modified by the patch file. - -@end ifset - -@section Using the bit_gdb script - -The simplest way to build gdb for RTEMS is to use the @code{bit_gdb} script. -This script interprets the settings in the @code{user.cfg} file to -produce the gdb configuration most appropriate for the target CPU. - -This script is invoked as follows: - -@example -./bit_gdb CPU -@end example - -Where CPU is one of the RTEMS supported CPU families from the following -list: - -@itemize @bullet -@item hppa1.1 -@item i386 -@item i386-elf -@item i386-go32 -@item i960 -@item m68k -@item mips64orion -@item powerpc -@item sh -@item sparc -@end itemize - -If gdb supports a CPU instruction simulator for this configuration, then -it is included in the build. - -@section Using the gdb configure Script Directly - -@subsection GDB with Sparc Instruction Simulation (SIS) - -@subheading Make the Build Directory - -Create a build directory for the SIS Debugger - -@example -cd tools -mkdir build-sis -@end example - -@subheading Configure for the Build - -Configure the GNU Debugger for the -Sparc Instruction Simulator (SIS): - -@example -cd tools/build-sis -../@value{GDB-UNTAR}/configure --target-sparc-erc32-aout \ - --program-prefix=sparc-rtems- \ - --disable-gdbtk \ - --enable-targets=all \ - --prefix=<INSTALL_POINT_FOR_SIS> -@end example - -Where <INSTALL_POINT_FOR_SIS> is a unique location where the gdb -with SIS will be created. - -@subheading Make the Debugger - -From tools/build-sis execute the following command sequence: - -@example -gmake all install -@end example - - -@subsection GDB with PowerPC Instruction Simulator - -@subheading Make the Build Directory - -Create a build directory for the SIS Debugger - -@example -cd tools -mkdir build-ppc -@end example - -@subheading Configure for the Build - -Configure the GNU Debugger for the PowerPC -Instruction Simulator (PSIM): - -@example -cd tools/build-ppc -../@value{GDB-UNTAR}/configure \ - --target=powerpc-unknown-eabi \ - --program-prefix=powerpc-rtems- \ - --enable-sim-powerpc \ - --enable-sim-timebase \ - --enable-sim-inline \ - --enable-sim-hardware \ - --enable-targets=all \ - --prefix=<INSTALL_POINT_FOR_PPC> -@end example - -Where <INSTALL_POINT_FOR_PPC> is a unique location where the gdb -with PSIM will be created. - - -@subheading Make the Debugger - -From tools/build-ppc execute the following command sequence: - -@example -gmake all install -@end example - - -@subsection GDB for DINK32 - -@subheading Make the Build Directory - -Create a build directory for the DINK32 Debugger - -@example -cd tools -mkdir build-dink32 -@end example - -@subheading Configure for the Build - -Configure the GNU Debugger to communicate with -the DINK32 ROM monitor: - -@example -cd tools/build-dink32 -../@value{GDB-UNTAR}/configure --target-powerpc-elf \ - --program-prefix=powerpc-rtems- \ - --enable-targets=all \ - --prefix=<INSTALL_POINT_FOR_DINK32> -@end example - -Where <INSTALL_POINT_FOR_DINK32> is a unique location where the -gdb Dink32 will be created. - -@subheading Make the Debugger - -From tools/build-dink32 execute the following command sequence: - -@example -gmake all install -@end example - diff --git a/doc/started/intro.t b/doc/started/intro.t deleted file mode 100644 index c5100b3292..0000000000 --- a/doc/started/intro.t +++ /dev/null @@ -1,162 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Introduction - -The purpose of this document is to guide you through the process of -installing a GNU cross development environment to use with RTEMS. - -If you are already familiar with the concepts behind a cross compiler and -have a background in Unix, these instructions should provide the bare -essentials for performing a setup of the following items: - -@itemize @bullet -@item GNU C/C++ Cross Compilation Tools for RTEMS on your host system -@item RTEMS OS for the target host -@item GDB Debugger -@end itemize - -The remainder of this chapter provides background information on real-time -embedded systems and cross development and an overview of other -resources of interest on the Internet. If you are not familiar with -real-time embedded systems or the other areas, please read those sections. -These sections will help familiarize you with the -types of systems RTEMS is designed to be used in and the cross development -process used when developing RTEMS applications. - -@section Real-Time Embedded Systems - -Real-time embedded systems are found in practically every facet of our -everyday lives. Today's systems range from the common telephone, automobile -control systems, and kitchen appliances to complex air traffic control -systems, military weapon systems, an d production line control including -robotics and automation. However, in the current climate of rapidly changing -technology, it is difficult to reach a consensus on the definition of a -real-time embedded system. Hardware costs are continuing to rapidly decline -while at the same time the hardware is increasing in power and functionality. -As a result, embedded systems that were not considered viable two years ago -are suddenly a cost effective solution. In this domain, it is not uncommon -for a single hardware configuration to employ a variety of architectures and -technologies. Therefore, we shall define an embedded system as any computer -system that is built into a larger system consisting of multiple technologies -such as digital and analog electronics, mechanical devices, and sensors. - -Even as hardware platforms become more powerful, most embedded systems are -critically dependent on the real-time software embedded in the systems -themselves. Regardless of how efficiently the hardware operates, the -performance of the embedded real-time software determines the success of the -system. As the complexity of the embedded hardware platform grows, so does -the size and complexity of the embedded software. Software systems must -routinely perform activities which were only dreamed of a short time ago. -These large, complex, real-time embedded applications now commonly contain -one million lines of code or more. - -Real-time embedded systems have a complex set of characteristics that -distinguish them from other software applications. Real-time embedded -systems are driven by and must respond to real world events while adhering to -rigorous requirements imposed by the environment with which they interact. -The correctness of the system depends not only on the results of -computations, but also on the time at which the results are produced. The -most important and complex characteristic of real-time application systems is -that they must receive and respond to a set of external stimuli within rigid -and critical time constraints. - -A single real-time application can be composed of both soft and hard -real-time components. A typical example of a hard real-time system is a -nuclear reactor control system that must not only detect failures, but must -also respond quickly enough to prevent a meltdown. This application also has -soft real-time requirements because it may involve a man-machine interface. -Providing an interactive input to the control system is not as critical as -setting off an alarm to indicate a failure condition. However, th e -interactive system component must respond within an acceptable time limit to -allow the operator to interact efficiently with the control system. - -@section Cross Development - -Today almost all real-time embedded software systems are developed in a -@b{cross development} environment using cross development tools. In the cross -development environment, software development activities are typically -performed on one computer system, the @b{host} system, while the result of the -development effort (produced by the cross tools) is a software system that -executes on the @b{target} platform. The requirements for the target platform are -usually incompatible and quite often in direct conflict with the requirements -for the host. Moreover, the target hardware is often custom designed for a -particular project. This means that the cross development toolset must allow -the developer to customize the tools to address target specific run-time -issues. The toolset must have provisions for board dependent initialization -code, device drivers, and error handling code. - -The host computer is optimized to support the code development cycle with -support for code editors, compilers, and linkers requiring large disk drives, -user development windows, and multiple developer connections. Thus the host -computer is typically a traditional UNIX workstation such as are available -from SUN or Silicon Graphics, or a PC running either a version of MS-Windows -or UNIX. The host system may also be required to execute office productivity -applications to allow the software developer to write documentation, make -presentations, or track the project's progress using a project management -tool. This necessitates that the host computer be general purpose with -resources such as a thirty-two or sixty-four bit processor, large amounts of -RAM, a monitor, mouse, keyboard, hard and floppy disk drives, CD-ROM drive, -and a graphics card. It is likely that the system will be multimedia capable -and have some networking capability. - -Conversely, the target platform generally has limited traditional computer -resources. The hardware is designed for the particular functionality and -requirements of the embedded system and optimized to perform those tasks -effectively. Instead of hard driverss and keyboards, it is composed of -sensors, relays, and stepper motors. The per-unit cost of the target platform -is typically a critical concern. No hardware component is included without -being cost justified. As a result, the processor of the target system is -often from a different processor family than that of the host system and -usually has lower performance. In addition to the processor families -targeted only for use in embedded systems, there are versions of nearly every -general-purpose process or specifically tailored for real-time embedded -systems. For example, many of the processors targeting the embedded market -do not include hardware floating point units, but do include peripherals such -as timers, serial controllers, or network interfaces. - -@section Resources on the Internet - -This section describes various resources on the Internet which are of -use to RTEMS users. - -@subsection RTEMS Mailing List - -rtems-list@@OARcorp.com - -This mailing list is dedicated to discussion of issues related -to RTEMS. If you have questions about RTEMS, wish to make -suggestions, or just want to pick up hints, this is a good -list to subscribe to. Subscribe by sending a message with -the one line "subscribe" to rtems-list-request@@OARcorp.com. - -@subsection CrossGCC Mailing List - -crossgcc@@cygnus.com - -This mailing list is dedicated to the use of the GNU tools in -cross development environments. Most of the discussions -focus on embedded issues. Subscribe by sending a message with -the one line "subscribe" to crossgcc-request@@cygnus.com. - -The crossgcc FAQ as well as a number of patches and utiliities -of interest to cross development system users are available -at ftp://ftp.cygnus.com/pub/embedded/crossgcc. - -@subsection EGCS Mailing List - -egcs@@cygnus.com - -This mailing list is dedicated to the EGCS Project which was -formed to speed the development and integration of the various -GNU languages. The RTEMS and Linux communities were among those -initially targetted by the EGCS Project as being important -for its success. Numerous RTEMS users have made contributions -to this project. Subscribe by sending a message with -the one line "subscribe" to egcs-request@@cygnus.com. - diff --git a/doc/started/nt.t b/doc/started/nt.t deleted file mode 100644 index 9c5160b726..0000000000 --- a/doc/started/nt.t +++ /dev/null @@ -1,365 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@set CYGWIN-VERSION B19 -@set CYGWIN-FTP http://www.cygnus.com/misc/gnu-win32/ -@set CYGWIN-COOLVIEW http://www.lexa.ru/sos/ -@set DOS2UNIX-FTP ftp://ftp.micros.hensa.ac.uk/platforms/ibm-pc/ms-dos/simtelnet/txtutl/dos2unix.zip -@set PFE-FTP http://www.lancs.ac.uk/people/cpaap/pfe/ - -@chapter Using MS-Windows as a Development Host - -This chapter discusses the installation of the GNU tool chain -on a computer running the Microsoft Windows NT operating system. - -This chapter is based on a draft provided by -Geoffroy Montel <g_montel@@yahoo.com>. Geoffroy's -procedure was based on information from -David Fiddes <D.J@@fiddes.surfaid.org>. -Their input and feedback is greatly appreciated. - -@b{STATUS:} This chapter should be considered preliminary. -Please be careful when following these instructions. - -@section Version Information - -This installation process works well under Windows NT. -Using Windows 95 or 98 is not recommended although it -should be possible with version 3.77 of gmake and an updated -cygwinb19.dll. - -This procedure should also work with newer version of -the tool versions listed in this chapter, but this has -not been verified. If you have success with a particular -version of the toolset or notice problems in this chapter, -please let the RTEMS maintainers know so they can be -addressed in future revisions of this document. - -@section MS-Windows Host Specific Requirements - -This section details the components required to install -and build a Windows hosted GNU cross development toolset. - -@subsection Unzipping Archives - -You will have to uncompress many archives during this -process. You must @b{NOT} use @code{WinZip} or -@code{PKZip}. Instead the un-archiving process uses -the GNU @code{zip} and @code{tar} programs as shown below: - -@example -tar -xzvf archive.tgz -@end example - -@code{tar} is provided with Cygwin32. - -@subsection Text Editor - -You absolutely have to use a text editor which can -save files with Unix format (so don't use Notepad -nor Wordpad). If you do not have an appropriate -text editor, try @b{Programmers File Editor}, it is -free and very convenient. This editor may be downloaded -from: - -@ifset use-html -@href{@value{PFE-FTP},,@value{PFE-FTP}} -@end ifset -@ifclear use-html -@value{PFE-FTP} -@end ifclear - -@subsection Bug in Patch Utility - -There is a bug in the @code{patch} utility -provided in Cygwin32 B19. The files modified end up -having MS-DOS style line termination. They must have -Unix format, so a @code{dos2unix}-like command must -be used to put them back into Unix format as shown below: - -@example -$ dos2unix XYZ -Dos2Unix: Cleaning file XYZ ... -@end example - -The dos2unix utility may be downloaded from: - -@ifset use-html -@href{@value{DOS2UNIX-FTP},,,@value{DOS2UNIX-FTP}} -@end ifset -@ifclear use-html -@value{DOS2UNIX-FTP} -@end ifclear - -You @b{must} change the format of every patched file -for the toolset build to work correctly. - -@subsection Files Needed - -This section lists the files required to build and install -a Windows hosted GNU cross development toolset and their -home WWW site. In addition to the sources required -for the cross environment listed earlier in @ref{Get All the Pieces}, -you will need to download the following -files from their respective sites using your favorite -Web browser or ftp client. - -@table @b - -@item cdk.exe -@ifset use-html -@href{@value{CYGWIN-FTP},,@value{CYGWIN-FTP}} -@end ifset -@ifclear use-html -@value{CYGWIN-FTP} -@end ifclear - -@item coolview.tar.gz -@ifset use-html -@href{@value{CYGWIN-COOLVIEW},,@value{CYGWIN-COOLVIEW}} -@end ifset -@ifclear use-html -@value{CYGWIN-COOLVIEW} -@end ifclear - -@end table - -@subsection System Requirements - -Although the finished cross-compiler is fairly easy on resources, -building it can take a significant amount of processing power and -disk space. The recommended build system spec is: - -@enumerate - -@item An AMD K6-300, Pentium II-300 or better processor. GNU C and Cygwin32 are -@b{very} CPU hungry. - -@item At least 64MB of RAM. - -@item At least 400MB of FAT16 disk space or 250MB if you have an NTFS partition. - -@end enumerate - -Even with this spec of machine expect the full suite to take over 2 hours to -build with a further half an hour for RTEMS itself. - - -@section Installing Cygwin32 B19 - -This section describes the process of installing the -version @value{CYGWIN-VERSION} of the Cygwin32 environment. It assumes -that this toolset is installed in a directory -referred to as @code{<RTOS>}. - -@enumerate - -@item Execute cdk.exe. These instructions assume that you -install Cygwin32 under the <RTOS>\cygnus\b19 directory. - -@item Execute Cygwin.bat (either on the start menu or -under <RTOS>\cygnus\b19). - -@item At this point, you are at the command line of @code{bash}, -a Unix-like shell. You have to mount the "/" directory. Type: - -@example -umount / -mount -b <RTOS> / -@end example - -For example, the following sequence mounts the @code{E:\unix} as the -root directory for the Cygwin32 environment. Note the use of two @code{\}s -when specifying DOS paths in bash: - -@example -umount / -mount -b e:\\unix / -@end example - -@item Create the /bin, /tmp, /source and /build directories. - -@example -mkdir /bin -mkdir /tmp -mkdir /source -mkdir /build -mkdir /build/binutils -mkdir /build/egcs -@end example - -@item The light Bourne shell provided with Cygwin B19 is buggy. -You should copy it to a fake name and copy @code{bash.exe} to @code{sh.exe}: - -@example -cd <RTOS>/cygnus/b19/H-i386-cygwin32/bin -mv sh.exe old_sh.exe -cp bash.exe sh.exe -@end example - -The Bourne shell has to be present in /bin directory to run shell scripts properly: - -@example -cp <RTOS>/cygnus/b19/H-i386-cygwin32/bin/sh.exe /bin -cp <RTOS>/cygnus/b19/H-i386-cygwin32/bin/bash.exe /bin -@end example - - -@item Open the file -@code{/cygnus/b19/H-i386-cygwin32/lib/gcc-lib/i386-cygwin32/2.7-b19/specs}, -and change the following line: - -@example --lcygwin %@{mwindows:-luser32 -lgdi32 -lcomdlg32@} -lkernel32 -@end example - -to: - -@example --lcygwin %@{mwindows:-luser32 -lgdi32 -lcomdlg32@} -lkernel32 -ladvapi32 -@end example - -@end enumerate - -At this point, you have a native installation of Cygwin32 and -are ready to proceed to building a cross-compiler. - -@c -@c BINUTILS -@c - -@section Installing binutils - -@enumerate - -@item Unarchive @value{BINUTILS-TAR} following the -instructions in @ref{Unarchiving the Tools} into the /source directory. -Apply the appropriate RTEMS specific patch as detailed in -@ref{Apply RTEMS Patch to binutils}. - -@item In the @code{/build/binutils} directory, execute the following -command to configure @value{BINUTILS-VERSION}: - -@example -/source/@value{BINUTILS-UNTAR}/configure --verbose --target=m68k-rtems \ - --prefix=/gcc-m68k-rtems --with-gnu-as --with-gnu-ld -@end example - -Replace @code{m68k-rtems} with the target configuration -of your choice. See @ref{Running the bit Script} for a -list of the targets available. - -@item Execute the following command to compile the toolset: - -@example -make -@end example - -@item Install the full package with the following command: - -@example -make -k install -@end example - -There is a problem with the gnu info package which will cause an -error during installation. Telling make to keep going with -k allows -the install to complete. - -@item In the @code{cygnus.bat} file, add the directory -containing the cross-compiler executables to your search path -by inserting the following line: - -@example -PATH=E:\unix\gcc-m68k-rtems\bin;%PATH% -@end example - -@item You can erase the /build/binutils directory content if -disk space is tight. - -@item Exit bash and run @code{cygnus.bat} to restart -the Cygwin32 environment with the new path. - -@end enumerate - -@c -@c EGCS -@c - -@section Installing EGCS AND NEWLIB - -@enumerate -@item Unarchive and patch @value{EGCS-TAR} and @value{NEWLIB-TAR} -following the instructions in @ref{Unarchiving the Tools}. -Apply the appropriate RTEMS specific patches as detailed in -@ref{Apply RTEMS Patch to EGCS} and @ref{Apply RTEMS Patch to newlib}. - -@b{NOTE}: See @ref{Bug in Patch Utility}. - -@item Remove the following directories (we cannot use Fortran -or Objective-C as Cygwin32 cross-compilers): - -@example -/source/@value{GCC-UNTAR}/libf2c -/source/@value{GCC-UNTAR}/gcc/objc -/source/@value{GCC-UNTAR}/gcc/f -@end example - -@b{NOTE}: See @ref{Bug in Patch Utility}. - -@item Link the following directories from Newlib to the main EGCS directory, -/source/@value{GCC-UNTAR}/ : - -@itemize @bullet -@item ln -s ../@value{NEWLIB-UNTAR}/newlib newlib -@item ln -s ../@value{NEWLIB-UNTAR}/libgloss libgloss -@end itemize - -@item Change to the /build/egcs directory to configure the compiler: - -@example -/source/@value{GCC-UNTAR}/configure --verbose --target=m68k-rtems \ - --prefix=/gcc-m68k --with-gnu-as --with-gnu-ld \ - --with-newlib -@end example - -Replace @code{m68k-rtems} with the target configuration -of your choice. See @ref{Running the bit Script} for a -list of the targets available. - -@item Compile the toolset as follows: - -@example -make cross -@end example - -You must do a @code{make cross} (not a simple @code{make}) -to insure that the different packages are built in the correct -order. Making the compiler can take several hours even on -fairly fast machines, beware. - -@item Install with the following command: - -@example -make -k install -@end example - -@item Just as with binutils package, a problem with the gnu -info package not building correctly requires that you use -k to -keep going. - -@example -make -k install -@end example - -@end enumerate - -With any luck, at this point you having a working cross-compiler. So -as Geoffroy said: - -@center @b{That's it! Celebrate!} - diff --git a/doc/started/pictures/bit_ada.jpg b/doc/started/pictures/bit_ada.jpg Binary files differdeleted file mode 100644 index 774b103711..0000000000 --- a/doc/started/pictures/bit_ada.jpg +++ /dev/null diff --git a/doc/started/pictures/bit_ada.vsd b/doc/started/pictures/bit_ada.vsd Binary files differdeleted file mode 100644 index 51e8e1fe53..0000000000 --- a/doc/started/pictures/bit_ada.vsd +++ /dev/null diff --git a/doc/started/pictures/bit_c.jpg b/doc/started/pictures/bit_c.jpg Binary files differdeleted file mode 100644 index 158beb4bd1..0000000000 --- a/doc/started/pictures/bit_c.jpg +++ /dev/null diff --git a/doc/started/pictures/bit_c.vsd b/doc/started/pictures/bit_c.vsd Binary files differdeleted file mode 100644 index a6db26bd15..0000000000 --- a/doc/started/pictures/bit_c.vsd +++ /dev/null diff --git a/doc/started/pictures/scfile10.jpg b/doc/started/pictures/scfile10.jpg Binary files differdeleted file mode 100644 index 22a83877ce..0000000000 --- a/doc/started/pictures/scfile10.jpg +++ /dev/null diff --git a/doc/started/pictures/scfile10.vsd b/doc/started/pictures/scfile10.vsd Binary files differdeleted file mode 100644 index 07efb1f18b..0000000000 --- a/doc/started/pictures/scfile10.vsd +++ /dev/null diff --git a/doc/started/pictures/scfile11.jpg b/doc/started/pictures/scfile11.jpg Binary files differdeleted file mode 100644 index f70986ef55..0000000000 --- a/doc/started/pictures/scfile11.jpg +++ /dev/null diff --git a/doc/started/pictures/scfile11.vsd b/doc/started/pictures/scfile11.vsd Binary files differdeleted file mode 100644 index 25871be19a..0000000000 --- a/doc/started/pictures/scfile11.vsd +++ /dev/null diff --git a/doc/started/pictures/scfile12.jpg b/doc/started/pictures/scfile12.jpg Binary files differdeleted file mode 100644 index 22a83877ce..0000000000 --- a/doc/started/pictures/scfile12.jpg +++ /dev/null diff --git a/doc/started/pictures/scfile12.vsd b/doc/started/pictures/scfile12.vsd Binary files differdeleted file mode 100644 index 750e7cdf56..0000000000 --- a/doc/started/pictures/scfile12.vsd +++ /dev/null diff --git a/doc/started/pictures/scfile13.jpg b/doc/started/pictures/scfile13.jpg Binary files differdeleted file mode 100644 index 7ea418b7a7..0000000000 --- a/doc/started/pictures/scfile13.jpg +++ /dev/null diff --git a/doc/started/pictures/scfile13.vsd b/doc/started/pictures/scfile13.vsd Binary files differdeleted file mode 100644 index 581eff901c..0000000000 --- a/doc/started/pictures/scfile13.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile1.jpg b/doc/started/pictures/scsfile1.jpg Binary files differdeleted file mode 100644 index d1d497e955..0000000000 --- a/doc/started/pictures/scsfile1.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile1.vsd b/doc/started/pictures/scsfile1.vsd Binary files differdeleted file mode 100644 index a7314848fc..0000000000 --- a/doc/started/pictures/scsfile1.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile2.jpg b/doc/started/pictures/scsfile2.jpg Binary files differdeleted file mode 100644 index afbe1db125..0000000000 --- a/doc/started/pictures/scsfile2.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile2.vsd b/doc/started/pictures/scsfile2.vsd Binary files differdeleted file mode 100644 index d2bb29a6e8..0000000000 --- a/doc/started/pictures/scsfile2.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile3.jpg b/doc/started/pictures/scsfile3.jpg Binary files differdeleted file mode 100644 index b0e135994d..0000000000 --- a/doc/started/pictures/scsfile3.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile3.vsd b/doc/started/pictures/scsfile3.vsd Binary files differdeleted file mode 100644 index da98158c85..0000000000 --- a/doc/started/pictures/scsfile3.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile4.jpg b/doc/started/pictures/scsfile4.jpg Binary files differdeleted file mode 100644 index 1c01cbb460..0000000000 --- a/doc/started/pictures/scsfile4.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile4.vsd b/doc/started/pictures/scsfile4.vsd Binary files differdeleted file mode 100644 index 50823fa67e..0000000000 --- a/doc/started/pictures/scsfile4.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile5.jpg b/doc/started/pictures/scsfile5.jpg Binary files differdeleted file mode 100644 index 8fe8df173c..0000000000 --- a/doc/started/pictures/scsfile5.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile5.vsd b/doc/started/pictures/scsfile5.vsd Binary files differdeleted file mode 100644 index 614736593a..0000000000 --- a/doc/started/pictures/scsfile5.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile6.jpg b/doc/started/pictures/scsfile6.jpg Binary files differdeleted file mode 100644 index 58a3489242..0000000000 --- a/doc/started/pictures/scsfile6.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile6.vsd b/doc/started/pictures/scsfile6.vsd Binary files differdeleted file mode 100644 index a970df509a..0000000000 --- a/doc/started/pictures/scsfile6.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile7.jpg b/doc/started/pictures/scsfile7.jpg Binary files differdeleted file mode 100644 index 68cff033b8..0000000000 --- a/doc/started/pictures/scsfile7.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile7.vsd b/doc/started/pictures/scsfile7.vsd Binary files differdeleted file mode 100644 index 0af5ae9f4f..0000000000 --- a/doc/started/pictures/scsfile7.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile8.jpg b/doc/started/pictures/scsfile8.jpg Binary files differdeleted file mode 100644 index a2ef5954ca..0000000000 --- a/doc/started/pictures/scsfile8.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile8.vsd b/doc/started/pictures/scsfile8.vsd Binary files differdeleted file mode 100644 index 0ed6dedf6d..0000000000 --- a/doc/started/pictures/scsfile8.vsd +++ /dev/null diff --git a/doc/started/pictures/scsfile9.jpg b/doc/started/pictures/scsfile9.jpg Binary files differdeleted file mode 100644 index 04f623e62d..0000000000 --- a/doc/started/pictures/scsfile9.jpg +++ /dev/null diff --git a/doc/started/pictures/scsfile9.vsd b/doc/started/pictures/scsfile9.vsd Binary files differdeleted file mode 100644 index ca3222b4cf..0000000000 --- a/doc/started/pictures/scsfile9.vsd +++ /dev/null diff --git a/doc/started/pictures/sfile12c.jpg b/doc/started/pictures/sfile12c.jpg Binary files differdeleted file mode 100644 index aba5bf21a2..0000000000 --- a/doc/started/pictures/sfile12c.jpg +++ /dev/null diff --git a/doc/started/pictures/sfile12c.vsd b/doc/started/pictures/sfile12c.vsd Binary files differdeleted file mode 100644 index fc0616cf1e..0000000000 --- a/doc/started/pictures/sfile12c.vsd +++ /dev/null diff --git a/doc/started/require.t b/doc/started/require.t deleted file mode 100644 index 9ac3d2033f..0000000000 --- a/doc/started/require.t +++ /dev/null @@ -1,56 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Requirements - -A fairly large amount of disk space is required to perform the build of the -GNU C/C++ Cross Compiler Tools for RTEMS. The following table may help in -assessing the amount of disk space required for your installation: - -@example -+----------------------------------------+------------------------------+ -| Component | Disk Space Required | -+----------------------------------------+------------------------------+ -| archive directory | 30 Mbytes | -| tools src unzipped | 100 Mbytes | -| each individual build directory | 300 Mbytes worst case | -| each installation directory | 20-400 Mbytes | -+----------------------------------------+------------------------------+ -@end example - -The disk space required for each installation directory depends -primarily on the number of RTEMS BSPs which are to be installed. -If a single BSP is installed, then the size of each install directory -will tend to be in the 40-60 Mbyte range. - -The instructions in this manual should work on any computer running -a UNIX variant. Some native GNU tools are used by this procedure -including: - -@itemize @bullet -@item GCC -@item GNU make -@item GNU makeinfo -@end itemize - -In addition, some native utilities may be deficient for building -the GNU tools. - -@section GNU makeinfo Version Requirements - -In order to build egcs 1.1b or newer, the GNU @code{makeinfo} program -installed on your system must be at least version 1.68. The appropriate -version of @code{makeinfo} is distributed with egcs 1.1b. - -The following demonstrates how to determine the version of @code{makeinfo} -on your machine: - -@example -makeinfo --version -@end example - diff --git a/doc/started/sample.t b/doc/started/sample.t deleted file mode 100644 index b2910319bc..0000000000 --- a/doc/started/sample.t +++ /dev/null @@ -1,57 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@chapter Building the Sample Application - -@section Unpack the Sample Application - -Use the following command to unarchive the sample application: - -@example -cd tools -tar xzf ../archive/hello_world_c.tgz -@end example - -@section Set the Environment Variable RTEMS_MAKEFILE_PATH - -It must point to the appropriate directory containing RTEMS build for our -target and board support package combination. - -@example -export RTEMS_MAKEFILE_PATH = \ -<INSTALLATION_POINT>/rtems/<BOARD_SUPPORT_PACKAGE> -@end example - -Where <INSTALLATION_POINT> and <BOARD_SUPPORT_PACKAGE> are those used when -configuring and installing RTEMS. - -@section Build the Sample Application - -Use the following command to start the build of the sample application: - -@example -cd tools/hello_world_c -gmake -@end example - -If no errors are detected during the sample application build, it is -reasonable to assume that the build of the GNU C/C++ Cross Compiler Tools -for RTEMS and RTEMS itself for the selected host and target -combination was done properly. - -@section Application Executable - -If the sample application has successfully been build, then the application -executable is placed in the following directory: - -@example -tools/hello_world_c/o-<BOARD_SUPPORT_PACKAGE>/<filename>.exe -@end example - -How this executable is downloaded to the target board is very dependent -on the BOARD_SUPPORT_PACKAGE selected. diff --git a/doc/started/started.texi b/doc/started/started.texi deleted file mode 100644 index 3ed67ec472..0000000000 --- a/doc/started/started.texi +++ /dev/null @@ -1,117 +0,0 @@ -\input ../texinfo/texinfo @c -*-texinfo-*- -@c %**start of header -@setfilename started -@syncodeindex vr fn -@synindex ky cp -@paragraphindent 0 -@c @smallbook -@c %**end of header - -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c Master file for the Getting Started (C) Guide -@c - -@include ../common/setup.texi - -@c -@c Now set all the tool version dependent information -@c -@include versions.texi - -@ignore -@ifinfo -@format -START-INFO-DIR-ENTRY -* Getting Started with RTEMS for C/C++ Users (started): -END-INFO-DIR-ENTRY -@end format -@end ifinfo -@end ignore - -@c -@c Title Page Stuff -@c - -@set edition @value{RTEMS-EDITION} -@set version @value{RTEMS-VERSION} -@set update-date @value{RTEMS-UPDATE-DATE} -@set update-month @value{RTEMS-UPDATE-MONTH} - -@c -@c I don't really like having a short title page. --joel -@c -@c @shorttitlepage Getting Started with RTEMS - -@setchapternewpage odd -@settitle Getting Started with RTEMS for C/C++ Users -@titlepage -@finalout - -@title Getting Started with RTEMS for C/C++ Users -@subtitle Edition @value{edition}, for @value{version} -@sp 1 -@subtitle @value{update-month} -@author On-Line Applications Research Corporation -@page -@include ../common/cpright.texi -@end titlepage - -@c This prevents a black box from being printed on "overflow" lines. -@c The alternative is to rework a sentence to avoid this problem. - -@include intro.texi -@include require.texi -@include buildc.texi -@include buildrt.texi -@include sample.texi -@include gdb.texi -@include nt.texi - -@ifinfo -@node Top, Introduction, (dir), (dir) -@top started - -This is the online version of the Getting Started with RTEMS for C/C++ Users. - -@menu -* Introduction:: -* Requirements:: -* Building the GNU C/C++ Cross Compiler Toolset:: -* Building RTEMS:: -* Building the Sample Application:: -* Building the GNU Debugger:: -* Using MS-Windows as a Development Host:: -@end menu - -@c * Command and Variable Index:: -@c * Concept Index:: -@end ifinfo -@c -@c -@c Need to copy the emacs stuff and "trailer stuff" (index, toc) into here -@c - -@c @node Command and Variable Index, Concept Index, Installing EGCS AND NEWLIB, Top -@c @unnumbered Command and Variable Index - -@c There are currently no Command and Variable Index entries. - -@c @printindex fn - -@c @node Concept Index, , Command and Variable Index, Top -@c @unnumbered Concept Index - -@c There are currently no Concept Index entries. -@c @printindex cp - -@contents -@bye - diff --git a/doc/started/versions.texi b/doc/started/versions.texi deleted file mode 100644 index 63bca0f05b..0000000000 --- a/doc/started/versions.texi +++ /dev/null @@ -1,86 +0,0 @@ -@c -@c COPYRIGHT (c) 1988-1998. -@c On-Line Applications Research Corporation (OAR). -@c All rights reserved. -@c -@c $Id$ -@c - -@c -@c This file contains all toolset version dependent information -@c - -@c -@c Comment out setting the "XYZ-RTEMSPATCH" variable if there is no -@c patch required. The documentation will detect this and print -@c an appropriate message in a short section. -@c - - -@c -@c GCC/EGCS Version -@c - -@set GCC-VERSION egcs 1.1b -@set GCC-TAR egcs-1.1b.tar.gz -@set GCC-UNTAR egcs-1.1b -@set GCC-FTPSITE egcs.cygnus.com -@set GCC-FTPDIR /pub/egcs/releases/egcs-1.1b -@set GCC-HTTPDIR /pub/egcs/releases/index.html -@set GCC-RTEMSPATCH egcs-1.1b-rtems-diff-19981027.gz - -@c -@c BINUTILS Version -@c - -@c The "official" binutils -@set BINUTILS-VERSION binutils 2.9.1 -@set BINUTILS-TAR binutils-2.9.1.tar.gz -@set BINUTILS-UNTAR binutils-2.9.1 -@set BINUTILS-FTPSITE ftp.gnu.org -@set BINUTILS-FTPDIR /pub/gnu -@set BINUTILS-RTEMSPATCH binutils-2.9.1-rtems-diff-19981027.gz - -@c When forced to use a snapshot -@c @set BINUTILS-VERSION gas 980314 -@c @set BINUTILS-TAR gas-980314.tgz -@c @set BINUTILS-UNTAR gas-980314 -@c @set BINUTILS-FTPSITE ftp.OARcorp.com -@c @set BINUTILS-FTPDIR /oarcorp/private/beta3/ada_tools -@c @set BINUTILS-RTEMSPATCH binutils-2.8.1-rtems-diff-1998xxxx.gz - -@c -@c NEWLIB Version -@c - -@set NEWLIB-VERSION newlib 1.8.0 -@set NEWLIB-TAR newlib-1.8.0.tar.gz -@set NEWLIB-UNTAR newlib-1.8.0 -@set NEWLIB-FTPSITE ftp.cygnus.com -@set NEWLIB-FTPDIR /pub/newlib -@set NEWLIB-RTEMSPATCH newlib-1.8.0-rtems-diff-19981027.gz - -@c -@c GDB Version -@c - -@set GDB-VERSION gdb 4.17 -@set GDB-TAR gdb-4.17.tar.gz -@set GDB-UNTAR gdb-4.17 -@set GDB-FTPSITE ftp.gnu.org -@set GDB-FTPDIR /pub/gnu -@set GDB-RTEMSPATCH gdb-4.17-rtems-diff-19981027.gz - - -@c -@c RTEMS Version -@c - -@set RTEMS-VERSION RTEMS 4.0.0 -@set RTEMS-TAR rtems-4.0.0.tgz -@set RTEMS-UNTAR rtems-4.0.0 -@set RTEMS-FTPSITE ftp.OARcorp.com -@set RTEMS-FTPDIR /pub/rtems/4.0.0 -@set BUILDTOOLS-TAR c_build_scripts-4.0.0.tgz - - |
