BSP Developer's Guide

J
BSP Validation Test Suite Reference Entries
network
NAME
SYNOPSIS
DESCRIPTION
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.
NOTE: This reference entry lists the most likely reasons for a test’s failure. However, it
does not list all possible reasons.
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.
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
J
385