BSP Developer's Guide

2
BSP Organization
Version 1.0 BSPs are written for all standard VxWorks releases up to and including
VxWorks 5.2. Version 1.1 BSPs are written for Tornado 1.0 and Tornado 1.0.1.
Version 1.2 identifies a BSP designed for use with Tornado 2.x. The main interface
differences between 1.1 and 1.2 BSPs is support for the networking stack and
different packaging. With each new version sequence, the revision number begins
with 0 and is incremented each time the BSP is released for production.
To specify a BSP version number, you can define BSP_VERSION to be the string
“1.2” or “1.1”. Otherwise, you can define either of the macros BSP_VER_1_1 or
BSP_VER_1_2, whichever is appropriate. To set the revision number, use BSP_REV,
which you should set to a string value such as “/0”. The revision number includes
the slash character. The full BSP release number is the concatenation of the two
string macros BSP_VER and BSP_REV: for example, “1.2/0”.
Thus, to set a BSP’s release number to “1.2/0”, define the following:
2
#define BSP_VER_1_1
#define BSP_VER_1_2
#define BSP_VERSION "1.2"
#define BSP_REV "/0" /* Increment for each new release */
configAll.h. Include configAll.h (located in the target/config/all directory) in your
config.h so the reasonable configuration defaults for a BSP are adopted. Use
config.h as the main user-editable configuration file for your BSP.
Use config.h as the main user-editable configuration file for your BSP. To pick up
the reasonable configuration defaults for a BSP at your site, your config.h should
include configAll.h (located in the target/config/all directory). 1
Within your config.h you can override these site defaults, with values more
appropriate to this particular BSP. You should also present your config.h to
subsequent users of your BSP as the configuration file that they should edit either
to override configAll.h or to configure whatever optional features you have built
into your BSP.
When building project images, components and parameters selected using the
project override any values assigned in either configAll.h, config.h, or even
bspname.h. Any macro known to the project facility is assigned the project value,
overriding any other assignment.
1. Here, the term “user” refers to developers who use your BSP to build their VxWorks applications.
In addition, if a value is not optional but always required and must not be edited,
set it in bspname.h, not config.h.
17