Not able to use Timers Library for Texas’s Tiva C series Processor

Hi, I am using TI’s EK-1294XL board for development and FreeRTOS. One of my requirement is to run some of tasks at every 10 seconds. To do this I am creating Timer task using xTimerCreate() but while trying to build it is saying that task is not available. I included the source file and also while writing code the function is accessible but while doing compilation it is giving error. Using Code Composure Studio for development and using CCS compiler for build. Not using GCC. Any solution for this? Thanks, Bhavesh

Not able to use Timers Library for Texas’s Tiva C series Processor

Set configUSE_TIMERS to 1 in FreeRTOSConfig.h.

Not able to use Timers Library for Texas’s Tiva C series Processor

You can also use a task instead of a software timer with the vTaskDelay() or vTaskDelayUntil() function to create the 10 second delay.

Not able to use Timers Library for Texas’s Tiva C series Processor

Hi, Got the issue resolved. Now able to build the project. Creating timer using follow: xTimerCreate(“TimerHndl”, (100), pdTRUE, (void *)1, UserTimerTask) Inside UserTimerTask() just have the Print statement. This functions should go to UserTimerTask() at every 100 ticks but its not running the callback even once. Other normal task created are working fine. Any reason for not going inside callback function? Thanks, Bhavesh

Not able to use Timers Library for Texas’s Tiva C series Processor

Is the timer task being starved of CPU time? Try setting its priority higher.

Not able to use Timers Library for Texas’s Tiva C series Processor

Hi, Problem was with stack size of Timer task. It was not sufficient which I allocated (32 word size was not enough, at least 128 word size is required for TI processor I am using). So timer was not able to run. Timer handler was not able to start but it was not creating any error so was not able to figure out issue. Thanks for your help.
  • Bhavesh

Not able to use Timers Library for Texas’s Tiva C series Processor

FreeRTOS has features that allow you to trap such errors immediately, without any debugging or support effort required. Look at using configASSERT(), malloc failed hooks and stack overflow hooks in your application. They will save/will have saved you hours of time. Regards.