3 weeks, 4 days ago.

Handling BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST for NRF52832 based BLE devices.

I had logged an enhancement request to implement the BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST in mbed-os and Vincent (@Pan) was kind enough to provide a work around to accept any incoming Connection Params Update request on the BLE central/Master side of the code base as mentioned in the github issues link below.

Here is the issue that we are facing:

  • We are using a Murata MBN52832 Development kit for a peripheral and the peripheral sends a Connections Parameters update request to the BLE Central which is a NRF52_DK Development kit.
  • The BLE Central implements the code to handle this request and accepts it and I have debugged this to see the Update request getting updated connection params and BLE central accepts this change to the connection params.
  • This works perfectly when the NRF52_DK development kit is used as the peripheral, but with the Murata Development kit is used as the peripheral the active BLE connection is disconnected and the when the connection is re-established the connection params are still what the original connection was started with and not the updated connection params as requested by the Peripheral.

So my question what is the scenario where when the BLE connections params update is requested and is accepted by the central, would this end up failing at the Peripherals end and revert back to the original connection params.

Thanks, Ajay

Question relating to:

The nRF52 Development Kit is a single-board development kit for Bluetooth Smart, ANT and 2.4GHz proprietary applications using the nRF52 Series SoC. This kit supports both development for nRF52832 SoCs.
Comment on this question
Be the first to answer this question.

To post an answer, please log in.