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/prj.conf

47 lines
964 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_SYSTEM_WORKQUEUE_STACK_SIZE=2048
Bluetooth: Mesh: Add skeleton for persistent storage Add initial skeleton for doing settings-based persistent storage for the mesh network state. This patch only includes restoring some core network state such as IV Index, Sequence number, Net Keys, App Keys and the Replay Protection list. The remaining state, and actually storing the state, is left for follow-up patches. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-05-07 14:50:49 +08:00
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=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: Mesh: Add skeleton for persistent storage Add initial skeleton for doing settings-based persistent storage for the mesh network state. This patch only includes restoring some core network state such as IV Index, Sequence number, Net Keys, App Keys and the Replay Protection list. The remaining state, and actually storing the state, is left for follow-up patches. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-05-07 14:50:49 +08:00
CONFIG_SETTINGS=y
Bluetooth: Mesh: Add some actual behavior in sample Populates the onoff server stubs in the Bluetooth Mesh sample, and implements generic LED based hardware support to include more boards. Fixes #31031. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2021-03-11 22:10:42 +08:00
CONFIG_HWINFO=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_OBSERVER=y
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 19:45:13 +08:00
CONFIG_BT_CTLR_DUP_FILTER_LEN=0
CONFIG_BT_CTLR_LE_ENC=n
Bluetooth: Add common Kconfig option to disable LE Data Length Update This adds common option to disable support for LE Data Length Update procedure in controller and host. This will reduce flash usage by compiling out le_data_len_change event handler that will never be called if controller has been compiled with BT_CTLR_DATA_LENGTH option disabled. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-11-21 18:14:19 +08:00
CONFIG_BT_DATA_LEN_UPDATE=n
Bluetooth: Add common Kconfig option to disable PHY Update This adds common option to disable support for PHY Update procedure in controller and host. This will reduce flash usage by compiling out le_phy_update_complete event handler that will never be called if controller has been compiled with BT_CTLR_PHY option disabled. Signed-off-by: Mariusz Skamra <mariusz.skamra@codecoup.pl>
2018-11-21 17:52:18 +08:00
CONFIG_BT_PHY_UPDATE=n
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 19:45:13 +08:00
CONFIG_BT_CTLR_CHAN_SEL_2=n
Bluetooth: controller: Add Minimum Number of Used Channels Proc Add implementation to support Bluetooth 5.0 Minimum Number of Used Channels Procedure. Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2017-08-18 19:46:49 +08:00
CONFIG_BT_CTLR_MIN_USED_CHAN=n
Bluetooth: controller: Rename Kconfig prefix Rename the BT_CONTROLLER prefix used in all of the Kconfig variables related to the Bluetooth controller to BT_CTLR. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-08-14 19:45:13 +08:00
CONFIG_BT_CTLR_PRIVACY=n
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_PERIPHERAL=y
CONFIG_BT=y
CONFIG_BT_TINYCRYPT_ECC=y
CONFIG_BT_L2CAP_TX_BUF_COUNT=5
CONFIG_BT_MESH=y
Bluetooth: Mesh: Model extension concept Adds the model extension concept to the access layer, as described in the Mesh Profile Specification, Section 2.3.6. Extensions are implemented as a tree, using two pointers in each model: The extends pointer points to the first extended model, and the next pointer points to the next sibling or (if the NEXT_IS_PARENT flag is set) the parent model in the tree, forming a cyclical "Left-child right-sibling" (LCRS) tree. The tree root can be obtained by calling bt_mesh_model_root_get(), and the extended models can be walked by calling bt_mesh_model_tree_walk(). According to the Mesh Profile Specification Section 4.2.3, all models in the same extension tree share one subscription list per element. This is implemented by walking the model's extension tree, and pooling the subscription lists of all models in the same element into one. If the config server adds a subscription to a model, it may be stored in any of the model tree's models' subscription lists. No two models in the same extension tree and element will have duplicate groups listed. This allows us to increase extended models' capacity for subscriptions significantly. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2019-10-18 19:23:06 +08:00
CONFIG_BT_MESH_MODEL_EXTENSIONS=y
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_RELAY=y
samples: bluetooth/mesh: Add Friend support Make it possible to use the mesh sample app as a Friend node. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-02 03:54:23 +08:00
CONFIG_BT_MESH_FRIEND=y
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_PB_GATT=y
CONFIG_BT_MESH_PB_ADV=y
CONFIG_BT_MESH_GATT_PROXY=y
Bluetooth: Mesh: Clean up sample config Removes redundant and invalid configurations from the bluetooth/mesh sample. Removes some stale disabled config entries. Fixes L2CAP related warning in config step of sample. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2019-11-08 18:00:04 +08:00
#CONFIG_BT_MESH_LOW_POWER=y
samples: bluetooth/mesh: Fix configuration This sample is often the first one used as reference for Bluetooth Mesh, so it should have a good configuration as a starting point. Comment out the LPN options to eliminate Kconfig warnings, since the LOW_POWER option they depend on is not enabled. Also disable INIT_STACKS since that's only needed for fine-tuning the app configuration, and otherwise only causes unnecessary spam in the console. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2019-03-19 19:01:31 +08:00
#CONFIG_BT_MESH_LPN_SCAN_LATENCY=30
#CONFIG_BT_MESH_LPN_RECV_DELAY=40
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_LPN_POLL_TIMEOUT=300
CONFIG_BT_MESH_SUBNET_COUNT=2
CONFIG_BT_MESH_APP_KEY_COUNT=2
CONFIG_BT_MESH_MODEL_GROUP_COUNT=2
CONFIG_BT_MESH_LABEL_COUNT=3
CONFIG_BT_DEBUG_LOG=y
samples: bluetooth/mesh: Add Friend support Make it possible to use the mesh sample app as a Friend node. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-11-02 03:54:23 +08:00
CONFIG_BT_MESH_DEBUG=y
Bluetooth: Mesh: Add some actual behavior in sample Populates the onoff server stubs in the Bluetooth Mesh sample, and implements generic LED based hardware support to include more boards. Fixes #31031. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2021-03-11 22:10:42 +08:00
CONFIG_BT_MESH_DEBUG_MODEL=y