Hi. Bluetooth mesh provisioning freezes. I tried to change gatt proxy for better compatibility with sdk 15. Mesh sdk: 2.2.0
I changed mesh_gatt.c file only:
Added:
static void gatt_handler(nrf_ble_gatt_t * p_gatt, nrf_ble_gatt_evt_t const * p_evt) {
if (p_evt->evt_id == NRF_BLE_GATT_EVT_ATT_MTU_UPDATED) {
m_gatt.connections[p_evt->conn_handle].effective_mtu = p_evt->params.att_mtu_effective;
}
}
Then I removed following code because sdk 15 already handle that events in the same way:
/* TODO: The following events should be handled by an SDK module/the application. */
case BLE_GATTS_EVT_SYS_ATTR_MISSING:
{
NRF_MESH_ERROR_CHECK(sd_ble_gatts_sys_attr_set(p_ble_evt->evt.gatts_evt.conn_handle, NULL, 0, 0));
break;
}
case BLE_GAP_EVT_DATA_LENGTH_UPDATE_REQUEST:
{
ble_gap_data_length_params_t dl_params;
memset(&dl_params, BLE_GAP_DATA_LENGTH_AUTO, sizeof(dl_params));
NRF_MESH_ERROR_CHECK(sd_ble_gap_data_length_update(p_ble_evt->evt.gap_evt.conn_handle,
&dl_params,
NULL));
break;
}
case BLE_GAP_EVT_SEC_PARAMS_REQUEST:
NRF_MESH_ERROR_CHECK(sd_ble_gap_sec_params_reply(p_ble_evt->evt.gap_evt.conn_handle,
BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP,
NULL,
NULL));
break;
case BLE_GAP_EVT_PHY_UPDATE_REQUEST:
{
ble_gap_phys_t const phys =
{
.rx_phys = BLE_GAP_PHY_AUTO,
.tx_phys = BLE_GAP_PHY_AUTO,
};
NRF_MESH_ERROR_CHECK(sd_ble_gap_phy_update(p_ble_evt->evt.gap_evt.conn_handle, &phys));
break;
}
case BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST:
exchange_mtu_req_handle(p_ble_evt);
break;
Provisioning log:
0> <t: 11881>, fsm.c, 199, PB-GATT bearer: state S_IDLE -> S_LISTENING 0> <t: 11885>, mesh_initializer.c, 87, Device UUID : 005955BB000000004862CBB042C6BD93 0> <error> nrf_ble_gatt: sd_ble_gap_data_length_update() (request) on connection 0x2 returned NRF_ERROR_RESOURCES. 0> <error> nrf_ble_gatt: The requested TX/RX packet length is too long by 178/178 octets. 0> <t: 545462>, fsm.c, 232, PB-GATT bearer: E: E_CONNECTED 0> <t: 545469>, fsm.c, 185, PB-GATT bearer: A: A_LINK_OPEN 0> <t: 545472>, fsm.c, 199, PB-GATT bearer: state S_LISTENING -> S_CONNECTED 0> <t: 601791>, fsm.c, 232, PB-GATT bearer: E: E_TX_READY 0> <t: 601794>, fsm.c, 185, PB-GATT bearer: A: A_LINK_TIMER_START 0> <t: 601797>, fsm.c, 199, PB-GATT bearer: state S_CONNECTED -> S_LINK_ACTIVE 0> <t: 649706>, fsm.c, 232, PB-GATT bearer: E: E_PDU_RX 0> <t: 649709>, fsm.c, 185, PB-GATT bearer: A: A_PDU_RX 0> <t: 649712>, prov_provisionee.c, 317, Provisionee: invite received! 0> <t: 649715>, prov_provisionee.c, 110, Provisionee: sending capabilities 0> <t: 649718>, fsm.c, 232, PB-GATT bearer: E: E_PDU_TX 0> <t: 649721>, fsm.c, 185, PB-GATT bearer: A: A_PDU_TX 0> <t: 652904>, fsm.c, 232, PB-GATT bearer: E: E_TX_COMPLETE 0> <t: 652907>, fsm.c, 185, PB-GATT bearer: A: A_PDU_ACK 0> <t: 652912>, fsm.c, 232, PB-GATT bearer: E: E_PDU_RX 0> <t: 652915>, fsm.c, 185, PB-GATT bearer: A: A_PDU_RX 0> <t: 652918>, prov_provisionee.c, 341, Provisionee: provisioning start message received! 0> <t: 656145>, fsm.c, 232, PB-GATT bearer: E: E_PDU_RX 0> <t: 656148>, fsm.c, 185, PB-GATT bearer: A: A_PDU_RX 0> <t: 656151>, prov_provisionee.c, 369, Provisionee: public key message received! 0> <t: 656155>, fsm.c, 232, PB-GATT bearer: E: E_PDU_TX 0> <t: 656158>, fsm.c, 185, PB-GATT bearer: A: A_PDU_TX 0> <t: 670467>, fsm.c, 232, PB-GATT bearer: E: E_TX_COMPLETE 0> <t: 670471>, fsm.c, 185, PB-GATT bearer: A: A_PDU_ACK
