Home
last modified time | relevance | path

Searched +full:hci +full:- +full:uart (Results 1 – 25 of 203) sorted by relevance

123456789

/Zephyr-latest/dts/bindings/bluetooth/
Dzephyr,bt-hci-uart.yaml1 # UART Bluetooth HCI device
3 description: Bluetooth HCI behind a UART device (H:4)
5 compatible: "zephyr,bt-hci-uart"
7 include: bt-hci.yaml
10 bt-hci-name:
12 bt-hci-bus:
13 default: "uart"
Dzephyr,bt-hci-3wire-uart.yaml1 # UART Bluetooth HCI device
3 description: Bluetooth HCI behind a 3-Wire UART device (H:5)
5 compatible: "zephyr,bt-hci-3wire-uart"
7 include: bt-hci.yaml
10 bt-hci-name:
12 bt-hci-bus:
13 default: "uart"
Dinfineon,cyw43xxx-bt-hci.yaml4 # SPDX-License-Identifier: Apache-2.0
7 CYW43xxx Connectivity that uses Zephyr's Bluetooth Host Controller Interface UART
14 current-speed = <115200>;
16 /* HCI-UART pins*/
17 pinctrl-0 = <&p3_1_scb2_uart_tx &p3_0_scb2_uart_rx
19 pinctrl-names = "default";
21 /* HW Flow control must be enabled for HCI H4 */
22 hw-flow-control;
24 bt-hci {
26 compatible = "infineon,cyw43xxx-bt-hci";
[all …]
Dnxp,bt-hci-uart.yaml2 # SPDX-License-Identifier: Apache-2.0
7 compatible: "nxp,bt-hci-uart"
12 sdio-reset-gpios:
13 type: phandle-array
16 w-disable-gpios:
17 type: phandle-array
20 hci-operation-speed:
23 HCI UART baudrate for feature operation. If not defined
24 bus/current-speed will be used as default.
26 hw-flow-control:
[all …]
Dzephyr,bt-hci-userchan.yaml1 description: Bluetooth HCI provided by a Linux HCI user channel socket
3 compatible: "zephyr,bt-hci-userchan"
5 include: bt-hci.yaml
8 bt-hci-name:
9 default: "HCI User Channel"
10 bt-hci-bus:
11 default: "uart"
Dbt-hci.yaml1 # Common fields for Bluetooth HCI devices
6 bt-hci-name:
8 description: Name of the HCI transport
9 bt-hci-bus:
13 - "virtual"
14 - "usb"
15 - "pccard"
16 - "uart"
17 - "rs232"
18 - "pci"
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart_async/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart_async
2 :name: HCI UART async
3 :relevant-api: hci_raw bluetooth uart_interface
5 Expose a Bluetooth controller to another device or CPU over asynchronous UART.
10 Expose Bluetooth Controller support over a standard Bluetooth HCI UART interface.
12 This sample performs the same basic function as the HCI UART sample, but it uses the UART_ASYNC_API
13 instead of UART_INTERRUPT_DRIVEN API. Not all boards implement both UART APIs, so the board support
14 of the HCI UART sample may be different.
21 Default UART settings
52 .. zephyr-app-commands::
[all …]
Dsample.yaml2 name: Bluetooth HCI UART Async
4 This sample is a batteries-included example of a Bluetooth HCI UART
7 It demonstrates a possible implementation of an HCI UART (H4)
9 over a UART.
11 This implementation is based on the Zephyr Asynchoronous UART API.
16 - nrf52dk/nrf52832
18 - uart
19 - bluetooth
/Zephyr-latest/samples/bluetooth/hci_uart/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart
2 :name: HCI UART
3 :relevant-api: hci_raw bluetooth uart_interface
5 Expose a Bluetooth controller to another device or CPU over UART.
10 Expose Bluetooth controller support over UART to another device/CPU
11 using the H:4 HCI transport protocol (requires HW flow control from the UART).
18 Default UART settings
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
52 .. zephyr-app-commands::
[all …]
/Zephyr-latest/drivers/bluetooth/hci/
DKconfig4 # SPDX-License-Identifier: Apache-2.0
6 comment "Bluetooth HCI Driver Options"
14 bool "H:4 UART"
19 Bluetooth H:4 UART driver. Requires hardware flow control
23 bool "H:5 UART [EXPERIMENTAL]"
29 Bluetooth three-wire (H:5) UART driver. Implementation of HCI
30 Three-Wire UART Transport Layer.
40 Bluetooth HCI driver for communication with another CPU
48 HCI packets are sent and received as single Byte transfers,
64 Bluetooth HCI over SPI driver for communication with Bluetooth
[all …]
/Zephyr-latest/samples/bluetooth/hci_uart_3wire/
DREADME.rst1 .. zephyr:code-sample:: bluetooth_hci_uart_3wire
2 :name: HCI 3-wire (H:5)
3 :relevant-api: hci_raw bluetooth uart_interface
5 Expose a Bluetooth controller to another device or CPU over H5:HCI transport.
10 Expose Bluetooth controller support over UART to another device/CPU
11 using the H:5 HCI transport protocol.
18 Default UART settings
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
52 .. zephyr-app-commands::
[all …]
/Zephyr-latest/boards/infineon/cy8cproto_062_4343w/
Dcy8cproto_062_4343w.dts3 * SPDX-License-Identifier: Apache-2.0
6 /dts-v1/;
9 #include "cy8cproto_062_4343w-common.dtsi"
10 #include "cy8cproto_062_4343w-pinctrl.dtsi"
17 uart-5 = &uart5;
18 i2c-0 = &i2c3;
27 zephyr,shell-uart = &uart5;
28 zephyr,bt-hci = &bt_hci_uart;
37 compatible = "infineon,cat1-uart";
39 current-speed = <115200>;
[all …]
/Zephyr-latest/boards/qemu/cortex_m3/
Dqemu_cortex_m3.dts2 /* SPDX-License-Identifier: Apache-2.0 */
4 /dts-v1/;
9 model = "QEMU Cortex-M3";
10 compatible = "ti,lm3s6965evb-qemu", "ti,lm3s6965";
13 uart-0 = &uart0;
14 uart-1 = &uart1;
15 uart-2 = &uart2;
22 zephyr,shell-uart = &uart0;
23 zephyr,bt-hci = &bt_hci_uart;
24 zephyr,uart-pipe = &uart1;
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/
Dbluetooth-arch.rst1 .. _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:
46 (HCI) protocol. HCI can be implemented over a range of different physical
47 transports like UART, SPI, or USB. This protocol defines the commands that a Host
49 the format for user and protocol data that needs to go over the air. The HCI
[all …]
Dfeatures.rst1 .. _bluetooth-features:
15 grown to be mature and feature-rich, as can be seen in the section below.
26 * Support for :ref:`all combinations <bluetooth-hw-setup>` of Host and
29 * Controller-only (HCI) over UART, SPI, USB and IPC physical transports
30 * Host-only over UART, SPI, and IPC (shared memory)
33 * :ref:`Bluetooth-SIG qualifiable <bluetooth-qual>`
38 * :ref:`Bluetooth Low Energy Controller <bluetooth-ctlr-arch>` (LE Link Layer)
42 * Concurrent multi-protocol support ready
47 real-time specifics so that they can be encapsulated in a hardware-specific
49 * Support for Controller (HCI) builds over different physical transports
[all …]
/Zephyr-latest/tests/bluetooth/hci_uart_async/src/
Dtest_hci_uart_async.c2 * SPDX-License-Identifier: Apache-2.0
18 #include <zephyr/drivers/uart/serial_test.h>
22 /* This is a mock UART. Using `serial_vnd_...` on this simulates
86 struct drv_data *drv = dev->data; in drv_open()
90 drv->recv = recv; in drv_open()
105 LOG_DBG("buf %p type %d len %u", buf, bt_buf_get_type(buf), buf->len); in drv_send()
106 LOG_HEXDUMP_DBG(buf->data, buf->len, "buf"); in drv_send()
115 /* Mock UART c2h TX handler. {{{ */
123 LOG_HEXDUMP_DBG(data, size, "uart tx"); in serial_vnd_data_callback()
125 /* If a test needs to look at the c2h UART traffic, it can be in serial_vnd_data_callback()
[all …]
/Zephyr-latest/boards/shields/mikroe_ble_tiny_click/
Dmikroe_ble_tiny_click.overlay4 * SPDX-License-Identifier: Apache-2.0
9 zephyr,bt-hci = &bt_hci_uart;
17 compatible = "zephyr,bt-hci-uart";
21 compatible = "renesas,bt-hci-da1453x";
22 reset-gpios = <&mikrobus_header 1 GPIO_ACTIVE_HIGH>;
/Zephyr-latest/boards/shields/renesas_us159_da14531evz/
Drenesas_us159_da14531evz.overlay4 * SPDX-License-Identifier: Apache-2.0
9 zephyr,bt-hci = &bt_hci_uart;
17 compatible = "zephyr,bt-hci-uart";
21 compatible = "renesas,bt-hci-da1453x";
23 reset-gpios = <&pmod_header 5 GPIO_ACTIVE_LOW>;
/Zephyr-latest/boards/up-bridge-the-gap/up_squared/
Dup_squared.dts4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
20 i2c-0 = &i2c0;
21 i2c-1 = &i2c1;
27 zephyr,shell-uart = &uart0;
28 zephyr,bt-hci = &bt_hci_uart;
29 zephyr,uart-pipe = &uart1;
30 zephyr,bt-mon-uart = &uart1;
34 #address-cells = <1>;
35 #size-cells = <0>;
[all …]
/Zephyr-latest/tests/bsim/bluetooth/hci_uart/
Dcompile.sh3 # SPDX-License-Identifier: Apache-2.0
7 #set -x #uncomment this line for debugging
8 set -ue
14 cmake_extra_args=-DEXTRA_DTC_OVERLAY_FILE=hci-uart.overlay compile
16 cmake_extra_args=-DEXTRA_DTC_OVERLAY_FILE=hci-uart.overlay compile
/Zephyr-latest/tests/bluetooth/init/
Dh5.overlay3 zephyr,bt-hci = &bt_hci_3wire_uart;
13 compatible = "zephyr,bt-hci-3wire-uart";
/Zephyr-latest/boards/shields/x_nucleo_wb05kn1/
Dx_nucleo_wb05kn1_uart.overlay4 * SPDX-License-Identifier: Apache-2.0
9 zephyr,bt-hci = &bt_hci_uart;
14 current-speed = <921600>;
17 compatible = "zephyr,bt-hci-uart";
/Zephyr-latest/tests/bluetooth/shell/boards/
Dmimxrt1060_evk_mimxrt1062_qspi.overlay4 * SPDX-License-Identifier: Apache-2.0
9 zephyr,bt-hci = &bt_hci_uart;
15 current-speed = <3000000>;
16 hw-flow-control;
19 compatible = "zephyr,bt-hci-uart";
/Zephyr-latest/boards/shields/frdm_kw41z/
Dfrdm_kw41z.overlay4 * SPDX-License-Identifier: Apache-2.0
9 zephyr,bt-hci = &bt_hci_uart;
15 current-speed = <115200>;
18 compatible = "zephyr,bt-hci-uart";
/Zephyr-latest/subsys/bluetooth/common/
DKconfig5 # SPDX-License-Identifier: Apache-2.0
16 Controller. This value does not include the HCI ACL header.
21 In a Host-only build the Host will read the maximum ACL size supported
27 The Controller will return this value in the HCI LE Read Buffer
48 The Controller will return this value in the HCI LE Read Buffer Size
63 the Host. This value does not include the HCI ACL header.
109 enforced by a build-time check: BT_BUF_ACL_RX_COUNT needs to be at
113 int "Maximum supported HCI Event buffer length"
120 Maximum supported HCI event buffer size. This value does not include
121 the HCI Event header.
[all …]

123456789