source: rtems/doc/bsp_howto/target.t @ f96e8ee

4.104.114.84.95
Last change on this file since f96e8ee was f96e8ee, checked in by Joel Sherrill <joel.sherrill@…>, on 08/28/98 at 13:27:36

Added CVS Ids.

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