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 | Introduction |
---|
8 | ############ |
---|
9 | |
---|
10 | Before reading this documentation, it is strongly advised to read the RTEMS |
---|
11 | Development Environment Guide to get acquainted with the RTEMS directory |
---|
12 | structure. This document describes how to do a RTEMS Board Support Package, |
---|
13 | i.e. how to port RTEMS on a new target board. Discussions are provided for the |
---|
14 | following topics: |
---|
15 | |
---|
16 | - RTEMS Board Support Package Organization |
---|
17 | |
---|
18 | - Makefiles and the Linker Command Script |
---|
19 | |
---|
20 | - Board Initialization Sequence |
---|
21 | |
---|
22 | - Device Drivers: |
---|
23 | |
---|
24 | - Console Driver |
---|
25 | - Clock Driver |
---|
26 | - Timer Driver |
---|
27 | - Real-Time Clock Driver |
---|
28 | - Non-Volatile Memory Driver |
---|
29 | - Networking Driver |
---|
30 | - Shared Memory Support Driver |
---|
31 | - Analog Driver |
---|
32 | - Discrete Driver |
---|
33 | |
---|
34 | The original version of this manual was written by Geoffroy Montel |
---|
35 | <g_montel@yahoo.com>. When he started development of the gen68340 |
---|
36 | BSP, this manual did not exist. He wrote the initial version of |
---|
37 | this manual as the result of his experiences. At that time, this |
---|
38 | document was viewed internally as the most important "missing manual" |
---|
39 | in the RTEMS documentation set. |
---|
40 | |
---|
41 | The gen68340 BSP is a good example of the life of an RTEMS BSP. It is |
---|
42 | based upon a part not recommended for new designs and none of the core RTEMS |
---|
43 | Project team members have one of these boards. Thus we are unlikely to |
---|
44 | perform major updates on this BSP. So as long as it compiles and links all |
---|
45 | tests, it will be available. |
---|
46 | |
---|
47 | The RTEMS Project team members are always trying to identify common |
---|
48 | code across BSPs and refactoring the code into shared routines. |
---|
49 | As part of this effort, the we will enhance the common BSP Framework. |
---|
50 | Not surprisingly, not every BSP takes advantage of every feature in |
---|
51 | the framework. The gen68340 does not take advantage of as many features |
---|
52 | as the ERC32 BSP does. So in many ways, the ERC32 is a better example |
---|
53 | BSP at this point. But even the ERC32 BSP does not include examples |
---|
54 | of every driver template and framework available to the BSP author. |
---|
55 | So in this guide we will try to point out good examples from other BSPs. |
---|
56 | |
---|
57 | Our goal is for you to be able to reuse as much code as possible and |
---|
58 | write as little board specific code as possible. |
---|