RE: BLE event generation

Einar Thorsrud — Fri, 21 Jan 2022 13:35:13 GMT

Hi Morten,

The SoftDevice can trigger many different events in different situations (se SoftDevice API documentation for all events). Depending on use case you may never see some of them. Regarding these you mention here:

BLE_GAP_EVT_PHY_UPDATE_REQUEST this is triggered when the peer requests to update the PHY. If you are testing with nRF Connect for _Desktop, you can click the cogwheel in the box representing the connection and select "Update phy..." to test this.
BLE_GAP_EVT_SEC_PARAMS_REQUEST - Initiate pairing.
BLE_GATTS_EVT_SYS_ATTR_MISSING - from the peer (like nRF Connect for desktop), read a CCCD that has not been set.
BLE_GATTC_EVT_TIMEOUT - This indicates that a GATTC operation timed out so the GATT server on the peer needs to not respond in time in order to trigger this.
BLE_GATTS_EVT_TIMEOUT - same here, the event indicates that the peer (GATT client in this case) did not respond in time. So you would need to make a GATT client that misbehaves/does not respond in order to trigger it.

Einar