zephyr/samples/bluetooth
Luiz Augusto von Dentz e9083dfcd7 Bluetooth: GATT: Add flags to attribute write callback
This adds flags parameter to write callback which can be used to indicate
that data only need to be prepared with use of BT_GATT_WRITE_FLAG_PREPARE
fixing qualification tests that needs to check authorization or other
errors that cannot be verified with just the permissions.

Change-Id: I3d662b2027718ffb52a280e3bbc9750be14f89ae
Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2016-06-28 17:36:08 +03:00
..
beacon Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
central Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
central_hr Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
gatt Bluetooth: GATT: Add flags to attribute write callback 2016-06-28 17:36:08 +03:00
ipsp Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
peripheral Bluetooth: GATT: Add flags to attribute write callback 2016-06-28 17:36:08 +03:00
peripheral_csc Bluetooth: GATT: Add flags to attribute write callback 2016-06-28 17:36:08 +03:00
peripheral_dis Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
peripheral_esp Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
peripheral_hr Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
peripheral_sc_only Bluetooth: samples: Unify config for QEMU and Arduino101 targets 2016-06-15 12:17:06 +00:00
README Bluetooth: IPSP: Add README 2016-06-14 15:59:50 +03: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_H4) 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/sanitycheck [-P <platform>]

To only run Bluetooth tests use the -t bluetooth switch:

$ scripts/sanity_chk/sanitycheck -t bluetooth