This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

app_timer_start and app_sched_execute

Should I call app_sched_execute at least once before the first app_timer_start ? I have a strange bug and I realized that calling it before is a fix but I don't see this in the doc

Another way for me to fix my bug is to call app_timer_start with a higher number that usual

Does it make any sense ? Many thanks

N.B : I use APP_TIMER_INIT(APP_TIMER_PRESCALER, APP_TIMER_MAX_TIMERS, APP_TIMER_OP_QUEUE_SIZE, true);

Parents
  • Hi Thomas,

    It doesn't make much sense to me. You meant if you only call app_sched_execute after (in the main loop maybe ? ) it didn't work. But if you add one call for app_sched_execute before you call app_timer_start() it worked ?

    What happened when it didn't work ? Have you tried to add a breakpoint inside app_sched_execute() and check out the queue ?

Reply
  • Hi Thomas,

    It doesn't make much sense to me. You meant if you only call app_sched_execute after (in the main loop maybe ? ) it didn't work. But if you add one call for app_sched_execute before you call app_timer_start() it worked ?

    What happened when it didn't work ? Have you tried to add a breakpoint inside app_sched_execute() and check out the queue ?

Children
No Data
Related