zephyr

History

Peter Mitsis 9d63adf3ea Renames supported platform configurations Renames supported platform configurations to conform to new platform configuration naming scheme. Example usage with PLATFORM_CONFIG: make PLATFORM_CONFIG=basic_cortex_m3 make PLATFORM_CONFIG=basic_atom make PLATFORM_CONFIG=basic_minuteia make PLATFORM_CONFIG=galileo xxx_ti_lm3s6965_defconfig -> xxx_basic_cortex_m3_defconfig xxx_generic_pc_atom_n28xx_defconfig -> xxx_basic_atom_defconfig xxx_generic_pc_minuteia_defconfig -> xxx_basic_minuteia_defconfig xxx_quark_defconfig -> xxx_galileo_defconfig Change-Id: I696eb8b9ad9a72d7a72efbe1341ce23500335764 Signed-off-by: Peter Mitsis <peter.mitsis@windriver.com>		2016-02-05 20:14:39 -05:00
..
beacon	Renames supported platform configurations	2016-02-05 20:14:39 -05:00
central	Renames supported platform configurations	2016-02-05 20:14:39 -05:00
init	Renames supported platform configurations	2016-02-05 20:14:39 -05:00
peripheral	Renames supported platform configurations	2016-02-05 20:14:39 -05:00
shell	Renames supported platform configurations	2016-02-05 20:14:39 -05:00
test_bluetooth	Bluetooth: Move HCI driver API to dedicated header file	2016-02-05 20:14:23 -05:00
tester	Renames supported platform configurations	2016-02-05 20:14:39 -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