zephyr/samples/bluetooth
Grzegorz Kolodziejczyk 76bf6f60aa Bluetooth: Use generic read string handler for db descriptors
There is no need to define for each descriptor its own read handler.
Each string descriptor will use generic string read handler if
possible.

Change-Id: I468a082c6875400ec4515588131132ef27cc8082
Signed-off-by: Grzegorz Kolodziejczyk <grzegorz.kolodziejczyk@tieto.com>
2016-02-05 20:15:38 -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: Add new attribute with signed write permission 2016-02-05 20:15:24 -05:00
shell Bluetooth: Use generic read string handler for db descriptors 2016-02-05 20:15:38 -05:00
test_bluetooth Bluetooth: Redesign Bluetooth init API 2016-02-05 20:14:44 -05:00
tester Bluetooth: Fix tester application automated build 2016-02-05 20:15:37 -05:00
README samples: Update sanity_chk usage notes 2016-02-05 20:14:43 -05:00

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