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

26 lines
590 B
Plaintext
Raw Normal View History

Bluetooth: Introduce skeleton for settings-based storage Introduce a basic skeleton for peristent storage based on the settings subsystem. Also enable support for this to the peripheral sample application, so the new code gets exersized by CI. For now, the implementation provides the same level support as the bt_storage API ever did, i.e. for the identity address and the IRK. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-04-27 03:05:26 +08:00
# Incresed stack due to settings API usage
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_DEBUG_LOG=y
CONFIG_BT_SMP=y
CONFIG_BT_SIGNING=y
CONFIG_BT_PERIPHERAL=y
subsys: bluetooth: services: dev. information service enhancements This commit moves the BLE GATT Device Information service from /samples/bluetooth/gatt to /subsys/bluetooth/services and adds a Kconfig entry to enable and configure the service; when enabled, it will register itself automatically. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no> Signed-off-by: Radoslaw Koppel <radoslaw.koppel@nordicsemi.no>
2018-11-01 23:44:52 +08:00
CONFIG_BT_GATT_DIS=y
samples: bluetooth: peripheral: Fix RX buffer size GATT long messages require buffers to store multiple packets. The actual configuration for the bluetooth peripheral sample defines only two buffers to store these messages. As the default ATT payload size is 18 bytes, the maximum payload size for a long ATT message is 36 bytes. As the variable `vnd_long_value[]` has a defined size of 74 bytes, it cannot be fully modified due to the 36 bytes limitation. Set CONFIG_BT_ATT_PREPARE_COUNT=5 so all the maximum payload size goes to 90 bytes and all the 74 bytes can be written to `vnd_long_value[]`. Signed-off-by: Joao Cordeiro <jvcc@cesar.org.br>
2019-05-13 21:36:27 +08:00
CONFIG_BT_ATT_PREPARE_COUNT=5
Bluetooth: services: battery service enhancements This commit moves the BLE GATT Battery service from /samples/bluetooth/gatt to /subsys/bluetooth/services and adds a Kconfig entry to enable and configure the service; when enabled, it will register itself automatically. Signed-off-by: Emanuele Di Santo <emdi@nordicsemi.no> Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2018-09-11 20:05:46 +08:00
CONFIG_BT_GATT_BAS=y
Bluetooth: services: Move Heart rate service This commit moves the BLE GATT heart rate service from samples/bluetooth/gatt to subsys/bluetooth/services and adds a Kconfig entry to enable and configure the service. Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2019-07-04 22:44:29 +08:00
CONFIG_BT_GATT_HRS=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_PRIVACY=y
Bluetooth: peripheral: Set CONFIG_BT_DEVICE_NAME_MAX This force CONFIG_BT_DEVICE_NAME_MAX to be set even in boards where CONFIG_BT_SETTINGS won't be defined so it exercise such configuration. In addition to that set a long name that would not fix in the ScanData. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2018-07-10 21:35:23 +08:00
CONFIG_BT_DEVICE_NAME="Zephyr Peripheral Sample Long Name"
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_DEVICE_APPEARANCE=833
Bluetooth: att: Add option to disable GATT writable name This allow to set name at runtime while leaving GAP name characteristic read only. Signed-off-by: Szymon Janc <szymon.janc@codecoup.pl>
2018-08-01 01:57:08 +08:00
CONFIG_BT_DEVICE_NAME_DYNAMIC=y
Bluetooth: peripheral: Set CONFIG_BT_DEVICE_NAME_MAX This force CONFIG_BT_DEVICE_NAME_MAX to be set even in boards where CONFIG_BT_SETTINGS won't be defined so it exercise such configuration. In addition to that set a long name that would not fix in the ScanData. Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
2018-07-10 21:35:23 +08:00
CONFIG_BT_DEVICE_NAME_MAX=65
Bluetooth: Introduce skeleton for settings-based storage Introduce a basic skeleton for peristent storage based on the settings subsystem. Also enable support for this to the peripheral sample application, so the new code gets exersized by CI. For now, the implementation provides the same level support as the bt_storage API ever did, i.e. for the identity address and the IRK. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-04-27 03:05:26 +08:00
Bluetooth: Keys: add key overwrite feature for key storage. Key overwrite feature allows to overwrite old pairing key records when key storage is full and a new pairing request occurs, or new keys are distributed. If enabled when key storage is full and a keys storage slot is requested, the oldest keys added will be removed. So new devices can be paired with no limitations and no need to determine, which devices should be unpaired to free key storage space explicitly in application. To enable the feature set CONFIG_BT_KEYS_OVERWRITE_OLDEST=y. Oldest keys are determined by minimum value of up-counting aging counter. If you set CONFIG_BT_KEYS_SAVE_AGING_COUNTER_ON_PAIRING=y aging counter values will be updated each time the secure connection is established. This might increase flash wear out if at least two secure connections are established and shut down periodically. When the option disabled aging counter is still updated on each new secure connection, but not stored to flash. Signed-off-by: Sergiy Nikolayenko <sergiy_nikolayenko@jabil.com>
2019-09-26 22:27:50 +08:00
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y
Bluetooth: Introduce skeleton for settings-based storage Introduce a basic skeleton for peristent storage based on the settings subsystem. Also enable support for this to the peripheral sample application, so the new code gets exersized by CI. For now, the implementation provides the same level support as the bt_storage API ever did, i.e. for the identity address and the IRK. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-04-27 03:05:26 +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: Introduce skeleton for settings-based storage Introduce a basic skeleton for peristent storage based on the settings subsystem. Also enable support for this to the peripheral sample application, so the new code gets exersized by CI. For now, the implementation provides the same level support as the bt_storage API ever did, i.e. for the identity address and the IRK. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2018-04-27 03:05:26 +08:00
CONFIG_SETTINGS=y