mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-08 01:32:30 +00:00
This patch changes the way the attributes are added to the database. From now, attributes will be registered one by one in gatt_db_add function. This change is needed, because the handle of the attribute is assigned in bt_gatt_register, and the tester application has to respond to the command with valid attribute handles. Moreover, Set Value command rely on the attribute handle, based on which it looks for an attribute with handle spacified by tester to set it's value. Change-Id: I1f251f9bd5579bde2a52ebe3f1997da49c1b1721 Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com> |
||
---|---|---|
.. | ||
beacon | ||
central | ||
init | ||
peripheral | ||
shell | ||
test_bluetooth | ||
tester | ||
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_UART) 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/sanity_chk [-P <platform>] For quick regression test use bt_regression, it only check Bluetooth test $ samples/bluetooth/bt_regression.sh