Debuging a problem with S310 - program hangs after BT connects

RE: Debuging a problem with S310 - program hangs after BT connects

dragilla — Mon, 08 Mar 2021 22:49:39 GMT

Ok. My assumption was correct. I made it all work with nrf_drv_timer wit High Priority matched with GPIOTE High Priority.

Thank you very much for your advice in the first post.

RE: Debuging a problem with S310 - program hangs after BT connects

dragilla — Mon, 08 Mar 2021 20:01:19 GMT

To be clear. I'm not calling anything from the API myself. I just use the softdevice to receive data. My whole program logic happns based on the incoming data and I use the interrupt on GPIOTE to initiate a timer (app_timer currently) that sets a pin to low or high. I calculate the delay of that timer depending on the data coming form ANT+. So in theory I could still set my timmer priority to HIGH, right?

RE: Debuging a problem with S310 - program hangs after BT connects

dragilla — Mon, 08 Mar 2021 19:17:18 GMT

Well yes, this kinda works, but then I have to set the GPIOTE priority to LOW as well and that causes my program to work "jerky". I use it to dim the ligjht and the light blinks while being dimmed, telling me the tmers don't work as they should.

But at least it doesn'f freeze ;)

Any other way around it? I guess I could go back to experimenting with the Timers (not app-timers) but I had other problems there :)

RE: Debuging a problem with S310 - program hangs after BT connects

Kenneth — Mon, 08 Mar 2021 14:51:44 GMT

Hi,

It is very likely that you are trying to call the softdevice api from an application interrupt level 0, 1 or 2. You need to call it from priority 3 or main. See Figure 4 and 5 in the S310 softdevice specification:

So this means you should set the priority level for your app_timer to 3 (not 0, 1, 2).

Kenneth