User manual

C hwtest
--cfg <file name> configuration file
--cycles <number> number of test cycles. Default: infinite
--size <bytes> test file size in bytes. Default: 1048576 bytes
--mode <mode> uless for userless, fint for fully interactive, hint for half
interactive. Default: uless
--failstop stop testing after the first failure
--verbose verbose output
--net <params> network test module with its parameters
--mpci <params> MiniPCI test module with its parameters
--serial <params> serial test module with its parameters
--gpio <params> GPIO test module with its parameters
--cf <params> CompactFlash test module with its parameters
--i2c <params> I2C and RTC test module with its parameters
--epld <params> EPLD test module with its parameters
--usb <params> USB test module with its parameters
--can <params> CAN test module with its parameters
--wlanbtn <params> WLAN button test with its parameters
Table 9: Common parameters and test modules
C.1. Network Test
Two interfaces must be connected with each other for the network test (either with a patch or
crossover cable). A test file will be sent as raw Ethernet packets. To see the packet content use
the --verbose flag. The size of the Ethernet packet (in bytes) can be defined with --nblock
option. The delays between two packets will be defined with the --ndelay option (default 100000
microseconds).
Usage example:
hwtest --cycles=1 --size=4096 --net --verbose
executes the network test with a 4096 byte test file in verbose mode
C.2. MiniPCI Test
During the test /proc/bus/pci/devices will be searched for the presence of the WLAN card. If
the WLAN card is found the name of the chip will be printed. After that, the WLAN environment
will be searched for available participants.
Usage example:
hwtest --cycles=1 --mpci
executes the MiniPCI test
C.3. Serial Test
To test the serial port you will need a special null-modem cable. Following pinout will be used (see
Table 10 and Figure 33 without USB-CAN connector):
May 2014 OnRISC User Manual 77