• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 3 answers
  • Subscribers 82 subscribers
  • Views 386 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:

TMS320F2800157: eQEP Timer Period and Value

TMS320F2800157: TMS320F280015x

Jack he
Prodigy 30 points
Part Number: TMS320F2800157
Other Parts Discussed in Thread: C2000WARE

Tool/software:

Hello,experts Team,

I want to use PWMXBAR as input for eQEP, and tried several times but unsuccessful. The Technical Reference Manual(SPRUIY4B) not specify the PWMXBAR input source, and the "board.c" file generated by SysCfg configuration is also an empty function.

How can I set up a way to route InputXBAR to PWMXBAR?

Regards,

Jack

  • 0
    TI__Mastermind 21275 points

    HI Jack,

    You can reference the example provided in C2000Ware example "eqep_ex3_epwm_xbar" this example should demonstrate how to calculate the frequency of an PWM signal using the eQEP module. This ePWM signal is connected to input of eQEP using Input CrossBar and EPWM XBAR.

    Location in C2000Ware: driverlib\f280015x\examples\eqep

    Regards,

    Ozino

  • 0 in reply to Ozino Odharo
    Prodigy 30 points

    Hi Ozino，

    Thank you for your reply. The problem has been resolved now, and the changes are as follows:

    1 Manually input Xbar initialization statement, previously Xbar funtion in the "board. c" file generated by SysCfg was an empty function:

    XBAR_enableEPWMMux(EPWM_TRIP4, XBAR_MUX17);
    XBAR_setInputPin(INPUTXBAR_BASE, TUBESG_XBAR_INPUT, TUBESG_XBAR_SOURCE);
    XBAR_setEPWMMuxConfig(EPWM_TRIP4, XBAR_EPWM_MUX17_INPUTXBAR7);

    XBAR_setEPWMMuxConfig(EPWM_TRIP4, XBAR_EPWM_MUX17_INPUTXBAR7);
    XBAR_enableEPWMMux(EPWM_TRIP4, XBAR_MUX17);

    2 No instruction found in the manual(spruiy4B) for XbarInput7 corresponding to PwmXbar.1, but the yellow font in the following image reminded me to change the original XbarInput2 to XbarInput7, and the problem was solved!

    Regards,

    Jack

  • 0 in reply to Jack he
    TI__Mastermind 21275 points

    Hi Jack,

    Awesome! Glad to hear you got it working. Thanks for sharing your feedback.

    Regards,

    Ozino