windows logo kit usbif testing.docx

windows logo kit usb-if testing - 10windows logo kit usb-if testing九月 9, 2010abstractthis paper provides information about the windows logo kit (wlk) usb implementers forum (usb-if) testing requirements for windows operating systems. it provides guidelines for hardware vendors and device manufacturers to prepare their usb devices and host controllers for windows logo program submission.this information applies to the following operating systems:windows server 2008 r2windows7windows server 2008windows vistareferences and resources discussed here are listed at the end of this paper.the current version of this paper is maintained on the web at: /whdc/connect/usb/wlk-usb-if-testing.mspxdisclaimer: this document is provided “as-is”. information and views expressed in this document, including url and other internet web site references, may change without notice. you bear the risk of using it.this document does not provide you with any legal rights to any intellectual property in any microsoft product. you may copy and use this document for your internal, reference purposes. 2010 microsoft corporation. all rights reserved.document historydatechangeaugust 25, 2010first publicationcontentsintroduction3background3connect-0093 and busport-0034 requirements overview5windows logo program submission options5usb-if certification5usb-if self-testing6acquiring usb-if certification8usb-if certification cost8usb-if certification steps9feedback10resources10introductionthe previous version of the wlk usbif testing requirements stated that a usb device or host controller must first be certified by the usb-if to qualify for a windows logo. usb is not the only device connectivity technology that must meet the electrical and mechanical requirements of an independent standards organization to receive a windows logo. for example, for a bluetooth device to receive a windows logo, the device manufacturer must first qualify their product with the bluetooth special interest group. when the usbif testing requirements were originally introduced, our usb device vendor partners raised concerns about the cost, timing, and fringe device cases with the usbif certification process. to address those concerns, we reworked the wlk usbif requirements so that usb device vendors are not required to submit their devices to the usb-if for testing. however, we still recommend usbif certification, as it covers more in-depth testing of usb devices and host controllers and ensures a high-quality usb implementation.the new version of the wlk usb-if testing requirements allows partners to download and run tests from the usbif website, the results of which will be consumed by the wlk. if your device has been certified by the usb-if, you simply need to provide the usbif test id (tid) for the device to the wlk. this enables partners who get their devices usbif certified to avoid any test duplication. partners who do not get their devices usb-if certified simply need to run a few of the usb-if tests on their own and then provide the logs from those tests to the wlk.backgroundover the past decade a number of special interest groups (sigs) were formed to help address interoperability issues between devices and computers and between each other. one of those groups is the usb-if, which maintains the usb specifications and also provides test specifications and tools. today, the wlk and the usb-if compliance program have several overlapping tests to ensure coverage of both the windows logo tests and the usb-ifs tests, as shown in figure1.figure 1. usb-if and windows logo testsusb devices that do not comply with the usb specification can negatively affect the pc ecosystem. even if usb devices pass todays microsoft windows logo program requirements, many of those devices do not fully comply with the usb specification. over the years, microsoft product teams and usb engineering groups analyzed these problems. based on our experience with product and quality assurance testing in our usb labs, we identified the following trends in usb specification non-compliance:hubsa common failure of a usb hub is that it reports having external power when it actually has only bus power, leading to an invalid voltage condition on the bus.hard disk drivesa common failure of a usb hard disk drive is that it does not enumerate correctly because of excessive power draw from the usb bus. in many situations, these hard disk drives require non-standard cables to work correctly.flash drivesa common failure of a usb flash drive is that it does not handle the descriptor requests correctly, which can cause the device to fail the microsoft os descriptor and hang.card readersa common failure of a usb card reader is that it does not enter into the selective suspend state.printersa common failure of a usb printer is that it does not resume from standby.audioa common failure of a usb audio device is that it does not resume from standby.shipping non-compliant usb devices can negatively affect many parts of the pc ecosystem. a non-compliant usb device can cause a poor user experience, difficult public relations, product returns and loss of revenue, high product support call volume, and increased costs associated with servicing bugs in shipped products.microsoft has spent a great amount of time and effort over the past few years to develop, test, and provide many solutions in windows to address and prevent issues that are caused by non-compliant usb devices. microsoft has identified the following characteristics of devices that have both usb-if certification and windows logo qualification: they offer a much more reliable windows user experience. they are much less likely to incur support costs. they are more interoperable with other devices and computers in the windows ecosystem. they are easier to identify as devices that have been tested for compatibility with windows.when a usb device does not comply with the usb specification and does not adhere to its architecture, the windows user experience can be poor and often the device does not function as expected.connect-0093 and busport-0034 requirements overviewwe understand that requiring usb-if certification might not meet the specific business needs and market solutions for all usb devices. while we strongly suggest usb-if certification, wlk requirements connect0093 and busport0034 no longer require usb-if certification. instead, these requirements state that the device can be either usb-if certified or a subset of the usb-ifs certification tests can be run on the device during wlk testing. for more information about how to run the required usb-if tests, see ”usb-if self-testing” later in this paper.these requirements apply to both usb device manufacturers and usb host controller manufacturers. system manufacturers should be aware of these requirements when selecting usb host controllers to integrate into their systems. the connect0093 requirement also applies to the unclassified windows logo program for devices.we believe that these requirements are a significant step forward to improving the customer experience with usb devices, helping to prevent key reasons for crashes and hangs, and reducing the amount of time spent by microsoft and our partners debugging non-compliance issues.windows logo program submission optionsto submit your usb devices for windows logo qualification to meet the new usb-if testing requirement, follow one of the scenarios that are summarized in table 1.table 1. windows logo program submission optionssubmission optionsubmission sequenceusb-if certificationfirst obtain usb-if certification from a usbif authorized testing lab. then submit the device for windows logo qualification.usb-if self-testingfirst download the usb command verifier test tools and the usb interoperability test documents and run the required tests. then submit the device for windows logo qualification.the following sections describe each of these windows logo program submission options in more detail.usb-if certificationthe following steps describe how to obtain usb-if certification for your device to qualify for a windows logo. submit your device to one of the many usb-if authorized independent test labs for testing. for more information about the location of these labs, see the independent test labs page on the usb-if website.alternatively, you can bring your device to one of the usb-if sponsored compliance workshops. each year, four workshops are held in the usa, and one is held in asia. for more information about these workshops, see the usb-if compliance program page of the usb-if website. if your device passes the usb-if certification tests, you will receive a test id number from the testing lab. you provide this test id number to the wlk when you run the rest of the wlk tests for your device.usb-if self-testingthere are two main test areas to focus on if you select the usb-if self-testing option to meet the usb-if testing requirements to qualify for a windows logo:usb command verifier teststhese tests verify the ability of your device to understand and accept common usb commands.usb interoperability teststhese tests target the functionality and the ability of your device to coexist with other usb peripherals.both of these tests are downloaded and run outside of the wlk. after these tests are run, the wlk consumes the log files that are generated by the tests. note that these tests only need to be run on the latest version of windows (as specified by the usbif), even if you are submitting your usb device for windows logo qualification for multiple versions of windows. the results of these tests are applicable for all windows logo submissions for all versions of windows.the following steps describe how to perform the required usb-if tests yourself to qualify your device for a windows logo. download the usb command verifier test tool (usb20cv), the usb 3.0 command verifier test tool (usb30cv), and the interoperability test documents from the usb-if website. run the usb-if tests for your usb hardware as specified in the following tables.table 2. usb-if tests for usb devicesusb versionusb-if testsusb 2.0 run the chapter 9 tests in the usb command verifier test tool (usb20cv) with the device attached behind an ehci host controller. run the chapter 9 tests usb 2.0 devices in the usb 3.0 command verifier test tool (usb30cv) with the device attached behind an xhci host controller. run the interoperability tests as described in section d of the “universal serial bus implementers forum full and low speed electrical and interoperability compliance test procedure” document. run these tests twiceonce with the device attached behind an ehci host controller and once with the device attached behind an xhci host controller.usb 3.0 run the chapter 9 tests usb 3.0 devices in the usb 3.0 command verifier test tool (usb30cv) with the device attached behind an xhci host controller. run the chapter 9 tests in the usb command verifier test tool (usb20cv) with the device attached behind an ehci host controller. run the interoperability tests as described in the “xhci interoperability testing” document. run these tests twiceonce with the device attached behind an ehci host controller and once with the device attached behind an xhci host controller.table 3. usb-if tests for usb hubsusb versionusb-if testsusb 2.0 run the chapter 9 tests and the chapter 11 tests in the usb command verifier test tool (usb20cv) with the hub attached behind an ehci host controller. run the chapter 9 tests usb 2.0 devices and the chapter 11 tests usb 2.0 devices in the usb 3.0 command verifier test tool (usb30cv) with the hub attached behind an xhci host controller. run the interoperability tests as described in section d of the “universal serial bus implementers forum full and low speed electrical and interoperability compliance test procedure” document. run these tests twiceonce with the device attached behind an ehci host controller and once with the device attached behind an xhci host controller.usb 3.0 run the chapter 9 tests usb 3.0 devices and the chapter 11 tests usb 3.0 devices in the usb 3.0 command verifier test tool (usb30cv) with the hub attached behind an xhci host controller. run the chapter 9 tests in the usb command verifier test tool (usb20cv) with the hub attached behind an ehci host controller. run the interoperability tests as described in the “xhci interoperability testing” document. run these tests twiceonce with the device attached behind an ehci host controller and once with the device attached behind an xhci host controller.table 4. usb-if tests for usb host controllersusb versionusb-if testsall run the interoperability tests as described in section c.2 of the “usb-if embedded host compliance plan” document.note: the interoperability tests are not currently automated. however, they will be automated in the future. when this occurs, the wlk will be updated so that it can consume the logs from the interoperability tests. a tool will be provided in the wlk to consume the usb-if test results. run this tool to integrate the results of the usb-if tests with the results of your wlk tests. acquiring usb-if certificationthis section provides details for obtaining usb-if certification and ensuring compliance for your usb device. you can certify your usb device in the following two ways: submit your device to one of the many usb-if authorized independent test labs. these test labs offer testing services for a wide range of usb products. for more information about the location of these labs, see the independent test labs web page. bring your device to one of the usb-if sponsored compliance workshops. each year four workshops are held in the usa, and one workshop is held in asia. for more information about these workshops, see the usb-if website.the following two prerequisites are required for submitting a usb device to one of the authorized independent test labs for usb-if certification: the device manufacturer must register with the lab. the device manufacturer must have a valid vendor id (vid).after your device has successfully passed the usb-if certification tests, you are entitled to the take the following actions: you can use the usb logo for brochures, packaging, and product information for your device. you can be listed on the usb-if integrators list.typically, a single usb device that is submitted to an authorized independent test lab can take one to two weeks to be tested for compliance with the usb specification.usb-if certification costthe cost of tes