Timer scheduler

RE: Timer scheduler

Shorosky — Fri, 11 Mar 2016 10:30:22 GMT

Ok, I will remember it on the future. Thank you.

RE: Timer scheduler

Anders Strand — Fri, 11 Mar 2016 09:47:47 GMT

There is no API call for checking how full the queue is. You can always initialize the queue with a slightly higher number than what you know you will need. This will of course impact you RAM usage a bit. You can check if the queue is full by checking if app_timer_start/stop returns NRF_ERROR_NO_MEM (0x4).

RE: Timer scheduler

Shorosky — Fri, 11 Mar 2016 08:56:56 GMT

Problem is solved. I did what you say, and it works even with only value 1 on the APP_TIMER_QUEUE_SIZE. It is probably that I have more problems similar like that on the future, so if could to know how many tasks are pending on scheduler, I would be grateful for it.

Thank you for helping

RE: Timer scheduler

Anders Strand — Fri, 11 Mar 2016 08:45:06 GMT

The best solution is to avoid the problem completely. Raise a flag (set a variable) when you find the correct advertisement. When you get back to main(), check the flag. Then you reset the timer accordingly.

RE: Timer scheduler

Shorosky — Thu, 10 Mar 2016 15:40:23 GMT

I do this only on "good packets" but I will have to work, sometimes with 4 different signals, so I have to solve the problem of priorities. There is a way to know how many tasks are queued on the timer scheduler?

Thank you.

RE: Timer scheduler

Anders Strand — Thu, 10 Mar 2016 12:38:04 GMT

Are you doing this on every received advertising event, or are you checking the advertisement packet before you start/stop the timers? If it is the first, you will be doing this very often if there is a couple of BLE devices advertising around you.

RE: Timer scheduler

Shorosky — Thu, 10 Mar 2016 10:47:02 GMT

Hi, Anders. Thank you for answering. I readed the documentation, but I was not sure if queue is to start and stop timers, or while micro was attending an interruption of timer and another more priority interruption is comming. I think that the problem comes when I queue the two operations (start and stop), the program finish the on_ble_evt, and before to execute the instructions queued, it recives a new ble interruption.

I'll try to start and stop the timer on main function, and watch what happens.

Thank you. Regards

RE: Timer scheduler

Anders Strand — Thu, 10 Mar 2016 10:33:20 GMT

Hi.

From the app_timer documentation:

When calling app_timer_start() or app_timer_stop(), the timer operation is just queued, and the software interrupt is triggered. The actual timer start/stop operation is executed by the SWI0 interrupt handler. Since the SWI0 interrupt is running in APP_LOW, if the application code calling the timer function is running in APP_LOW or APP_HIGH, the timer operation will not be performed until the application handler has returned.

This means that both the call to app_timer_stop and app_timer_start is queued, and then executed when you exit the on_ble_evt function.

If you get the error with queue size = 2, it is probably because an app_timer is being used somewhere else in your code.