• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 850 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.

interrupt handling in omapl138

kaushal kumar
Prodigy 10 points

Other Parts Discussed in Thread: OMAPL138

I am new to dsp programming and started with omapl138 . starting with the few examples provided by ti in the page http://processors.wiki.ti.com/index.php/QuickStartOMAPL1x_rCSL i began to explore it more. the program timer_interrupt provided in the package is : a timer running in 32 bit unchained mode and generating an interrupt every second automatically. this interrupt is mapped onto cpu hardware interrupt int4 which then executes the interrupt service routine of counting the no. of interrupts occured so far. i am confused in the sense that is int4 also will be generated after every second so the interrupt service routine for int4 should also get executed after every second and as it should not take a lot of time to execute in almost 3 to 4 seconds we should get a message on the screen intimating that 3 or 4 interrupts have occurred. am i right or not. or it is regarding a interrupt being generated every second by the timer and mapping it onto int4 and executing the isr but why is it taking so much of time to execute any help will be appreciated at the earliest. and to start learning interrupt handling can anyone suggest some scenarios which can be programmed to easily understand the interrupt handling from the basic. 

  • 0
    TI__Guru 57257 points

    I'm not sure I understand the distinction between your two questions.

    But in summary, this example 1) maps the timer interrupt to the DSP int4.  2) enables the timer to trigger an interrupt every second, 3) in the int4 isr (which is mapped to teh timer) it simply prints the number of times that the interrupt occurs.  4) It exits after 5 occurences.

    So ... .on the console, you should see something like:

    Interrupt Count: 1

    Interrupt Count: 2

    <snip>

    Interrupt Count: 5

    (The above should happen at 1 second intervals, and exit after 5 seconds).

    As a side note, you should consider moving to the OMAPL138 Starterware package, which has low level non-os driver support for various peripherals, including the timer, and DSP interrupts. Examples are provided for the same.  That is available here:

    www.ti.com/starterware

    Regards
    Kyle