mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-08-27 01:25:58 +00:00
81546cfc0a
This adds gatt-exchange-mtu which works as follow: btshell> gatt-exchange-mtu <bdaddr> <bdaddr_type> bt: bt_gatt_exchange_mtu (0x0010c138): Client MTU 65 Exchange pending btshell> bt: bt_att_recv (0x0010e310): Received ATT code 0x03 len 3 bt: att_mtu_rsp (0x0010e310): Server MTU 517 Exchange successful Change-Id: I7280fb9d9fafc0f4bd1ef0f2226c255a5acf2592 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