Prerequisites for the USB Stress Test (Windows Embedded CE 6.0)
1/6/2010
Hardware Requirements
The following table shows the hardware that is required on the host computer for the USB stress test.
| Requirement | Description |
|---|---|
Test platform |
Host computer, from which tests are run. |
USB host controller card |
Provides functionality for the performance test. |
CEPC |
Used as a test function, alternatively, you can use a CEPC as the host computer, and use another platform for USB functionality. |
USB Function Controller |
Whereas we recommend that you use the Net2280 card, if the correct drivers are supplied, any USB Function controller card is acceptable. |
USB cable |
Required for setting up the test. |
USB Clicker |
Applies to Windows Embedded CE 6.0 R2 Optional device for automated connection and disconnection testing. |
Software Requirements for the Host Computer
The following table shows the software that is required on the host computer for the USB stress test.
| Requirement | Description |
|---|---|
Tux.exe |
Tux test harness, required to run the test. |
Kato.dll |
Kato logging engine, required for logging the test data. |
Ktux.exe |
Kernel mode test utility. |
Usbstress.dll |
Test module. |
USB host controller driver |
USB support required (USB, EHCI/OHCI/UHCI). |
Tooltalk.dll |
Applies to Windows Embedded CE 6.0 R2 Handles transport between target device and development workstation. |
XXX_clicker.dll |
Applies to Windows Embedded CE 6.0 R2 Optional test model for Clicker support, must meet the API Conformity Requirements. |
Software Requirements for the Device
The following table shows the software that is required on the device for the USB stress test.
| Requirement | Description |
|---|---|
Lufldrv.exe |
Tool that loads the driver. |
LpBkCfg1.dll |
Configures a USB function controller with six endpoints in addition to endpoint zero. |
LpBkCfg2.dll |
Configures a USB function controller with four endpoints in addition to endpoint zero. |
USB Function driver |
USB Function Controller driver support. |
API Conformity Requirements
The Clicker API is specified in the clicker.h header file in the Test\BaseOS\Drivers|USB\Common folder. The following example shows the four key functions that you must define for your Clicker hardware.
typedef BOOL(*LPUN_CLICKER_INIT)(TCHAR *);//exported as ClickerInittypedef BOOL(*LPUN_CLICKER_DEINIT)(void);//exported as ClickerDeInittypedef BOOL(*LPUN_CLICKER_CONNECT)(void);//exported as ClickerConnecttypedef BOOL(*LPUN_CLICKER_DISCONNECT)(void);//exported as ClickerDisconnect