zephyr/samples/bluetooth
Andrew Boie 6acbe63aea initial commit for next-gen sanity checks
The online help ./scripts/sanitycheck --help describes usage.
Most users will simply want to run with no arguments.

Change-Id: Icedbbfc22599a64a6e3dbbb808ff3276db06f2e0
Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-02-05 20:14:42 -05:00
..
beacon initial commit for next-gen sanity checks 2016-02-05 20:14:42 -05:00
central initial commit for next-gen sanity checks 2016-02-05 20:14:42 -05:00
init initial commit for next-gen sanity checks 2016-02-05 20:14:42 -05:00
peripheral initial commit for next-gen sanity checks 2016-02-05 20:14:42 -05:00
shell initial commit for next-gen sanity checks 2016-02-05 20:14:42 -05:00
test_bluetooth Bluetooth: Move HCI driver API to dedicated header file 2016-02-05 20:14:23 -05:00
tester initial commit for next-gen sanity checks 2016-02-05 20:14:42 -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