The information given in this document shall in no event be regarded as a guarantee of conditions or
characteristics. With respect to any examples or hints given herein, any typical values stated herein and/or any
information regarding the application of the device, Infineon Technologies hereby disclaims any and all
warranties and liabilities of any kind, including without limitation, warranties of non-infringement of intellectual
property rights of any third party.
Information
For further information on technology, delivery terms and conditions and prices, please contact the nearest
Due to technical requirements, components may contain dangerous substances. For information on the types in
question, please contact the nearest Infineon Technologies Office.
Infineon Technologies components may be used in life-support devices or systems only with the express written
approval of Infineon Technologies, if a failure of such components can reasonably be expected to cause the
failure of that life-support device or system or to affect the safety or effectiveness of that device or system. Life
support devices or systems are intended to be implanted in the human body or to support and/or maintain and
sustain and/or protect human life. If they fail, it is reasonable to assume that the health of the user or other
persons may be endangered.
PRIMECELL™, REALVIEW™, THUMB™, µVision™ of ARM Limited, UK. AUTOSAR™ is licensed by
AUTOSAR development partnership. Bluetooth™ of Bluetooth SIG Inc. CAT-iq™ of DECT Forum.
COLOSSUS™, FirstGPS™ of Trimble Navigation Ltd. EMV™ of EMVCo, LLC (Visa Holdings Inc.).
EPCOS™ of Epcos AG. FLEXGO™ of Microsoft Corporation. FlexRay™ is licensed by FlexRay
Consortium. HYPERTERMINAL™ of Hilgraeve Incorporated. IEC™ of Commission Electrotechnique
Internationale. IrDA™ of Infrared Data Association Corporation. ISO™ of INTERNATIONAL
ORGANIZATION FOR STANDARDIZATION. MATLAB™ of MathWorks, Inc. MAXIM™ of Maxim
Integrated Products, Inc. MICROTEC™, NUCLEUS™ of Mentor Graphics Corporation. Mifare™ of
NXP. MIPI™ of MIPI Alliance, Inc. MIPS™ of MIPS Technologies, Inc., USA. muRata™ of MURATA
MANUFACTURING CO., MICROWAVE OFFICE™ (MWO) of Applied Wave Research Inc.,
OmniVision™ of OmniVision Technologies, Inc. Openwave™ Openwave Systems Inc. RED HAT™
Red Hat, Inc. RFMD™ RF Micro Devices, Inc. SIRIUS™ of Sirius Satellite Radio Inc. SOLARIS™ of
Sun Microsystems, Inc. SPANSION™ of Spansion LLC Ltd. Symbian™ of Symbian Software Limited.
TAIYO YUDEN™ of Taiyo Yuden Co. TEAKLITE™ of CEVA, Inc. TEKTRONIX™ of Tektronix Inc.
TOKO™ of TOKO KABUSHIKI KAISHA TA. UNIX™ of X/Open Company Limited. VERILOG™,
PALLADIUM™ of Cadence Design Systems, Inc. VLYNQ™ of Texas Instruments Incorporated.
VXWORKS™, WIND RIVER™ of WIND RIVER SYSTEMS, INC. ZETEX™ of Diodes Zetex Limited.
5.6 Emergency Recovery from Hibernate Mode ...................................................................................... 37
Device Guide 4 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Basics
Hibernate Mode Basics
Device Guide 5 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Basics
1 Hibernate Mode Basics
Hibernate Mode is one of the system power states of the XMC4000 device. The XMC4000 devices
implements Power Management control that aims at reduction of power consumption. The available
Power Modes (also referred to as Power States) of the system, depicted in Figure 1., offer different
features they may be utilized in an application specific manner, with the focus on different aspects,
like current consumption, transition time between states, system topology, etc.
Figure 1 System Power States
The XMC family implements the following Power Modes:
Active Mode - the normal operation state.
−Entered automatically after system reset release
Sleep Mode - clock of the CPU and selected peripherals is stopped.
−Entered via WFI or WFE instruction of the CPU (for details please refer to Cortex-M4
documentation)
−Wake-up on any valid interrupt/exception
Deep Sleep Mode – similar to Sleep Mode, with an ability to power down additional peripherals
− Entered via WFI or WFE instruction of the CPU (for details please refer to Cortex-M4
documentation)
−Wake-up on any valid interrupt/exception
Hibernate Mode – Power Supply to the chip or to the core (on some family XMC4000 family
members) is switched off and only Hibernate Domain remain powered on
The Hibernate Mode is the power mode of the lowest power consumption, offering Real Time Clock
keeping and preservation of a context specific data in a retention memory (for details on power
consumption and timing figures please refer to Data Sheet). Transitions into and from the power
states are controlled with user software and valid wake-up events respectively. The wake-up trigger
events may be generated by different sources, like external signals or RTC events, configured by the
user prior to entering a power saving state.
There are two implementations of the Hibernate Mode Control.
Externally Controlled Hibernate Mode (ECHM) with an IO actively controlling External Voltage
Regulator
Device Guide 6 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Basics
Internally Controlled Hibernate Mode (ICHM) with an internal signal actively controlling Embedded
Voltage Regulator (EVR)
1.1 Externally Controlled Hibernate Use Cases
Generic application scenarios of Externally Controlled Hibernate Mode are illustrated in Figure 2.
These use case scenarios enable the XMC4000 to act as a system Power Control Master. All system
components supplied with VDDP are powered off and no current is drawn in the VDDP power
domain. Upon a wake-up trigger complete VDDP power domain of the system on PCB will be brought
into operation.
Figure 2 Examples of Externally Controlled Hibernate Mode use case
The external hibernate control is performed via the Hibernate Control Signal that will switch off the
Voltage Regulator providing VDDP voltage to all components of the board. VBAT will still be supplied
from an auxiliary source like e.g. a coin battery, or, a capacitor while in the Externally Controlled
Device Guide 7 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Basics
Hibernate Mode. A wake-up trigger will come from an external source and/or from the internal RTC
module.
1.2 Internally Controlled Hibernate Use Cases
Generic application scenarios of Internally Controlled Hibernate Mode are illustrated in Figure 3.
These use case scenarios enable the XMC4000 to act as a system Power Control Slave. All system
components in the VDDP power remain powered on while Core Domain of the XMC4000 device is
powered off and I/Os are reset to input operation mode. Upon a wake-up trigger Core Domain of the
XMC4000 will be powered-up and brought into operation.
Figure 3 Examples of Internally Controlled Hibernate Mode use case
The internal hibernate control is performed via an internal circuit inside of the XMC4000 that will
switch off the Embedded Voltage Regulator providing VDDC voltage to the Core Domain of the chip.
While in Internally Controlled Hibernate Mode VBAT may still be supplied directly from the VDDP
source while main supply is available, and/or from an auxiliary source like e.g. a coin battery, or, a
Device Guide 8 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Basics
capacitor when the mains supply if off. A wake-up trigger will come from an external source and/or
from the internal RTC module and will enable Core Domain voltage generation (if VDDP is still
available).
Note: The Internally Controlled Hibernate Mode is not supported on XMC4500 device.
Device Guide 9 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Basics
Hibernate Mode
Implementations
Device Guide 10 V1.0, 2013-04
Hibernate
Table 1 Hibernate Wake-up Triggers
Trigger Source
I/O Signals
Description
RTC event
n/a
RTC Alarm or RTC Periodic Event.
Watchdog of RTC external
crystal oscillator
n/a
The RTC external crystal oscillator (OSC_ULP) watchdog
is capable of generating a wakeup trigger if the RTC clock
generated with external crystal, or, a direct external clock
stops unexpectedly
Digital Input Signal
HIB_IO_0
HIB_IO_1
Exclusive selection of one of the digital inputs. Depending
of an application a rising and/or falling edge of the signal
may be selected as a wake-up trigger. For external
hibernate mode it is possible to combine Hibernate Control
and Wake-up function in the same digital IO. For availability
of the IOs please refer to the Data Sheet.
Analog Input Signal
HIB_IO_0
HIB_IO_1
Voltage threshold level crossing detection performed in the
Low Power Comparator (LPAC) module. Depending of an
application a rising and/or falling voltage event may be
selected as a wake-up trigger. The level crossing detection
can be performed continuously, periodically, or, may be
triggered with an external digital signal. Multiple analog
channels may be used for the wake-up trigger detection.
For availability of the LPAC module please refer to the Data
Sheet.
VBAT Supply Level Detection
VBAT
VBAT voltage detection can be performed with LPAC
module. Depending of an application a rising and/or falling
voltage event may be selected as a wake-up trigger. The
VBAT input level can be performed continuously,
periodically, or, triggered with an external digital signal. For
availability of the LPAC module please refer to the Data
Sheet.
XMC4000 Family
Hibernate Mode Implementations
2 Hibernate Mode Implementations
The two Hibernate Mode implementations, ECHM and ICHM, described in this section differ in the
way the core voltage generation control mechanism. However, the wake-up trigger detection
mechanism is the same for both Hibernate Mode implementations. The wakeup source can be digital
or analog, internal (RTC event) or external (input signal on an I/O). For more details please refer to
Table 1.
Various combinations of wake-up triggers are possible and a wide range of possible applications is
considered. The optimal selection of the Hibernate Mode and wake-up triggers application specific
requirements and availability of resources need to be taken in consideration.
Some system topologies may combine capabilities of both implementation of the Hibernate Mode and
can be applied interchangeably when required. However, only one of the Hibernate Modes can be
applied at the time.
2.1 Externally Controlled Hibernate Mode Concept
The system configuration assumes that the XMC4000 device acts as the power management master
of the system on PCB and is capable to switch off/on the external Voltage Regulator. The Hibernate
Mode is entered by switching off the power supply VDDP of the device with the HIB_IO_0 pin. The
HIB_IO_0 pin remains in control of the External Voltage Regulator after entering Hibernate Mode
since entire Hibernate Domain remains supplied with the VBAT voltage from an auxiliary supply
Device Guide 11 V1.0, 2013-04
Hibernate
XMC4000 Family
Hibernate Mode Implementations
voltage, e.g. a coin battery or a capacitor. A more detailed example scenario superset depicted in
Figure 1 shows the components of the complete system that enable use of the Hibernate Mode.
The Hibernate Control Unit (HCU) implements a circuit capable of controlling an External Voltage
Regulator via an I/O and detecting occurrence of an event matching user programmed wake-up
condition.
Entering Hibernate Mode is performed with a software request to a control register in the HCU module
which results in toggling an I/O connected to the External Voltage regulator.
Figure 5 Externally Controlled Hibernate Mode Power Sequencing
Device Guide 12 V1.0, 2013-04
Loading...
+ 26 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.