zephyr

History

Andy Ross f288d1e4a7 tests: samples: Apps shouldn't set tick rate Tick rate is becoming a platform tunable in the tickless world. Some apps were setting it due to requirements of drivers or subsystems (or sometimes for reasons that don't make much sense), but the dependency goes the other way around now: board/soc/arch level code is responsible for setting tick rates that work with their devices. A few tests still use hard-configured tick rates, as they have baked-in assumptions (like e.g. "a tick will be longer than a millisecond") that need to be addressed first. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>		2019-07-02 22:52:29 -04:00
..
src	dts: Rename SW._GPIO_* -> DT_ALIAS_SW._GPIOS_*	2019-07-01 07:14:36 -05:00
CMakeLists.txt	license: cleanup: add SPDX Apache-2.0 license identifier	2019-04-07 08:45:22 -04:00
README.rst	doc: Bluetooth: Documentation overhaul	2019-03-13 10:40:05 +01:00
prj.conf	Bluetooth: Introduce separate pool for discardable events	2019-07-01 16:36:15 +03:00
prj_bbc_microbit.conf	tests: samples: Apps shouldn't set tick rate	2019-07-02 22:52:29 -04:00
prj_nrf51_blenano.conf	Bluetooth: samples/mesh_demo: Convert to using Configuration Client API	2017-11-14 16:48:49 +02:00
sample.yaml	samples: add test identifier	2019-03-29 17:44:11 -04:00

README.rst

.. _ble_mesh_demo:

Bluetooth: Mesh Demo
####################

Overview
********

This sample is a Bluetooth Mesh application intended for demonstration
purposes only. The application provisions and configures itself (i.e. no
external provisioner needed) with hard-coded network and application key
values. The local unicast address can be set using a NODE_ADDR build
variable (e.g. NODE_ADDR=0x0001 for unicast address 0x0001), or by
manually editing the value in the ``board.h`` file.

Because of the hard-coded values, the application is not suitable for
production use, but is quite convenient for quick demonstrations of Mesh
functionality.

The application has some features especially designed for the BBC
micro:bit boards, such as the ability to send messages using the board's
buttons as well as showing information of received messages on the
board's 5x5 LED display. It's generally recommended to use unicast
addresses in the range of 0x0001-0x0009 for the micro:bit since these
map nicely to displayed addresses and the list of destination addresses
which can be cycled with a button press.

A special address, 0x000f, will make the application become a heart-beat
publisher and enable the other nodes to show information of the received
heartbeat messages.

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/mesh_demo` 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/mesh_demo
   :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.