forked from Imagelibrary/rtems
Added BSP chapter to FAQ.
This commit is contained in:
@@ -65,6 +65,7 @@ END-INFO-DIR-ENTRY
|
||||
@include basic.texi
|
||||
@include tools.texi
|
||||
@include concepts.texi
|
||||
@include bsp.texi
|
||||
@include debug.texi
|
||||
@include freesw.texi
|
||||
@include embeddedinfo.texi
|
||||
@@ -85,6 +86,7 @@ Common questions have been divided into the following categories.
|
||||
* Basic Information::
|
||||
* General Development Tool Hints::
|
||||
* RTEMS Concepts::
|
||||
* BSP Questions::
|
||||
* Debugging Hints::
|
||||
* Free Software that Works with RTEMS::
|
||||
* Resources for Embedded Information::
|
||||
|
||||
@@ -18,7 +18,7 @@ dirs:
|
||||
COMMON_FILES=../common/cpright.texi ../common/setup.texi
|
||||
|
||||
GENERATED_FILES= \
|
||||
basic.texi tools.texi concepts.texi debug.texi freesw.texi \
|
||||
basic.texi tools.texi concepts.texi bsp.texi debug.texi freesw.texi \
|
||||
embeddedinfo.texi hwdebugaids.texi
|
||||
|
||||
FILES=$(PROJECT).texi $(GENERATED_FILES)
|
||||
@@ -75,6 +75,11 @@ concepts.texi: concepts.t Makefile
|
||||
-u "Top" \
|
||||
-n "" ${*}.t
|
||||
|
||||
bsp.texi: bsp.t Makefile
|
||||
$(BMENU) -c -p "" \
|
||||
-u "Top" \
|
||||
-n "" ${*}.t
|
||||
|
||||
debug.texi: debug.t Makefile
|
||||
$(BMENU) -c -p "" \
|
||||
-u "Top" \
|
||||
|
||||
35
doc/FAQ/bsp.t
Normal file
35
doc/FAQ/bsp.t
Normal file
@@ -0,0 +1,35 @@
|
||||
@c
|
||||
@c COPYRIGHT (c) 1988-1998.
|
||||
@c On-Line Applications Research Corporation (OAR).
|
||||
@c All rights reserved.
|
||||
@c
|
||||
@c $Id$
|
||||
@c
|
||||
|
||||
@chapter BSP Questions
|
||||
|
||||
The items in this category provide answers to questions
|
||||
commonly asked about BSPs.
|
||||
|
||||
@section What is a BSP?
|
||||
|
||||
BSP is an acronym for Board Support Package.
|
||||
|
||||
A BSP is a collection of device drivers, startup code, linker scripts,
|
||||
and compiler support files (specs files) that tailor RTEMS for a
|
||||
particular target hardware environment.
|
||||
|
||||
@section What has to be in a BSP?
|
||||
|
||||
The basic set of items is the linker script, bsp_specs, and startup code.
|
||||
If you want standard IO, then you need a console driver. This is needed
|
||||
to run any of the RTEMS tests. If you want to measure passage of time,
|
||||
you need a clock tick driver. This driver is needed for all RTEMS tests
|
||||
EXCEPT hello world and the timing tests. The timer driver is a benchmark
|
||||
timer and is needed for the tmtests (timing tests). Sometimes you will
|
||||
see a shmsupp directory which is for shared memory multiprocessing
|
||||
systems. The network driver and real-time clock drivers are optional
|
||||
and not reqired by any RTEMS tests.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user