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/hci_uart/nrf5.conf

16 lines
369 B
Plaintext
Raw Normal View History

Bluetooth: hci-uart: Add a sample configuration file for nRF5x Add a config file for boards using the Nordic Semiconductor nRF5x ICs with reasonable defaults in terms of UART configuration and controller settings. Change-Id: Iaa5904c96c0f40a2749b7dda0398dd35fa809f24 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2016-10-25 22:39:44 +08:00
CONFIG_CONSOLE=n
CONFIG_STDOUT_CONSOLE=n
CONFIG_UART_CONSOLE=n
CONFIG_GPIO=y
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y
CONFIG_UART_NRF5_BAUD_RATE=1000000
CONFIG_UART_NRF5_FLOW_CONTROL=y
Bluetooth: hci_uart: reduce configured stack sizes From stack_analyze function, used isr stack is 368 bytes with the controller build, main stack is 288 bytes and idle stack is 56 bytes. Hence, configuring sizes of 512, 512, and 256 bytes for isr, main and idle stacks respectively. Increased max connections from 16 to 20 utilizing the RAM free from the reduced stack sizes. Change-id: I67d073fd1893cafc53d36e89035a6fd931488a46 Signed-off-by: Vinayak Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>
2016-11-19 17:48:47 +08:00
CONFIG_MAIN_STACK_SIZE=512
Bluetooth: Set hci_uart RAM config to fit privacy With the introduction of privacy, the system workqueue is now being linked into the image, growing the RAM footprint considerably. In order for the sample to fit in QFAA and QFAB variants of the nRF51 (16KB of RAM) we reduce the workqueue stack size to 512 since the RPA update mechanism doesn't use more than 340 bytes and we stick to 16 connections maximum. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2017-06-22 17:54:48 +08:00
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=512
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_HCI_RAW=y
CONFIG_BT_MAX_CONN=16
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_ASSERT_HANDLER=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_TINYCRYPT_ECC=n