Single Shot App Timer Draws Much More Current Than Repeated App Timer

Hi!

I've followed the app timer example to implement app timers in my project. My project is low power consumption oriented. When I use a repeated timer, power consumption stay pretty low at about 2 uA. But When I start a single shot timer, power consumption raise at about 500 uA and never goes back to 2 uA. Maybe this is caused by the high frequency clock enabled by a single shot timer? Why a single shot timer would increase power consumption that much vs a repeated timer? What is the issue? I use SDK 16.0.0.

Thank you!

Parents
  • Hi,

    This does not make any sense no. Are there any other app_timers running here while you are starting the one shot timer? It could be an idea to have a slow "dummy" app_timer running with repeated interval of for instance 200seconds timeout (don't make it longer than 255seconds due to potential overflow issues). This will avoid that app_timer need to start and stop the clock tree if no other app_timers are running.

    Kenneth

Reply
  • Hi,

    This does not make any sense no. Are there any other app_timers running here while you are starting the one shot timer? It could be an idea to have a slow "dummy" app_timer running with repeated interval of for instance 200seconds timeout (don't make it longer than 255seconds due to potential overflow issues). This will avoid that app_timer need to start and stop the clock tree if no other app_timers are running.

    Kenneth

Children
No Data
Related