Lines Matching +full:child +full:- +full:ref

1 .. zephyr:code-sample:: bluetooth_hci_uart
3    :relevant-api: hci_raw bluetooth uart_interface
39 provide a modern Bluetooth LE 5.0 controller to a Linux-based machine for native
40 BLE support or QEMU-based development.
43 instructions in the :ref:`bluetooth_bluez` section.
48 found in :ref:`nordic_segger`.
52 .. zephyr-app-commands::
53    :zephyr-app: samples/bluetooth/hci_uart
57 .. _bluetooth-hci-uart-qemu-posix:
62 In order to use the HCI UART controller with QEMU or :ref:`native_sim <native_sim>` you will need
66 .. code-block:: console
68    sudo btattach -B /dev/ttyACM0 -S 1000000 -R
80    The ``-R`` flag passed to ``btattach`` instructs the kernel to avoid
88 :ref:`bluetooth_qemu_native` section to use QEMU with it.
90 .. _bluetooth-hci-uart-bluez:
99 .. code-block:: console
101    sudo btattach -B /dev/ttyACM0 -S 1000000
116 :ref:`bluetooth_ctlr_bluez` section to use BlueZ with it.
124 .. code-block:: console
126    west build samples/bluetooth/hci_uart -- -DEXTRA_CONF_FILE='debug.conf'
128 Then attach RTT as described here: :ref:`Using Segger J-Link <Using Segger J-Link>`
137 .. code-block:: console
139    west build samples/bluetooth/hci_uart -b nrf52833dk/nrf52833@df -- -DCONFIG_BT_CTLR_DF=y
146 Check the :zephyr:code-sample:`ble_direction_finding_connectionless_rx` and the
147 :zephyr:code-sample:`ble_direction_finding_connectionless_tx` for more details.
160 On the controller side, the ``zephyr,bt-c2h-uart`` DTS property (in the ``chosen``
165 .. code-block:: dts
170          zephyr,shell-uart = &uart0;
171          zephyr,bt-c2h-uart = &uart1;
176 driver instead of the built-in controller:
178 .. code-block:: cfg
183 Similarly, the ``zephyr,bt-hci`` DTS property selects which HCI instance to use.
184 The UART needs to have as its child node a HCI UART node:
186 .. code-block:: dts
191          zephyr,shell-uart = &uart0;
192          zephyr,bt-hci = &bt_hci_uart;
199          compatible = "zephyr,bt-hci-uart";