• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 31 subscribers
  • Views 519 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

RTOS/TM4C1294NCPDT: Timer used by RTOS

Pranav Saraswala
Intellectual 435 points

Part Number: TM4C1294NCPDT

Tool/software: TI-RTOS

Hi,

I noticed that even though i have not configured clock module in my RTOS application, bios seems to use Timer0 for its own use (and is now not available for me)

What is this timer0 being used by bios? Can i make it free.

BR,

Pranav

  • 0
    Intellectual 435 points
    TI Team,

    Waiting for reply on this.
  • 0 in reply to Pranav Saraswala
    TI__Guru**** 191886 points
    Hi Pranav,

    The O/S kernel also needs timer for itself. Normally based on the TI-RTOS cfg file the build will will pick the first timer ( normally TIMER0) that is available for the OS tick generation. However, if user specifically used TIMER0 by using timer_create or timer_construct API then the build process will look for the next available timer modules such as TIMER1 for the kernel.
  • 0 in reply to Charles Tsai
    Intellectual 435 points
    Thanks Chales for reply.

    Can you please point me towards relevant TI literature that can help me to understand this in more details.


    BR,
    Pranav.
  • 0 in reply to Pranav Saraswala
    TI__Guru**** 191886 points

    Hi Pranav,

     If you are configuring the timer statically then you could select ANY for the Timer Id. Please see below. If you choose ANY then the xdctool will choose whichever one that is available.   Or you can specify other timer instance of your choice. If you were configuring the timer dynamically you could use something like timerHandle = Timer_create(Timer_ANY, tickFxn, &timerParams, &eb) where Timer_ANY is used. Please refer to the in page 178 of the SPRUEX3T.pdf where it says "Runtime example: This C example creates a timer that runs the tickFxn() every 2 milliseconds using any available timer peripheral"