BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
Step 3:
Set Up Initialization
If your component must be initialized, use the INIT_RTN property of the
component object class to specify the initialization routine and its arguments to be
called, as in fooInit(arg1, arg2). If your component needs more than a single line of
initialization, create or add the initialization code to a .c file and use the
CONFIGLETTES property instead. By associating a configlette with an
initialization routine, you are securing the configlettes place in the initialization
sequence.
...
INIT_RTN
...
fooInit(arg1, arg2);
If you are not using the MODULES property of the component object, use the
LINK_SYMS property to include your object module from a linked archive. The
system generates an unresolved reference to the symbol _fooRtn1, causing the
linker to resolve it by extracting your module from the archive.
...
LINK_SYMS
...
_fooRtn1
Step 4:
Establish the Initialization Sequence
Initialization order is important. You can control when in the initialization
sequence your component is initialized with the _INIT_ORDER property. A
component (or initGroup) that is bound to an existing initGroup using the
_INIT_ORDER property is, by default, initialized last within that group. This is
typically the desired effect; however, you can override this behavior by explicitly
using the INIT_BEFORE property.
...
_INIT_ORDER
INIT_BEFORE
...
usrRoot
INCLUDE_USER_APPL
In the example, INCLUDE_FOO is declared a member of the usrRoot initGroup.
INIT_BEFORE has been used for fine control, and INCLUDE_FOO is initialized
before INCLUDE_USER_APPL.
Alternatively, you can create a new initialization group and declare
INCLUDE_FOO a member; however, you would have to declare the new initGroup
a member of an existing initGroup. For more information on initialization groups,
see E. Component Language.
130