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

[MartinBL]

1. Does the app stop sending commands because of an error on the phone side or the peripheral side?
2. If the nRF52 seems unresponsive, have you tried to debug to see what your code is doing in this state?

[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.

[MartinBL]

That is pretty strange. Are you able to provide a sniffer trace? You can use one of our development kits and our sniffer solution if you don't have any more professional gear.

[thomas]

Since we've switched from polling to interrupt for receiving the BLE events and use a FIFO to separate the receive and the handling of them, we couldn't reproduce the problem. It's more a workaround than a solution, but it works.

[laran]

I am having similar problem on SDK 14.2, using s132_nrf52_5.0.0_sd and running the nrf52 in central mode, listening to a connection. The peripheral sends a LL_TERMINATE_IND, then starts re-advertise itself. the nrf52 never return from the device discovery unless I reset it. on reset it connects again, as expected. I would expect a timeout if the discovery does not complete in time, right?