zephyr/samples/bluetooth
Mariusz Skamra b1c31ced58 Bluetooth: tester: Fix supported_settings to be sent in le order
All the data shall be sent in little-endian byte order.

Change-Id: I6d4ab0760f92e202ddcb348d30f0d1f208f84f1d
Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com>
2016-02-05 20:24:23 -05:00
..
beacon Bluetooth: Redesign Bluetooth init API 2016-02-05 20:14:44 -05:00
central Bluetooth: Check if bt_gatt_subscribe return -EALREADY 2016-02-05 20:14:44 -05:00
init Bluetooth: Redesign Bluetooth init API 2016-02-05 20:14:44 -05:00
peripheral Bluetooth: Make signed_value static in periperal sample 2016-02-05 20:15:40 -05:00
shell Bluetooth: SMP: Use tinycrypt if available 2016-02-05 20:24:23 -05:00
test_bluetooth Bluetooth: Redesign Bluetooth init API 2016-02-05 20:14:44 -05:00
tester Bluetooth: tester: Fix supported_settings to be sent in le order 2016-02-05 20:24:23 -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