BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
For Tornado 2.x, the same feature captured by the Tornado 1.0.1 code above, would
be written in CDL as follows:
Selection SELECT_TIMESTAMP {
NAME
select timestamping
COUNT 1-1
CHILDREN INCLUDE_SYS_TIMESTAMP \
INCLUDE_USER_TIMESTAMP \
INCLUDE_SEQ_TIMESTAMP
DEFAULTS INCLUDE_SEQ_TIMESTAMP
}
There are three timestamp drivers available, as indicated by the three values for the
CHILDREN property. The COUNT permits a choice of one, that is, a minimum and
a maximum of 1.
Components
The component object class defines the source and object code associated with a
component, much of the integration information, and any associated parameters.
In the project facility, components are represented by the building block icon, as
shown in Figure 6-1.
Previously, this kind of information was included in usrConfig.c or src/config/*
files and surrounded by #ifdef/#endif statements, as follows:
#ifdef INCLUDE_LOGGING
logInit (consoleFd, MAX_LOG_MSGS);
#endif /* INCLUDE_LOGGING */
Tornado 2.x configuration files contain only the information necessary to build the
application or VxWorks, and not all the code related to the hundreds of other
components that could be included. Furthermore, dependencies among
components can be detected and the related components can be automatically
added by the project facility. It does this by analyzing the global symbols in each
associated object module and knowing within which components they are
contained. The same message logging component above could be written in CDL
as follows:
Component INCLUDE_LOGGING {
NAME
message logging
SYNOPSIS Provides logMsg support
MODULES logLib.o
INIT_RTN logInit (consoleFd, MAX_LOG_MSGS);
CFG_PARAMS MAX_LOG_MSGS
HDR_FILES logLib.h
}
120