BSP Developer's Guide

E
Component Language
initialization group. It can also declare that it should be initialized before or after
other components within that group.
The two primary initGroups for project compilation are usrInit and usrRoot. Each
initialization group translates to a C function declaration where the body of the
function is the initialization code from each of the constituent components.
In the initialization sequences that follow, names appearing all in uppercase are
component names. Names appearing in all lowercase are routine names. Each
initialization group has a routine with the same name as the initialization group.
Indentation is used in this chart to represent the hierarchy of the standard
components as defined by Tornado 2.x. When the prjConfig.c file is generated,
each included component is replaced by its initialization code fragment, as defined
in the CDF for that component. Excluded components do not contribute code
fragments to their initialization group.
NOTE: The project facility build process does not apply to boot ROMs. Boot ROMs
for Tornado 2.x can only be built from the traditional command line.
E.3.1 romInit.s
Only used for ROMmed VxWorks images, this assembly code initializes the
processor and memory. This code always ends by calling romStart( ).
E
E.3.2 romStart.c
Only used for ROMmed VxWorks images, this code relocates text and data from
within the ROM itself into RAM. It terminates by calling the routine located at
RAM_DST_ADRS. This is normally the address of usrEntry( ).
E.3.3 usrEntry.c
Only used for ROMmed VxWorks images, this routine does some
architecture-specific initialization and terminates by calling usrInit( ) in
prjConfig.c.
239