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–based device. The Serial Communications Test evaluates basic functions, conducts stress tests, and tests hardware functionality.
The Serial Communications Test does not appear by default in the Windows Embedded CE 6.0 Test Kit (CETK) window. You can add the test to the CETK with the User-Defined Test Wizard. For more information about the User-Defined Test Wizard, see Adding a Custom Test to the CETK.
The Serial Communications Test requires two Windows Embedded CE–based devices. One Windows Embedded CE–based device must run as a client with the -s parameter while the other Windows Embedded CE–based device runs as a server with the -m parameter. Each time you run this test, you must have one server and one client. The test does not support a server-to-server or client-to-client arrangement. You can run these tests between an NT machine and Windows Embedded CE–based device, as in the following example of the test run between two Windows Embedded CE–based devices. CEPC1 COM1: port is connected to the CEPC2 COM1: port.
To run the Serial Communications Test between a Windows NT-based computer and a test device
Connect COM1 of CEPC1 and COM1: of CEPC2 using a null modem.
Upload Windows Embedded CE images to both the CEPCs** using Platform Builder**.
On CE command prompt of CEPC1 execute:
tux –dpserial.dll –c"-pCOM1: -m"
On CE command prompt of CEPC2 execute:
s tux –dpserial.dll –c"-pCOM1: -s"
You should run the test on the target device with the target device being the client and also with the target device being the server. Tests that succeed when the target device is the server may fail when the target device is the client.
Prior to running this test, confirm that all serial cable connections have a cable for debug output and a cable for serial communications. Verify that the RAS server does not run on your development workstation while the Serial Communications Test runs.
The flags for performance (-e) or stress (-t) must be added to the command line in order to fun these test cases, even if you use the -x option to specify individual performance or stress test cases.
In This Section
- Prerequisites for the Serial Communications Test
Lists the hardware and software prerequisites for the test.
- Test Cases for the Serial Communications Test
Describes test cases that are within the overall test and a description for each test
- Command-Line Parameters for the Serial Communications Test
Specifies the command line parameters that can be used for this test.
- Troubleshooting the Serial Communications Test
Provides troubleshooting information for this test