BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
following subsections is required to ensure smooth integration of the BSP into the
VxWorks development system.
BSP Contents
Determining the files and directories that are delivered as part of a BSP product is
one of the last and most important steps in creating a BSP. The BSP must include
all the files needed to recompile the BSP. It must not contain any files that would
cause another BSP to fail to compile on the user’s system.
Default Configuration
Before beginning the BSP packaging phase, you must establish and set the default
configuration for the BSP. This means setting the configuration options in config.h
and selecting the default deliverables using the RELEASE variable in the makefile.
In some cases, the target board for which the BSP is written may be available in
several different configurations. For example, it may be available with different
memory modules, peripheral controllers, processor types, or revision levels. One
BSP that supports all possible configurations is usually the desired solution.
To this end, you are encouraged to configure the final BSP for the default case with
the minimum configuration possible. This allows the ROM set and VxWorks image
to run, as shipped, on most all variations of the target board. Thus, the default
memory size should be the minimum available, and all optional peripheral
controllers should be configured out of the BSP. If end users have more memory or
an optional module, they can then configure in the appropriate support and
rebuild the VxWorks image and VxWorks boot ROMs when necessary.
Any BSP configuration mechanisms for tuning target board support should be
accessible through parameters in config.h. These parameters are typically either
macros or conditional compilation directives. Any uncommon or complex
configuration mechanisms should be explained fully in config.h and in the
SPECIAL CONSIDERATIONS section of target.nr.
The standard delivered makefile targets for Wind River BSPs include bootrom,
vxWorks, and vxWorks.st. The standard make variable RELEASE is defined to be
these targets. If a different set of targets (say, bootrom_uncmp.hex instead of
bootrom.hex) is to be delivered, RELEASE should be redefined in the makefile. For
example:
196