Command-Line Parameters for the USB Stress Test (Windows Embedded CE 6.0)
1/6/2010
This test runs common scenarios for USB ports on the platform being tested. In order to stress the system and reveal possible defects, these scenarios run at a higher rate of frequency and with larger payloads than generally would occur under normal circumstances.
The following example shows the syntax for the two commands you must run in sequence for the USB Host-Controller Driver test. For information about the Lufldrv command, see Running the USB Host-Controller Driver Test.
Syntax
lufldrv.exe {-1|-2|-3|-f}
tux.exe [tuxparams] -d usbstress.dll [-c "[{-r|-s|-m|-v|-o}] [-t minutes] [-l clickerdll [probability] [params]]"]
Command-Line Parameters
Command line parameter | Description |
---|---|
lufldrv.exe |
Loads the required loop-back configuration driver. |
-1 |
Specifies that lufldrv.exe loads the Loop-back Configuration #1 driver, LpBkCfg1.dll. |
-2 |
Specifies that lufldrv.exe loads the Loop-back Configuration #2 driver, LpBkCfg2.dll. |
-3 |
Specifies that lufldrv.exe loads the LpBkCfgNew.dll you created. For more information, see Running the USB Host-Controller Driver Test |
-f |
Specifies that the test causes the device to operate at full-speed instead of the default high-speed. |
tux.exe tuxparams |
For information about the command-line parameters of the Tux test harness, see Tux Command-Line Parameters. |
-d usbstress.dll |
Specifies the DLL to use for the USB Stress test. |
-c " … " |
Specifies a list of test-specific parameters that Tux passes to the test DLL. |
-r |
Specifies that the test simulates typical RNDIS client behavior: several various-sized control packet transmissions, in addition to larger data transfers on bulk pipes, all using an interrupt pipe for transfer completion notification. |
-s |
Specifies that the test simulates typical serial client behavior: polling on an interrupt pipe for a transfer request, followed by data transfer using bulk pipes. |
-m |
Specifies that the test simulates typical mass storage behavior: control transfer used to queue larger bulk data transfer. This parameter works whether or not the hardware uses an interrupt pipe for signaling. |
-v |
Specifies typical video capture device behavior: isochronous transfers of fixed size, using high bandwidth and frequency in order to stress the system. |
-o |
Specifies that the test overloads the client by issuing transfers of all types on all available pipes. This is the default behavior if you omit the -r, -s, -m, -v, and -o parameters. Recommended to run alone as it will cover all clients mentioned above as well. |
-t minutes |
Specifies the test duration in minutes. |
-l clickerdll |
Applies to Windows Embedded CE 6.0 R2 Specifies the optional clicker DLL. |
probability |
Applies to Windows Embedded CE 6.0 R2 Specifies the percent chance that the test causes a disconnect during any individual 1KB transfer. |
params |
Specifies a semicolon-delimited list of parameters passed to the Clicker_Init function of the clicker DLL. For example, |