1CONFIG_BT=y
2CONFIG_BT_BROADCASTER=y
3CONFIG_BT_OBSERVER=y
4CONFIG_BT_EXT_ADV=y
5CONFIG_BT_EXT_ADV_MAX_ADV_SET=2
6CONFIG_BT_DEVICE_NAME="Broadcaster Multiple"
7
8# Enable Advertising Data chaining in Zephyr Bluetooth LE Controller
9CONFIG_BT_CTLR_ADVANCED_FEATURES=y
10CONFIG_BT_CTLR_ADV_DATA_CHAIN=y
11
12# Zephyr Bluetooth LE Controller will need to use chain PDUs when AD data
13# length > 191 bytes
14# - 31 bytes will use 22 bytes for the default name in this sample plus 9 bytes
15#   for manufacturer data
16# - 191 bytes will use 22 bytes for the default name in this sample plus 169
17#   bytes for manufacturer data
18# - 277 bytes will use 22 bytes for the default name in this sample plus 255
19#   bytes for manufacturer data
20CONFIG_BT_CTLR_ADV_DATA_LEN_MAX=1650
21
22# Increase Advertising PDU buffers to number of advertising sets times the
23# number of chain PDUs per advertising set when using Zephyr Bluetooth LE
24# Controller
25CONFIG_BT_CTLR_ADV_DATA_BUF_MAX=2
26
27# Maximum Extended Scanning buffer size
28CONFIG_BT_EXT_SCAN_BUF_SIZE=1650
29
30# Set maximum scan data length for Extended Scanning in Bluetooth LE Controller
31CONFIG_BT_CTLR_SCAN_DATA_LEN_MAX=1650
32
33# The Zephyr Controller does not combine all the 1650 bytes before
34# fragmenting into 8 HCI reports, if a PDU has 255 bytes,
35# it will generate 2 HCI reports and so we need to reserve 16 buffers
36CONFIG_BT_BUF_EVT_RX_COUNT=16
37
38# Increase Zephyr Bluetooth LE Controller Rx buffer to receive complete chain
39# of PDUs
40CONFIG_BT_CTLR_RX_BUFFERS=9
41