Information
The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

Recommended USB tests for system development

If you are building a new system, the tests in this topic are recommended.

To run DF tests listed in this topic, you must have MUTT devices. Depending on the stage, you will need to update driver for the device by running this command:

muttutil -updatedriver <driver_inf>.inf

The MuttUtil tool is included in the MUTT software package.

If you are building a new system, here are the recommended USB HCK tests:

Stage 1—System bring-up

For each xHCI controller on the system, configure this topologyRunning the recommended test
  1. Connect a USB 3.0 hub to a SuperSpeed port of the system.
  2. Connect a SuperMUTT downstream of the USB 3.0 hub.

    Device driver:  The SuperMUTT device must have Winusb.sys as the device driver. Run this command:

    muttutil -updatedriver usbfx2.inf

    System bring-up topology

Note  If system does not have a Type A connector, then an adapter should be included with the system.
 
  1. In Windows HCK Studio, on the Selection tab, click Device manager.
  2. Select the xHCI controller and its root hub.
    Note  To quickly find the controller, type "xhci" in search.
     
  3. From the View By list, choose Basic.
  4. Run the recommended for the selected controller.

 

Stage 2—System integration

For each xHCI controller on the system, configure this topologyRunning the recommended test

For each xHCI controller on the system, configure this topology

  1. Connect a USB 3.0 hub to a SuperSpeed port of the system.
  2. Connect a SuperMUTT downstream of the USB 3.0 hub.

    Device driver:  The SuperMUTT device must have Usbtcd.sys as the device driver. Run this command:

    muttutil -updatedriver usbtcd.inf

  3. Connect a SuperMUTT Pack downstream of the USB 3.0 hub.

System integration topology

Note  If system does not have a Type A connector, then an adapter should be included with the system.
 

To run the tests:

  1. On the Selection tab, click Device manager.
  2. Select the xHCI controller and its root hub.
    Note  To quickly find the controller, type "xhci" in search.
     
  3. From the View By list, choose Functional.
  4. Run the recommended for the selected controller.

 

Stage 3—System tuneup

System 1

System 2

System 3 (if dock supported)

For each xHCI controller on the system, configure this topologyRunning the recommended test

System 1

See system bring-up topology.

Device driver:  The SuperMUTT device must have Usbtcd.sys as the device driver. Run this command:

muttutil -updatedriver usbtcd.inf

System 2

For each xHCI controller on the system, configure this topology

  1. Connect a USB 3.0 hub to a SuperSpeed port of the system.
  2. Connect a SuperMUTT downstream of the USB 3.0 hub.
  3. Connect a SuperMUTT Pack downstream of the USB 3.0 hub.
  4. Connect a MUTT Pack downstream of the USB 3.0 hub.
  5. Connect four self-powered USB 3.0 hubs downstream of each other (forming a chain) with the first hub downstream of the SuperMUTT Pack.
  6. Connect a MUTT (or a SuperMUTT Pack) downstream of the last USB 3.0 hub in the chain.
System tuning topology

System 3 (if dock supported)

See system integration stage.

System 1

  1. On the Selection tab, click Device manager.
  2. Select the xHCI controller and its root hub.
    Note  To quickly find the controller, type "xhci" in search.
     
  3. From the View By list, choose Certification.
  4. Run the recommended for the selected controller.

System 2

  1. On the Selection tab, click Device manager.
  2. Select all MUTT devices in the topology, shown in the list.
    Note  To quickly find the controller, type "MUTT" in search.
     
  3. From the View By list, choose Functional.
  4. Run the recommended tests for system 2.
  5. Use 2 meter long cables to connect hubs to the system.

System 3

 

Related topics

Windows Hardware Certification Kit Tests for USB

 

 

Send comments about this topic to Microsoft

Show: