
VxWorks
BSP Developer’s Guide, 6.0
26
sysHwInit2( ). These routines are described in 2.3.4 Required Routines, p.32. Also
see the source code in your reference BSP or the template BSP.
While sysLib.c is the largest BSP file, in the early phases of BSP development it is
advisable to implement only the basics, including sysModel( ), sysBspRev( ),
sysHwInit( ), sysHwInit2( ), and sysMemTop( ).
The file sysLib.c also includes the following NVRAM stub drivers during initial
development:
#include "mem/nullNvram.c"
#include "vme/nullVme.c"
Additional information about NVRAM support is provided in 3.3.4 NVRAM, p.74.
The sysHwInit( ) routine is the heart of sysLib.c, and most of the initial work is
done here. sysHwInit( ) is the routine that resets all devices to a quiescent state so
that they do not generate interrupts later on when interrupts are enabled.
target.ref or target.nr
This file describes the BSP, and is used to generate automatic online documentation
in HTML format. To format the documentation as HTML, type make man in the
BSP directory.
For more information on updating and using this file, see 3.3.8 Updating
BSP-Specific Documentation, p.98, and B. Documentation Guidelines.
board.jpg
This optional file contains a JPEG image of the target system board. You may wish
to label the images to show the serial connector, power connector, and Ethernet
connector.
sysDev.c
Each device driver available for target hardware has its own sysDev.c file, where
Dev is a short identifier for the target hardware. For example, sysNet.c and
NOTE: When hardware features are missing, it is usually safe to code an empty
stub in sysLib.c. If any return value is required, the stub can return
ERROR or
NULL, whichever is appropriate.
Comentarios a estos manuales