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.

TMS320F28377D: ePWM EXTSYNCIN1 detection

Part Number: TMS320F28377D

Hello,

I'm trying to synchronize the timebase of an ePWM module to an external clock. The external clock has a 50% duty cycle, and a 5us period (same period that ePWM timebase is set for). Thus I plan to route the external clock from a GPIO to EXTSYNCIN1 via INPUTXBAR5.

However it's unclear how the SYNCI event is actually detected from EXTSYNCIN1. All the examples I can find of using EXTSYNCIN1 have it connected to the EXTSYNCOUT from another ePWM module (like for syncing two launchpads), which means the EXTSYNCOUT pulse is 8 PLLSYSCLK in duration (I assume the pulse is active high). I also see in the datasheet the minimum sync input pulse width is two ePWM clock periods. Is there a problem if the pulses are much longer (like 2.5us from my external clock)?

Also, is it possible to set things up to the SYNCI event occurs on a falling edge of my external clock? Can I just do that by inverting the GPIO input via its GPxINV register? I'm not sure if that works with the input Xbar....

Regards,

Mike

  • Hi Mike, 

     I also see in the datasheet the minimum sync input pulse width is two ePWM clock periods. Is there a problem if the pulses are much longer (like 2.5us from my external clock)?

    The sync event will only occur on the rising edge, so there should not be a problem if the pulses are much longer.

    Also, is it possible to set things up to the SYNCI event occurs on a falling edge of my external clock? Can I just do that by inverting the GPIO input via its GPxINV register?

    This should work as well. If you configure the GPIO to be inverted, inputxbar should carry that signal forward to the ePWM module.

    Best,

    Ma