VxWorks BSP Developer's Reference : VxWorks BSP Validation Test Suite
network - I/O tests for network
bspVal options network
This test verifies basic network functionality, independent of network media. This script is written in Tcl and uses some wtx protocol functions. It also uses tclSerial library functions for accessing the serial port(s). The entire test can take several minutes to run. See bspVal.sh for an explanation of options.
This test requires two targets. The target being tested is the master. The second target, the slave, is used to run ping and udpEchoTest. The VxWorks image running on the slave must be built with the macro INCLUDE_PING defined. Both the targets require a VxWorks image built with INCLUDE_NET_SHOW defined. If using project facility, add components INCLUDE_PING and INCLUDE_NET_SHOW to respective VxWorks images.
NOTE: This reference entry lists the most likely reasons for a test's failure. However, it does not list all possible reasons. The first test uses ping to send approximately 50 ICMP packets (datagrams) to the ICMP server resident on the master. Each packet contains a request for a response from the server; the response should be received by the slave. The round-trip time, from sending to receiving, is displayed for each packet. As long as approximately 50 responses are logged by the slave, this test passes. If this test fails, check the network connection and make sure that the target IP address is correct.
The first test requires that ping be present on the slave. A check is done to make sure that it is in the path. If ping is missing, the test aborts because the UDP test uses the ping statistics.
The second test spawns the pkUdpEchoTest( ), a pkLib.c routine, on the slave to send a quantity of UDP packets to a UDP echo daemon running on the master, which is started by spawning pkUdpEchod( ), also a pkLib.c routine. Each UDP packet is sent by the slave to the master, echoed, read back in by the slave, then checked for correct size and content. Sixteen different size packets are sent and received. If pkUdpEchoTest( ) times out waiting for the echo, the packet is resent once. If the resent packet does not make it, the test is marked as a failure. The timeout value for individual UDP packets is derived from the statistics displayed in the ping test. This value depends on the network media being used. The actual packet round-trip time, however, should be considerably less than the calculated timeout value used. If this test fails, make sure that a reliable host is being used and that the network is not being overloaded by other packet traffic.
The UDP/IP networking protocol is used in the second test. UDP/IP makes no guarantees with regard to packet delivery, thus the host and/or target might occasionally drop packets. Although several dropped packets does not constitute a failed test, a large number of dropped packets (greater than one percent of the total sent) could indicate a problem with any of the following: network configuration, network device, device driver, networking software.
Barring serious hardware or software limitations (such as an identifiable VxWorks problem), the target board must pass all tests for the BSP to be validated.
A target that continually fails the second test might or might not be functioning properly. If it can be proven that the host is responsible for dropping the packets (for example, by running etherfind), then the target cannot be declared to have passed or failed this test. Hardware and network environment limitations need to be taken into consideration when evaluating the results of this test.
- T1_BOOT_TN 20
- Master target name (required).
- T1_BOOT_E
- Master target IP address (required).
- T1_BOOT_B
- Master target backplane address (required).
- T2_BOOT_TN
- Slave target name (required).
- T2_BOOT_E
- Slave target IP address (required).
- T2_BOOT_B
- Slave target backplane address (required).
- T2_UDP_TRANS
- Number of packets used in UDP test.
Output consists of:
BSP VALIDATION TEST ------------------- Target server : t53-160 BSP : mv147 Second target server : t214-2 Second BSP : mv147 Log file : /tmp/bspValidationLog.6425 network : ping target test : PASS UDP packet echo test : PASS Tests RUN 2 Tests PASSED 2 Tests FAILED 0 Tests SKIPPED 0
bspVal.sh, networkLib.tcl, pkLib.c