• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 31 subscribers
  • Views 318 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.

LAUNCHXL2-RM57L: ADC from HW Trigger of HET2_5

Marcus Fritzmann
Prodigy 50 points

Part Number: LAUNCHXL2-RM57L
Other Parts Discussed in Thread: HALCOGEN

Hi everyone,

i successfully set up a Hardware Trigger from HET2_1 for ADC1G1. Now i configurated everything for the ADC2G1 and HET2_5 but it seems like the ADC's is not triggered.

I verified the ADC Setup by switching the HET2_1 and HET2_5 pins, which worked.

Are there any issues by using two hardware triggers of het2 for 2 adc's?

  • 0
    TI__Mastermind 27355 points

    Hello,

    Some things to check for:

    • Ensure HET2 and ADC2 driver is enabled under the "Driver Enable" table in HALCoGen.
    • Make sure the PINMUX is configured for N2HET2[5] in HALCoGen. This is row D16 under the Pin Muxing tab.
    • Under "Special Pin Muxing" ensure you have checked "Use Alternate ADC Trigger Option-A" 
    • Ensure HET2_5 is selected as the ADC2 Group 1 Trigger.
    • Ensure the Hardware Trigger option is selected.

    I don't see N2HET2[5] broken out on the LaunchPad, it may be good to test with another pin that is broken out so that you can verify that it is toggling as expected. 

  • 0 in reply to Sahin Okur
    Prodigy 50 points

    Thank you for your suggestions. I got it.

    Halcogen was a bit missleading as the drop down of the alterative triggers suggested both - the alternative Trigger A and B. Het2_1 was B and HET2_5 is A.

    Het2_5 is there =)