michaelh/zephyr
1
0
Fork 0
Code Releases Activity
zephyr/samples/boards/nrf/mesh/onoff-app/prj.conf

100 lines
2.3 KiB
Text
Raw Normal View History

samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
#CONFIG_INIT_STACKS=y # if set, lots of noise from mesh/adv.c: STACK_ANALYZE
CONFIG_MAIN_STACK_SIZE=512
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=2048
samples: nrf52: mesh: onoff-app: add missing CONFIG_GPIO Add missing CONFIG_GPIO required by the nRF52 board-specific Bluetooth Mesh On/Off application sample. Signed-off-by: Henrik Brix Andersen <henrik@brixandersen.dk>
2019-02-16 20:12:08 +01:00
CONFIG_GPIO=y
samples: mesh/onoff-app: Enable persistent storage support Enable persistent storage support in samples/boards/nrf52/mesh/onoff-app. Signed-off-by: Vikrant More <vikrant8051@gmail.com>
2018-06-15 17:19:42 +05:30
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 11:44:18 +02:00
CONFIG_NVS=y
samples: mesh/onoff-app: Enable persistent storage support Enable persistent storage support in samples/boards/nrf52/mesh/onoff-app. Signed-off-by: Vikrant More <vikrant8051@gmail.com>
2018-06-15 17:19:42 +05:30
CONFIG_SETTINGS=y
CONFIG_BT_MESH_RPL_STORE_TIMEOUT=600
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
CONFIG_BOOT_BANNER=y
CONFIG_BT_OBSERVER=y
CONFIG_BT_BROADCASTER=y
CONFIG_BT_CTLR_DUP_FILTER_LEN=0
CONFIG_BT_CTLR_LE_ENC=n
CONFIG_BT_CTLR_LE_PING=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 11:14:19 +01: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 10:52:18 +01:00
CONFIG_BT_PHY_UPDATE=n
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
CONFIG_BT_CTLR_CHAN_SEL_2=n
CONFIG_BT_CTLR_MIN_USED_CHAN=n
CONFIG_BT_CTLR_PRIVACY=n
CONFIG_BT_PERIPHERAL=y
CONFIG_BT=y
CONFIG_BT_TINYCRYPT_ECC=y
CONFIG_BT_L2CAP_TX_BUF_COUNT=8
CONFIG_BT_MESH=y
CONFIG_BT_MESH_RELAY=y
Bluetooth: Mesh: Encapsulate feature config Moves mesh feature configuration to a separate module, deprecating the bt_mesh_cfg_srv structure. The initial values for the features should now be enabled through KConfig, where new config entries have been added for each feature. This removes the upward dependency on the config server from the core stack, and makes the config server a pure frontend for the configuration states, as all spec mandated behavior around the feature states is now encapsulated. Signed-off-by: Trond Einar Snekvik <Trond.Einar.Snekvik@nordicsemi.no>
2020-08-18 13:36:38 +02:00
CONFIG_BT_MESH_RELAY_ENABLED=n
CONFIG_BT_MESH_BEACON_ENABLED=n
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
CONFIG_BT_MESH_LOW_POWER=n
CONFIG_BT_MESH_FRIEND=n
CONFIG_BT_MESH_FRIEND_QUEUE_SIZE=16
CONFIG_BT_MESH_ADV_BUF_COUNT=20
Bluetooth: Mesh: Improve outgoing segment count configuration The Mesh specification doesn't support more than 32 transport layer segments, the way the number was so far derived from the advertising buffer count could result in a highre numbe than 32, thereby wasting memory. Make the number of supported segments build-time configurable through a new BT_MESH_TX_SEG_MAX configuration option. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-07-23 20:47:12 +03:00
CONFIG_BT_MESH_TX_SEG_MAX=6
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
CONFIG_BT_MESH_PB_GATT=y
CONFIG_BT_MESH_PB_ADV=y
CONFIG_BT_MESH_GATT_PROXY=y
CONFIG_BT_MESH_CFG_CLI=y
#CONFIG_BT_MESH_LPN_SCAN_LATENCY=30
#CONFIG_BT_MESH_LPN_RECV_DELAY=40
#CONFIG_BT_MESH_LPN_POLL_TIMEOUT=300
CONFIG_BT_MESH_SUBNET_COUNT=2
CONFIG_BT_MESH_APP_KEY_COUNT=2
CONFIG_BT_MESH_MODEL_KEY_COUNT=2
CONFIG_BT_MESH_MODEL_GROUP_COUNT=2
CONFIG_BT_MESH_LABEL_COUNT=3
#CONFIG_BT_MESH_IV_UPDATE_TEST=y
CONFIG_UART_CONSOLE=y
# this outputs btmon formatted data to the serial port
Bluetooth: Add option to log btsnoops over RTT There is a choice to log btmon logs over UART or RTT. You can choose number of RTT buffer, set its name and size. Replaced CONFIG_BT_DEBUG_MONITOR with CONFIG_BT_DEBUG_MONITOR_UART for UART usage and CONFIG_BT_DEBUG_MONITOR_RTT for RTT. Signed-off-by: Magdalena Kasenberg <magdalena.kasenberg@codecoup.pl>
2021-04-17 13:33:20 +02:00
#CONFIG_BT_DEBUG_MONITOR_UART=y
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
Bluetooth: Samples: Remove usage of `BT_DEBUG_LOG` Remove usage of Kconfig symbol `CONFIG_BT_DEBUG_LOG` from samples. It has been deprecated since this PR: https://github.com/zephyrproject-rtos/zephyr/pull/56183 The Kconfig symbols has been replaced by `CONFIG_LOG=y` on most of the cases. Or it has been removed when not needed anymore. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
2023-06-07 07:52:31 +02:00
CONFIG_LOG=y
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
Bluetooth: Use Zephyr standard log system instead of `bluetooth/common/log` The `bluetooth/common/log.h` and `bluetooth/common/log.c` files have been removed. Files that were using them have been updated to use `zephyr/logging/log.h` instead. Those replacement have been done consequently: - `/BT_DBG/LOG_DBG/` - `/BT_ERR/LOG_ERR/` - `/BT_WARN/LOG_WRN/` - `/BT_INFO/LOG_INF/` - `/BT_HEXDUMP_DBG/LOG_HEXDUMP_DBG/` - `/BT_DBG_OBJ_ID/LOG_DBG_OBJ_ID/` Also, some files were relying on the `common/log.h` include to include `zephyr/bluetooth/hci.h`, in those cases the include of `hci.h` has been added. For files that were including `common/log.h` but not using any logs, the include has been removed and not replaced. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
2022-11-02 14:31:13 +01:00
CONFIG_BT_MESH_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_PROXY_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_BEACON_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_NET_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_TRANS_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_LOW_POWER_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_FRIEND_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_MODEL_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_ACCESS_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_CRYPTO_LOG_LEVEL_DBG=y
#CONFIG_BT_MESH_ADV_LOG_LEVEL_DBG=y
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
#CONFIG_BT_MESH_SELF_TEST=y
#CONFIG_STACK_USAGE=y
CONFIG_BT_RX_STACK_SIZE=4096
Bluetooth: Use Zephyr standard log system instead of `bluetooth/common/log` The `bluetooth/common/log.h` and `bluetooth/common/log.c` files have been removed. Files that were using them have been updated to use `zephyr/logging/log.h` instead. Those replacement have been done consequently: - `/BT_DBG/LOG_DBG/` - `/BT_ERR/LOG_ERR/` - `/BT_WARN/LOG_WRN/` - `/BT_INFO/LOG_INF/` - `/BT_HEXDUMP_DBG/LOG_HEXDUMP_DBG/` - `/BT_DBG_OBJ_ID/LOG_DBG_OBJ_ID/` Also, some files were relying on the `common/log.h` include to include `zephyr/bluetooth/hci.h`, in those cases the include of `hci.h` has been added. For files that were including `common/log.h` but not using any logs, the include has been removed and not replaced. Signed-off-by: Théo Battrel <theo.battrel@nordicsemi.no>
2022-11-02 14:31:13 +01:00
#CONFIG_BT_HCI_DRIVER_LOG_LEVEL_DBG=y
#CONFIG_BT_HCI_CORE_LOG_LEVEL_DBG=y
#CONFIG_BT_GATT_LOG_LEVEL_DBG=y
#CONFIG_BT_CONN_LOG_LEVEL_DBG=y
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
CONFIG_BT_MAX_CONN=1
CONFIG_BT_CTLR_RX_BUFFERS=6
Bluetooth: Refactor bluetooth buffer configuration for simplification Refactor and simplify the bluetooth buffer configurations to improve the easy of configurations and eliminate invalid ones. By moving configurations out of host and controller specific configurations and into a common one it becomes easier to configure the host and controller separately as the same configurations can be used as would be for a combined build. All HCI configurations are now given exluding the matching HCI header, which eases the configuration as the application don't have to know the different header sizes. The BT_RX_BUF_LEN is split into ACL and Event, as well as the suprising use of Command size. BT_L2CAP_RX_MTU is removed as the stack does not support reassembling of HCI ACL data to larger L2CAP PDUs. The application will have to set ACL RX size and account for the L2CAP PDU header itself. BT_EATT_RX_MTU was removed as it is only used for setting a different default value for another option which leads to the stuck kconfig symbol problem. The configurations can be updated according to the table below: ** New configuration | ** Old configuration All configurations BT_BUF_ACL_RX_SIZE | BT_L2CAP_RX_MTU + 4 BT_BUF_ACL_RX_SIZE | BT_RX_BUF_LEN - 4 BT_BUF_EVT_RX_SIZE | BT_RX_BUF_LEN - 2 BT_BUF_CMD_TX_SIZE | BT_RX_BUF_LEN - 3 BT_BUF_CMD_TX_COUNT | BT_HCI_CMD_COUNT BT_BUF_EVT_RX_COUNT | BT_RX_BUF_COUNT BT_BUF_ACL_RX_COUNT | BT_RX_BUF_COUNT BT_BUF_ACL_RX_COUNT | BT_ACL_RX_COUNT BT_BUF_EVT_DISCARDABLE_SIZE | BT_DISCARDABLE_BUF_SIZE - 2 BT_BUF_EVT_DISCARDABLE_COUNT | BT_DISCARDABLE_BUF_COUNT Controller-build BT_BUF_ACL_TX_SIZE | BT_CTLR_TX_BUFFERS_SIZE BT_BUF_ACL_TX_COUNT | BT_CTLR_TX_BUFFER HCI-bridge BT_BUF_ACL_TX_SIZE | BT_HCI_ACL_DATA_SIZE BT_BUF_ACL_TX_COUNT | 6 Fixed invalid configurations setting either BT_L2CAP_RX_MTU or BT_CTLR_DATA_LENGTH_MAX larger than BT_RX_BUF_LEN could lead to buffer overruns. Fix advertising report max data length calculation. This always used the BT_DISCARDABLE_BUF_SIZE macro but this feature can be turned off and advertising reports will be allocated from the RX buffer in that case. Also controller-build does not have this buffer (in hci_raw.c). Also the wrong HCI header was used in the calculation, HCI event header should have been used instead of HCI ACL header. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2021-04-27 10:38:23 +02:00
CONFIG_BT_BUF_ACL_TX_COUNT=4
CONFIG_BT_BUF_CMD_TX_COUNT=4
samples: onoff-app: Add OnOff Model for the Nordic nRF52840-PDK board Signed-off-by: Steve Brown <sbrown@cortland.com> --- The updates to BlueZ' meshctl have not been submitted. I am submitting this PR only for review. It could be committed after the patches for the meshctl commands are applied.
2017-12-08 03:08:19 -07:00
CONFIG_BT_ATT_PREPARE_COUNT=2
#CONFIG_NET_BUF_SIMPLE_LOG=y
#CONFIG_NET_BUF_LOG=y
#CONFIG_BT_CTLR_DEBUG_PINS=y
Copy permalink