Power Sequence
Power Sequence — MacBook Pro Apple Silicon (M-Series Pro / Max & Base)
Status:
workActiveinReferenceprogress./ Verified against A2338 (M2 13") & A2779 (M2 Pro 14", 820-02841).Scope:
StepsCovers1–24powercomedeliveryfromarchitecturetheforpower-sequenceApplediagramSiliconofMacBookstheA2338 MacBook(M1/M2/M3/M4 ProM2&(13")Max series).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 on those boards.
ThePower
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 pagePP3V8_AON.
Stages at a glanceGlance
| Stage | Steps |
|---|
PPVDD_AON_MAIN PPBUS_AON established
5.0 V / 0.00 A – 0.03 A
Stage B
8–9
Enable chain for PP3V8_AON Stage A — USB-C attach/ andMagSafe systemAttach bus& System Bus Generation
Steps & Signals
[diagram]USB-C
JE700) presentsUSBC0_CC1_CONN UF300USBC0_CC2_CONNor MagSafe 3 detects cable insertion.
[diagram]Charger
PPVBUS_USBC0.
USB-C Controller Auxiliary LDO Starts [diagram]CD3217 / ACE Port Controller (
UF400) generates local LDO PP3V3_UPC0_LDO. Powers local SPI ROM (UF260) for CD3217 configuration loading (SPI_UPC01_R_CS_L, CLK, MOSI, MISO).
VBUS Passes Ingress Filter to Charger [diagram]Passes input MOSFETs (
PPHV_INT0_AONSW), Fuse (FF200), and sense resistor (R5220) to form PPDCIN_USBC_AON.
Intersil / Renesas Charger IC Power Up [diagram]Charger IC (
U5200, e.g., ISL9240 / ISL9241 or Apple Custom PMU Charger) powered via VDDP / VDDA.
Charger Enters Boost Mode [diagram]Since VBUS is only 5V and battery may be depleted/disconnected, the Charger IC operates in Boost Mode to raise system voltage to ~12.0V–13.1V. System Main Rail Established (
PPVDD_AON_MAIN / PPBUS_AON) [diagram]PPVDD_AON_MAIN is generated. This is the 🔴 Stage A Failures & Troubleshooting
Symptom: 0.00 V / 0.00 A or stuck at 5.0 V / 0.00 A.
3.Common USB-CFaults:
FF200) or shorted input MOSFETs.
Short circuit on [diagram]UF400PPVDD_AON_MAIN (CD3217BPP3V3_UPC0_LDOUF26025Q80)SPI_UPC01_R_CS_LSPI_UPC01_R_CLKSPI_UPC01_R_MOSISPI_UPC01_R_MISO.
4.
[diagram]PPHV_INT0_AONSWFF200R5220PPDCIN_USBC_AON5. The charger controller becomes operational [diagram] Charger controller U5200 (ISL9240HI) receives its 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 enough to establish the system bus.
7. The system bus is established [diagram] PPBUS_AON rises to approximately 13 V while the charger is 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.88V VAlways-On always-onRail rail(PP3V8_AON)
Steps & Signals
[diagram]PPVDD_AON_MAIN reaches stable voltage threshold, triggering U5200VDD_MAIN_PWR_GOOD CHGR_EN_MVRPP3V8_AONU5340P3V8AON_PWR_EN9. The 3.8 V always-on rail startsStarts [diagram]
Multi-phase PMIC P3V8AON_PWR_ENenables/ U5700,Buck whichRegulator generates PP3V8_AON (~3.8V).
Note: PP3V8_AON is critical as it directly powers the primary System PMUs (PMU_TOP / PMU_MAIN).
🔴 Stage B Failures & Troubleshooting
Symptom: Stuck at 5.0 V / 0.01 A – 0.03 A.
Common Faults:
PP3V8_AON (Feeds multiple audio, wireless, and PMU circuits).
Blown inductor or damaged PMIC drive circuit on the 3.8V switching phases.
Stage C — PMU always-onAlways-On railsRails and& clocksSystem Clocks
Steps & Signals
[diagram]Primary PMU receiving
PP3V8_AON U8100U7700From U8100:
(GPIO & PMU Logic)PP1V8_AON_MPMUPP1V8_AONPP1V8_AONPP1V2_AON- /
PP3V3_S2_LDOPP0V8_AON PP1V2_AWAKE_PLL
PP1V2_AON_MPMUSecure Enclave RTC & Standby Cores)
PP3V3_AON PP0V855_S2SW_CIO(Sensors PP3V3_S2SW_SNS& PP1V2_S2_CIOBoot PP1V5_LDOINT_MPMUROMs)
From U7700:
PP1V2_AON_SPMU
PP0V72_S2_VDD_LOWMain PP0V8_S1_VDD_FIXEDCrystal Oscillator 11. The main PMU crystal oscillator startsStarts [diagram]
PMU Crystalactivates 24 Y84A1startsMHz oscillatingRTC and supplies MPMU_XOUT to U8100.
12. The/ 32.768 kHz SoC clock becomesoutput.
[diagram]Low-power
U8100clocks PMU_CLK32K_SOCSLEEP_32K🔴 Stage C Failures & Troubleshooting
Symptom: Stuck at 5.0 V / 0.03 A – 0.05 A.
Common Faults:
PP1V8_AON or PP0V8_AON (Often indicates dead SoC U0600Always-On block or shorted decoupling cap).
Dead 24MHz/32kHz Crystal.
Stage D — Power-onOn requestRequest and& SoCSSD / SSDAWAKE railsRails
Steps & Signals
[diagram]PMU
PMU_ONOFF_Lopen, IPD_LID_OPEN_1V814. The PMUs enable the main SoCinsertion and asserts PMU_SYS_ALIVE / AON_PWR_GOOD.
[diagram]PMUs
U8100turn U7700AWAKES1S2SoC-relatedpower rails:
PPVDD_AWAKE_PCPUPP2V5_NAND_AONPPVDD_AWAKE_GPUPP1V2_NAND- /
PPVDD_S1_SOC
PP1V8_S2PPVDD_S2SW_VDD2HPPVDD_AWAKE_CPU_SRAMPPVDD_S1_DCSPPVDD_AWAKE_ECPUPP1V25_S2PP1V8_AWAKEPP1V25_AWAKE_IOPP0V779_S1_SRAMPPVDD_S1_DISPPPVDD_S1_VDDQLPP0V88_S1PP1V12_S2SW_AMPHPP0V9_NAND
S2RAM & SOC Core Standby Rails startup (PP1V8_S2RAM, PPVDD_SOC_S1).
🔴 Stage D Failures & Troubleshooting
NANDSymptom: Board stuck in DFU Mode or 5.0 V / SSD0.05 rails:A - 0.10 A Boot Loop.
Common Faults:
- Short circuit on
or damaged NAND chip (Very common on M1/M2/M3 boards).PP2V58_AWAKE_NAND_VCCPP2V5_NAND_AON PP1V25_AWAKE_NAND_VCCQ
PP0V88_AWAKE_NAND_VDDApple Silicon Firmware / BridgeOS ➔ Requires DFU restore via Apple Configurator.
The diagram assigns all these rails to step 14. It does not establish their exact internal order. Order and timing still have to be captured on a healthy board.
Stage E — SoC startCore andExecution firmware& Firmware Boot
Steps & Signals
[diagram]SOC_RESET_L Y0714PMU_RESET_L16. SoC reset is releasedpulled high.
[diagram]Secondary
PMU_RESET_LCOLD_RESET*PPVDD_CPU_E PPVDD_CPU_P PPVDD_GPU 17. The SoC fetches its low-level firmwareExecution [diagram] The M2
SoC communicatesexecutes withinternal code, SOCROMROM U1900(25S64)reads overNOR SPI:
SPI_SOCROM_CS_Lverifies Secure Enclave signature, and initializes RAM.
SPI_SOCROM_CLK_RHandshake SPI_SOCROM_MOSI_Rto SPI_SOCROM_MISOUSB-C PD [inferred] The boot ROM itself is inside the SoC. U1900 is an external SPI NOR flash that holds low-level firmware.
18. Firmware initialization and hardware self-test beginSubsystem [diagram]
SoC software driver communicates with CD3217 / ACE port controllers over I2C/SPMI.
🔴 Stage E Failures & Troubleshooting
Symptom: Current rises to ~0.15 A – 0.30 A at 5V and shuts off, or loops.
Common Faults:
CompleteBlowninternalDrMOSSoC/initialization.Power Stage forPPVDD_CPU_PorPPVDD_GPU.VerifyRAMRAM./ LPDDR5 power rail fault (PP1V1_S2RAM).VerifyCorrupteddevicesNORon the SPMI and I²C buses.
Communication
SPMI_NUB_MPMU_CLKSPMI_NUB_MPMU_DATASPMI_NUB_SPMU_CLKSPMI_NUB_SPMU_DATAI2C_SEEPROM_SCLI2C_SEEPROM_SDAStage F — USB-C controllerPD handover,Negotiate 20(20V VSwitch) and& buckBuck modeMode
Steps
& Signals
OrderingSoCnote/ PMU Requests High Voltage[inferred]diagram]:
SystemThefirmwarediagramcommandslistsCD3217USB/ ACE controllers to negotiate 20V (or 28V via MagSafe 3). Power DeliverynegotiationNegotiationto[diagram]
CD321720exchangesVBMC(steppackets21)onafterCCthelineSoC 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 bywith the USB-CcontrollerCharger.UF400,VBUSsoRisesittomay 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 established20V [diagram]
USB-C TheCharger systemswitches communicatesoutput withfrom 5V UF400through:
I2C_SMC_UPC_SDA20V.
I2C_SMC_UPC_SCLCharger UPC_SMC_I2C_INT_LController Switches 20.to TheBuck USB-C CC1 connection is processedMode [diagram] The USBC0_CC1 signal reaches the C_CC1
Since input ofvoltage (20V) is now higher than (~12.5V), UF400PPVDD_AON_MAINallowingCharger theIC USB-C(U5200) controllerseamlessly switches from Boost Mode to identifyBuck andMode.
21. USB Power Delivery raises VBUS to 20 VEnabled [diagram]
Charger Afterenables successfulSMBus/I2C USB-PDbattery negotiation:
PPVBUS_USBC0if PPHV_INT0_AONSWFull PPDCIN_USBC_AON22. The charger detects the negotiated adapter voltageOutput [diagram]
Display backlight rails (), U5200PPVOUT_S0_BKLTsensesAudio, thePCIe, elevatedand inputThunderbolt throughperipherals AUX_DET.powered on. macOS boots.
🔴 Stage F Failures & Troubleshooting
Symptom: Board boots and works at 5V (slowly), but never switches to 20V, OR shuts off immediately upon 20V switch.
23.Common The charger changes to buck modeFaults: [diagram] Once the negotiated input voltage is above the required system-bus voltage, U5200 changes from boost to buck operation.
24. The bus is maintained in buck mode [diagram] U5200 steps the approximately 20 V USB-C input down to maintain PPBUS_AON at approximately 13 V. The same node can also receive power from the battery through Q5265 and PPVBAT_AON.
Reference measurements (to fill in from a healthy board)
PPVBUS_USBC0PPVBUS_USBC0PPBUS_AONPPBUS_AONPPBUS_AONP3V8AON_PWR_ENPP3V8_AONPP3V3_AONPMU_CLK32K_SOCPMU_RESET_LOpen points
WhatFaultyenablesCD3217the/ACEPPHV_INT0_AONSWswitchController(stepor4)?dirty CC line communication.ConditionShortor threshold forCHGR_EN_MVRandP3V8AON_PWR_EN(step 8).
PMU_ONOFF_LIPD_LID_OPEN_1V8PP1V8_AON_SPMUPP1V5_LDOINT_SPMUBSTLQPP5V_S2PPVBAT_AONQ5265PPBUS_AONQuick Diagnostic Flowchart for Repairs
[ Plug in USB-C Meter ]
│
├── 0.00V / 0.00A ► Check Fuse FF200, CD3217 LDO (PP3V3_UPC0_LDO), VBUS MOSFETs
│
├── 5.00V / 0.00A ► Check PPVDD_AON_MAIN (Short circuit?) & ISL9240 Charger IC
│
├── 5.00V / 0.03A ► Check PP38_AON, PP1V8_AON, PP0V8_AON (PMU Always-On)
│
├── 5.00V / 0.08A ► Check NAND Rails (PP2V5_NAND_AON). Plug into host Mac ➔ Check DFU Mode!
│
└── 20.0V / Dynamic ► Sequence Successful! If no display, check PPVOUT_S0_BKLT or Display Driver.