BSP Developer's Guide

VxWorks 5.5
BSP Developer’s Guide
In Tornado 2.0, neither the BSP nor the base product includes any generic Wind
River driver elements. Generic driver elements are a separate product on the
CD-ROM, where they are usually listed in the contents as “Driver
objects/headers”. This product contains all the object modules for network and
SCSI drivers. It also contains all the source for other drivers, as well as the header
files.
Also new for Tornado 2.0 is the BSP project. Each BSP should include a default
project that represents the default configuration of the BSP. End-users should be
encouraged to base the new projects on a BSP’s default project; they should not be
developed directly from a BSP.
Documentation deliverables have also changed. The new documentation standard
is based on HTML pages that can be browsed. This replaces UNIX-style man
pages. For more information, see L. Refgen.
A.4.1 Product Restrictions
■
Do not provide any files or modules that overwrite anything provided by
Wind River in any product:
target/config/anything
target/lib/obj$(CPU)$(TOOL)vx/anything
target/config/all/anything
target/src/drv/any.c
target/h/drv/any.c
■
Do not include any BSP-specific file or module in a restricted Wind River
directory. (that is, third parties must deliver files in target/config/xxxx
directories only):
target/config/all/*
target/src/*
target/h/*
target/lib/*
■
Do not include the BSP dependency file used with command-line building. By
not including this file, the make system is forced to rebuild the information the
first time the user gives a make command:
target/config/target/depend.target
206