zephyr

History

Johan Hedberg eb07178236 Bluetooth: samples: Use Kconfig DEVICE_NAME variable when possible Instead of using a hard-coded string, make the sample use the Kconfig variable for the device name. Change-Id: Ib09f594e1cba221f9064318572bd90d38bd2733a Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>		2017-01-28 08:43:41 +02:00
..
src	Bluetooth: samples: Use Kconfig DEVICE_NAME variable when possible	2017-01-28 08:43:41 +02:00
Makefile	samples: tests: remove obsolete KERNEL_TYPE and kernel variables	2016-11-04 15:47:25 -04:00
README.rst	doc: update bluetooth samples with pointers	2017-01-26 20:02:35 +00:00
prj.conf	Bluetooth: samples: Use Kconfig DEVICE_NAME variable when possible	2017-01-28 08:43:41 +02:00
prj_nble.conf	Bluetooth: samples: Use Kconfig DEVICE_NAME variable when possible	2017-01-28 08:43:41 +02:00
testcase.ini	Bluetooth: samples: Limit tests to just qemu platforms	2016-10-28 20:15:01 +00:00

README.rst

Bluetooth: Eddystone
####################

Overview
********
Application demostrating `Eddystone Configuration Service`_

The Eddystone Configuration Service runs as a GATT service on the beacon while
it is connectable and allows configuration of the advertised data, the
broadcast power levels, and the advertising intervals. It also forms part of
the definition of how Eddystone-EID beacons are configured and registered with
a trusted resolver.


Requirements
************

* BlueZ running on the host, or
* A board with BLE support

Building and Running
********************
This sample can be found under :file:`samples/bluetooth/eddystone` in the
Zephyr tree.

See :ref:`bluetooth setup section <bluetooth_setup>` for details.

.. _Eddystone Configuration Service: https://github.com/google/eddystone/tree/master/configuration-service