WICED Manufacturing Bluetooth Test Tool, Document Number: 002-14799 Rev. *E
4
2
Setup
2.1 Device Configuration
The Cypress Bluetooth device to be tested must expose an HCI UART and that this UART can be connected to a COM port or
to a Serial to USB device of a PC. The HCI UART supports HCI Commands and Events described in this document.
The device should be preprogrammed with an application image and should be reset after it has been connected to the PC and
the COM port drivers are loaded.
Check the device specific Kit Guide or Quick Start Guide for any DIP switch settings or jumper settings to configure the device
to expose the HCI UART interface.
2.2 Environment Variables
2.2.1 MBT_BAUD_RATE
Cypress SoC Bluetooth devices support adjustable baud rates up to 4 Mbps via the
wiced_transport_init()
API included
with the WICED Bluetooth SDK. If this API is not utilized in an application to re-configure the baud rate, the default rate of 115.2
Kbps will be used by the device. The
MBT_BAUD_RATE
environment variable must be set to match what the device is using before
running WMBT.
As an example, to configure
MBT_BAUD_RATE
for 3 Mbps on a windows command line:
<ModusToolbox>\tools\wiced-tools-1.0\BT\wmbt\bin>set MBT_BAUD_RATE=3000000
2.2.2 TRANSPORT_MODE
The Bluetooth Core Specification [1] defines the HCI, which provides a standardized communication protocol between the BT
host stack and BT controller. Cypress SoC Bluetooth devices provide a high level of integration, for example, BT Controller and
embedded BT Host Stack in a single chip, to simplify BT product development for customers so that they are not required to be
familiar with all HCI commands and events. Typically, when the embedded stack is utilized in the Cypress device and it interfaces
to an onboard MCU, the MCU software would likely need to send and receive commands and events to the Cypress device. For
such a solution, WICED HCI is defined and provided as an example, see WICED HCI UART Control Protocol [2].
WMBT provides support for both HCI and WICED HCI via the
TRANSPORT_MODE
environment variable. If WICED HCI is
desired, your application must implement handlers for
HCI_CONTROL_TEST_COMMAND_ENCAPSULATED_HCI_COMMAND;
see
hci_control_test.c
included with the watch sample application. HCI should be sufficient for most cases since the devices
support this by default. The
TRANSPORT_MODE
environment variable must be set to the desired mode before running WMBT.
As an example, to configure
TRANSPORT_MODE
for HCI on a windows command line:
<ModusToolbox>\tools\wiced-tools-1.0\BT\wmbt\bin>set
TRANSPORT_MODE=0
