Secure Digital Host Controller Testing Prerequisites

This topic describes the tasks that you must complete before you test your audio device by using the Windows Hardware Certification Kit (Windows HCK):

Secure Digital I/O (SDIO) host controllers must comply with Peripheral Component Interconnect (PCI) 2.3 or later requirements for that interface. For PCI configuration registers and interface information, see the SD Host Controller Specification, Version 1.0, Appendix A, which is available from the SD Association website.

Hardware requirements

The following hardware is required for SDIO host controller testing. You might need additional hardware if the controller includes additional capabilities. See the test description for each test that is listed for the device in Windows HCK Studio to determine whether your hardware requires additional tests.

  • One test computer that meets the Windows HCK prerequisites. See Windows HCK Prerequisites for more information.

  • One test SDIO host controller.

  • Any secure digital memory card that complies with the requirements of the "Designed for Microsoft Windows" Logo Program for Hardware.


    If the SDIO host controller test device supports High Speed mode, the memory card used must also support High Speed mode.


To certify your product for use on servers, the test computer must support four processors and a minimum of 1 GB of RAM. These system capabilities are required to test the Rebalance, D3 State, and Multiple Processor Group functionality of the device and driver. You do not need a computer that actually has more than 64 processors to test your device. Additionally, the server system(s) being used for device or driver testing must have Server Core installed prior to testing. For more information see Windows Server Installation Options.

If you use a pool of test computers to test devices, at least one computer in the pool must contain four processors and a minimum of 1 GB of RAM. Additionally, that computer must contain the device and the driver that you want to test. As long as the driver is the same on all the computers in the pool, the system creates a schedule to run against all test computers.

For tests that do not include a driver to test, such as hard disk drive tests, the Windows HCK scheduler constrains the tests that validate the device’s and driver’s Rebalance, D3 State and Multiple Processor Groups functionality to run on the default test computer. You must manually configure this computer to have multiple processor groups. The default computer is the first test computer in the list. Test personnel must make sure that the first test computer in the list meets the minimum hardware requirements.


Except for para-virtualization drivers (as defined by Logo Program Requirement Policy-0020), you may not use any form of virtualization when you test physical devices and their associated drivers for server certification or signature. All virtualization products do not support the underlying functionality that is required to pass the tests that relate to multiple processor groups, device power management, device PCI functionality, and other tests.


Software requirements

The following software is required to run the SDIO host controller tests:

  • The drivers for the test device.

Test computer configuration

Only one test computer is required for SDIO host controller testing. To configure the test computer for SDIO host controller testing:

  1. Install the appropriate Windows operating system on the test computer, and then configure the computer for your test network. The test network is the network that contains the Windows HCK Studio and Windows HCK Controller.

  2. Install the SDIO host controller, if the controller is not embedded on the motherboard.

  3. Install the manufacturer-supplied device driver, if it is required, on the test computer.

  4. Verify that the SDIO host controller functions correctly by using the secure digital memory card.


    It is a best practice to verify full functionality of the SDIO host controller before you begin testing.

  5. Install the Windows HCK client application on the test computer.

  6. Use Windows HCK Studio to create a machine pool, and then move the test computer to that pool.

Make sure that the test computer is in the ready state before you begin your testing. If a test requires parameters to be set before it is run, a dialog box will be displayed for that test. Review the specific test topic for more information.

Some Windows HCK tests require user intervention. When running tests for a submission, it is a best practice to run the automated tests in a block separately from manual tests. This prevents a manual test from interrupting completion of an automated test.



Send comments about this topic to Microsoft