forked from Imagelibrary/rtems
6449498bc7
* SUPPORT, LICENSE: New files. * Numerous files touched as part of merging the 4.5 branch onto the mainline development trunk and ensuring that the script that cuts snapshots and releases works on the documentation.
43 lines
1.3 KiB
Plaintext
43 lines
1.3 KiB
Plaintext
@c
|
|
@c COPYRIGHT (c) 1988-2002.
|
|
@c On-Line Applications Research Corporation (OAR).
|
|
@c All rights reserved.
|
|
@c
|
|
@c $Id$
|
|
@c
|
|
|
|
@ifinfo
|
|
@node Preface, Development Tools, Top, Top
|
|
@end ifinfo
|
|
@unnumbered Preface
|
|
|
|
The purpose of this manual is to provide a roadmap to those people porting
|
|
RTEMS to a new CPU family. This process includes a variety of activities
|
|
including the following:
|
|
|
|
@itemize @bullet
|
|
|
|
@item targeting the GNU development tools
|
|
|
|
@item porting the RTEMS executive code
|
|
|
|
@item developing a Board Support Package
|
|
|
|
@item writing an RTEMS CPU Supplement manual for the completed port.
|
|
|
|
@end itemize
|
|
|
|
This document focuses on the process of actually porting the RTEMS
|
|
executive code proper. Each of the data structures, routines, and macro
|
|
definitions required of a port of RTEMS is described in this document.
|
|
|
|
Porting any operating system, including RTEMS, requires knowledge of the
|
|
operating system, target CPU architecture, and debug environment. It is
|
|
very desirable to have a CPU simulator or hardware emulator when debugging
|
|
the port. This manual assumes that the user is familiar with building and
|
|
using RTEMS, the C programming language, and the target CPU architecture.
|
|
It is desirable to be familiar with the assembly language for the target
|
|
CPU family but since only a limited amount of assembly is required to port
|
|
RTEMS.
|
|
|