Lines Matching +full:- +full:- +full:build +full:- +full:only

1 .. _bluetooth-arch:
13    Zephyr supports mainly Bluetooth Low Energy (BLE), the low-power
18 .. _bluetooth-layers:
27   multiple (non real-time) network and transport protocols enabling
31   low-level, real-time protocol which provides, in conjunction with the Radio
32   Hardware, standard-interoperable over-the-air communication. The LL schedules
39 .. _bluetooth-hci:
54 .. _bluetooth-configs:
63 * **Single-chip configuration**: In this configuration, a single microcontroller
65   system-on-chip (SoC) implementation. In this case the BLE Host and the BLE
68   single-chip configuration and so how HCI commands, events, and data flows between
69   the two can be implementation-specific. This configuration is well suited for
72 * **Dual-chip configuration**: This configuration uses two separate ICs,
74   and the Radio Hardware. This is sometimes also called a connectivity-chip
85 .. _bluetooth-build-types:
87 Build Types
91 the BLE subsystem can be configured in multiple ways during the build process to
92 include only the features and layers that are required to reduce RAM and ROM
94 BLE-enabled builds that can be produced from the Zephyr project codebase:
96 * **Controller-only build**: When built as a BLE Controller, Zephyr includes
100   * :zephyr:code-sample:`bluetooth_hci_uart`
101   * :zephyr:code-sample:`bluetooth_hci_usb`
102   * :zephyr:code-sample:`bluetooth_hci_spi`
106   and responding with events and received data.  A build of this type sets the
116 * **Host-only build**: A Zephyr OS Host build will contain the Application and
119   A build of this type sets the following Kconfig option values:
127   sure that the ``zephyr,bt-hci`` device tree chosen property points at it.
130   used for Controller-only builds can be built as Host-only
132 * **Combined build**: This includes the Application, the Host and the
133   Controller, and it is used exclusively for single-chip (SoC) configurations.
134   A build of this type sets the following Kconfig option values:
143   used for Controller-only builds can be built as Combined
145 The picture below shows the SoC or single-chip configuration when using a Zephyr
146 combined build (a build that includes both a BLE Host and a Controller in the
151    :alt: BLE Combined build on a single chip
153    A Combined build on a Single-Chip configuration
155 When using connectivity or dual-chip configurations, several Host and Controller
160    :alt: BLE dual-chip configuration builds
162    Host-only and Controller-only builds on dual-chip configurations
166 must be programmed into each of the chips respectively. The Host build image
168 SPI), while the Controller build runs either the
169 :zephyr:code-sample:`bluetooth_hci_uart`, or the
170 :zephyr:code-sample:`bluetooth_hci_spi` app to provide an interface to
176 via UART or USB to one or more instances of the Zephyr OS Controller build.
192   :ref:`Bluetooth LE Controller <bluetooth-ctlr-arch>` implementation.
193   Implements the controller-side of HCI, the Link Layer as well as access to the
202   the two common types of UART transport protocols (3-Wire and 5-Wire)
206   :zephyr:code-sample-category:`Sample Bluetooth code <bluetooth>`. This is a good reference to
217 .. _Bluetooth Specification: https://www.bluetooth.com/specifications/bluetooth-core-specification