Lines Matching full:and
26 * **Host**: This layer sits right below the application, and is comprised of
27 multiple (non real-time) network and transport protocols enabling
28 applications to communicate with peer devices in a standard and interoperable
33 packet reception and transmission, guarantees the delivery of data, and
35 * **Radio Hardware**: Hardware implements the required analog and digital
36 baseband functional blocks that permit the Link Layer firmware to send and
48 can send to a Controller and the events that it can expect in return, and also
49 the format for user and protocol data that needs to go over the air. The HCI
50 ensures that different Host and Controller implementations can communicate
51 in a standard way making it possible to combine Hosts and Controllers from
59 The three separate layers of the protocol and the standardized interface make
60 it possible to implement the Host and Controller on different platforms. The two
64 implements all three layers and the application itself. This can also be called a
65 system-on-chip (SoC) implementation. In this case the BLE Host and the BLE
66 Controller communicate directly through function calls and queues in RAM. The
68 single-chip configuration and so how HCI commands, events, and data flows between
70 those applications and designs that require a small footprint and the lowest
73 one running the Application and the Host, and a second one with the Controller
74 and the Radio Hardware. This is sometimes also called a connectivity-chip
77 interoperability among Host and Controller implementations, including of course
78 Zephyr's very own BLE Host and Controller, users of the Zephyr Controller can
82 and the Zephyr OS BLE Host. Conversely, combining an IC running the Zephyr
90 The Zephyr software stack as an RTOS is highly configurable, and in particular,
92 include only the features and layers that are required to reduce RAM and ROM
97 the Link Layer and a special application. This application is different
104 This application acts as a bridge between the UART, SPI or USB peripherals and
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
126 together with enabling the device tree node for some other HCI driver and making
132 * **Combined build**: This includes the Application, the Host and the
133 Controller, and it is used exclusively for single-chip (SoC) configurations.
146 combined build (a build that includes both a BLE Host and a Controller in the
155 When using connectivity or dual-chip configurations, several Host and Controller
162 Host-only and Controller-only builds on dual-chip configurations
167 contains the application, the BLE Host and the selected HCI driver (UART or
187 :ref:`The host stack <bluetooth_le_host>`. This is where the HCI command and
189 the core protocols such as L2CAP, ATT, and SMP is also here.
202 the two common types of UART transport protocols (3-Wire and 5-Wire)