Configuring Bluetooth mesh in nRF Connect SDK
The Bluetooth® mesh support is controlled by CONFIG_BT_MESH, which depends on the following configuration options:
CONFIG_BT- Enables the Bluetooth subsystem.CONFIG_BT_OBSERVER- Enables the Bluetooth Observer role.CONFIG_BT_PERIPHERAL- Enables the Bluetooth Peripheral role.
Optional features configuration
Optional features in the Bluetooth mesh stack must be explicitly enabled:
CONFIG_BT_MESH_RELAY- Enables message relaying.CONFIG_BT_MESH_FRIEND- Enables the Friend role.CONFIG_BT_MESH_LOW_POWER- Enables the Low Power role.CONFIG_BT_MESH_PROVISIONER- Enables the Provisioner role.CONFIG_BT_MESH_GATT_PROXY- Enables the GATT Proxy Server role.CONFIG_BT_MESH_PB_GATT- Enables the GATT provisioning bearer.CONFIG_BT_MESH_CDB- Enables the Configuration Database subsystem.
The persistent storage of the Bluetooth mesh provisioning and configuration data is enabled by CONFIG_BT_SETTINGS.
See the Persistent storage section of Bluetooth Stack Architecture for details.
Mesh models
The nRF Connect SDK Bluetooth mesh model implementations are optional features, and each model has individual Kconfig options that must be explicitly enabled. See Bluetooth mesh models for details.
Additional configuration options
This section lists additional configuration options that can be used to configure behavior and performance of Bluetooth mesh.
CONFIG_SOC_FLASH_NRF_PARTIAL_ERASE- Enables partial erase on supported hardware platforms. Partial erase allows the flash page erase operation to be split into several small chunks preventing longer CPU stalls. This improves responsiveness of a mesh node during the defragmentation of storage areas used by the settings subsystem.