This page lists and describes tools that can be used to assist during Bluetooth stack or application development in order to help, simplify and speed up the development process.
It is often useful to make use of existing mobile applications to interact with hardware running Zephyr, to test functionality without having to write any additional code or requiring extra hardware.
The recommended mobile applications for interacting with Zephyr are:
Using BlueZ with Zephyr¶
The Linux Bluetooth Protocol Stack, BlueZ, comes with a very useful set of tools that can be used to debug and interact with Zephyr’s BLE Host and Controller. In order to benefit from these tools you will need to make sure that you are running a recent version of the Linux Kernel and BlueZ:
Linux Kernel 4.10+
Additionally, some of the BlueZ tools might not be bundled by default by your Linux distribution. If you need to build BlueZ from scratch to update to a recent version or to obtain all of its tools you can follow the steps below:
git clone git://git.kernel.org/pub/scm/bluetooth/bluez.git cd bluez ./bootstrap-configure --disable-android --disable-midi make
You can then find
btproxy in the
tools/ folder and
btmon in the
You’ll need to enable BlueZ’s experimental features so you can access its
most recent BLE functionality. Do this by editing the file
and making sure to include the
-E option in the daemon’s execution
Finally, reload and restart the daemon:
sudo systemctl daemon-reload sudo systemctl restart bluetooth
Running on QEMU and Native POSIX¶
It’s possible to run Bluetooth applications using either the QEMU emulator or Native POSIX. In either case, a Bluetooth controller needs to be exported from the host OS (Linux) to the emulator. For this purpose you will need some tools described in the Using BlueZ with Zephyr section.
Using the Host System Bluetooth Controller¶
The host OS’s Bluetooth controller is connected in the following manner:
To the second QEMU serial line using a UNIX socket. This socket gets used with the help of the QEMU option
-serial unix:/tmp/bt-server-bredr. This option gets passed to QEMU through QEMU_EXTRA_FLAGS automatically whenever an application has enabled Bluetooth support.
To a serial port in Native POSIX through the use of a command-line option passed to the Native POSIX executable:
On the host side, BlueZ allows you to export its Bluetooth controller through a so-called user channel for QEMU and Native POSIX to use.
You only need to run
btproxy when using QEMU. Native POSIX handles
the UNIX socket proxying automatically
If you are using QEMU, in order to make the Controller available you will need
one additional step using
Make sure that the Bluetooth controller is down
Use the btproxy tool to open the listening UNIX socket, type:
sudo tools/btproxy -u -i 0 Listening on /tmp/bt-server-bredr
You might need to replace
-i 0with the index of the Controller you wish to proxy.
Once the hardware is connected and ready to use, you can then proceed to building and running a sample:
Choose one of the Bluetooth sample applications located in
To run a Bluetooth application in QEMU, type:
west build -b qemu_x86 samples/bluetooth/<sample> west build -t run
Running QEMU now results in a connection with the second serial line to the
bt-server-bredrUNIX socket, letting the application access the Bluetooth controller.
To run a Bluetooth application in Native POSIX, first build it:
west build -b native_posix samples/bluetooth/<sample>
And then run it with:
$ sudo ./build/zephyr/zephyr.exe --bt-dev=hci0
Using a Zephyr-based BLE Controller¶
Depending on which hardware you have available, you can choose between two transports when building a single-mode, Zephyr-based BLE Controller:
Using Zephyr-based Controllers with BlueZ¶
If you want to test a Zephyr-powered BLE Controller using BlueZ’s Bluetooth Host, you will need a few tools described in the Using BlueZ with Zephyr section. Once you have installed the tools you can then use them to interact with your Zephyr-based controller:
sudo tools/btmgmt --index 0 [hci0]# auto-power [hci0]# find -l
You might need to replace
--index 0 with the index of the Controller
you wish to manage.
Additional information about
btmgmt can be found in its manual pages.