MC33989PEG Freescale Semiconductor, MC33989PEG Datasheet - Page 21

• Manufacturer Part Number: MC33989PEG
• Description: SBC-HS
• Manufacturer: Freescale Semiconductor

STANDBY MODE
interface is available. Other functions available are wake-up input reading through SPI and HS1 activation. The Watchdog is
running.
NORMAL MODE
mode (Watchdog, wake-up input reading through SPI, HS1 activation, CAN communication). The software Watchdog is running
and must be periodically cleared through SPI.
STOP MODE
to deliver few mA. The objective is to maintain the MCU of the application supplied while it is turned into power saving condition
(i.e Stop or Wait modes). In Stop mode the device supply current from V
cyclic sense, forced wake-up, CAN message, wake-up inputs and over-current on VDD1), or the MCU side (key wake-up, etc.).
selection by the SPI (RCR, bit WDSTOP). To clear the watchdog, the SBC must be awakened by a CS pin (SPI wake-up). In
Stop mode, SBC wake-up capability are identical as in Sleep mode. Please refer to
SLEEP MODE
cyclic sense via the wake-up inputs pins and HS1 output, from the forced wake-up function and from the CAN physical interface.
When a wake-up occurs the SBC goes first into reset mode before entering Normal Request mode.
RESET MODE
Normal Request mode. Reset mode is entered if a reset condition occurs (V
closed window).
NORMAL REQUEST MODE
Stop mode. After wake-up from the Sleep mode or after the device power-up, the SBC enters the Reset mode before entering
the Normal Request mode. After a wake-up from the Stop mode, the SBC enters Normal Request mode directly.
Request mode an internal 350 ms timer is started. During these 350 ms the microcontroller of the application must address the
SBC via the SPI, configuring the Watchdog register. This is the condition for the SBC to stop the 350 ms timer and to go into the
Normal or Standby mode and to set the watchdog timer according to configuration.
NORMAL REQUEST ENTERED AND NO WD CONFIGURATION OCCURS
configuration occurs while the SBC is in Normal Request mode, the SBC goes to Reset mode after the 350 ms time period is
expired before again going into Normal Request mode. If no WD configuration is achieved, the SBC alternatively goes from
Normal Request into reset, then Normal Request modes etc.
SBC is in Normal Request mode, the SBC goes back to Sleep mode.
APPLICATION WAKE-UP FROM SBC SIDE
CAN, Wake-up input, etc.) the SBC turns itself into Normal Request mode and generates an interrupt pulse at the INT pin.
Analog Integrated Circuit Device Data
Freescale Semiconductor
Only regulator 1 is ON. Regulator 2 is turned OFF by disabling the V2 control pin. Only the wake-up capability of the CAN
In this mode, both regulators are ON. This corresponds to the normal application operation. All functions are available in this
Regulator 2 is turned OFF by disabling the V2 control pin. The regulator 1 is activated in a special low power mode, allowing
When the application is in Stop mode (both MCU and SBC), the application can wake-up from the SBC side (for example:
Stop mode is always selected by the SPI. In Stop mode the software Watchdog can be running or idle depending upon
Regulators 1 and 2 are OFF. The current from VSUP pin is reduced. In this mode, the device can be awakened internally by
In this mode, the Reset (RST) pin is low and a timer is running for a time RST
This is a temporary mode automatically accessed by the device after the reset mode, or after the SBC wake-up from
In Normal Request mode the VDD1 regulator is ON, V2 is OFF, the reset pin is high. As soon as the device enters the Normal
In case the Normal Request mode is entered after SBC power-up, or after a wake-up from Stop mode, and if no WD
In case the Normal Request mode is entered after a wake-up from Sleep mode, and if no WD configuration occurs while the
When an application is in Stop mode, it can wake-up from the SBC side. When a wake-up is detected by the SBC (for example,
BAT
DD1
is very low.
low, watchdog timeout or watchdog trigger in a
DUR
Table
. After this time is elapsed, the SBC enters
5.
FUNCTIONAL DEVICE OPERATION
OPERATIONAL MODES
33989
21