zephyr

History

Arkadiusz Lichwa b62f778664 Bluetooth: Start outgoing connection with tracking Enables make outgoing connection with error handling. Free connection objects maintained in polls are assigned to active connection by result of lookup on the polls based on input peer LE address. Updates shell application to reflect above changes in stack. Change-Id: Ibc71343c0d122cc78c48bac2ff1e50533369b7d2 Signed-off-by: Arkadiusz Lichwa <arkadiusz.lichwa@tieto.com>		2016-02-05 20:14:31 -05:00
..
beacon	Bluetooth: Fix public Bluetooth includes	2016-02-05 20:14:23 -05:00
central	Bluetooth: Introduce LE scan callback	2016-02-05 20:14:24 -05:00
init	Rename TIMO -> ZEPHYR	2016-02-05 20:14:16 -05:00
peripheral	Bluetooth: Replace peer address with conn in GATT API	2016-02-05 20:14:30 -05:00
shell	Bluetooth: Start outgoing connection with tracking	2016-02-05 20:14:31 -05:00
test_bluetooth	Bluetooth: Move HCI driver API to dedicated header file	2016-02-05 20:14:23 -05:00
tester	Bluetooth: Notify about connection events in tester app	2016-02-05 20:14:31 -05:00
README	Bluetooth: Update README in samples	2016-02-05 20:14:19 -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 -T gcc [-B <BSP>]

For quick regression test use bt_regression, it only check Bluetooth test

$ samples/bluetooth/bt_regression.sh