zephyrproject-rtos/zephyr
0
0
Fork 0
mirror of https://github.com/zephyrproject-rtos/zephyr synced 2025-09-08 23:42:51 +00:00
Code Issues Packages Projects Releases Wiki Activity
ceef6099dd
zephyr/samples/bluetooth
History
Mariusz Skamra ceef6099dd Bluetooth: shell: Improve device found event callback 
With this patch device name obtained from advertising packets
will be printed out.

[DEVICE]: D0:03:4B:DA:10:46 (public), AD evt type 0,
			RSSI -83 AppleLETester
[DEVICE]: D0:03:4B:DA:10:46 (public), AD evt type 4,
			RSSI -82
[DEVICE]: 00:A0:50:00:00:08 (public), AD evt type 0,
			RSSI -80 BLE Keyboard

Change-Id: Ic5116bce958d5b4479d481c40b2658ab56ecb819
Signed-off-by: Mariusz Skamra <mariusz.skamra@tieto.com>
2016-02-05 20:24:30 -05:00
..
beacon Change BSD-3 licenses to Apache 2 2016-02-05 20:24:29 -05:00
central Change BSD-3 licenses to Apache 2 2016-02-05 20:24:29 -05:00
init Change BSD-3 licenses to Apache 2 2016-02-05 20:24:29 -05:00
peripheral Bluetooth: Add authentication callbacks to the peripheral app 2016-02-05 20:24:30 -05:00
shell Bluetooth: shell: Improve device found event callback 2016-02-05 20:24:30 -05:00
test_bluetooth Change BSD-3 licenses to Apache 2 2016-02-05 20:24:29 -05:00
tester Bluetooth: Remove outdated comment from tester 2016-02-05 20:24:30 -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