• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 82 subscribers
  • Views 579 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.

Original question:

120cycles Interrupt latency on 28035

TMS320F28035: for loop and while loop can lead to interrupt latency?

Soldier 76
Intellectual 555 points
Part Number: TMS320F28035

Hi，everyone

I am puzzled by the interruption delay，with a  search then i found this two below posts. According to my understanding，it means for loop cannot be interrupted,  it must complete the branch before the interrupt will be taken.  If I understand right, Is there a high probability of interrupt delay if loop in main code?

post 1,  

https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/535190?120cycles-Interrupt-latency-on-28035

 

POST 2:

https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/266633 

Am i understand right?

thanks for any help.

  • 0
    TI__Mastermind 27200 points

    There will always be some interrupt latency, whether the interrupt takes place inside a 'for' loop or not. This is true for any MCU. In the first post you referenced the issue appeared to be related to interrupt payload. In the second, code execution from (slower) flash memory was involved.  Neither issue was caused by the presence of a for loop.

    It is not true that a 'for' loop cannot be interrupted. Certain instructions, such as the RPT instruction mentioned in the first post, are non-interruptible, but they are not related to the loop.

    Regards,

    Richard

  • 0 in reply to Richard Poley
    Intellectual 555 points

    Hi, Richard

    Thanks for your help,your answer is helpful to me