Can't start advertising in timer callback

RE: Can't start advertising in timer callback

Vaibhav Aggarwal — Thu, 08 Sep 2016 08:34:04 GMT

Awesome thanks! Is the only way to react to the connection event through on_ble_evt? I'd like my code for this action to all be in one place if possible. If not, I could just call a function from on_ble_evt.

RE: Can't start advertising in timer callback

Thomas R. — Thu, 08 Sep 2016 08:02:38 GMT

The problem is the while loop inside the interrupt handler, thereby you are blocking all interrupts at this and lower levels. Therefore you are never getting any ble event (these are usually delivered at APP_IRQ_PRIORITY_LOW level) and so the advertising module can not work properly. Usually the m_conn_handle variable is also changed in an event handler, but due to the fact, that you're blocking these event handlers, this variable will never change.

To solve this, you should get rid of the while loop, so just start advertising in the rtc handler, and do the the rest when you get the connection event.

RE: Can't start advertising in timer callback

Vaibhav Aggarwal — Wed, 07 Sep 2016 20:23:48 GMT

@Aryan Please look at my edit. Thanks!

RE: Can't start advertising in timer callback

Susheel Nuguru — Wed, 07 Sep 2016 07:08:00 GMT

what is the priority for the RTC IRQ handler? Are you using app_timer library? It is perfectly OK to start advertising from RTC callbacks ONLY if you use APP_IRQ_PRIORITY_LOW = 6 or APP_IRQ_PRIORITY_LOWEST = 7, This is because you need to be in lower priority (higher number) than SVC priority (currently set to 4 in nRF52). Else you will get a hardfault. Other than that i do not see anything wrong with this function atleast.