mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-05 23:31:57 +00:00
This application is intended for automated testing. It used binary protocol for communication over UART and can be used for driving Bluetooth stack by external tester. Currently only single command registering (init) GAP service is implemented. Change-Id: I62e151baa2badc0f1297e65591b5f494ff7b841e Signed-off-by: Szymon Janc <szymon.janc@tieto.com> |
||
---|---|---|
.. | ||
beacon | ||
central | ||
init | ||
peripheral | ||
shell | ||
test_bluetooth | ||
tester | ||
bt_regression.sh | ||
README |
Bluetooth subsystem = Building = Build samples $ make -C samples/bluetooth/<app> = Testing = Host Bluetooth controler is connected to the second qemu serial line through a UNIX socket (qemu option -serial unix:/tmp/bt-server-bredr). 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 Now qemu can connect serial line to the 'bt-server-bredr' UNIX socket with following command: $ make qemu Extra parameter to qemu might be added through QEMU_EXTRA_FLAGS. There is smoke test application in nanokernel and microkernel test directories which gets run in sanity check script: $ scripts/sanity_chk/sanity_chk -T gcc [-B <BSP>] For quick regression test use bt_regression, it only check Bluetooth test $ samples/bluetooth/bt_regression.sh