• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..--

boards/03-Apr-2024-3228

src/03-Apr-2024-333240

CMakeLists.txtD03-Apr-2024294 117

README.rstD03-Apr-20241.4 KiB4129

prj.confD03-Apr-2024360 1410

sample.yamlD03-Apr-2024351 1615

README.rst

1.. _bluetooth-hci-spi-sample:
2
3Bluetooth: HCI SPI
4##################
5
6Overview
7********
8
9Expose Zephyr Bluetooth Controller support over SPI to another device/CPU using
10the Zephyr SPI HCI transport protocol (similar to BlueNRG).
11
12Requirements
13************
14
15A board with SPI slave, GPIO and Bluetooth Low Energy support.
16
17Building and Running
18********************
19
20You then need to ensure that your :ref:`devicetree <dt-guide>` defines a node
21for the HCI SPI slave device with compatible
22:dtcompatible:`zephyr,bt-hci-spi-slave`. This node sets an interrupt line to
23the host and associates the application with a SPI bus to use.
24
25See :zephyr_file:`boards/nrf51dk_nrf51422.overlay
26<samples/bluetooth/hci_spi/boards/nrf51dk_nrf51422.overlay>` in this sample
27directory for an example overlay for the :ref:`nrf51dk_nrf51422` board.
28
29You can then build this application and flash it onto your board in
30the usual way; see :ref:`boards` for board-specific building and
31flashing information.
32
33You will also need a separate chip acting as BT HCI SPI master. This
34application is compatible with the HCI SPI master driver provided by
35Zephyr's Bluetooth HCI driver core; see the help associated with the
36:kconfig:option:`CONFIG_BT_SPI` configuration option for more information.
37
38Refer to :ref:`bluetooth-samples` for general Bluetooth information, and
39to :ref:`96b_carbon_nrf51_bluetooth` for instructions specific to the
4096Boards Carbon board.
41