Power Sequence
-
Power Sequence
VBUSStatus:attach:work in progress.Scope: Steps 1–24 come from the
CD3217spower-sequencewakediagramfrom their own LDOs and negotiate 5 V first, then 20 V once their firmware runs. PPBUS_AON should read around 12.3 V.
The following information is for an A2338 MacBook Pro M2 (1313"). inch)The A2779 (14", M2 Pro, 820-02841) and the 16" models have additional USB-C ports and controllers plus MagSafe. Differences must still be verified withon somethose 14" or 16" Pro/Max variant.
Source tags: [diagram] taken from the schematic power-sequence diagram · [measured] measured on the bench · [inferred] not confirmed.
The step numbers follow the diagram. They do not necessarily reflect the real timing, especially inside a stage.
Details of the 3.8 V always-on regulator (phases, coils, current sensing) are on the page PP3V8_AON.
Stages at a glance
PPBUS_AON established
B
8–9
Enable chain for the 3.8 V always-on rail, PP3V8_AON starts
C
10–12
PMU always-on rails, main PMU crystal, 32 kHz clock to the SoC
D
13–14
Power-on request, PMUs enable AWAKE / S1 / S2 rails (SoC and SSD)
E
15–18
24 MHz clock, SoC reset released, firmware, self-test
F
19–24
SMC ↔ USB-C controller communication, PD to 20 V, charger switches to buck mode
Stage A — USB-C attach and system bus
1. USB-C connection is detected
[diagram] The USB-C connector JE700 presents the USBC0_CC1_CONN signal through UF300.
2. Initial 5 V USB-C input appears
[diagram] The charger supplies approximately 5 V on PPVBUS_USBC0. This is the default USB-C voltage before Power Delivery negotiation.
3. USB-C controller auxiliary supply starts
[diagram] USB-C controller UF400 (CD3217B) generates PP3V3_UPC0_LDO.
This rail powers the controller's external SPI ROM UF260 (25Q80), accessed through:
SPI_UPC01_R_CS_LSPI_UPC01_R_CLKSPI_UPC01_R_MOSISPI_UPC01_R_MISO
4. The initial 5 V reaches the charger input
[diagram] The input passes through PPHV_INT0_AONSW, fuse FF200 and current-sense resistor R5220, becoming PPDCIN_USBC_AON.
At this point,point the input is still approximately 5 V because USB Power Delivery negotiation has not yet raised VBUS.
5. The charger controller becomes operational
[diagram] Charger controller U5200 (ISL9240HI) receives its required bias and sensing connections through VDDP, VDDA, CELL and PBUS.
6. The charger initially operates in boost mode
[diagram] U5200, together with MOSFETs Q5230 and Q5240 and inductor L5230, operates as a boost converter.
This raises the initial USB-C input sufficientlyenough to establish the system bus.
7. The 13 V system bus is established
[diagram] PPBUS_AON rises to approximately 13 V while the charger is operating in boost mode.
This rail supplies the always-on power system, including U5700. The actual voltage depends on the operating conditions (battery present or not, boost or buck mode). See the reference table at the end of this page.
Stage
B — 3.8 V always-on rail8. The main voltage-regulator enable is generated
[diagram] U5200 activates CHGR_EN_MVR. Through logic device U5340, this produces P3V8AON_PWR_EN.
9. The 3.8 V always-on rail starts
[diagram] P3V8AON_PWR_EN enables U5700, (RAA225501C).
generates U5700then generates:
PP3V8_AON.
Stage
C — PMU always-on rails and clocks10. The PMU always-on and standby LDO rails start
[diagram] PP3V8_AON supplies the main PMU U8100 and the secondary PMU U7700. The diagram marks the following rails as part of this stage.
From U8100:
PP1V8_AON_MPMUPP1V8_AONPP3V3_S2_LDOPP1V2_AWAKE_PLLPP1V2_AON_MPMUPP3V3_AONPP0V855_S2SW_CIOPP3V3_S2SW_SNSPP1V2_S2_CIOPP1V5_LDOINT_MPMU
From U7700:
PP1V2_AON_SPMUPP0V72_S2_VDD_LOWPP0V8_S1_VDD_FIXED
11. The main PMU crystal oscillator starts
[diagram] Crystal Y84A1 starts oscillating and supplies MPMU_XOUT to U8100.
12. The 32.768 kHz SoC clock becomes available
[diagram] U8100 provides PMU_CLK32K_SOC from its SLEEP_32K output to the M2 SoC U0600.
Stage
D — Power-on request and SoC / SSD rails13. A power-on request is received
[diagram] The active-low PMU_ONOFF_L signal is asserted, normally by pressing the power button.
The diagram also shows IPD_LID_OPEN_1V8 as an input to the main PMU, although it is not assigned a separate sequencestep number.
14. The PMUs enable the main SoC and SSD rails
[diagram] U8100 and U7700 enable the switched AWAKE, S1 and S2 rails required by the M2 SoC and the onboard NAND storage.
Main SoC-related rails shown in the diagram:rails:
PPVDD_AWAKE_PCPUPPVDD_AWAKE_GPUPPVDD_S1_SOCPP1V8_S2PPVDD_S2SW_VDD2HPPVDD_AWAKE_CPU_SRAMPPVDD_S1_DCSPPVDD_AWAKE_ECPUPP1V25_S2PP1V8_AWAKEPP1V25_AWAKE_IOPP0V779_S1_SRAMPPVDD_S1_DISPPPVDD_S1_VDDQLPP0V88_S1PP1V12_S2SW_AMPH
NAND/SSD-relatedNAND / SSD rails:
PP2V58_AWAKE_NAND_VCCPP1V25_AWAKE_NAND_VCCQPP0V88_AWAKE_NAND_VDD
The diagram assigns all these rails to
stagestep 14. It does not establish their exact internal order. Order and timing still have to be captured on a healthy board.
Stage
E — SoC start and firmware15. The M2 24 MHz reference clock starts
[diagram] Crystal Y0714 provides the 24 MHz reference clock for the M2 SoC.
16. SoC reset is released
[diagram] The main PMU releases PMU_RESET_L, connected to the SoC's COLD_RESET* input.
Because the signal is active-low, “released”"released" normally means that it transitionsgoes high.
17. The SoC bootfetches ROMits islow-level accessedfirmware
[diagram] The M2 SoC communicates with SOCROM U1900 (25S64) over SPI:
SPI_SOCROM_CS_LSPI_SOCROM_CLK_RSPI_SOCROM_MOSI_RSPI_SOCROM_MISO
[inferred]
U1900 is an external SPI NOR flash that holds low-level firmware.
18. Firmware initialization and hardware self-test begin
[diagram]
- Complete internal SoC initialization.
- Verify RAM.
- Verify devices on the SPMI and I²C buses.
- Verify NAND storage and read its low-level data.
- Verify the configuration/logic EEPROM.
- Verify the trackpad and fingerprint sensor.
Communication shown during this stage includes:stage:
SPMI_NUB_MPMU_CLKSPMI_NUB_MPMU_DATASPMI_NUB_SPMU_CLKSPMI_NUB_SPMU_DATAI2C_SEEPROM_SCLI2C_SEEPROM_SDA- NAND SPI and PCIe connections
Stage
F — USB-C controller handover, 20 V and buck modeOrdering note
[inferred]: The diagram lists USB Power Delivery negotiation to 20 V (step 21) after the SoC firmware stage. It is not yet known whether this reflects real timing or only the layout of the diagram. Steps 1 and 20 both concern the CC1 path, and the negotiation is carried out by the USB-C controllerUF400, so it may well happen shortly after attach, independent of steps 15–18.Bench observation, faulty A2779 in a reset loop
[measured]: 20 V is negotiated in every cycle shortly before the reset. Whether the SoC reaches step 18 in each cycle is not yet known. A scope capture ofPMU_RESET_LagainstPPVBUS_USBC0would answer this. Record the real order here once captured on a healthy board.
19. USB-C controller communication is established
[diagram] The system communicates with UF400 through:
I2C_SMC_UPC_SDAI2C_SMC_UPC_SCLUPC_SMC_I2C_INT_L
20. The USB-C CC1 connection is processed
[diagram] The USBC0_CC1 signal reaches the C_CC1 input of UF400, allowing the USB-C controller to identify and communicate with the connected power adapter.
21. USB Power Delivery raises VBUS to 20 V
[diagram] After successful USB-PD negotiation:
PPVBUS_USBC0rises from approximately 5 V to 20 V.PPHV_INT0_AONSWalso rises to approximately 20 V.- The higher voltage reaches
PPDCIN_USBC_AON.
22. The charger detects the negotiated adapter voltage
[diagram] U5200 senses the elevated input through AUX_DET.
23. The charger changes to buck mode
[diagram] Once the negotiated input voltage is above the required system-bus voltage, U5200 changes from boost operation to buck operation.
24. The 13 V bus is maintained in buck mode
[diagram] U5200 steps the approximately 20 V USB-C input down to maintain:
PPBUS_AON at approximately 13 The same system-bus node can also receive power from the battery through Q5265 and PPVBAT_AON.
Reference measurements (to fill in from a healthy board)
PPVBUS_USBC0
after attach, before PD
5.0V
(+-5%)
PPVBUS_USBC0
after PD
20.0V
(+-5%)
PPBUS_AON
5 V input, no battery
12.3V
PPBUS_AON
20 V input, no battery
PPBUS_AON
20 V input, battery connected
P3V8AON_PWR_EN
PP3V8_AON
3.8V
PP3V3_AON
3.3V
PMU_CLK32K_SOC
32kHz
PMU_RESET_L
release relative to VBUS 20 V
Open points
PPHV_INT0_AONSW switch (step 4)?
Condition or threshold for CHGR_EN_MVR and P3V8AON_PWR_EN (step 8).
Which event starts S2 on a bare board without button press: PMU_ONOFF_L, the default state of IPD_LID_OPEN_1V8, or charger attach (step 13)?
Real order and timing of the stage D rails, captured on a healthy board.
PP1V8_AON_SPMU, PP1V5_LDOINT_SPMU, a 5 V boost (BSTLQ) and PP5V_S2 appear in forum documentation of an M2 13" board but not in this diagram's lists. Check whether the diagram omits them or they don't exist on this board family.
Provenance of the self-test list in step 18: diagram annotation or firmware behaviour?
Differences on 14" / 16" models: number of USB-C controllers, MagSafe path, additional rails.
Battery-path behaviour (PPVBAT_AON, Q5265) and its effect on PPBUS_AON.
Real timing of the PD negotiation relative to steps 15–18 (see ordering note in stage F).