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.

Changing SYSBIOS Default Timer

Other Parts Discussed in Thread: SYSBIOS

Hi,


I have an application where I need to use timer 0 to generate a very fast pulse. This is on the ompal137 on the dsp and arm side. I can accomplish this by telling the clock module to use timer 1 leaving timer 0 for the pulse generation. If I disable the clock module it defaults to timer 0 and I have not figured out how to tell sysbios which timer to use without using the clock module. The documentation is really scarce on this topic. Sadly the only timer exposed to the outside world is TM64P0_OUT12 so that side of the timer is exclusive for the ADC convert clock.

What I'm trying to do, since the OMAPL137 has two 64 bit timers from which SYSBIOS grabs one 32 bit unchain mode, is to control which timer SYSBIOS uses. I need to allocate halves of the 64 bit to different things. For example DSP uses timer 1 lower half and ARM timer 1 upper half.

On the ARM side I'm also running SYSBIOS and I'm not sure if both OS can use the same timerid for example timer 1. If not, is it possible to assign in sysbios one half of timer 1 to the DSP and the other half to the ARM?

  • Hi Hoffiz,

    I found two potentially useful links below in case you have not seen them.
    As for the DSP and ARM sharing two different 32-bit halves of the 64-bit timers used in unchained mode,basically this is possible as long as you make sure the ARM/DSP both don't use the same half of any Timer and choose only one of the cores as the 'master'.

    Excerpting and editing from the e2e post: To specify who the 'master' of the Timer is you set the 'master' field of the module wide config paramter 'timerSettings[]'. By default, the 'master' field is TRUE on both devices which means, both of them would release the specified Timer from reset. Generally, for devices with both an ARM and DSP, the ARM should be the 'master' since it usually initializes peripherals, memory, etc...before it release the DSP. If that is the case, set the 'master' field for the DSP to be 'FALSE' so the DSP does not try to release the Timer from reset again.

    e2e.ti.com/.../91503

    www.ti.com/.../sprufm5d.pdf

    Murat
  • Hi Hoffiz,
    Can you please mark this thread as answered if this answers your question, otherwise, do you still have some specific questions?
    Murat