mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-02 09:12:44 +00:00
d26e482dab
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> |
||
|---|---|---|
| .. | ||
| src | ||
| CMakeLists.txt | ||
| microbit_gatt.conf | ||
| prj_bbc_microbit.conf | ||
| prj_nrf51_blenano.conf | ||
| prj.conf | ||
| README.rst | ||
| sample.yaml | ||
.. _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.