mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-30 23:16:20 +00:00
2975ca0754
The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
44 lines
1.1 KiB
ReStructuredText
44 lines
1.1 KiB
ReStructuredText
.. _bluetooth_setup:
|
|
|
|
Bluetooth
|
|
##########
|
|
|
|
To build any of the Bluetooth samples, follow the instructions below:
|
|
|
|
.. code-block:: console
|
|
|
|
$ make -C samples/bluetooth/<app>
|
|
|
|
Host Bluetooth controller is connected to the second QEMU serial line through a
|
|
Unix socket (QEMU option -serial unix:/tmp/bt-server-bredr). This option is
|
|
already added to QEMU through QEMU_EXTRA_FLAGS in Makefile.
|
|
|
|
On the host side BlueZ allows to "connect" Bluetooth controller through a
|
|
so-called user channel. Use the btproxy tool for that:
|
|
|
|
Note that before calling ``btproxy`` make sure that Bluetooth controller is
|
|
down.
|
|
|
|
.. code-block:: console
|
|
|
|
$ sudo tools/btproxy -u
|
|
Listening on /tmp/bt-server-bredr
|
|
|
|
Running the application in QEMU will connect the second serial line to
|
|
``bt-server-bredr`` Unix socket. When Bluetooth (CONFIG_BT) and Bluetooth
|
|
HCI UART driver (CONFIG_BT_H4) are enabled, the Bluetooth driver
|
|
registers with the system.
|
|
|
|
From now on Bluetooth may be used by the application. To run applications in
|
|
the QEMU emulation environment, type:
|
|
|
|
.. code-block:: console
|
|
|
|
$ make run
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
:glob:
|
|
|
|
**/*
|