02.03.2014 Views

BSP Developer's Guide

BSP Developer's Guide

BSP Developer's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7<br />

Validation Testing<br />

sysProcNumGet Test :<br />

sysProcNumGet() return value : PASS<br />

. . .<br />

The bspVal shell script sets up a default environment and then calls bspVal.tcl, the<br />

Tcl script that runs the individual tests.<br />

The bspVal script runs in batch mode only. Using command-line options, you can<br />

specify the tests you want to run. The example above uses the -all option to run all<br />

the tests in the <strong>BSP</strong> VTS. For more information on running bspVal, see the<br />

reference entry provide in J. <strong>BSP</strong> Validation Test Suite Reference Entries.<br />

NOTE: To abort testing, enter the tty interrupt character (usually CTRL+C)fromthe<br />

host. This stops the test on the host, although the target board might continue to<br />

execute local tasks. In this case, you might need to reboot the target board.<br />

7<br />

7.4.2 Monitoring a <strong>BSP</strong> Test<br />

At startup, the <strong>BSP</strong> VTS prints a header to standard output. This header displays<br />

the names of the target server, the <strong>BSP</strong>, and the log file. At the start of each test, the<br />

<strong>BSP</strong> VTS prints the test name. As subtests within a test are completed, the <strong>BSP</strong> VTS<br />

prints the name of the subtest along with some PASS/FAIL status information. The<br />

PASS/FAIL messages are also written to a log file, which is also used to catch the<br />

output of commands such as ifShow or smNetShow.<br />

Normally, if a test fails, all the other tests still run. However, some errors are fatal.<br />

In this case, the <strong>BSP</strong> VTS aborts and displays a fatal error message, such as:<br />

FATAL ERROR: error in ioctl() command<br />

If you set the environment variable TEST_LOG_FILE to the name of a writable file,<br />

the <strong>BSP</strong> VTS appends its output to this file. To monitor the <strong>BSP</strong> VTS on a second<br />

terminal, run tail -f on the file. For more information on log files, see the bspVal<br />

reference entry provided in J. <strong>BSP</strong> Validation Test Suite Reference Entries.<br />

Example 7-1<br />

Testing the Auxiliary Clock<br />

This example demonstrates the use of the <strong>BSP</strong> VTS to test the auxiliary clock. Note<br />

that the example shown in this section is a test run on the MVME147 <strong>BSP</strong>. This<br />

example is useful for showing how to work with the <strong>BSP</strong> VTS on a single target.<br />

1. Verify that the target board can boot VxWorks. Using the Tornado launcher,<br />

start a target server and open a WindSh. From the WindSh, verify that there is<br />

communication with the target.<br />

155

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!