Chapter 8 Mode Entry Module (MC_ME)
MPC5606BK Microcontroller Reference Manual, Rev. 2
176
Freescale Semiconductor
S_DMA bit of the ME_IMTS register is set. This condition is detected regardless of whether the
proper key mechanism is followed while writing the ME_MCTL register.
•
If the target mode is not a valid mode with respect to current mode, the mode request illegal status
bit S_MRI of the ME_IMTS register is set. This condition is detected only when the proper key
mechanism is followed while writing the ME_MCTL register. Otherwise, the write operation is
ignored.
•
If further new mode requests occur while a mode transition is in progress (the S_MTRANS bit of
the ME_GS register is 1), the mode transition illegal status bit S_MTI of the ME_IMTS register is
set. This condition is detected only when the proper key mechanism is followed while writing the
ME_MCTL register. Otherwise, the write operation is ignored.
NOTE
As the causes of invalid mode transitions may overlap at the same time, the
priority implemented for invalid mode transition status bits of the
ME_IMTS register in the order from highest to lowest is S_SEA, S_NMA,
S_DMA, S_MRI, and S_MTI.
As an exception, the mode transition request is not considered as invalid under the following conditions:
•
A new request is allowed to enter the RESET or SAFE mode irrespective of the mode transition
status.
•
As the exit of HALT and STOP modes depends on the interrupts of the system, which can occur at
any instant, these requests to return to RUN0…3 modes are always valid.
•
In order to avoid any unwanted lockup of the device modes, software can abort a mode transition
by requesting the parent mode if, for example, the mode transition has not completed after a
software determined reasonable amount of time for whatever reason. The parent mode is the device
mode before a valid mode request was made.
•
Self-transition requests (e.g. RUN0
RUN0) are not considered as invalid even when the mode
transition process is active (i.e. S_MTRANS is 1). During the low-power mode exit process, if the
system is not able to enter the respective RUN0…3 mode properly (i.e. all status bits of the ME_GS
register match with configuration bits in the ME_
<mode>
_MC register), then software can only
request the SAFE or RESET mode. It is not possible to request any other mode or to go back to the
low-power mode again.
Whenever an invalid mode request is detected, the interrupt pending bit I_IMODE of the ME_IS register
is set, and an interrupt request is generated if the mask bit M_IMODE is ME_IM register is 1.
8.4.5.3
SAFE mode transition interrupt
Whenever the system enters the SAFE mode as a result of a SAFE mode request from the MC_RGM due
to a hardware failure, the interrupt pending bit I_SAFE of the ME_IS register is set, and an interrupt is
generated if the mask bit M_SAFE of ME_IM register is 1.
The SAFE mode interrupt pending bit can be cleared only when the SAFE mode request is deasserted by
the MC_RGM (see
Chapter 9, Reset Generation Module (MC_RGM)
, for details on how to clear a SAFE
mode request). If the system is already in SAFE mode, any new SAFE mode request by the MC_RGM
Summary of Contents for MPC5605BK
Page 2: ...This page is intentionally left blank...
Page 20: ...MPC5606BK Microcontroller Reference Manual Rev 2 20 Freescale Semiconductor...
Page 103: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 103 Clocks and power...
Page 645: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 643 Timers...
Page 715: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 713 ADC system...
Page 787: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 787 Memory...
Page 893: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 893 Integrity...
Page 943: ...MPC5606BK Microcontroller Reference Manual Rev 2 Freescale Semiconductor 943 Debug...