zephyr

History

Aksel Skauge Mellbye bc6c363bc9 boards: silabs: Consistently name dev kits Rename all Silicon Labs dev kits to always use the official kit name as board target name. Previous kit names used various naming schemes, including putting part of the SoC name in the board name. With HWMv2, SoC names (if needed) should go in the SoC board qualifier. Use HWMv2 revisions for the two variants of SLTB010A. Split the xG27 Dev Kit from the EFR32BG22 Thunderboard. This attempt at deduplication is confusing due to the very different kit names and use of different ICs (BG22 vs BG27), and was not continued with the xG24 Dev Kit, meaning that it wasn't consistent. Signed-off-by: Aksel Skauge Mellbye <aksel.mellbye@silabs.com>		2024-06-12 12:52:28 -04:00
..
boards	boards: silabs: Consistently name dev kits	2024-06-12 12:52:28 -04:00
src
CMakeLists.txt
prj.conf
README.rst
sample.yaml

README.rst

.. _bluetooth-ibeacon-sample:

Bluetooth: iBeacon
##################

Overview
********

This simple application demonstrates the BLE Broadcaster role
functionality by advertising an Apple iBeacon. The calibrated RSSI @ 1
meter distance can be set using an IBEACON_RSSI build variable
(e.g. IBEACON_RSSI=0xb8 for -72 dBm RSSI @ 1 meter), or by manually
editing the default value in the ``main.c`` file.

Because of the hard-coded values of iBeacon UUID, major, and minor,
the application is not suitable for production use, but is quite
convenient for quick demonstrations of iBeacon functionality.

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

* A board with Bluetooth LE support, or
* QEMU with BlueZ running on the host

Building and Running
********************

This sample can be found under :zephyr_file:`samples/bluetooth/ibeacon` in the
Zephyr tree.

See :ref:`bluetooth samples section <bluetooth-samples>` for details on how
to run the sample inside QEMU.

For other boards, build and flash the application as follows:

.. zephyr-app-commands::
   :zephyr-app: samples/bluetooth/ibeacon
   :board: <board>
   :goals: flash
   :compact:

Refer to your :ref:`board's documentation <boards>` for alternative
flash instructions if your board doesn't support the ``flash`` target.