Preparing for Bluetooth Controller Testing

Note  This content applies to the Windows Logo Kit (WLK). For the latest information using the new Windows Hardware Certification Kit (HCK), see Windows HCK User's Guide on the Windows Hardware Dev Center.

Before running the tests, you must configure the system and install the operating system. This section summarizes the related procedures.

The Microsoft Bluetooth Driver Stack is the only driver stack that is supported to logo your device. Loading any other driver stack causes the tests to fail.

For a complete list of required hardware, software, and tester knowledge, see the Bluetooth Controller Testing Overview.

Many of the tests in the Windows Driver Kit (WDK) require a test system to restart (often more than once) to complete a test run. The test description and the running instructions specify whether a test requires a system restart. Although these tests programmatically restart the test system, you must manually log on to the test system after each system restart so that the test run can resume. You can avoid this requirement by enabling autologon functionality on the test system. For more information about autologon,see How to turn on automatic logon in Windows XP.

Test system configuration

To configure your test system for Bluetooth controller testing, do the following:

  1. Install the appropriate Microsoft Windows operating system.

  2. Install the test device and any accessories. You should not need to install a driver for this device.

  3. Install DTM client.

  4. Configure the machine for testing in DTM Studio:

    • Add the machine to a machine pool.
  5. When you connect the Bluetooth controller to the test system:

    • If any test system contains an OHCI USB controller, attach the Bluetooth controller downstream of a USB 2.0 high-speed hub for the Bluetooth - SCO test.
  6. If the Bluetooth controller contains an embedded USB 1.1 full-speed hub, do the following:

    • For the USB Device Framework (CV) Test and USB HIDView (CV) Test attach the device downstream of a USB 2.0 high-speed hub.
    • For all other tests, attach the Bluetooth radio directly to the system.
  7. If the Bluetooth controller does not contain an embedded hub, do the following:

    • For the USB Device Framework (CV) Test, USB HIDView (CV) Test, and USB Selective Suspend test, attach the device downstream of a USB 2.0 high-speed hub.
    • For all other tests, attach the Bluetooth radio directly to the system.
  8. If the Bluetooth controller is embedded inside the test system and cannot be removed, do the following:

    • Set the IsEmbeddedUSBDevice job parameter to TRUE when you run only the USB Device Framework (CV) Test, USB HIDView (CV) Test, USB Selective Suspend test, and USB Serial Number test. To set the parameter, right-click the device in the Device Console, and click Edit Parameters.

    • All other tests should be run with the IsEmbeddedUSBDevice job parameter set to its default of FALSE.

 

 

Build date: 9/14/2012