Hi
i saw this question already in another thread, but did not get an answer. Is there a list of cases in which this timeout is generated?
Wim
Hi
i saw this question already in another thread, but did not get an answer. Is there a list of cases in which this timeout is generated?
Wim
Hi,
I'm wondering if is it possible somehow figure out who/which gap operation actually triggered timeout? Of course I can implement some state machine on my own, but is there any possiblity to get this info from soft device (i'm using s130_nrf51_2.0.1_softdevice)
Thanky for reply
Found it -> there are defines BLE_GAP_TIMEOUT_SOURCES GAP and this source is reported via p_ble_evt->evt.gap_evt.params.timeout.src
Hi Matej, You are right, the received event when it is a BLE_GAP_EVT_TIMEOUT should contain the source
p_ble_evt->evt.gap_evt.params.timeout.src