zephyr

History

Johan Hedberg 2975ca0754 Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>		2017-08-09 11:14:19 +03:00
..
src	Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_*	2017-08-09 11:14:19 +03:00
Makefile	…
README.rst	samples: fixed typo in README.rst	2017-06-07 22:53:54 -04:00
prj.conf	Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_*	2017-08-09 11:14:19 +03:00
sample.yaml	tests: samples: convert testcase files to yaml	2017-06-21 20:56:53 -04:00

README.rst

.. _bluetooth-eddystone-sample:

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

Overview
********
Application demonstrating `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