Command Line Parameters for the Bluetooth Performance Test (Windows Embedded CE 6.0)
1/6/2010
The Bluetooth Performance Test executes the tux -o -d perf_bluetooth -c "-s serverAddress -b numberOfBuffers -p serverChannelNumber" command line. For the client (or device under test), all these parameters are mandatory. For the server (or peer device), all parameters are mandatory except for the -s flag.
You can modify the behavior of the Bluetooth Performance Test by editing the command line for the test. To specify one or more of the following optional command line parameters for this test, use the –c command line parameter, with the parameter list following in quotation marks. The -c parameter forces Tux to pass the specified string into the test module. For more information about how to edit the command line for a test, see Editing the Command-Line for a Test.
The following table shows the command line parameters for the Bluetooth Performance Test.
| Command line parameter | Description |
|---|---|
-b numberOfBuffers |
Number of buffers to transfer for data transfer stress test |
-p serverChannelNumber |
RFCOMM channel at which server is listening |
-s serverAddress |
Bluetooth address of server or peer device in 12-digit hex format .gif "Ee506320.note(en-US,WinEmbedded.60).gif") Note:
Do not use an initial 0x
|
Note
Bluetooth hardware is not generally very reliable. Test cases often fail due to hardware failure. If the test continues to fail after numerous tries, hardware may not be the issue.