Skip to main content

Power Sequence

    Power Sequence — MacBook Pro Apple Silicon (M-Series Pro / Max & Base)

    Status: workActive inReference progress./ Verified against A2338 (M2 13") & A2779 (M2 Pro 14", 820-02841).

    Scope: StepsCovers 1–24power comedelivery fromarchitecture thefor power-sequenceApple diagramSilicon ofMacBooks the A2338 MacBook(M1/M2/M3/M4 Pro M2& (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.

    Source tags:Tags: [diagram] takenSchematic fromPower-Sequence the schematic power-sequence diagramDiagram · [measured] measuredBench on the benchMeasurement · [inferred] notInferred confirmed./ Logic Flow.

    The

    Power 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 glanceGlance

    Stage Steps WhatKey happensArchitecture & Rail State
    Typical USB-C Ammeter Behavior Stage A 1–7 USB-C attach,Attach, 55V VVBUS, input,Charger chargerBoost inMode, boostPPVDD_AON_MAIN mode,/ PPBUS_AON established 5.0 V / 0.00 A – 0.03 A Stage B 8–9 Enable chain for the 3.8 V always-on rail, PP3V8_AON startsBuck Regulator 5.0 V / 0.03 A – 0.05 A Stage C 10–12 PMU always-onAlways-On rails, mainMain PMU crystal,Crystal 32(24MHz/32kHz kHz clockclocks to theSoC) SoC5.0 V / 0.05 A – 0.08 A Stage D 13–14 Power-onOn request,Request, PMUs enablePMU AWAKE / S1 / NAND / S2 railsRails enabled 5.0 V / 0.08 A – 0.15 A (SoCor andStuck SSD)in DFU) Stage E 15–18 24 MHz clock, SoC resetReset released,Release, firmware,Secure self-testEnclave Boot, Internal ROM & NOR Firmware execution 5.0 V ➔ 20.0 V Transition Stage F 19–24 SMCSMC/PMU ↔ USB-CCD3217 controllerHandshake, communication,Negotiate PD20V/28V toPD, 20 V, chargerCharger switches to buckBuck modeMode 20.0 V / 0.50 A – 2.50 A+

    Stage A — USB-C attach/ andMagSafe systemAttach bus& System Bus Generation

    Steps & Signals

      1.Physical USB-CConnection connection is detectedDetected [diagram] The
      USB-C connector (JE700) presents the USBC0_CC1_CONN signal through/ UF300USBC0_CC2_CONN.

      or MagSafe 3 detects cable insertion.

      2. Initial 55V VVBUS USB-CInput input appearsAppears [diagram]
      Charger Theinputs charger supplies approximately 5 V5V on 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 defaultprimary USB-Csystem voltagepower beforebus Powerfeeding Deliveryall negotiation.secondary buck regulators.

      🔴 Stage A Failures & Troubleshooting

      Symptom: 0.00 V / 0.00 A or stuck at 5.0 V / 0.00 A.

      3.Common USB-CFaults:

      controller
      auxiliary
      supplyBlown startsInput Fuse (FF200) or shorted input MOSFETs. Short circuit on [diagram] USB-C controller UF400PPVDD_AON_MAIN (CD3217B)very generatescommon — cracked ceramic capacitor or dead ISL9240). Missing PP3V3_UPC0_LDO. Thisdue railto powersa thedead controller'sCD3217 externalIC or corrupt/missing SPI ROM (UF260 (25Q80), accessed through:
        SPI_UPC01_R_CS_L SPI_UPC01_R_CLK SPI_UPC01_R_MOSI SPI_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 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 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

          8.Enable TheSignal main voltage-regulator enable is generatedIssued [diagram]
          PPVDD_AON_MAIN reaches stable voltage threshold, triggering U5200VDD_MAIN_PWR_GOOD activatesor internal PMU enable lines. CHGR_EN_MVRPP3V8_AON. ThroughBuck logicRegulator device U5340, this produces P3V8AON_PWR_EN.

          9. The 3.8 V always-on rail startsStarts [diagram]
          Multi-phase P3V8AON_PWR_ENPMIC enables/ 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:

            Short circuit on 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

              10.Main ThePMUs PMUBoot always-on and standby LDO rails startUp [diagram]
              Primary PMU receiving PP3V8_AON suppliesoutputs thecore mainAON PMU U8100 and the secondary PMU U7700. The diagram marks the following rails as part of this stage.

              From U8100:

              rails:
              • PP1V8_AON_MPMUPP1V8_AON (GPIO & PMU Logic)
              • PP1V8_AONPP1V2_AON
              • / PP3V3_S2_LDOPP0V8_AON
              • PP1V2_AWAKE_PLL
              (SoC 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 Y84A124 startsMHz oscillatingRTC and supplies MPMU_XOUT to U8100.

                12. The/ 32.768 kHz SoC clock becomesoutput.

                availableAlways-On Clocks Routed to SoC [diagram]
                Low-power U8100clocks provides PMU_CLK32K_SOC from its SLEEP_32Koutputrouted to theSoC M2Always-On domain to enable power-state monitoring.

                🔴 Stage C Failures & Troubleshooting

                Symptom: Stuck at 5.0 V / 0.03 A – 0.05 A.

                Common Faults:

                  Short circuit on 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

                    13.Power-On ATrigger power-on/ requestAWAKE is receivedState [diagram]
                    PMU Thedetects active-lowlid PMU_ONOFF_Lopen, signalkeypress, isor asserted,charger 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 step number.

                    14. The PMUs enable the main SoCinsertion and asserts PMU_SYS_ALIVE / AON_PWR_GOOD.

                    SSD rails& S1/S2 Secondary Rails Enabled [diagram]
                    PMUs U8100turn and U7700 enable the switched AWAKE, S1 and S2rails required by the M2 SoC and the onboardon NAND storage.Flash

                    SoC-relatedpower rails:

                    • PPVDD_AWAKE_PCPUPP2V5_NAND_AON
                    • PPVDD_AWAKE_GPUPP1V2_NAND
                    • / PPVDD_S1_SOC
                    PP1V8_S2 PPVDD_S2SW_VDD2H PPVDD_AWAKE_CPU_SRAM PPVDD_S1_DCS PPVDD_AWAKE_ECPU PP1V25_S2 PP1V8_AWAKE PP1V25_AWAKE_IO PP0V779_S1_SRAM PPVDD_S1_DISP PPVDD_S1_VDDQL PP0V88_S1 PP1V12_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 PP2V58_AWAKE_NAND_VCCPP2V5_NAND_AON or damaged NAND chip (Very common on M1/M2/M3 boards).
                    • PP1V25_AWAKE_NAND_VCCQ
                    Corrupted 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

                      15.SoC TheReset M2 24 MHz reference clock startsRelease [diagram]
                      SOC_RESET_L Crystal/ Y0714PMU_RESET_L provides the 24 MHz reference clock for the M2 SoC.

                      16. SoC reset is releasedpulled high.

                      High-Power CPU / GPU Rails Switched On [diagram]
                      Secondary ThePMUs mainand PMUDrMOS releasesstages bring up:
                        PMU_RESET_L, connected to the SoC's COLD_RESET*PPVDD_CPU_E input.(Efficiency BecauseCores) thePPVDD_CPU_P signal(Performance isCores) active-low,PPVDD_GPU "released"(Graphics normallyEngine) means that itInternal goesBoot high.ROM

                        17. The SoC fetches its low-level firmwareExecution [diagram] The M2
                        SoC communicatesexecutes withinternal SOCROMROM U1900code, (25S64)reads overNOR SPI:

                        Flash
                          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:

                          • CompleteBlown internalDrMOS SoC/ initialization.Power Stage for PPVDD_CPU_P or PPVDD_GPU.
                          • VerifyRAM RAM./ LPDDR5 power rail fault (PP1V1_S2RAM).
                          • VerifyCorrupted devicesNOR 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.Flash.

                          Communication

                          shown during this stage:
                            SPMI_NUB_MPMU_CLK SPMI_NUB_MPMU_DATA SPMI_NUB_SPMU_CLK SPMI_NUB_SPMU_DATA I2C_SEEPROM_SCL I2C_SEEPROM_SDA NAND SPI and PCIe connections

                            Stage F — USB-C controllerPD handover,Negotiate 20(20V VSwitch) and& buckBuck modeMode

                            Steps

                            & Signals

                              OrderingSoC note/ PMU Requests High Voltage [inferred]diagram]:
                              System Thefirmware diagramcommands listsCD3217 USB/ ACE controllers to negotiate 20V (or 28V via MagSafe 3). Power Delivery negotiationNegotiation to[diagram]
                              CD3217 20exchanges VBMC (steppackets 21)on afterCC theline 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 bywith the USB-C controllerCharger. UF400,VBUS soRises itto 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 of PMU_RESET_L against PPVBUS_USBC0 would 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 UF4005V through:

                              to
                                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 UF400PPVDD_AON_MAIN (~12.5V), allowingCharger theIC USB-C(U5200) controllerseamlessly switches from Boost Mode to identifyBuck andMode.

                                communicateBattery withCharging the connected power adapter.

                                21. USB Power Delivery raises VBUS to 20 VEnabled [diagram]
                                Charger Afterenables successfulSMBus/I2C USB-PDbattery negotiation:

                                charging
                                  path PPVBUS_USBC0if risesbattery fromis approximately 5 V to 20 V.connected. PPHV_INT0_AONSWFull alsoSystem risesInitialization to& approximatelyDisplay 20 V. The higher voltage reaches PPDCIN_USBC_AON.

                                  22. The charger detects the negotiated adapter voltageOutput [diagram]
                                  Display backlight rails (U5200PPVOUT_S0_BKLT), sensesAudio, 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)

                                  Node / signal Condition Value Notes 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

                                  • WhatFaulty enablesCD3217 the/ PPHV_INT0_AONSWACE switchController (stepor 4)?dirty CC line communication.
                                  • ConditionShort or threshold for CHGR_EN_MVR and P3V8AON_PWR_EN (step 8).
                                  Which event starts S2circuit on a baresecondary board20V withouthigh-side buttonMOSFET press: PMU_ONOFF_L,in the default state of IPD_LID_OPEN_1V8,Charger or chargerBacklight attachcircuit (stepcauses 13)?immediate Realshutdown orderwhen and20V timing ofhits 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)board).

                                  Quick 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.