Command-Line Parameters for the Serial Communications Test (Windows Embedded CE 6.0)
1/6/2010
The Serial Communications Test verifies the functionality of serial communications on a Windows Embedded CE powered device. Evaluates basic functions, conducts stress tests, and tests hardware functionality.
Syntax
tux.exe [tuxparams] -d pserial.dll [-c "[-p COMX] [-x] [-m] [-s] [-g device] [-d] [-t iterations] [-e seconds]"]
Command-line Parameters
| Command line parameter | Description |
|---|---|
tux.exe tuxparams |
For information about the command-line parameters of the Tux test harness, see Tux Command-Line Parameters. |
-d pserial.dll |
Specifies the DLL to use for the Serial Communications Test. |
-c " … " |
Specifies a list of test-specific parameters that Tux passes to the test DLL. |
-p COMX: |
Specifies a communications (COM) port to test, where COM is a literal string and X represents the number of the serial port; for example, -p COM1: |
-x |
Specifies individual test cases to run |
-m |
Runs the test in master mode. |
-s |
Runs the test in subordinate mode. |
-g device |
Specifies the name of the serial device attached to the COM port being tested. |
-d |
Dumps binary data. |
-t iterations |
Specifies how many times to run a stress test. This parameter is required when running a stress test case. |
-e seconds |
Specifies how long to runs the performance test, measured in seconds. This parameter is required when running a performance test case. |
Remarks
When using the Tux parameter -x to specify individual test cases, always include test cases 10 and 11. Test case 10 verifies the serial connection and the ability of the two devices to synchronize. Test case 11 determines what properties the two serial ports share and is required when running the other test cases.