Nick,
is it possible to use HCI_ReadRssiCmd as some kind of workaround to get the unsuccessful connection events? Here is description:
* @fn HCI_ReadRssiCmd API
*
* @brief This BT API is used to read the RSSI of the last packet
* received on a connection given by the connection handle. If
* the Receiver Modem test is running (HCI_EXT_ModemTestRx), then
* the RF RSSI for the last received data will be returned. If
* there is no RSSI value, then HCI_RSSI_NOT_AVAILABLE will be
* returned.
Does that mean if I request the RSSI and the last connection was unsuccessful HCI_RSSI_NOT_AVAILABLE will be returned? If so, calling ReadRssiCmd between each connection event and counten the amount HCI_RSSI_NOT_AVAILABLE would give the nr of unsuccessful connection events, wouldn't it?
Best Regards