Command Line Parameters for the Bluetooth HCI Transport Driver Test (Windows Embedded CE 6.0)
1/6/2010
The following table shows the command line parameters for the Bluetooth HCI Transport Driver Test.
| Command line parameter | Description |
|---|---|
/class hex_type |
Specifies the Bluetooth class type (in hexadecimal) to connect/accept; for example, /class 0x010000 |
/i iterations |
Specifies an integer number of iterations |
/accept |
Requires the device to accept the incoming connections |
The Bluetooth HCI Transport Driver Test uses KITL/Tux standard output. The expected result is Passed. To run the Bluetooth HCI Transport Driver Test, follow the procedure below.
Running the Bluetooth HCI Transport Driver Test
Copy the hciqa_con.dll, ddlx.dll, and Kato.dll, files to the Windows directory on the Windows Embedded CE-based devices that you want to use as subordinate device. Alternatively, if Platform Builder is connected to the Windows Embedded CE–based device that you want to use as subordinate, copy the files to the release directory. You can find these binaries in the Cepb\Wcetk\Ddtk\%_TGTCPU% directory in the directory where you installed Platform Builder.
Load and start OS mage with a Bluetooth support on both Windows Embedded CE-based devices.
Initiate Bluetooth pairing.
In the Windows Embedded CE Test Kit window, right-click on Bluetooth HCI Test, and then choose Edit Command Line. Modify the command line to pass to the test iterations and class type.
For example, if you desire two iterations and the class type is 0x010000, then the command line will read:
s tux -o -d ddlx.dll -c"-d hciqa_con.dll -i 2 -c /class 0x010000"
On the subordinate Windows Embedded CE-based device (using the above example), run
s tux – o -d ddlx.dll –c "-d hciqa_con.dll –i 2 –c /accept /class 0x010000"
From the Windows Embedded CE Test Kit window, start the test by selecting Bluetooth HCI Test.
Note
You must run Step 6 within 30 seconds after running Step 5.