1 | @c |
---|
2 | @c COPYRIGHT (c) 1988-1999. |
---|
3 | @c On-Line Applications Research Corporation (OAR). |
---|
4 | @c All rights reserved. |
---|
5 | @c |
---|
6 | @c $Id$ |
---|
7 | @c |
---|
8 | |
---|
9 | @ifinfo |
---|
10 | @node Preface, Development Tools, Top, Top |
---|
11 | @end ifinfo |
---|
12 | @unnumbered Preface |
---|
13 | |
---|
14 | The purpose of this manual is to provide a roadmap to those people porting |
---|
15 | RTEMS to a new CPU family. This process includes a variety of activities |
---|
16 | including the following: |
---|
17 | |
---|
18 | @itemize @bullet |
---|
19 | |
---|
20 | @item targeting the GNU development tools |
---|
21 | |
---|
22 | @item porting the RTEMS executive code |
---|
23 | |
---|
24 | @item developing a Board Support Package |
---|
25 | |
---|
26 | @item writing an RTEMS CPU Supplement manual for the completed port. |
---|
27 | |
---|
28 | @end itemize |
---|
29 | |
---|
30 | This document focuses on the process of actually porting the RTEMS |
---|
31 | executive code proper. Each of the data structures, routines, and macro |
---|
32 | definitions required of a port of RTEMS is described in this document. |
---|
33 | |
---|
34 | Porting any operating system, including RTEMS, requires knowledge of the |
---|
35 | operating system, target CPU architecture, and debug environment. It is |
---|
36 | very desirable to have a CPU simulator or hardware emulator when debugging |
---|
37 | the port. This manual assumes that the user is familiar with building and |
---|
38 | using RTEMS, the C programming language, and the target CPU architecture. |
---|
39 | It is desirable to be familiar with the assembly language for the target |
---|
40 | CPU family but since only a limited amount of assembly is required to port |
---|
41 | RTEMS. |
---|
42 | |
---|