Software timers sleep indefinitely after systick overflow

kelvinelton wrote on Friday, March 10, 2017:

I am currently developing a project with FreeRTOS (v8.2.1) on ARM Cortex-M3 (STM32F103xE) and IAR Compiler and all the software timers callbacks stopped being called after a systick overflow.

I also created a minimal example and the result was the same. The timer worked just fine until the overflow on xTickCount. Am I missing something here or is there really a bug?

I also tried to create the timer within a task, or starting it after osKernelStart(), but it’s always the same result.


#define configUSE_16_BIT_TICKS                   1
#define configTICK_RATE_HZ                       ((TickType_t)1000)
#define configUSE_TIMERS                         1
#define configTIMER_TASK_PRIORITY                3
#define configTIMER_QUEUE_LENGTH                 6
#define configMINIMAL_STACK_SIZE                 ((uint16_t)128)
#define configTIMER_TASK_STACK_DEPTH             configMINIMAL_STACK_SIZE


static volatile uint32_t testtick = 0;
TimerHandle_t test_timer = NULL;

void testticktimer(void * n) {
    testtick += 10;

int main() {
    // Hardware configuration (clock, systick, ...)
    test_timer = xTimerCreate("test_timer", pdMS_TO_TICKS(10), pdTRUE, (void *) 2, testticktimer);
    xTimerStart(test_timer, 0);

rtel wrote on Friday, March 10, 2017:

The behaviour of software timers when the tick overflows is very well tested. In addition soak tests that use a 16-bit counter, which results in frequent overflows, run for months with no failures. That doesn’t mean there are not bugs though, just that if there are our tests don’t find them.

It looks like you are using an abstraction layer on top of the FreeRTOS API. My first suggestion would be to try using the native API directly. If you still have a demostatable issue after that please create the smallest project possible that exhibits the behaviour along with instructions on how to observe the error and we can investigate.

kelvinelton wrote on Monday, March 13, 2017:

Actually I was using the version 8.2.2 and the problem occurs only in this version.
I tried 8.2.1 or 8.2.3 and it worked as excepted. It’s probably the same bug fix related to tickless low power applications.

rtel wrote on Monday, March 13, 2017:

Didn’t realise you were using tickless - tickless and software timers
didn’t used to work together but that was changed some versions ago.

kelvinelton wrote on Monday, March 13, 2017:

I am not using tickless. I just suspect that the same bugfix that corrected the tickless problem between 8.2.2 and 8.2.3 also corrected my problem.