BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
NOTE: In general, the project facility is designed to increase flexibility when
selecting components, that is, to increase scalability; specifying a REQUIRES
relationship reduces flexibility. Be sure that using REQUIRES is the best course of
action in your situation before implementing it.
Step 7:
List Associated Parameters
In the component object, use the CFG_PARAMS property to declare all associated
parameters, for example, FOO_MAX_COUNT.
...
CFG_PARAMS
...
FOO_MAX_COUNT
Step 8:
Define Parameters
For each parameter declared by CFG_PARAMS, create a parameter object to
describe it. Provide a name using the NAME property.
Use the TYPE property to specify the data type, either int, uint, bool, string, exists,
or untyped.
Use the DEFAULT property to specify a default value for each parameter.
Parameter FOO_MAX_COUNT {
NAME
Foo maximum
TYPE
uint
DEFAULT 50
}
! CAUTION: A component is considered misconfigured if it contains a parameter
without an assigned value. Be sure to assign default values, unless there is no
reasonable default and you want to force the user to set it explicitly.
Step 9:
Define Group Membership
A component must be associated with either a folder or selection, otherwise it is
not visible in the project facility GUI. Assign a component to a folder because of its
logical inclusion in the group defined by the folder, based on similar or shared
functionality, for example. By including a component in a folder, you make it
possible for the user to load it simultaneously with other components in its group
by declaring them as default values for the folder, using the folder object’s
DEFAULTS property.
...
_CHILDREN
...
FOLDER_ROOT
132