• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 297 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.

TMS320F28069: Getting unexpected timeout interrupt.

Alex Lifshitz
Intellectual 560 points

Part Number: TMS320F28069

Dear all,

I'm working with a timer configured as one-shot (id=1). Part number: TMS320F28069.

Start mode:timer will be started by user.

Inside the ISR, I reload the period by calling the "Timer_setPeriodMicroSecs()" function with desired timeout. The value provided is between 1000 and 21000 usec. After that, I start the timer again.

Once in a while (May come after few hundred cycles and may come after hundreds of thousands of cycles), I get an interrupt about 80 usec after the previous one. 

I'm sure (verified by debug tools) the value provided to Timer_setPeriodMicroSecs() at its last call, was at least 1000.

Please advise.

Alex.

  • 0
    TI__Genius 17315 points
    Alex,

    Please try to isolate the issue by creating a simple test case. Create a project consisting of only the code needed for the timer (main function, initialization code, and the single ISR). Disable the watchdog and test your code. (For a test you can place a breakpoint in the beginning of main). If this works as expected, then the issue is not with the timer but other code/functions running in your project.

    I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

    - Ken
  • 0 in reply to Ken Schachter
    TI__Genius 17315 points
    Alex,

    It's been a while since I have heard from you last. Therefore, I am assuming that my last reply resolve your issue. If this isn’t the case, please reject this resolution or reply to this thread. If this thread locks, please make a new thread describing the current status of your issue. Thank you.

    - Ken
  • 0 in reply to Ken Schachter
    Intellectual 560 points
    Hi Ken,
    After some changes in my application, I can't reproduce the issue any more.
    Probably it was some kind of memory overflow causing writing garbage to timer, but I'm still not sure about it.
    Anyway, thank you for your help and I'll update about any news.
    BR,
    Alex.
  • 0 in reply to Alex Lifshitz
    TI__Genius 17315 points
    Alex,

    Thanks for letting me know.

    - Ken