zephyr

History

Johan Hedberg d26e482dab Bluetooth: Mesh: Use more reasonable advertising buffer counts The number of buffres influences e.g. the maximum SDU size, which in turn influences call stack consumption. Use lower values where a high number of buffers isn't necessary, and use the default (6) where it's sufficient. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>		2018-07-25 18:16:45 +03:00
..
src	samples: fix u32_t type usage	2018-07-18 12:32:23 -04:00
CMakeLists.txt	…
README.rst	samples: bluetooth: mesh: Add basic documentation	2018-03-05 19:53:48 -05:00
microbit_gatt.conf	driver: ILI9340 LCD display driver	2018-05-18 20:21:45 +03:00
prj.conf	Bluetooth: Mesh: Use more reasonable advertising buffer counts	2018-07-25 18:16:45 +03:00
prj_bbc_microbit.conf	driver: ILI9340 LCD display driver	2018-05-18 20:21:45 +03:00
prj_nrf51_blenano.conf	…
sample.yaml	…

README.rst

.. _ble_mesh:

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

Overview
********

This sample demonstrates Bluetooth Mesh functionality. It has several
standard Mesh models, and supports provisioning over both the
Advertising and the GATT Provisioning Bearers (i.e. PB-ADV and PB-GATT).
The application also needs a functioning serial console, since that's
used for the Out-of-Band provisioning procedure.

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

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

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

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

See :ref:`bluetooth setup section <bluetooth_setup>` 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
   :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.