zephyr

History

Andrei Emeltchenko 3760dc8709 Bluetooth: Add Bluetooth nanokernel smoke test The test registers Bluetooth driver to the Bluetooth subsystem and runs bt_init() which calls open() callback. We return expected error to indicate that there is no real Bluetooth device attached. Change-Id: I1b324c82ce8be2ce73f2b41a07135b0bc76eed61 Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>		2016-02-05 20:13:50 -05:00
..
init	Bluetooth: Add Bluetooth init sample	2016-02-05 20:13:45 -05:00
peripheral	Bluetooth: Add LE peripheral sample app	2016-02-05 20:13:49 -05:00
test_bluetooth	Bluetooth: Add Bluetooth nanokernel smoke test	2016-02-05 20:13:50 -05:00
README	Bluetooth: Add Bluetooth init sample	2016-02-05 20:13:45 -05:00

README

Bluetooth subsystem

= Architecture =

All processing is done in fibers. Basic structure for packet processing
is bt_buf. Packets are queued to different queues and processed. Packet
allocation is done through a free packets queue which gets populated
during the stack init.

= Building =

$ make -C host/src
$ make -C samples/bluetooth/<app>

= Testing =

Host Bluetooth controler is connected to the second qemu serial line
through a UNIX socket (qemu option -serial unix:/tmp/bt-server-bredr).

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

Now qemu can connect serial line to the 'bt-server-bredr' UNIX socket
with following command:

$ make -C samples/bluetooth/<app> NODE1.qemu