• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 252 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

TMS570LS0714: ADC Group trigger from Option A - N2HET2[5] or N2HET2[13]

v01d
Expert 1965 points
Part Number: TMS570LS0714
Other Parts Discussed in Thread: HALCOGEN

ADC1/2 have this as option of hw triggers, from dev data sheet: Under OPTION A, I would like to use N2HET2[5] (or N2HET2[13] say;  must be second het HET2)

Problem is, I cannot find any MCU pin dedicated or mux'able to this N2HET2[5] channel, for either 144 pins or 100 pin package.  I'm using / have to use the 100 pin option.
Is it not routed out?

How can I then use this trigger?  On the LS043x,  I was successfully using an odd numbered HET output this way by generating PWM and channeling it into this HET channel/pin, but, there was a pin mux option to output it on the physical pin, which only then would trigger my ADC group.

Where / how can N2HET2[5]  be used as hw trigger to my ADC group, with generating needed frequency with one of this HET's PWMs ?

  • 0
    TI__Guru**** 193196 points

    Hi,

    This device (PGE and PZ packages) does not have N2HET2[5] and N2HET2[13]. For PGE package (144-pin), only N2HET2 0/2/4/6/8/10/12/14/16/18 are available.  For PZ package (100pin), there are only  4 N2HET2 signals available (0/2/4/6).

  • 0 in reply to QJ Wang
    TI__Mastermind 49120 points

    Triggering ADC conversions using N2HET2 signals does not require these N2HET2 signals to be output on the pins. The connection between N2HET and ADC modules are made internally, so you can trigger the ADC using these PWM outputs even if the corresponding pin is not available on that package.

  • 0 in reply to Sunil Oak
    Expert 1965 points

    Is it possible to confirm  that that package does _not_ have these hets ?  Because HalCoGen for PZ _does_ show me them ..

      really would be disappointing that your datasheet for both of these devices does list that as trigger available.

    This is frustrating. 

  • +1 in reply to v01d
    TI__Mastermind 49120 points

    Let me explain again: you don't need an N2HET2 signal to be available on a package pin in order to use it to trigger an ADC conversion. That is what the foot notes mean. See highlighted text below:

    You can enable N2HET2[5] as the trigger source for the ADC conversions using HALCoGen, and configure the N2HET2 module to generate a PWM waveform on the N2HET2[5] channel.

    This will trigger the ADC periodically, no external connections required.

  • 0 in reply to Sunil Oak
    Expert 1965 points

    Hi ,

    It makes sense, but, I needed to make this dead sure as the board will be finalized today then and time is tight for rework.

    So I'm very happy you replied so fast, appreciate it, and I will go by this. I wasn't sure if QJ Wang replies _just_ about physical pins out, or availability..  Because I do see table 4-20 for PZ  H2HET does _not_ list N2HET2[5] at all, 

    Yet I 've found your note.   So im' a little bit lost in the datasheet, but with your help its clearing up.

  • 0 in reply to v01d
    TI__Mastermind 49120 points

    You are right - QJ had replied only about the availability of the physical pins. The timer channels are present even if they are not bonded out to pins.

    You can try it out yourself. Generate code to trigger ADC using N2HET2[5] and ensure that it works.

  • 0 in reply to v01d
    Expert 1965 points

    Problem is I cannot try on taht exact PZ chip configuration - there is no PZ based dev kit with that model.

    The full hdk I have is based on x12, and its a bga where N2HET2[5] is routed out;   It does work however nicely to trigger my ADC. BUT I though that test is invalid.


    Thanks however so much for fast repyling.