
Enhanced Time Processing Unit (eTPU2)
MPC5644A Microcontroller Reference Manual, Rev. 6
Freescale Semiconductor
757
can be accessed, and interrupts and DMAs can be cleared and enabled/disabled. An engine only
enters Module Disable Mode when any currently running thread is finished (see
•
Stop Mode
Stop Mode is entered when eTPU answers device stop request assertion with stop acknowledge.
The definition of which clocks are stopped is made at the MCU level, which defines whether or not
registers can be accessed, interrupts and DMA requests cleared.
These modes are loosely selected: there is no unique register field or signals to choose between them.
Some features of one mode can be used with features of other mode(s). More on this subject can be found
on
Section 24.2.3.1, eTPU mode selection
, below.
NOTE
Throughout this document, an engine is said to be “stopped” if it is either in
Module Disable mode or Stop mode.
24.2.3.1
eTPU mode selection
User and User Configuration are the production operating modes, and differ from each other only in access
to SCM. User programmability is only possible with a RAM SCM.
On chips where the SCM is implemented as a RAM, it can either be accessed directly from IP-Bus for code
loading, or for software breakpoint setting. On chips with a ROM SCM, an internal SCM Emulation RAM
may be used, depending on the specific MCU implementation, to replace ROM SCM for test or debug
purposes. SCM Emulation RAM is selected in an MCU-specific way. For more details, see
Section 24.5.10.2.11, SCM emulation
.
For more information on SCM access, Debug and Test features, refer to
.
Debug Mode is characterized by the use of the debug interface features. Debug features may be
implemented using the eTPU-NDEDI internal interface. Specifically, this interface may be used with
Nexus implementation blocks to provide Nexus class 3 debug features. The use of eTPU-NDEDI interface
and Nexus implementation is MCU-dependent.
Module Disable Mode is entered by setting ETPU_ECR bit MDIS. eTPU engines can be individually
stopped going into Module Disable Mode (there is one ETPU_ECR for each engine). Each engine can
leave Module Disable Mode by writing MDIS = 0 (which can only be done if VIS = 0).
Stop Mode is activated by IP-Bus (device stop request). In this case, the eTPU waits for both eTPU engines
to enter in stop mode, and then asserts the stop acknowledge line. eTPU leaves Stop Mode when device
stop request is negated, but only if VIS = 0. If device stop request is negated and VIS = 1, eTPU will leave
Stop Mode as soon as VIS = 0.
NOTE
An engine can stay in Module Disable mode when it leaves Stop Mode if its
bit MDIS = 1, even if the other leaves it.
Summary of Contents for MPC5644A
Page 2: ...MPC5644A Microcontroller Reference Manual Rev 6 2 Freescale Semiconductor...
Page 24: ...MPC5644A Microcontroller Reference Manual Rev 6 24 Freescale Semiconductor...
Page 26: ...MPC5644A Microcontroller Reference Manual Rev 6 26 Freescale Semiconductor...
Page 52: ...Introduction MPC5644A Microcontroller Reference Manual Rev 6 52 Freescale Semiconductor...
Page 56: ...Memory Map MPC5644A Microcontroller Reference Manual Rev 6 56 Freescale Semiconductor...
Page 1228: ...Decimation Filter MPC5644A Microcontroller Reference Manual Rev 6 1228 Freescale Semiconductor...
Page 1440: ...FlexCAN Module MPC5644A Microcontroller Reference Manual Rev 6 1440 Freescale Semiconductor...