![Freescale Semiconductor MPC5632M Manual Download Page 952](http://html.mh-extra.com/html/freescale-semiconductor/mpc5632m/mpc5632m_manual_2330659952.webp)
MPC563XM Reference Manual, Rev. 1
952
Freescale Semiconductor
Preliminary—Subject to Change Without Notice
} while (temp != 0);
do
{
temp = ETPUC1HSRR_1;
} while (temp != 0);
//Write GTBE bit to start TCR1 and TCR2 time bases counting
//at the same time
ETPUMCR = (ETPUMCR | GTBE);
}// end of etpu_initialization routine
***********************************************************************************
23.6.3
Predefined Channel Mode Summary
explains channel double match predefined submode functionality by showing all event
sequence possibilities. The initial state considered for all submodes is channel flags MRL1, MRL2, TDL1
and TDL2 reset. From initial state one can follow the table and verify how each submode behaves in a
determined sequence of events. Note that the actions performed by an event type depend on all previous
events following the initial state, for a given channel submode.
There are three columns for each event: one for event type, one for enable/disable actions and one for
capture.
Event type
column can be match1, match2, trans1 and trans2 (for double transition modes).
Enable/disable actions
column (identified as “
[blocks](enables)
” in column head) specifies which other
events are enabled or disabled. Initially disabled events (specified in
“initially blocked”
column) are
usually enabled by other events.
In double transition submodes, the first transition detected is always considered trans1 and the second is
considered trans2. This means that trans1 event actually enables the detection of trans2 event. This is not
explicit in the table, since it is a general behavior for all double transition submodes.
A sequence of four events (two matches and two transitions) are necessary to describe the behavior of
some channel submodes. When a determined sequence of events has less than four events, the other event
columns are left blank.
Cells in an
“event type”
column that have light-grayed background indicate that a service request is
generated. More than one event in the same event sequence can issue service request.
NOTE
The table does not exhaust all possibilities of channel logic event sequences,
because it does not account for possible microcode interventions. For
instance, if matches are blocked by first transition and microcode resets
TDL1, the matches become enabled again, and from this point on the
channel behaves as if the first transition had never occurred.