GAP Disconnect seems to stop first application timer

RE: GAP Disconnect seems to stop first application timer

Ivan Herrera — Mon, 28 Sep 2020 08:33:20 GMT

I'm just going to port everything to the latest SDK and verify all the code. I'll let you know if the issue persists.

RE: GAP Disconnect seems to stop first application timer

Edvin — Fri, 25 Sep 2020 13:00:37 GMT

Is there some way for me to reproduce this on an nRF52 DK?

RE: GAP Disconnect seems to stop first application timer

Ivan Herrera — Fri, 25 Sep 2020 09:26:06 GMT

After a little bit more of debugging I found out that initially the timers start out with different ID's, but that after starting and stopping several timers, the pointer of the conn_params_instance gets changed to either another timer (my application timer in this case), or by 0x00000000. This is caused by app_timer.c's 'timer_list_insert' function, which is modifying p_timer->next. Still figuring out why that is happening.

RE: GAP Disconnect seems to stop first application timer

Ivan Herrera — Thu, 24 Sep 2020 16:14:46 GMT

No, you are correct. After some more debugging this is what seems to be happening.

1. I start my application timer

2. I connect to my DK. ble_conn_params starts a timer 'update_timeout_handler'. (p_instance->timer_id)

3. I disconnect within a couple seconds. ble_conn_params cancels p_instance->timer_id, but that now doesn't seem to be the original timer, but it seems to cancel one of my application timers?

4. After another second, my application errors because the 'update_timeout_handler' wasn't properly cancelled -> tried to update parameters on an instance which had no running connection.

I will report back once I find out more

RE: GAP Disconnect seems to stop first application timer

Edvin — Thu, 24 Sep 2020 13:13:33 GMT

Hello,

[quote user=""]Why does my application timer and the conn_params_timer have the same ID? [/quote]

Do they? How did you initialize them?

The ble_conn_params.c should use it's own instance of app_timers. It has one app_timer for every connection interval.

Is there some way for me to reproduce this on a DK?

Best regards,

Edvin