
69rlq62d-f714peg4 * Memec (Headquar
ter
s) - Unique
Tec
h,
Insight,
Impact
MAR
VELL CONFIDENTIAL,
UNDER ND
A# 12101050
69rlq62d-f714peg4 * Memec (Headquar
ter
s) - Unique
Tec
h,
Insight,
Impact
MAR
VELL CONFIDENTIAL,
UNDER ND
A# 12101050
69r
lq62d-f714peg4 * Memec (Headquar
ters) - Unique
T
ech, Insight, Impact * UNDER ND
A# 12101050
MAR
VELL CONFIDENTIAL - UNA
UTHORIZED DISTRIB
UTION OR USE STRICTL
Y PR
OHIBITED
PXA300 Processor and PXA310 Processor
Vol. I: System and Timer Configuration Developers Manual
Doc. No. MV-TBD-00 Rev. A
CONFIDENTIAL
Copyright © 12/13/06 Marvell
Page 188
Document Classification: Proprietary Information
December 13, 2006
Not approved by Document Control. For review only.
4.
5. The MPMU asserts SYS_EN, enabling the external high-voltage power supplies. The external voltage
regulators supply VCC_MVT first, followed by VCC_CARD1, VCC_CARD2, VCC_PLL, VCC_BG,
VCC_OSC13M, VCC_MEM, VCC_DF, VCC_MSL, VCC_CI, VCC_LCD, VCC_IO1, VCC_IO3,
VCC_BIAS(PXA310 processor), VCC_ULPI (PXA310 processor) and VCC_USB(PXA300 Processor).
6. The MPMU asserts PWR_EN and the power manager I
2
C module sends I
2
C commands, enabling the
external low-voltage power supplies: VCC_APPS and VCC_SRAM.
7. The power domains are powered up.
8. The MPMU negates nRESET_OUT.
Note:
The delay between the de-assertion of nRESET and nRESET_OUT is described in the PXA300
Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification.
Normal boot-up sequencing begins with all subsystems, beginning with their predefined reset conditions. The
core software must examine the “Application Subsystem Reset Status register (ARSR)” to determine that the
reset source was a hardware reset.
8.6.3
GPIO Reset
GPIO reset is used as a “soft” reset that allows users to reset the processor while maintaining data in external
memory devices and the real-time clock. GPIO reset is invoked when the nGPIO_RESET pin is asserted low or
when SWGR in the
“Power Management Unit Control Register (PMCR)”
is set to 1. GPIO reset does not reset
most of the services unit and does not reset the . If nBATT_FAULT is asserted while GPIO reset is asserted and
PCMR[BIE] = 0, the MPMU enters S3 state and does not exit until an enabled wake-up event is detected. If
nBATT_FAULT is asserted while nGPIO_RESET is asserted and PCMR[BIE] = 1, the MPMU completes the
GPIO reset sequence and then asserts the nBATT_FAULT interrupt if nBATT_FAULT is still asserted for 100
μ
s
after nGPIO_RESET is negated. The application subsystem must wait until GPIO reset is negated before exiting
reset.
If the MPMU is in S0 state when nGPIO_RESET is asserted, GPIO reset is propagated to the application
subsystem immediately. If the MPMU is in S2 state, the GPIO reset is first treated as a wake-up event by the
MPMU and then propagated to the application subsystem as a GPIO reset. If the MPMU is in S3 state and
SYS_EN is deasserted, the GPIO reset is ignored until an enabled S3 wakeup is asserted. If the MPMU is in the
process of entering S3 state and SYS_EN has not been deasserted when nGPIO_RESET is asserted, the S3 entry
is first completed and then the GPIO reset is treated as a wake-up event by the MPMU. Refer to the PXA300
Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specification for nGPIO_RESETtiming
requirements. In GPIO reset, all units in the processor subsystem are reset to their predefined reset states except
those listed in
The nGPIO_RESET pin has a pull-up inside the pad that is active following any reset except S3 low-power mode
exit until the PUDH bit in the
“Power Management Unit General Configuration Register (PCFR)”
is set. Refer to
the PXA300 Processor and PXA310 Processor Electrical, Mechanical, and Thermal Specificationfor
nGPIO_RESET timing requirements.