Hello,
I hope you are well.
I have a code inside the connection connected callback that sets the MTU to the maximum, which is working fine on ncs v3.0.2 but generates the following error on v3.2.0:
ASSERTION FAIL [err == 0] @ WEST_TOPDIR/zephyr/subsys/bluetooth/host/hci_core.c:504
Controller unresponsive, command opcode 0x2022 timeout with err -11
I am using:
static void on_connect(struct bt_conn *p_conn, uint8_t p_err) {
...
struct bt_conn_le_data_len_param data_len = {
.tx_max_len = BT_GAP_DATA_LEN_MAX,
.tx_max_time = BT_GAP_DATA_TIME_MAX,
};
if (bt_conn_le_data_len_update(p_conn, &data_len) != 0) {
LOG_ERR("Data Length update failed");
}
}
With the configuration:
CONFIG_BT=y CONFIG_BT_LL_SOFTDEVICE=y CONFIG_BT_SMP=y CONFIG_BT_HCI=y CONFIG_BT_REMOTE_VERSION=n CONFIG_BT_SETTINGS=n CONFIG_BT_PERIPHERAL=y CONFIG_BT_GATT_CLIENT=y CONFIG_BT_MAX_CONN=1 CONFIG_BT_GAP_AUTO_UPDATE_CONN_PARAMS=y CONFIG_BT_USER_PHY_UPDATE=y CONFIG_BT_USER_DATA_LEN_UPDATE=y CONFIG_BT_CTLR_DATA_LENGTH_MAX=251 CONFIG_BT_BUF_ACL_RX_SIZE=251 CONFIG_BT_BUF_ACL_TX_SIZE=251 CONFIG_BT_L2CAP_TX_MTU=247
And can't figure out why the assertion happens on v3.2.0.