• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 81 subscribers
  • Views 439 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Why don't motorware acknowledge the adc interrupt at the end of mainISR.

chen yuan
Prodigy 85 points
Other Parts Discussed in Thread: MOTORWARE, CONTROLSUITE

Motorware acknowledges the interrupt at the beginning of the mainISR. Why don't  acknowledge the adc interrupt  at the end of mainISR? 

what’s happened if there is recursive interrupt when the mainISR  is  in progress, and  will this cause some unstable issues in this situation?

  • 0
    TI__Expert 4595 points
    Good observation.

    The code was written specifically to acknowledge the interrupt event at the start of the ISR to match the design of the MCU. If the peripheral event that generated the interrupt flag were not acknowledged AND the same oeripheral event occurred again, this event would be lost. By acknowledging the event at the start of the ISR, it becomes a pending interrupt that is called immediately on exit from the current ISR (if it is the highest priority interrupt pending).

    Keep in mind that all interrupts are masked upon entry into an ISR. For nested interrupts to occur the code must re-enable the CPU mask but (INTM). There is a good example of nested priority interrupts in ControlSUITE.

    Jeff