blob: c405c7ee52bf08d07d0def812cb1381e37f3cf87 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
|
@c
@c COPYRIGHT (c) 1988-1998.
@c On-Line Applications Research Corporation (OAR).
@c All rights reserved.
@c
@c $Id$
@c
@chapter Target Dependent and Board Dependent Files
RTEMS divides board dependencies into two parts :
@itemize @bullet
@item the CPU dependant code : it provides basics calls to the kernel,
just as the context switch or the interrupt subroutine implementations.
Sources for the supported families of processors can be found in
$RTEMS_ROOT/c/src/exec/score/cpu. A good starti ng point for a new family
of processors is the no_cpu directory, which holds both prototypes and
descriptions of each needed CPU dependant function.
@item the board dependant code : it includes support for a given board,
such as the board initialization code and drivers for the various devices:
@end itemize
Porting RTEMS on a new board should raise two questions:
@itemize @bullet
@item is the main board CPU supported ?
@item does a BSP for a similar board exists ?
@end itemize
If the main board CPU is supported, you will only have do write the Board
Support Package. Otherwise you'll have to write both CPU dependant code
and the BSP. One should always start writing a BSP from a similar one.
|
