mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 17:42:37 +00:00
…
|
||
---|---|---|
.. | ||
beacon | ||
central | ||
central_hr | ||
gatt | ||
ipsp | ||
peripheral | ||
peripheral_csc | ||
peripheral_dis | ||
peripheral_esp | ||
peripheral_hr | ||
peripheral_sc_only | ||
README |
Bluetooth subsystem = Building = Build samples $ make -C samples/bluetooth/<app> = Bluetooth Sample application = 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: $ sudo tools/btproxy -u Listening on /tmp/bt-server-bredr Note that before calling btproxy make sure that Bluetooth controller is down. Now running qemu result connecting second serial line to 'bt-server-bredr' UNIX socket. When Bluetooth (CONFIG_BLUETOOTH) and Bluetooth HCI UART driver (CONFIG_BLUETOOTH_H4) are enabled, Bluetooth driver registers to the system. From now on Bluetooth might be used by the application. To run application in the qemu run: $ make qemu = Bluetooth sanity check = There is smoke test application in nanokernel and microkernel test directories which gets run in sanity check script: $ scripts/sanity_chk/sanitycheck [-P <platform>] To only run Bluetooth tests use the -t bluetooth switch: $ scripts/sanity_chk/sanitycheck -t bluetooth