We are using SoftDevice: sd132 v 5.0.
With event "BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST", the function "sd_ble_gatts_exchange_mtu_reply" always return with "NRF_ERROR_INVALID_STATE": anyone having any idea of why is this happening?
Thanks in advance!
We are using SoftDevice: sd132 v 5.0.
With event "BLE_GATTS_EVT_EXCHANGE_MTU_REQUEST", the function "sd_ble_gatts_exchange_mtu_reply" always return with "NRF_ERROR_INVALID_STATE": anyone having any idea of why is this happening?
Thanks in advance!
That is odd, the common issue is that the link is disconnected. Can it be that the connection handle is wrong (first parameter in
sd_ble_gatts_exchange_mtu_reply()) or that other code in your project have already called sd_ble_gatts_exchange_mtu_reply()?
First parameter is 'p_ble_evt->evt.gatts_evt.conn_handle' and there is no other places to call this function.
We changed the 'ble-connection-tag' (from 1 to 0) and now it replies NRF_ERROR_INVALID_PARAM.
The only way to get NRF_SUCCESS is when we used the default value (23) for the second parameter is 23 (even changing the NRF_SDH_BLE_GATT_MAX_MTU_SIZE to 247)
First parameter is 'p_ble_evt->evt.gatts_evt.conn_handle' and there is no other places to call this function.
We changed the 'ble-connection-tag' (from 1 to 0) and now it replies NRF_ERROR_INVALID_PARAM.
The only way to get NRF_SUCCESS is when we used the default value (23) for the second parameter is 23 (even changing the NRF_SDH_BLE_GATT_MAX_MTU_SIZE to 247)