Lines Matching +full:serial +full:- +full:console

1 .. zephyr:code-sample:: bluetooth_hci_uart_async
3    :relevant-api: hci_raw bluetooth uart_interface
47 debugger interface and a CDC ACM serial port bridge. More information can be
52 .. zephyr-app-commands::
53    :zephyr-app: samples/bluetooth/hci_uart_async
57 .. _bluetooth-hci-uart-async-qemu-posix:
66 .. code-block:: console
68    sudo btattach -B /dev/ttyACM0 -S 1000000 -R
71    Depending on the serial port you are using you will need to modify the
72    ``/dev/ttyACM0`` string to point to the serial device your controller is
76    The ``-R`` flag passed to ``btattach`` instructs the kernel to avoid
86 .. _bluetooth-hci-uart-async-bluez:
95 .. code-block:: console
97    sudo btattach -B /dev/ttyACM0 -S 1000000
100    Depending on the serial port you are using you will need to modify the
101    ``/dev/ttyACM0`` string to point to the serial device your controller is
116 .. code-block:: console
118    west build samples/bluetooth/hci_uart_async -- -DEXTRA_CONFIG='debug.mixin.conf'
120 Then attach RTT as described here: :ref:`Using Segger J-Link <Using Segger J-Link>`
128 On the controller side, the ``zephyr,bt-c2h-uart`` DTS property (in the ``chosen``
130 keep the console logs, we can keep console on uart0 and the HCI on uart1 like
133 .. code-block:: dts
137          zephyr,console = &uart0;
138          zephyr,shell-uart = &uart0;
139          zephyr,bt-c2h-uart = &uart1;
144 driver instead of the built-in controller:
146 .. code-block:: cfg
151 Similarly, the ``zephyr,bt-hci`` DTS property selects which HCI instance to use.
154 .. code-block:: dts
158          zephyr,console = &uart0;
159          zephyr,shell-uart = &uart0;
160          zephyr,bt-hci = &bt_hci_uart;
167          compatible = "zephyr,bt-hci-uart";