BSP Developer's Guide

7
Validation Testing
Table 7-2
Validation Test Suite Configuration Parameters: Target-Specific Parameters (Continued)
Parameter Default Description
T1_TMO_SLICES 4 Timestamp test measurements intervals. See
timestamp.tcl.
T1_TMO_TIMESTAMP 300 Duration of timestamp timer test (in seconds). See
timestamp.tcl.
T1_TMO_SCSI 3600 Timeout for testing SCSI (in seconds). See scsi.tcl.
{T1, T2}_TMO_BOOT 60 Timeout for booting VxWorks (in seconds).
7
T2_UDP_TRANS 5000 Number of UDP packets to send. See network.tcl.
7.4 Running the BSP VTS
Each test in the BSP VTS exercises one or more of the basic BSP functions. For the
most part, the source for these tests (implemented as Tcl/WTX scripts) is contained
in the host/src/test/bspVal/src/tests directory. However, if a procedure is shared by
a number of tests, that code is stored in the host/src/test/bspVal/src/lib directory.
These shared procedures handle things such as booting VxWorks, reporting
PASS/FAIL results, and so forth.
For example, BSP VTS tests for the system clock and the auxiliary clock are stored
in the files tests/sysClock.tcl and tests/auxClock.tcl. Both of these files call
procedures in lib/clockLib.tcl. In addition, many BSP tests use functions within
target/src/test/bspVal/pkLib.c, a library of C functions that execute on the
VxWorks target (although the host retains control of the progression of tests).
These C functions serve as low-level support routines.
7.4.1 Starting the BSP VTS
The BSP VTS runs from either a Windows or a UNIX host. After starting a bash
shell, running the BSP VTS from a Windows host is almost exactly the same as
running it from a UNIX host.
153