1 | .. comment SPDX-License-Identifier: CC-BY-SA-4.0 |
---|
2 | |
---|
3 | .. COMMENT: COPYRIGHT (c) 1988-2002. |
---|
4 | .. COMMENT: On-Line Applications Research Corporation (OAR). |
---|
5 | .. COMMENT: All rights reserved. |
---|
6 | |
---|
7 | Preface |
---|
8 | ******* |
---|
9 | |
---|
10 | The Real Time Executive for Multiprocessor Systems (RTEMS) is designed to be |
---|
11 | portable across multiple processor architectures. However, the nature of |
---|
12 | real-time systems makes it essential that the application designer understand |
---|
13 | certain processor dependent implementation details. These processor |
---|
14 | dependencies include calling convention, board support package issues, |
---|
15 | interrupt processing, exact RTEMS memory requirements, performance data, header |
---|
16 | files, and the assembly language interface to the executive. |
---|
17 | |
---|
18 | Each architecture represents a CPU family and usually there are a wide variety |
---|
19 | of CPU models within it. These models share a common Instruction Set |
---|
20 | Architecture (ISA) which often varies based upon some well-defined rules. |
---|
21 | There are often multiple implementations of the ISA and these may be from one |
---|
22 | or multiple vendors. |
---|
23 | |
---|
24 | On top of variations in the ISA, there may also be variations which occur when |
---|
25 | a CPU core implementation is combined with a set of peripherals to form a |
---|
26 | system on chip. For example, there are many ARM CPU models from numerous |
---|
27 | semiconductor vendors and a wide variety of peripherals. But at the ISA level, |
---|
28 | they share a common compatibility. |
---|
29 | |
---|
30 | RTEMS depends upon this core similarity across the CPU models and leverages |
---|
31 | that to minimize the source code that is specific to any particular CPU core |
---|
32 | implementation or CPU model. |
---|
33 | |
---|
34 | This manual is separate and distinct from the RTEMS Porting Guide. That manual |
---|
35 | is a guide on porting RTEMS to a new architecture. This manual is focused on |
---|
36 | the more mundane CPU architecture specific issues that may impact application |
---|
37 | development. For example, if you need to write a subroutine in assembly |
---|
38 | language, it is critical to understand the calling conventions for the target |
---|
39 | architecture. |
---|
40 | |
---|
41 | The first chapter in this manual describes these issues in general terms. In a |
---|
42 | sense, it is posing the questions one should be aware may need to be answered |
---|
43 | and understood when porting an RTEMS application to a new architecture. Each |
---|
44 | subsequent chapter gives the answers to those questions for a particular CPU |
---|
45 | architecture. |
---|