| /Zephyr-Core-3.5.0/dts/bindings/bluetooth/ |
| D | infineon,cyw43xxx-bt-hci.yaml | 4 # 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 bt-hci {
23 compatible = "infineon,cyw43xxx-bt-hci";
24 bt-reg-on-gpios = <&gpio_prt3 4 (GPIO_ACTIVE_HIGH)>;
26 fw-download-speed = <3000000>;
[all …]
|
| /Zephyr-Core-3.5.0/samples/bluetooth/hci_uart_async/ |
| D | sample.yaml | 2 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
|
| D | README.rst | 1 .. _bluetooth-hci-uart-async-sample:
3 Bluetooth: HCI UART based on ASYNC UART
6 Expose a Zephyr Bluetooth Controller over a standard Bluetooth HCI UART interface.
8 This sample performs the same basic function as the HCI UART sample, but it uses the UART_ASYNC_API
9 instead of UART_INTERRUPT_DRIVEN API. Not all boards implement both UART APIs, so the board support
10 of the HCI UART sample may be different.
17 Default UART settings
48 .. zephyr-app-commands::
49 :zephyr-app: samples/bluetooth/hci_uart_async
53 .. _bluetooth-hci-uart-async-qemu-posix:
[all …]
|
| /Zephyr-Core-3.5.0/drivers/bluetooth/hci/ |
| D | Kconfig | 4 # SPDX-License-Identifier: Apache-2.0
6 comment "Bluetooth HCI Driver Options"
14 prompt "Bluetooth HCI driver"
17 bool "H:4 UART"
20 Bluetooth H:4 UART driver. Requires hardware flow control
24 bool "H:5 UART [EXPERIMENTAL]"
28 Bluetooth three-wire (H:5) UART driver. Implementation of HCI
29 Three-Wire UART Transport Layer.
32 bool "HCI using RPMsg"
37 Bluetooth HCI driver for communication with another CPU
[all …]
|
| D | cyw43xxx.c | 5 * SPDX-License-Identifier: Apache-2.0
9 * @brief CYW43xxx HCI extension driver.
20 #include <zephyr/drivers/uart.h>
37 /* HCI Command packet from Host to Controller */
58 * This function executes vendor-specific commands sequence to
60 * bt_h4_vnd_setup function must be implemented in vendor-specific HCI
70 /* Get current UART configuration */ in bt_hci_uart_set_baudrate()
77 /* Re-configure UART */ in bt_hci_uart_set_baudrate()
94 * - To speed up application downloading, the MCU host commands the CYWxxx device in bt_update_controller_baudrate()
98 * In the above command, the xx xx xx xx bytes specify the 32-bit little-endian in bt_update_controller_baudrate()
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/cy8cproto_062_4343w/ |
| D | cy8cproto_062_4343w.dts | 3 * 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;
26 zephyr,shell-uart = &uart5;
36 compatible = "infineon,cat1-uart";
38 current-speed = <115200>;
40 pinctrl-0 = <&p5_1_scb5_uart_tx &p5_0_scb5_uart_rx>;
[all …]
|
| D | Kconfig.defconfig | 1 # CY8CPROTO-062-4343W PSoC™ 6 Wi-Fi BT Prototyping Kit configuration
4 # SPDX-License-Identifier: Apache-2.0
27 # Select HCI components
28 config UART config
|
| /Zephyr-Core-3.5.0/samples/bluetooth/hci_uart/ |
| D | README.rst | 1 .. _bluetooth-hci-uart-sample:
3 Bluetooth: HCI UART
9 Expose the Zephyr Bluetooth controller support over UART to another device/CPU
10 using the H:4 HCI transport protocol (requires HW flow control from the UART).
17 Default UART settings
38 provide a modern BLE 5.0 controller to a Linux-based machine for native
39 BLE support or QEMU-based development.
51 .. zephyr-app-commands::
52 :zephyr-app: samples/bluetooth/hci_uart
56 .. _bluetooth-hci-uart-qemu-posix:
[all …]
|
| D | sample.yaml | 2 name: Bluetooth HCI UART
3 description: Allows Zephyr to provide Bluetooth connectivity via UART
8 - nrf52dk_nrf52832
10 - uart
11 - bluetooth
17 - CONFIG_BT_CTLR_DF=y
19 - uart
20 - bluetooth
26 - CONFIG_BT_CTLR_DF=y
28 - uart
[all …]
|
| /Zephyr-Core-3.5.0/tests/bluetooth/hci_uart_async/src/ |
| D | test_hci_uart_async.c | 2 * 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
87 LOG_DBG("buf %p type %d len %u", buf, bt_buf_get_type(buf), buf->len); in drv_send()
88 LOG_HEXDUMP_DBG(buf->data, buf->len, "buf"); in drv_send()
97 /* Mock UART c2h TX handler. {{{ */
105 LOG_HEXDUMP_DBG(data, size, "uart tx"); in serial_vnd_data_callback()
107 /* If a test needs to look at the c2h UART traffic, it can be in serial_vnd_data_callback()
114 #define HCI_NORMAL_CMD_BUF_COUNT (CONFIG_BT_BUF_CMD_TX_COUNT - 1)
119 * - #bt_hci_cmd_hdr
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/ |
| D | bluetooth-arch.rst | 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:
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 …]
|
| D | overview.rst | 1 .. _bluetooth-overview:
15 grown to be mature and feature-rich, as can be seen in the section below.
20 Zephyr comes integrated with a feature-rich and highly configurable
34 * Controller-only (HCI) over UART, SPI, USB and IPC physical transports
35 * Host-only over UART, SPI, and IPC (shared memory)
38 * Bluetooth-SIG qualified
47 * Concurrent multi-protocol support ready
52 real-time specifics so that they can be encapsulated in a hardware-specific
54 * Support for Controller (HCI) builds over different physical transports
76 * Non-volatile storage support for permanent storage of Bluetooth-specific
[all …]
|
| D | bluetooth-tools.rst | 1 .. _bluetooth-tools:
10 .. _bluetooth-mobile-apps:
50 .. code-block:: console
54 ./bootstrap-configure --disable-android --disable-midi
63 and making sure to include the :literal:`-E` option in the daemon's execution
66 .. code-block:: console
68 ExecStart=/usr/libexec/bluetooth/bluetoothd -E
72 .. code-block:: console
74 sudo systemctl daemon-reload
94 with the help of the QEMU option :literal:`-serial unix:/tmp/bt-server-bredr`.
[all …]
|
| D | bluetooth-dev.rst | 1 .. _bluetooth-dev:
22 .. _bluetooth-hw-setup:
44 All the :ref:`bluetooth-configs` and :ref:`bluetooth-build-types` are supported
45 but you might need to build Zephyr more than once if you are using a dual-chip
50 <getting_started>`, choose one (or more if you are using a dual-chip solution)
54 .. _bluetooth-hci-tracing:
56 Embedded HCI tracing
57 --------------------
61 accessing the HCI traffic between the Host and the Controller. However, there
63 protocol that interleaves both normal log messages as well as the HCI traffic.
[all …]
|
| /Zephyr-Core-3.5.0/subsys/bluetooth/common/ |
| D | Kconfig | 5 # 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
26 The Controller will return this value in the HCI LE Read Buffer
46 The Controller will return this value in the HCI LE Read Buffer Size
61 the Host. This value does not include the HCI ACL header.
90 An L2CAP PDU is also referred to as an L2CAP basic frame or B-frame.
91 An L2CAP SDU is also referred to as an L2CAP Credit-based frame or
92 K-frame.
112 int "Maximum supported HCI Event buffer length"
[all …]
|
| /Zephyr-Core-3.5.0/samples/bluetooth/hci_uart_async/src/ |
| D | hci_uart_async.c | 2 * SPDX-License-Identifier: Apache-2.0
22 #include <zephyr/drivers/uart.h>
29 #include <zephyr/bluetooth/hci.h>
53 /** Send raw data on c2h UART.
55 * Blocks until completion. Not thread-safe.
58 * @retval -EBUSY Another transmission is in progress. This a
59 * thread-safety violation.
60 * @retval -errno @ref uart_tx error.
74 LOG_ERR("uart c2h tx: err %d", err); in uart_c2h_tx()
89 return ((const struct bt_hci_cmd_hdr *)hdr_buf)->param_len; in hci_payload_size()
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/96b_carbon_nrf51/ |
| D | 96b_carbon_nrf51.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "96b_carbon_nrf51-pinctrl.dtsi"
17 zephyr,shell-uart = &uart0;
18 zephyr,bt-mon-uart = &uart0;
38 pinctrl-0 = <&i2c0_default>;
39 pinctrl-1 = <&i2c0_sleep>;
40 pinctrl-names = "default", "sleep";
44 current-speed = <115200>;
46 pinctrl-0 = <&uart0_default>;
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/bl5340_dvk/ |
| D | bl5340_dvk_cpunet.dts | 2 * Copyright (c) 2021-2023 Laird Connectivity
4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "bl5340_dvk_cpunet-pinctrl.dtsi"
14 compatible = "lairdconnect,bl5340-dvk-cpunet";
18 zephyr,shell-uart = &uart0;
19 zephyr,uart-mcumgr = &uart0;
20 zephyr,bt-mon-uart = &uart0;
21 zephyr,bt-c2h-uart = &uart0;
24 zephyr,code-partition = &slot0_partition;
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/usb/device/ |
| D | usb_device.rst | 22 device requests in table 9-3 from the universal serial bus specification
42 See :zephyr:code-sample:`usb-audio-headphones-microphone` and
43 :zephyr:code-sample:`usb-audio-headset` samples for reference.
45 Bluetooth HCI USB transport layer
48 Bluetooth HCI USB transport layer implementation uses :ref:`bt_hci_raw`
49 to expose HCI interface to the host. It is not fully in line with the description
53 * HCI commands through control endpoint (host-to-device only)
54 * HCI events through interrupt IN endpoint
59 if HCI USB transport layer is the only interface that appears in the configuration,
61 The consequence is that if HCI USB is used in a composite configuration and is
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/raytac_mdbt53_db_40_nrf5340/ |
| D | raytac_mdbt53_db_40_nrf5340_cpunet.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "raytac_mdbt53_db_40_nrf5340_cpunet-pinctrl.dtsi"
13 model = "Raytac MDBT53-DB-40 NRF5340 Network";
14 compatible = "raytac,raytac-mdbt53-db-40-nrf5340-cpunet";
18 zephyr,shell-uart = &uart0;
19 zephyr,uart-mcumgr = &uart0;
20 zephyr,bt-mon-uart = &uart0;
21 zephyr,bt-c2h-uart = &uart0;
24 zephyr,code-partition = &slot0_partition;
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/raytac_mdbt53v_db_40_nrf5340/ |
| D | raytac_mdbt53v_db_40_nrf5340_cpunet.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "raytac_mdbt53v_db_40_nrf5340_cpunet-pinctrl.dtsi"
12 model = "Raytac MDBT53V-DB-40 NRF5340 Network";
13 compatible = "raytac,raytac-mdbt53v-db-40-nrf5340-cpunet";
17 zephyr,shell-uart = &uart0;
18 zephyr,uart-mcumgr = &uart0;
19 zephyr,bt-mon-uart = &uart0;
20 zephyr,bt-c2h-uart = &uart0;
23 zephyr,code-partition = &slot0_partition;
[all …]
|
| /Zephyr-Core-3.5.0/boards/arm/nrf5340_audio_dk_nrf5340/ |
| D | nrf5340_audio_dk_nrf5340_cpunet.dts | 4 * SPDX-License-Identifier: Apache-2.0
7 /dts-v1/;
9 #include "nrf5340_audio_dk_nrf5340_cpunet-pinctrl.dtsi"
13 compatible = "nordic,nrf5340-audio-dk-nrf5340-cpunet";
17 zephyr,shell-uart = &uart0;
18 zephyr,uart-mcumgr = &uart0;
19 zephyr,bt-mon-uart = &uart0;
20 zephyr,bt-c2h-uart = &uart0;
21 zephyr,bt-hci-rpmsg-ipc = &ipc0;
24 zephyr,code-partition = &slot0_partition;
[all …]
|
| /Zephyr-Core-3.5.0/samples/bluetooth/hci_uart/src/ |
| D | main.c | 3 * Copyright (c) 2015-2016 Intel Corporation
5 * SPDX-License-Identifier: Apache-2.0
21 #include <zephyr/drivers/uart.h>
28 #include <zephyr/bluetooth/hci.h>
57 * This is sized to align with a BLE HCI packet:
65 static int h4_read(const struct device *uart, uint8_t *buf, size_t len) in h4_read() argument
67 int rx = uart_fifo_read(uart, buf, len); in h4_read()
84 return ((const struct bt_hci_cmd_hdr *)hdr_buf)->param_len; in get_len()
87 sys_le16_to_cpu(((const struct bt_hci_iso_hdr *)hdr_buf)->len)); in get_len()
89 return sys_le16_to_cpu(((const struct bt_hci_acl_hdr *)hdr_buf)->len); in get_len()
[all …]
|
| /Zephyr-Core-3.5.0/boards/posix/native_posix/doc/ |
| D | index.rst | 19 a few peripherals such as an Ethernet driver, display, UART, etc., to enable
49 .. zephyr-app-commands::
50 :zephyr-app: samples/hello_world
51 :host-os: unix
63 .. code-block:: console
70 You can run it with the ``--help`` command line switch to get a list of
73 $ ./build/zephyr/zephyr.exe --help
102 (e.g., -O0) by setting :kconfig:option:`CONFIG_NO_OPTIMIZATIONS`.
152 LP64 ABI (x86-64 in x86 systems), where pointers and longs are 64 bits.
206 You can do this with the ``--rt`` and ``--no-rt`` options from the command line.
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/autopts/ |
| D | autopts-linux.rst | 1 .. _autopts-linux:
17 - Testing Zephyr Host Stack on QEMU
19 - Testing Zephyr Host Stack on native posix
21 - Testing Zephyr combined (controller + host) build on Real hardware (such as nRF52)
32 https://www.nordicsemi.com/Software-and-tools/Development-Tools/nRF-Command-Line-Tools/Download.
41 - JLink_Linux_V688a_x86_64.deb
43 - nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb
60 ---------------
64 Start -> Settings -> Update & Security -> Windows Update
67 ----------------
[all …]
|
