Bluetooth - Bluetooth LE Logo Tests (Windows v6.3)
This automated test examines the Bluetooth Simultaneous BR+EDR and LE logo requirements and verifies that the controller that you’re testing is using valid Bluetooth 4.0 specifications.
Test details
Associated requirements |
Device.BusController.Bluetooth.Base.4LeSpecification Device.BusController.Bluetooth.Base.LeStateCombinations Device.BusController.Bluetooth.Base.LeWhiteList Device.BusController.Bluetooth.Base.SimultaneousBrEdrAndLeTraffic |
Platforms |
Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 |
Expected run time |
~45 minutes |
Categories |
Certification Functional |
Type |
Automated |
Running the test
Before you run the test, complete the test setup as described in Bluetooth Controller Testing Prerequisites.
This test requires two test computers (one acts as Primary, the other Secondary). The test computers must have the same operating system and have a Bluetooth 4.0 Compliant LE radio. The primary test computer must have the radio being certified for logo (Device Under Test).
The Bluetooth radio must use the Microsoft Bluetooth Driver Stack for testing.
Tests are copied locally to the WTTJobsWorking directory and logs are copied to the default Logs server for WTT.
Enabling collection of Event Tracing for Windows (ETW) traces assists with diagnosing test failures.
These traces capture the HCI traffic sent to and from the Bluetooth stack. They can be decoded using Netmon and the Bluetooth ETW parsers. It is recommended to first investigate the issue internally using these traces or some other method of capturing over-the-air traces because many controller/stack inter-operability issues can be observed in these traces.
You can view the collected logs using Netmon and the Bluetooth NPL parsers. These parsers can be obtained through installing the WDK.
Troubleshooting
For troubleshooting information, see Troubleshooting Bus Controller Testing.
More information
To install the bthcsti driver, follow these steps:
Copy the bthcsti.inf, bthcsti.sys, bthcsti.cat, bthcstisetup.exe, and devcon.exe files into a directory. Run the remaining steps from this directory.
Run bthcstisetup.exe.
Run devcon dp_add bthcsti.inf.
Restart the computer.
In Device Manager, verify that the bthcsti driver is installed.
Parameters
| Parameter | Description |
|---|---|
ENABLETRACING |
Enables collection of ETW traces. If True, the ETW traces are enabled on the collection. If False, the ETW traces on the collection are turned off. Default value: False |
Test case list
Test case |
Description |
LOGOLE1.1.1 |
Verify minimum supported important and critical LE states |
LOGOLE2.1.1 |
Ensure device supports minimum list size of 25 |
LOGOLE2.1.2 |
Fill list and verify we do not receive ADV from unpaired device |
LOGOLE2.1.3 |
Receive ADV from paired device with full list |
LOGOLE2.1.4 |
Receive ADV from device with disabled list |
LOGOLE3.1.1 |
Verifies device claims to support Simultaneous BR/LE traffic |
LOGOLE4.1.1 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Descriptor (2900) |
LOGOLE4.1.2 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Descriptor (2901) |
LOGOLE4.1.3 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Descriptor (2902) |
LOGOLE4.1.4 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Descriptor (2903) |
LOGOLE4.1.5 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Descriptor (2904) |
LOGOLE4.1.6 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Descriptor (2905) |
LOGOLE4.1.7 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 1 Custom Descriptor |
LOGOLE4.1.8 |
Verify Descriptor (2904) outside and before Characteristic definition containing Descriptor (2905) |
LOGOLE4.1.9 |
Verify Descriptor (2904) outside and after Characteristic definition containing Descriptor (2905) |
LOGOLE4.1.10 |
Verify 1 UUID16 Primary Service with 1 Characteristic and 4 Descriptors |
LOGOLE5.1.1 |
Verify ability to retrieve Included Services, single level |
LOGOLE5.1.2 |
Verify ability to retrieve Included Services, single level |
LOGOLE5.1.3 |
Verify ability to retrieve Included Services, single level |
LOGOLE5.1.4 |
Verify ability to retrieve Included Services, multiple levels |
LOGOLE6.1.1 |
Verify ability to set a short char value (Unsigned Write with Response) |
LOGOLE6.1.2 |
Verify ability to set a short char value (Unsigned Write without Response) |
LOGOLE6.1.3 |
Verify ability to set a long char value (Unsigned Write with Response) |
LOGOLE6.1.4 |
Verify ability to set short desc value (Unsigned Write with Response) |
LOGOLE6.1.5 |
Verify ability to begin and end reliable write on short Characteristic Values |
LOGOLE6.1.6 |
Verify ability to begin and abort reliable write on short Characteristic Values |
LOGOLE6.1.7 |
Verify ability to begin and end reliable write on long Characteristic Values |
LOGOLE6.1.7 |
Verify ability to begin and end reliable write on long Characteristic Values |
LOGOLE6.1.8 |
Verify ability to begin and abort reliable write on long Characteristic Values |
LOGOLE8.1.1 |
Set up with ADV_IND and Verify simple data transfer over encrypted link |
LOGOLE9.1.1 |
Verify ability to register and unregister for Characteristic Value notification over encrypted link |
LOGOLE9.1.2 |
Verify ability to register and unregister for Characteristic Value indication over encrypted link |
LOGOLE10.1.4 |
Verify ability to retrieve Included Services, multiple levels over encrypted link |
LOGOLE11.1.5 |
Verify ability to begin and end reliable write on short Characteristic Values over encrypted link |
LOGOLE11.1.6 |
Verify ability to begin and abort reliable write on short Characteristic Values over encrypted link |
LOGOLE11.1.7 |
Verify ability to begin and end reliable write on long Characteristic Values over encrypted link |
LOGOLE11.1.8 |
Verify ability to begin and abort reliable write on long Characteristic Values over encrypted link |