Neither a disconnect nor a timeout after a LL_TERMINATE_IND

[thomas]

Hi,

we have an issue, related to an older post, but we don't get the timeout outlined in that post.

Our setup: we use the nRF52832 with the S132 V4.0.2 in the peripheral role and a iPhone / Android app in the central role. During a stress test we are rapidly sending commands from the app to the nRF. After a while the app stops sending commands because of an error and sends a LL_TERMINATE_IND packet. That is what we're logging with a bluetooth sniffer.

Now the problem is, that we don't get either a event or notification from the softdevice, that the connection has been terminated. We set the supervision timeout but also doesn't occur.

Has anybody an idea why we don't get either a BLE_GAP_EVT_DISCONNECTED or a timeout event?

Kind regards, Thomas

[thomas]

the app stops sending commands because of an error on the phone side. After a while the app recognizes that there is something going wrong and sends the LL_TERMINATE_IND to cancel the connection. We assume the softdevice (S132 V4.0.2) in our device (nRF52) receives this terminate packet, but we don't receive anything in our application. So we are not able to handle this terminate packet.