Expectation: After calling `bt_disable()` it is possible to use the Bluetooth APIs as if `bt_enable()` was never called. This was not the case for `bt_id_create()`, it was not possible to set the default identity. This prevented an application developer to restart the stack as a different identity. Keys also need to be cleared to avoid the following pattern: 1. Pair two devices 2. Central calls `bt_disable()` and `bt_enable()`. The central will now generate a new identity address. 3. Connect the two devices. 4. Re-establish encryption. Now the central will try to use the previously used keys. The procedure will fail because the peripheral does not have any keys associated with the new central address. The API documentation is updated accordingly. Signed-off-by: Rubin Gerritsen <rubin.gerritsen@nordicsemi.no>
25 lines
572 B
Text
25 lines
572 B
Text
CONFIG_BT=y
|
|
CONFIG_LOG=y
|
|
CONFIG_ASSERT=y
|
|
CONFIG_BT_SMP=y
|
|
CONFIG_BT_MAX_PAIRED=2
|
|
|
|
CONFIG_BT_DEVICE_NAME="CIS test"
|
|
|
|
CONFIG_BT_ISO_CENTRAL=y
|
|
CONFIG_BT_ISO_PERIPHERAL=y
|
|
CONFIG_BT_ISO_TX_BUF_COUNT=4
|
|
CONFIG_BT_ISO_MAX_CHAN=4
|
|
CONFIG_BT_ISO_TX_MTU=200
|
|
CONFIG_BT_ISO_RX_MTU=200
|
|
|
|
CONFIG_BT_ISO_LOG_LEVEL_DBG=y
|
|
|
|
# Controller Connected ISO configs
|
|
CONFIG_BT_CTLR_CENTRAL_ISO=y
|
|
CONFIG_BT_CTLR_PERIPHERAL_ISO=y
|
|
CONFIG_BT_CTLR_ISO_TX_BUFFER_SIZE=208
|
|
CONFIG_BT_CTLR_ISO_TX_BUFFERS=4
|
|
CONFIG_BT_CTLR_ISOAL_SOURCES=2
|
|
CONFIG_BT_CTLR_ISOAL_SINKS=2
|
|
CONFIG_BT_CTLR_CONN_ISO_STREAMS_PER_GROUP=4
|