USB OTG Bus IOCTL Test (Compact 7)
3/12/2014
The USB On-The-Go (OTG) Test verifies the Stream Interface Driver exposed by the USB OTG Driver. It does not verify the OTG functionality to switch between USB Host and Function.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following shows the hardware requirements for the OTG test.
| Requirement | Description |
|---|---|
USB OTG Port |
USB OTG Port to be tested. |
The following table shows the software requirements for the OTG Test.
| Requirement | Description |
|---|---|
Tux.exe |
Tux test harness, required for test execution |
Ktux.dll |
Tux test harness, required for kernel-mode tests |
Kato.dll |
Kato logging engine, required for logging test data |
USB OTG Driver |
Driver Library |
otgtest.dll |
Test library |
Ensure the following are true of the USB OTG driver being tested:
* The USB OTG driver must support the basic stream driver interface to be able to access the driver's functionalities.
* The USB OTG driver must support the CE7 USB OTG Driver model.
* The USB OTG driver must support power control to enter suspend mode.
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
1001 |
API Test OTG Port Open and Close |
1002 |
Load/Unload Test OTG Driver Load Unload |
1003 |
Request/Drop Test OTG Bus Request and Drop |
1004 |
Suspend/Resume Test OTG Bus Suspend Resume |
1005 |
Power Management Test OTG Power IOCTL Test |
Setting Up the Test
This test has no additional requirements, beyond the standard test environment setup.
Running the Test
The OTG test is an automated test suite.
The default command executed is: s tux -o -n -d otgtest.dll.
There are no additional parameters for this test.
Verifying the Test
When the test completes running, verify that "PASSED" appears in the test log for all subtests.
Troubleshooting the Test
* Determine the point of failure and record the exact error message.
* 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.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.