source: rtems-docs/cpu-supplement/preface.rst

Last change on this file was e52906b, checked in by Sebastian Huber <sebastian.huber@…>, on 01/09/19 at 15:14:06

Simplify SPDX-License-Identifier comment

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