Timer stops after 32 Times with using OpenThread

[Dnil]

Hello,

i'm currently working on my Bachelor Thesis using Makerdiary Board.
I recompiled the OpenThread Libraries to get the CLI working on my Board.

I need to read out sensors every 3 minutes, therefore I'm using the APP-Timer Library, but the timeout  handler stops working after some time.
To debug the problem I set the duration of the timer to 10 seconds there the timer stops after 32 times and the CLI becomes unresponsive.
I have no idea how to get rid of this problem.

I uploaded the Project to this private Thread.

Best regards

Dnil

[Jørgen Holmefjord]

Hi,

Like I said in the private thread, it looks like this is caused by a Hardfault, and that it is not related to the timer. Can you confirm if the CLI becomes unresponsive in your application, regardless of if you start the timer or not? This to make sure that I'm seeing the same problem that you are experiencing.

I will then try to debug further why the Hardfault is happening.

Best regards,
Jørgen

[Dnil]

Hi,

I can confirm that the CLI becomes unresponsive if I call the function 

app_timer_start(read_sensor_timer, READ_SENSOR_DURATION, NULL);

but when commenting this function, so it won't be called,  the CLI is still working fine.

Best regards,
Dnil

[Jørgen Holmefjord]

Hi,

Sorry for the slow response. I'm still not able to reproduce the behavior you describe. On my setup, I get only 18 timer events, and then the CLI becomes unresponsive.

Can you provide the project without any external device dependencies (TWI/SPI sensors, etc)?

Best regards,
Jørgen

[Dnil]

Hallo, 

i removed every TWI/SPI sensors and their dependencies.

In the mean time, I also tried a work around, i changed the timer with an topic subscription and every time the topic get updated it will read the sensor register but there the CLI also becomes unresponsive after about 3 min.

In the future I will try to add a button, to eliminate all the other timer.

Best regards,
Dnil

FirmwareV3.zip

[Jørgen Holmefjord]

Not sure why your application crashes, but it seems to correspond with the BLE_ADV_EVT_IDLE event.

If I set APP_ADV_DURATION to 0 instead of 18000 (3 minutes), the application seems to continue to work after 3 minutes.

What I do not understand is how you were not able to see this issue if you removed the call to app_timer_start() in the previous application.