Simulink - Embedded Coder - C2000 - TI320F2837xD - ePWM - Event Trigger

I can choose after how many events a trigger will occur and i can choose at which event a trigger will occur. This seems conflicting to me, because either i can choose after which number event a trigger will occur or i can choose at which event a trigger will occur and not both.

Can somebody explain this to me?

[Venkatesh Chilapur]

Hi Bernd,

Please can you explain your problem with screen shots.

Regards,

Venkatesh C

Answer 1

[Bernd Pfeifer]

Hi Venkatesh,

here is a screenshot of the event trigger in the ePWM block of the TMS320F2387xD.

I want to send an interrupt, when the Counter equals to period. So i choose "Counter equals to period". So far so good.

But furthermore i can decide in "Number of event for start of conversion A (SOCA) to be generated" at which event an interrupt occurs (first - fifteenth event). But the interrupt should not depend on the number of the event. It should only occur if the counter equals to zero. I cannot deselect the line "Number of event for start of conversion A (SOCA) to be generated". So far, the best method is to set this line to "fifteenth event". But if one timerperiod has more than 15 events, the block generates an unwanted interrupt. How can i avoid this interrupt? Or am i understanding something wrong?

Regards,

Bernd

[Venkatesh Chilapur]

It Just means after how many events you want the interrupt to be generated. In this case 'First event' would mean the interrupt would be generated every time 'Counter equals to period'. If you have a 5usec (200KHz) period, you would get interrupt every 5usec. In case you have configured for 'Second event', then alternate instance of 'Counter equals to period' generates interrupt, i.e you would get interrupt every 10 usec, and with '3rd Event' configured every 15 usec so on.. Hope this is clear..

[Bernd Pfeifer]

Ahh okay, i thought that every event would count. Now it makes sense. Thanks