zephyr

History

Andrzej Głąbek 5239bef610 drivers: pwm_nrf5_sw: Remove PWM_NRF5_SW_0_DEV_NAME Kconfig option This option determines the name under which the device represented by the `sw_pwm` node is registered in the system. But when the value of this option does not match the `label` property of the `sw_pwm` node, a problem arises when the `sw_pwm` node is referenced by a "pwm-leds" compatible node, since the `*_PWMS_CONTROLLER` macro that is generated for this referencing node contains a non-existing device name (as it is the `label` property value, not the Kconfig option value). This commit solves the issue described above by removing the Kconfig option and replacing all of its occurrences in sample applications by the standard macro generated for the `sw_pwm` node, containing the value of the `label` property of this node. Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>		2019-10-04 17:21:32 +02:00
..
src	drivers: pwm_nrf5_sw: Remove PWM_NRF5_SW_0_DEV_NAME Kconfig option	2019-10-04 17:21:32 +02: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	Bluetooth: samples: Reduce the bbc_microbit RAM usage	2019-08-15 15:07:12 +02:00
prj_nrf51_blenano.conf	…
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.