BSP Developer's Guide

7
Validation Testing
scsi
Requires that VxWorks image and pkLib.o must be built with SCSI support
included. For most BSPs, you can do this by defining INCLUDE_SCSI.
busTas
Requires that the VxWorks image for both targets include shared memory
components. Define the following macros:
– INCLUDE_SM_NET
– INCLUDE_SM_SEQ_ADDR
– INCLUDE_SM_NET_SHOW
Also, the VxWorks image for one target should define SM_OFF_BOARD as
TRUE, and the other as FALSE.
For more information, see the test descriptions in J. BSP Validation Test Suite
Reference Entries.
7
Configuring the BSP VTS
The BSP VTS is configurable through several parameters implemented as shell
environment variables. All of these parameters are defined in configuration files
(explained below), with one exception. The optional environment variable
TEST_LOG_FILE provides a means for the user to specify where the BSP VTS test
logs should be saved. Use the appropriate shell command to set this variable to the
filename (including a full path) to which the test results should be logged. When
this variable is not set, the tests are logged to
target/config/bspname/vtsLogs/bspValidationLog.PID. In either case, the screen
output is copied to the same location as the log file, and is named the same as the
log file with _screenDump appended to the filename.
The configuration parameters that control the behavior of the BSP VTS on a single
target reside in the host/resource/test/bspVal/bspName.T1 file. If a test requires two
targets, the host/resource/test/bspVal/bspName.T2 file supplies the parameters for
the second target. 3
These parameters include the path to the VxWorks image to be booted, the
characteristics of the host and target, and the details of how the test should
proceed. Many of the parameters are optional or have default values that are
reasonable in most situations. Some of the parameters are applicable only to
3. When creating a bspname.T1 or bspname.T2 file, you can copy the mv147.T1 and mv147.T2
files and edit the copies as needed.
149