BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
Exist type parameters are #defined if their value is TRUE and #undefined if
FALSE.
DEFAULT
The default value of the parameter, which appears above the list of parameter
IDs in the Params tab of the project facility Properties window, as shown in
Figure 6-3.
Initialization Groups
A component must include information that controls how it is integrated into an
executable “system image,” for example, an initialization routine and a description
of when in the initialization sequence that routine should be called. Initialization
groups or initGroups assemble related components for initialization and, thus,
define the system startup sequence. Initialization group hierarchy is run-time
related only and has no impact on the GUI.
For Tornado 1.0.1, the initialization order was determined in
target/config/all/usrConfig.c or target/src/config/*.c files and surrounded by
#ifdef/#endif statements, as follows:
#if defined(INCLUDE_EXC_HANDLING) && defined(INCLUDE_EXC_TASK)
excInit (); /* initialize exception handling */
#endif /* defined(INCLUDE_EXC_HANDLING) && defined(INCLUDE_EXC_TASK) */
#ifdef INCLUDE_LOGGING
logInit (consoleFd, MAX_LOG_MSGS); /* initialize logging */
#endif /* INCLUDE_LOGGING */
...
The BSP file sysLib.c determined (and still does) the order of most board hardware
initialization.
An initGroup is a routine from which components and other initGroups are called.
The code in the routine is determined by the included components and their
initialization code fragments. For example:
InitGroup usrIosExtraInit {
INIT_RTN usrIosExtraInit ();
SYNOPSIS extended I/O system
INIT_ORDER INCLUDE_EXC_TASK \
INCLUDE_LOGGING \
...
}
124