zephyr

History

Szymon Janc c0baad2262 Rename simple UART driver to pipe UART Original name was too generic and confusing. This patch renames driver to pipe UART and moves it to console drivers folder. Kconfig destription is also improved. Change-Id: I716fdbf7d636bbdc03b0fce27a59fd866f473246 Signed-off-by: Szymon Janc <ext.szymon.janc@tieto.com>		2016-02-05 20:24:52 -05:00
..
beacon	Bluetooth: Kconfig: Change topmost option	2016-02-05 20:24:47 -05:00
central	Bluetooth: Kconfig: Change topmost option	2016-02-05 20:24:47 -05:00
init	Bluetooth: Kconfig: Change topmost option	2016-02-05 20:24:47 -05:00
peripheral	Bluetooth: Kconfig: Change topmost option	2016-02-05 20:24:47 -05:00
shell	Bluetooth: SMP: Refactor keys handling	2016-02-05 20:24:52 -05:00
test_bluetooth	Bluetooth: Convert driver header info to hidden Kconfig options	2016-02-05 20:24:45 -05:00
tester	Rename simple UART driver to pipe UART	2016-02-05 20:24:52 -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