zephyr

mirror of https://github.com/zephyrproject-rtos/zephyr synced 2025-09-16 19:43:26 +00:00

History

Mariusz Skamra df7f3a193f Bluetooth: shell: Improve attribute discovery callback This patch makes attributes discovery more easier from the point of shell application user. UUIDs of discovered attribute declarations are now printed. For services handle range is shown. btshell> gatt-discover-primary 1800 btshell> Service 1800 found: start handle 00000001, end_handle 0000000b Characteristic properties are parsed to string and printed with characteristic value handle. Characteristic f000ffc1-0451-4000-b000-000000000000 found: handle 0000006a, value_handle 0000006b Properties: [write][write w/w rsp][notify] Change-Id: I6823fa562206ccf336dc301ee71bc4a02cecc14f Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com>		2016-02-05 20:24:30 -05:00
..
beacon
central
init
peripheral
shell	Bluetooth: shell: Improve attribute discovery callback	2016-02-05 20:24:30 -05:00
test_bluetooth
tester	Bluetooth: Remove outdated comment from tester	2016-02-05 20:24:30 -05:00
README

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