BLE Connection attempt returns opcode 0x2043 status 0x30

Question

Hi There, 
 Our peripheral firmware running nrf5 cannot seem to connect properly to our central running NCS 2.4.1 over BLE. We are consciously setting the connection to use CODED_PHY - that's not an oversight. Our attempts to connect report cause our central to report the following warning: <wrn> bt_hci_core: opcode 0x2043 status 0x30 We suspect this is a configuration issue, given the status. Looking for guidance on how to resolve this. 
 Peripheral (nrf5) adv_params.primary_phy = BLE_GAP_PHY_CODED;
adv_params.secondary_phy = BLE_GAP_PHY_CODED;
adv_params.properties.type = BLE_GAP_ADV_TYPE_EXTENDED_CONNECTABLE_NONSCANNABLE_UNDIRECTED; 
 Central (NCS 2.4.1) struct bt_conn_le_create_param *connection_params;
 
 connection_params = BT_CONN_LE_CREATE_PARAM(BT_CONN_LE_OPT_CODED | BT_CONN_LE_OPT_NO_1M, BT_GAP_SCAN_FAST_INTERVAL, BT_GAP_SCAN_FAST_INTERVAL);

err = bt_conn_le_create(addr, connection_params,
 BT_LE_CONN_PARAM_DEFAULT, &my_conn); 
 # BLE config
CONFIG_BT=y
CONFIG_BT_CENTRAL=y
CONFIG_BT_GATT_CLIENT=y
CONFIG_BT_DEVICE_NAME="xxxxxxx"

#BLE from Sensor
CONFIG_BT_EXT_ADV=y
CONFIG_BT_CTLR_ADV_EXT=y
CONFIG_BT_CTLR_PHY_CODED=y
CONFIG_BT_CTLR_PHY_2M=n
CONFIG_BT_CTLR_TX_PWR_PLUS_8=y
CONFIG_BT_FAST_PAIR=n
CONFIG_BT_AUTO_PHY_UPDATE=n 
 Many thanks in advance.

Vidar Berg · Accepted Answer

Hi, 
 I'm glad to hear that you found a way to work around the problem. Everything in your last snippet appears to be correct, except that you are passing the wrong 'connection_params' pointer to bt_conn_le_create() since you are adding the '&' operator in front of the pointer. 
 Does it work if you remove the '&' operator here: 
 err = bt_conn_le_create(addr, connection_params,
 BT_LE_CONN_PARAM_DEFAULT, &my_conn);

BLE Connection attempt returns opcode 0x2043 status 0x30

Top Replies