OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/samples/bluetooth/mesh_demo/prj.conf

26 lines
549 B
Plaintext
Raw Normal View History

Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
CONFIG_MAIN_STACK_SIZE=512
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT=y
CONFIG_BT_TINYCRYPT_ECC=y
Bluetooth: mesh_demo: Enable missing options in configuration file This enables missing Observer and Brodcaster roles in configuration file. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-06-27 15:37:39 +08:00
CONFIG_BT_OBSERVER=y
CONFIG_BT_BROADCASTER=y
Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT_MESH=y
CONFIG_BT_MESH_RELAY=y
CONFIG_BT_MESH_SUBNET_COUNT=1
CONFIG_BT_MESH_APP_KEY_COUNT=1
CONFIG_BT_MESH_MODEL_GROUP_COUNT=2
Bluetooth: samples/mesh_demo: Add support for settings-based storage Enable BT_SETTINGS and remove any custom flash access used for the sequence number. We do settings_load() before bt_mesh_provision() and use the return value from the latter to identity that settings_load() had recoved a full configuration. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-05-11 16:11:22 +08:00
CONFIG_BT_MESH_ADV_BUF_COUNT=10
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
CONFIG_BT_MESH_LABEL_COUNT=0
CONFIG_BT_MESH_PB_ADV=n
Bluetooth: samples/mesh_demo: Convert to using Configuration Client API Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-13 06:31:29 +08:00
CONFIG_BT_MESH_CFG_CLI=y
Bluetooth: Mesh: Add initial implementation Add an initial implementation for the Bluetooth Mesh Profile Specification. The main code resides in subsys/bluetooth/host/mesh and the public API can be found in include/bluetooth/mesh.h. There are a couple of samples provided as well under samples/bluetooth and tests/bluetooth. The implementation covers all layers of the Bluetooth Mesh stack and most optional features as well. The following is a list of some of these features and the c-files where the implementation can be found: - GATT & Advertising bearers (proxy.c & adv.c) - Network Layer (net.c) - Lower and Upper Transport Layers (transport.c) - Access Layer (access.c) - Foundation Models, Server role (health.c & cfg.c) - Both PB-ADV and PB-GATT based provisioning (prov.c) - Low Power Node support (lpn.c) - Relay support (net.c) - GATT Proxy (proxy.c) Notable features that are *not* part of the implementation: - Friend support (initial bits are in place in friend.c) - Provisioner support (low-value for typical Zephyr devices) - GATT Client (low-value for typical Zephyr devices) Jira: ZEP-2360 Change-Id: Ic773113dbfd84878ff8cee7fe2bb948f0ace19ed Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-06-16 17:30:54 +08:00
Bluetooth: samples/mesh_demo: Add support for settings-based storage Enable BT_SETTINGS and remove any custom flash access used for the sequence number. We do settings_load() before bt_mesh_provision() and use the return value from the latter to identity that settings_load() had recoved a full configuration. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-05-11 16:11:22 +08:00
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
samples: migrating to NVS backend with settings Bluetooth samples now use the NVS backend for Settings. Signed-off-by: Kamil Piszczek <Kamil.Piszczek@nordicsemi.no>
2019-10-08 17:44:18 +08:00
CONFIG_NVS=y
Bluetooth: samples/mesh_demo: Add support for settings-based storage Enable BT_SETTINGS and remove any custom flash access used for the sequence number. We do settings_load() before bt_mesh_provision() and use the return value from the latter to identity that settings_load() had recoved a full configuration. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-05-11 16:11:22 +08:00
CONFIG_SETTINGS=y
CONFIG_BT_MESH_RPL_STORE_TIMEOUT=600