Datasheet

166

RM57L843

SPNS215C –FEBRUARY 2014–REVISED JUNE 2016

www.ti.com

Submit Documentation Feedback

Product Folder Links: RM57L843

NOTE

For ADEVT trigger source, the connection to the MibADC1 module trigger input is made from

the output side of the input buffer. This way, a trigger condition can be generated either by

configuring ADEVT as an output function on to the pad (through the mux control), or by

driving the ADEVT signal from an external trigger source as input. If the mux control module

is used to select different functionality instead of the ADEVT signal, then care must be taken

to disable ADEVT from triggering conversions; there is no multiplexing on the input

connection.

If ePWM_B, ePWM_A2, ePWM_AB, N2HET2[1], N2HET2[5], N2HET2[13], N2HET1[11],

N2HET1[17], or N2HET1[19] is used to trigger the ADC, the connection to the ADC is made

directly from the N2HET or ePWM module outputs. As a result, the ADC can be triggered

without having to enable the signal from being output on a device terminal.

NOTE

For N2HETx trigger sources, the connection to the MibADC1 module trigger input is made

from the input side of the output buffer (at the N2HETx module boundary). This way, a

trigger condition can be generated even if the N2HETx signal is not selected to be output on

the pad.

NOTE

For the RTI compare 0 interrupt source, the connection is made directly from the output of

the RTI module. That is, the interrupt condition can be used as a trigger source even if the

actual interrupt is not signaled to the CPU.

7.4.2.2 MibADC2 Event Trigger Hookup

Table 7-17 lists the event sources that can trigger the conversions for the MibADC2 groups.