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

22 lines
483 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
CONFIG_BT_ATT_PREPARE_COUNT=2
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: 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
CONFIG_BT_SETTINGS=y
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_FCB=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_FCB=y