BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
■
Include the BSP help files created by make man:
docs/vxworks/bsp/bspname/*.*
A.5 Summary
You can model your porting activities on the following steps, which were taken at
Wind River Systems, to update 1.1 BSPs to version 1.2:
1. All Wind River BSPs were updated to use END-style drivers or modified BSD
4.4 drivers compatible with the SENS 1.1 product. This occurred when the
SENS product for Tornado 1.0.1 was delivered.
2. Some BSPs and drivers received normal maintenance patches. These had
nothing to do with the implementation of projects or components.
3. The macros BSP_VERSION, BSP_VER_1_2, and BSP_REV were added to
config.h. These macros must be inserted prior to the statement #include
"configAll.h", as it appears in the following file excerpt:
...
/* New BSP version/revision id */
#define BSP_VER_1_2 1
#define BSP_VER_1_1 1 /* compatible with 1.2 */
#define BSP_VERSION "1.2"
#define BSP_REV "/0" /* increment with each revision */
#include "configAll.h"
...
4. The prjParams.h file was included conditionally at the end of the config.h file,
as follows:
#if defined(PRJ_BUILD)
# include "prjParams.h"
#endif
5. The README file was modified to reflect the new release of the BSP. A new
entry was added to the top of the list to identify the new version and revision
of the BSP, for example:
1.2/0 - First release for Tornado 2.0.
208