zephyr

History

Mariusz Skamra 7dc3d35da6 Bluetooth: gatt: Unsubscribe notification from callback directly With this patch application can unsubscribe notifications from Subscribe value callback directly, if BT_GATT_ITER_STOP is returned. Change-Id: I7873594f5dbe6e8c5bef11bf397a74cdc870a464 Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com>		2016-02-05 20:24:47 -05:00
..
beacon	Change BSD-3 licenses to Apache 2	2016-02-05 20:24:29 -05:00
central	Bluetooth: gatt: Unsubscribe notification from callback directly	2016-02-05 20:24:47 -05:00
init	Change BSD-3 licenses to Apache 2	2016-02-05 20:24:29 -05:00
peripheral	Bluetooth: samples/peripheral: Remove dependency on internal define	2016-02-05 20:24:39 -05:00
shell	Bluetooth: gatt: Unsubscribe notification from callback directly	2016-02-05 20:24:47 -05:00
test_bluetooth	Bluetooth: Convert driver header info to hidden Kconfig options	2016-02-05 20:24:45 -05:00
tester	Bluetooth: tester: Handle add descriptor command	2016-02-05 20:24:46 -05:00
README	samples: Update sanity_chk usage notes	2016-02-05 20:14:43 -05:00

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