OAL KITL (Stress) v2 Tests (Compact 2013)
3/26/2014
This test verifies the Kernel Independent Transport Layer (KITL) by:
* Sending data back and forth by using all applicable KITL packet and window sizes, and verifying data integrity.
* Sending data at the same time by using multiple KITL streams.
* Measuring throughput and latency on the KITL channel.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following table describes the software requirements for the test:
Requirements |
Description |
|---|---|
tux.exe |
Tux test harness, required for the execution of the test |
kato.dll |
Kato logging engine, required for logging test data |
oaltestkitlv2.dll |
Library containing the OAL KITL Test files |
btsperflog.dll; ceperf.dll; perfscenario.dll |
Ceperf-related files for recording performance results in XML format. |
Subtests
The table below lists the subtests included in this test.
SubTest ID |
Description |
|---|---|
1 |
KITL Test Usage Message. |
1000 |
Vary packet sizes; 1 Thread ; ucWindowSize: 1 |
1001 |
Max outstanding packets; 1 Thread; ucWindowSize: 16 |
1002 |
Concurrency Stress; 10 Threads; ucWindowSize:16 |
1003 |
Maximum KITL Perf. |
1004 |
Maximum roundtrip latency one stream. |
Setting Up the Test
See the "Running the Test" section.
Running the Test
This test makes use of two test components:
* A desktop component working as a server.
* A device-side component, run as a tux test.
To run the test through the Test Kit (CTK):
1. Start Platform Builder for Windows Embedded Compact 2013 with Administrator privileges and download the run-time image to the device.
2. On the same host machine as Platform Builder, start the CTK with Administrator privileges.
3. Replace the DEVICE_BOOTME_NAME of the "Server Command Line" with the BOOTME name of the device under test. The name can be found by going to the "Target->Connectivity Options" menu item, or by looking at the bootloader output (ex. via serial cable).
4. If Perfscenario-formatted XML output is desired, change the "Current Command Line" to: -o -d oaltestkitlv2.dll -c "-BTSPerf"
5. Start the test through the CTK UI.
To run the test without the Test Kit (CTK):
1. Start Platform Builder with Administrator privileges and download the run-time image to the device.
2. On the same host machine as Platform Builder, open a command-prompt window with Administrator privileges.
3. At the desktop command prompt, execute the following command to start the KITL desktop server:
"KITLSrv.exe -b DEVICE_BOOTME_NAME" (where DEVICE_BOOTME_NAME is the BOOTME name of the device as seen by Platform Builder).
4. On the device, execute the following command to start the test:
"tux -o -d oaltestkitlv2.dll"
5. If you prefer XML logging by using CePerf/Perfscenario, make sure that CePerf.dll, BTSPerfLog.dll and Perfscenario.dll are available, and add an additional command-line parameter:
"tux -o -d oaltestkitlv2.dll -c "-BTSPerf""
Verifying the Test
When the test completes, verify that "PASSED" appears in the test log for all subtests.
Troubleshooting the Test
*Ensure that both Platform Builder and the CTK (or the command window used to start the desktop server if the test is started outside the CTK), have been opened with Administrator privileges.
*Determine the point of failure and record the exact error message. Check that the setup steps were followed and that all prerequisites were met. If the source code is available, examine the point of failure in code to see if any additional information can be gathered about the failure domain.