mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-24 13:06:04 +00:00
This adds gatt-discover-characteristic which works as follow: btshell>gatt-discover-characteristic <bdaddr> <bdaddr_type> [UUID] [start_handle] [end_handle] bt: bt_gatt_discover_characteristic (0x0010d098): start_handle 0x000b end_handle 0x0011 Discover pending btshell>bt: bt_att_recv (0x0010f294): Received ATT code 0x09 len 23 bt: att_handle_read_type_rsp (0x0010f294): bt: att_read_type_rsp (0x0010f294): err 0x00 bt: att_read_type_rsp (0x0010f294): handle 0x000b properties 0x02 value_handle 0x000c Discover found handle 11 bt: att_read_type_rsp (0x0010f294): handle 0x000d properties 0x10 value_handle 0x000e Discover found handle 13 bt: att_read_type_rsp (0x0010f294): handle 0x0010 properties 0x08 value_handle 0x0011 Discover found handle 16 Discover destroy Change-Id: I04aad56cc4f978e3a884adffc487ae4dcc1c4ee9 Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.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 -T gcc [-B <BSP>] For quick regression test use bt_regression, it only check Bluetooth test $ samples/bluetooth/bt_regression.sh