Lines Matching +full:verify +full:- +full:formatting

1 .. _bluetooth-tools:
14 .. _bluetooth-mobile-apps:
54 .. code-block:: console
58    ./bootstrap-configure --disable-android --disable-midi
67 and making sure to include the :literal:`-E` option in the daemon's execution
70 .. code-block:: console
72    ExecStart=/usr/libexec/bluetooth/bluetoothd -E
76 .. code-block:: console
78    sudo systemctl daemon-reload
99   with the help of the QEMU option :literal:`-serial unix:/tmp/bt-server-bredr`.
103   command-line option passed to the native_sim executable: ``--bt-dev=hci0``
106 through a so-called user channel for QEMU and :ref:`native_sim <native_sim>` to use.
119    .. code-block:: console
121       sudo tools/btproxy -u -i 0
122       Listening on /tmp/bt-server-bredr
124    You might need to replace :literal:`-i 0` with the index of the Controller
128    add :literal:`-z` to the ``btproxy`` command line to ignore any null bytes
139   .. zephyr-app-commands::
140      :zephyr-app: samples/bluetooth/<sample>
141      :host-os: unix
147   the :literal:`bt-server-bredr` UNIX socket, letting the application
152   .. zephyr-app-commands::
153      :zephyr-app: samples/bluetooth/<sample>
154      :host-os: unix
161      $ sudo ./build/zephyr/zephyr.exe --bt-dev=hci0
163 Using a Zephyr-based BLE Controller
167 transports when building a single-mode, Zephyr-based BLE Controller:
169 * UART: Use the :zephyr:code-sample:`bluetooth_hci_uart` sample and follow
170   the instructions in :ref:`bluetooth-hci-uart-qemu-posix`.
171 * USB: Use the :zephyr:code-sample:`bluetooth_hci_usb` sample and then
174 .. _bluetooth-hci-tracing:
181 in the format of a :ref:`bluetooth-hci` log.
182 In order to see those logs, you can use the built-in ``btmon`` tool from BlueZ:
184 .. code-block:: console
204 .. _bluetooth-embedded-hci-tracing:
207 --------------------
218 .. code-block:: cfg
223 - Setting :kconfig:option:`CONFIG_BT_DEBUG_MONITOR_UART` activates the formatting
224 - Clearing :kconfig:option:`CONFIG_UART_CONSOLE` makes the UART unavailable for
231 .. code-block:: console
233    $ btmon --tty <console TTY> --tty-speed 115200
235 If UART is not available (or you still want non-binary logs), you can set
239 .. code-block:: console
241    $ btmon --jlink nRF52840_xxAA,683578642
265    the branch ``controller-extended-advertising`` from Bumble.
286        ``emulator avd YOUR_AVD -packet-streamer-endpoint default``
289        the virtual controller from Android Emulator with the `Bumble`_ utility ``hci-bridge``.
291        ``bumble-hci-bridge tcp-server:_:1234 android-netsim``
298        ``./zephyr.exe --bt-dev=127.0.0.1:1234``
301 over the virtual Bluetooth controller that was bridged with Bumble. You can verify that the
304 peripheral samples such as :zephyr:code-sample:`ble_peripheral_hr` or
305 :zephyr:code-sample:`ble_peripheral_dis`.
309 Using Zephyr-based Controllers with BlueZ
312 If you want to test a Zephyr-powered BLE Controller using BlueZ's Bluetooth
315 Zephyr-based controller:
317    .. code-block:: console
319       sudo tools/btmgmt --index 0
320       [hci0]# auto-power
321       [hci0]# find -l
323 You might need to replace :literal:`--index 0` with the index of the Controller
329 .. _nRF Connect for iOS: https://itunes.apple.com/us/app/nrf-connect/id1054362403
331 .. _LightBlue for iOS: https://itunes.apple.com/us/app/lightblue-explorer/id557428110
333 .. _nRF Mesh for iOS: https://itunes.apple.com/us/app/nrf-mesh/id1380726771
337 .. _Android Device Manager: https://developer.android.com/studio/run/managing-avds