zephyr

History

Mariusz Skamra 4ccef33723 Bluetooth: Add interactive connection and disconnection commands Adds above commands to the shell app. Connection is made based on given address and type eg: btshell> connect 00:00:00:00:00:00 public In callback we get local connection id which is in fact, the number of array entry in which the pointer to the corresponding bt_conn has been written. To disconnect, just provide the id eg: btshell> disconnect 0 Change-Id: I24f7ec2de7f84c53ab847ded28a1821753c2a60d Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com>		2016-02-05 20:14:23 -05:00
..
beacon	Bluetooth: Fix public Bluetooth includes	2016-02-05 20:14:23 -05:00
central	Bluetooth: Use ccflags-y instead of EXTRA_CFLAGS	2016-02-05 20:14:23 -05:00
init	Rename TIMO -> ZEPHYR	2016-02-05 20:14:16 -05:00
peripheral	Bluetooth: Make Bluetooth UUID defines consistent	2016-02-05 20:14:23 -05:00
shell	Bluetooth: Add interactive connection and disconnection commands	2016-02-05 20:14:23 -05:00
test_bluetooth	Bluetooth: Move HCI driver API to dedicated header file	2016-02-05 20:14:23 -05:00
tester	Bluetooth: Use ccflags-y instead of EXTRA_CFLAGS	2016-02-05 20:14:23 -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