Neither a disconnect nor a timeout after a LL_TERMINATE_IND

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

Susheel Nuguru — Thu, 21 Sep 2023 12:07:30 GMT

I am not sure at this point, but we will try to debug the issue with their hardware to see if this is something caused by nRF BLE stack or if it is related to the peer timings.

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

laran — Thu, 21 Sep 2023 08:13:12 GMT

At the time I concluded the issue was with the device discovery module. However, it may be some configuration I had not understood or missed, basically miss use. My plan was to move to a more recent SDK although never got to it. Do you think that may solve the issue?

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

Susheel Nuguru — Wed, 20 Sep 2023 11:45:38 GMT

We have someone else claiming that they see similar issue. I thought you might have had a solution.

But thanks for caring to reply :)

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

laran — Tue, 19 Sep 2023 12:40:50 GMT

No, unfortunately not. Did you stumble upon this same issue?

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

Susheel Nuguru — Mon, 18 Sep 2023 08:20:59 GMT

Iaran, did you manage to find what the issue was in your case?

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

laran — Tue, 23 Jul 2019 19:54:15 GMT

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?

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

thomas — Wed, 31 Jan 2018 13:55:10 GMT

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.

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

MartinBL — Tue, 23 Jan 2018 12:12:33 GMT

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.

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

thomas — Tue, 23 Jan 2018 08:43:05 GMT

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.

RE: Neither a disconnect nor a timeout after a LL_TERMINATE_IND

MartinBL — Mon, 22 Jan 2018 11:52:17 GMT

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