How to prepare the test system to run MUTT test tools
Before using MUTT devices, you must prepare the test system.
The instructions in this document are based on the following assumptions:
- You have an understanding of the Windows command shell. Installation of the test tools requires an elevated command window. For that window, you can open a Command Prompt window by using the Run as administrator option.
- You are familiar with the tools that are included with the Windows Driver Kit (WDK).
- You are familiar with kernel debugging tools.
To prepare a system to run MUTT test tools for USB hardware testing
- Connect the test system to a kernel debugger.
- Attach MUTT devices into each available port of the host controller or hub to test.
You must attach the MUTT device to the test system before you run the installation scripts that are installed by the MUTT software package.
For information about the recommended test configurations, see MUTT Topologies in this document.
- Open an elevated command window on the test system and navigate to the folder in which the test tools were copied.
- In the elevated command window, install the necessary MUTT driver
C:\usbTest\pnputil –i –a usbfx2.inf
If you want to test by using driver verifier then you can run install.cmd instead of the previous command. This will install the necessary drivers as well as configure driver verifier. Note that using install.cmd is optional.
- The following dialog box appears while installing the test drivers:
Check Always trust software from “Microsoft Corporation” to prevent the dialog box from appearing when the tests are running.
The test system machine will reboot after install.cmd has completed installing.
- Switch the MUTT to the new driver C:\usbTest\MuttUtil –UpdateDriver usbfx2.inf
- Update the MUTT with the latest firmware C:\usbTest\MuttUtil.exe -UpdateFirmware
- If your test system is running Windows 8, we suggest that you perform a quick validation of your host controller before you start the tests.
From an elevated Command Prompt window, run the following command to collect information about your host controller and hubs that are connected to the system: C:\usbTest\xhciwmi -verify.
The tool displays information about the host controller in the command window. Information includes vendor ID, device ID, revision ID, and the firmware version. If known issues exist for the host controller under test, consider updating the firmware.
You can provide additional logs by capturing ETW traces by using the Logman tool. For information about how to read USB 2.0 ETW traces, see ETW in the Windows 7 USB core stack.