Similar to a network processor configuration (host_test), the BLE-StackĬan be configured to be pass a subset HCI commands from a transport HCI commands to implement an external Bluetooth application. Processor configurations should use both HCI and TI vendor-specific To the CC2640 wireless MCU using standard HCI LE commands. It is not possible to interface an external, off-chip Bluetooth host Have their corresponding events consumed by the TI BLE host. However, because the BLE host and controller both reside on the The network processor canĪccept all LE HCI commands over a external transport protocol (UART, SPI, etc) (host_test) that allows an application to running on an external The BLE-Stack supports a network processor configuration See BLE Stack API Reference for a description of available HCIĪnd HCI extension commands callable in the embedded application. Of the functionality of the controller for use by the application. Likewise, the controller sends received data andĮvents to the host and upper layers through HCI.Īs well as standard Bluetooth LE HCI commands, a number of HCIĮxtension vendor-specific commands are available which extend some

Pass from the upper layers of the protocol stack through the HCI layer to The controller, such as ATT, GAP, etc, will eventually call an HCI API to All of the commands and events discussed that communicate with

HCI layer is implemented through function calls and callbacks within the In embedded wireless MCU projects such as simple_peripheral project, the Layer is implemented through a transport protocol such as SPI or Processor application (that is, the host_test project), the HCI Transports commands and events between the host and controllerĮlements of the Bluetooth protocol stack. The host controller interface (HCI) layer is a thin layer which

Bt rssi