• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 30 subscribers
  • Views 834 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.

TMS570LS3137: N2HET1[1]/N2HET2[8] not working as capture inputs

Anand Meharwade
Expert 1090 points
Part Number: TMS570LS3137

Hello,

I am feeding a 100Hz/50% PWM signal on the pin 23 of TMS570LS3137 controller. The necessary driver and pin configuration is made but still not able to read the valid PWM freq and duty using the capGetSignal() function call. Kindly let me know how to resolve this issue. Below are the configuration setup for the capture input N2HET1[1]

I have tried with the similar driver setup for HET2[8] but it didnt work and the capGetSignal() read values for freq and duty are not valid. I am success with above configuration for N2HET1[4] and N2HET1[6] pins.

Appreciate for the early response and support. Thanks in advance.

Regards,

Anand M

  • 0
    TI__Mastermind 21425 points
    Hello,
    Please, check whether this thread helps: e2e.ti.com/.../692495

    Best regards,
    Miro
  • 0 in reply to Miro
    Expert 1090 points

    Dear Miroslav,

    Thanks for the response, the issue is same but with different pin set, I am not sure which bit need to be changed. I feel the HR share is cleared in the configuration for HET[1]. With this configuration, the capture is still not working for me. Kindly suggest.

    /** - Set HET pins high resolution share */

    hetREG1->HRSH = (uint32) 0x00000000U

    | (uint32) 0x00004000U

    | (uint32) 0x00002000U

    | (uint32) 0x00000000U

    | (uint32) 0x00000000U

    | (uint32) 0x00000400U

    | (uint32) 0x00000000U

    | (uint32) 0x00000100U

    | (uint32) 0x00000080U

    | (uint32) 0x00000000U

    | (uint32) 0x00000020U

    | (uint32) 0x00000000U

    | (uint32) 0x00000008U

    | (uint32) 0x00000004U

    | (uint32) 0x00000000U

    | (uint32) 0x00000000U;

     

    Regards,

    Anand M

  • 0 in reply to Anand Meharwade
    TI__Mastermind 21425 points
    Hello,
    Do you have any progress?

    Best regards,
    Miro
  • 0 in reply to Miro
    TI__Mastermind 21425 points
    Hello,
    I hope you have solved your problem. Since there is no feedback, I'll close this thread. You can reopen it at anytime with just replying or you can post new thread.

    Best regards,
    Miro