App Timer does not trigger his handle function

RE: App Timer does not trigger his handle function

Karl Ylvisaker — Tue, 25 Jan 2022 14:53:48 GMT

[quote user="Christos.Bou"]Thanks for your advice about the DEBUG ![/quote]

No problem at all - it is a very helpful configuration - I am happy to hear that you found my advice helpful!

[quote user="Christos.Bou"]The issue was that I was not initializing lfclk at the start.
Even if I have a SoftDevice, if I do not initialize the SoftDevice I need to intialize lfclk I guess[/quote]

I am not sure I have understood you fully here. With a SoftDevice present the clock peripherals will be restricted access, meaning that all clock related calls should be triggered through the SoftDevice API.
However, in an application without the SoftDevice present you will not need to manually start and stop the LFCLK in order to use the app_timer API - it will be done as part of the app_timer initialization and usage. Could you elaborate on what you meant here?

Best regards,
Karl

RE: App Timer does not trigger his handle function

Christos.Bou — Tue, 25 Jan 2022 10:49:11 GMT

The issue was that I was not initializing lfclk at the start.
Even if I have a SoftDevice, if I do not initialize the SoftDevice I need to intialize lfclk I guess

RE: App Timer does not trigger his handle function

Christos.Bou — Tue, 25 Jan 2022 09:47:35 GMT

Thanks for your advice about the DEBUG !

Unfortunally, adding the app_timer_init into my timer_init function didn't change anything...

Is there anything else that I could try to find the bug ?

RE: App Timer does not trigger his handle function

Karl Ylvisaker — Tue, 25 Jan 2022 09:41:59 GMT

Hello,

[quote user="Christos.Bou"]I'm using the RTT terminal because when I run the code, the debug terminal show me this : [/quote]

Thank you for clarifying.

It seems I glanced over the code too quickly yesterday. Please add the app_timer_init to your timer_init function, and see if this resolves the issue.

For future reference, please also add the DEBUG define to your preprocessor defines like shown in the included image:

This will make your logger output a detailed error message whenever a non-NRF_SUCCESS error code is passed to an APP_ERROR_CHECK.

Best regards,
Karl

RE: App Timer does not trigger his handle function

Christos.Bou — Tue, 25 Jan 2022 08:22:14 GMT

Hello,

I'm using the RTT terminal because when I run the code, the debug terminal show me this :

I just don't get the "Yes" from the timer handler on the terminal and I don't get why...

And no, when I debug, the code seems to work as expected in an infinite loop.

RE: App Timer does not trigger his handle function

Karl Ylvisaker — Mon, 24 Jan 2022 17:40:01 GMT

Hello Chris,

I do not immediately see anything wrong with your use of the application timer library so I suspect that the problem actually may be with the logging.
Which logger backend are you using?
The Segger Debug Terminal is an RTT terminal, so it will only show the loggings if the logger module is using the RTT backend. If you are using the UART backend you will need to use a serial terminal like Termite, PuTTy or similar to see the logs.
Are you seeing any other unexpected behavior? Is the device resetting unexpectedly, for example?

Best regards,
Karl