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