Power Sequence
Power Sequence —- MacBook Pro Apple Silicon (M-Series Pro / MaxMax)
Status:
ActiveFamily-level repair reference.Primary scope: MacBook Pro 14-inch and 16-inch logic boards introduced with M1 Pro/Max and their later Pro/Max successors.
Reference
/designs:VerifiedA2442/A2485against(M1A2338Pro/Max), A2779/A2780 (M213") & A2779 (M2 Pro 14"Pro/Max),820-02841).and later related designs. A2337/A2338 diagrams are useful early Apple-silicon references, but their exact rail names and checkpoint numbering must not be assumed to apply unchanged to Pro/Max boards.
Scope:Important:CoversThispowerisdeliveryaarchitecturefunctional sequence, not a time-scaled waveform. Rail names, controller designators, voltages, phase counts, port topology, NAND configuration, and the order of closely grouped rails vary by board number and revision. Always confirm against the schematic or boardview forAppletheSiliconboardMacBooksunder(M1/M2/M3/M4test.Pro & Max series).
SourceEvidence Tags:labels: [diagram] Schematiccomes Power-Sequencedirectly Diagramfrom ·a schematic or power-sequence diagram; [measured] Benchis Measurementa ·working-board observation with the test conditions recorded; [inferred] Inferredis /a Logicfunctional Flow.interpretation and must not be treated as a guaranteed timing specification.
PowerSafety Stagesand measurement rules
Architecture at a Glanceglance
| Stage | |||
|---|---|---|---|
PPBUS_AON
USB-C PPVDD_AON_MAINPPBUS_AONP3V8AON_PWR_EN enable chain PP3V8_AONThe checkpoint numbers are retained as a practical reference to the commonly circulated Apple-silicon sequence diagram. On Pro/Max boards, use the actual schematic net names and PMU sequence for the specific board rather than assuming a one-to-one match.
Stage A —- USB-CAdapter /attach MagSafeand Attachalways-on &system System Bus Generationbus
Steps & Signals
PhysicalCable/adapterConnectionattachmentDetectedis detected.[diagram]
One or more USB-C/ACE controllers detect the CC connection. MagSafe-equipped machines use an additional path, but the system still depends on the appropriate port-controller and charger communication.
[diagram]A USB-C source normally begins at approximately 5 V before a higher-voltage PD contract is negotiated. The port-controller auxiliary supply starts.
[diagram]The CD3217/ACE controller generates its local supply, commonly a rail such as
PP3V3_UPC*_LDO, and accesses its external ACE/SPI ROM.
Input power reaches the charger path. [diagram]VBUS passes through the applicable input switches, fuse/current-sense elements, and becomes the charger-input rail. Names and designators vary by port and board. The charger controller becomes biased.
[diagram]The charger IC receives its analog/digital bias and senses adapter, battery, and system-bus conditions. The charger establishes the system bus.
[diagram]During the initial low-voltage-input state, the bidirectional buck-boost charger can operate in the direction required to establish the always-on system bus.
PPBUS_AON becomes stable. [diagram]On verified M1 Pro/Max examples this bus is typically around 12 V; some related diagrams annotate approximately 13 V. Use the specified value for the actual board.
Stage A failure boundary
PPBUS_AON missing or collapsing: check for a short or overload on the bus, charger bias/enables, current-sense network, battery path, and charger power stage.
Stage B - 3.8 V always-on rail
[diagram]On designs using the familiar charger support chain,
CHGR_EN_MVR passes through the delay/buffer circuit and becomes P3V8AON_PWR_EN. Confirm the exact logic and designators on the target board (sometimes the Schmitt-Trigger is optimized away and CHGR_EN_MVR is directly attached to P3V8AON_PWR_EN [820-02841 "BATTERY CHARGER SUPPORT", pg 30].
The multiphase regulator generates PP3V8_AON. [diagram][802-02841 "POWER: 3V8 AON", pg 34,35]This rail supplies the MPMU/SPMU and other always-on loads. A stable enable with a missing output points toward the regulator, its bias/input rails, power stages, current-sense network, output short, or OTP/configuration issue.
Stage B failure boundary
PPBUS_AON present but P3V8AON_PWR_EN absent: work backward through the charger enable and delay/buffer chain.
Enable present but PP3V8_AON absent: check resistance to ground with power removed, then check the controller input/bias rails and switching activity with suitable probes. Also check the detailed PP3V8_AON page for in-depth details.
PP3V8_AON pulses or collapses: capture enable, output, and fault behavior on the same trigger instead of relying only on a DMM average.
Stage C - PMU always-on rails and low-frequency clock
[diagram]Typical families include
PP1V8_AON, PP1V2_AON, PP3V3_AON, early S2 rails, and board-specific PMU LDO outputs. Use exact schematic names; not every rail exists under the same name on every generation.
The PMU low-frequency oscillator operates. [diagram]The PMU oscillator/crystal starts. This must not be confused with the separate SoC 24 MHz reference clock that appears later.
PMU_CLK32K_SOC reaches the SoC. [diagram]The approximately 32.768 kHz clock allows the SoC always-on domain to continue sequencing.
Stage C failure boundary
PMU_CRASH_L.
Use a low-capacitance probe for the clock. A DMM frequency reading is not sufficient evidence of clock integrity.
Stage D - Power-on request and switched rail groups
[diagram]Depending on model and state, the initiating event can involve the power button, lid-open detection, charger attachment, or another PMU wake source. In the early reference diagram,
PMU_ONOFF_L is the explicitly numbered request signal.
The PMUs sequence AWAKE, S1/S2, memory, and NAND rails. [diagram]These rails form a group rather than one guaranteed simultaneous event. Pro/Max examples use board-specific SoC, GPU, CPU-SRAM, memory, I/O, and NAND rail names. NAND generations may use names such as
PP2V58_AWAKE_NAND_VCC/PP1V25_AWAKE_NAND_VCCQ/PP0V88_AWAKE_NAND_VDD or channel-specific rails such as PP0V9_NANDx/PP1V2_NANDx. Never substitute one naming family for another without checking the board schematic.
Stage D failure boundary
Stage E - SoC clock, reset release, and early firmware
[diagram]A reference design shows a separate 24.000 MHz oscillator. Confirm the frequency and test point for the actual board. SoC reset is released.
[diagram]PMU_RESET_L or the board-equivalent active-low reset transitions high and releases the SoC COLD_RESET* input.
The SoC accesses SOCROM/boot storage. [diagram]Look for activity on the applicable
SPI_SOCROM_* or equivalent external boot-ROM interface. Activity proves bus access, not valid contents.
Early firmware initialization and self-test proceed. [diagram]The reference sequence identifies internal initialization, RAM verification, SPMI/I2C device checks, NAND access, EEPROM/configuration checks, and later trackpad/Touch ID communication. The exact order and visibility vary by model and firmware.
Stage E failure boundary
Stage F - PD negotiation and stable buck-mode operation
[diagram]The reference design shows I2C/interrupt communication between the system controller and USB-C port controller. The port controller processes CC/PD communication.
[diagram]USB-C
JE700USBC0_CC1_CONNmessaging USBC0_CC2_CONNon [diagram]PPVBUS_USBC0[diagram]UF400PP3V3_UPC0_LDOAUX_DET[diagram]With adapter input above the required system-bus voltage, the charger regulates down to the always-on bus and manages the battery path as commanded.
PPBUS_AON remains stable in buck mode. [diagram]The system bus should remain near its board-specific nominal value while adapter VBUS is higher. Display, audio, PCIe, Thunderbolt, and macOS boot are later consumers and must not be treated as the definition of checkpoint 24.
Stage F failure boundary
PPBUS_AON, PP3V8_AON, and reset together to find the first collapsing node.
Do not assume that successful 20 V negotiation means the complete boot sequence succeeded.
Working-board measurement checklist
Purpose: Capture a reproducible baseline from a known-good board of the same board number, revision, memory/NAND configuration, and test state. Do not publish a value as universal unless it has been confirmed across multiple boards.
Record the test conditions first
Powered checks
PP3V3_UPC*_LDO
Approximately 3.3 V and stable
☐
A
Oscilloscope or logic analyzer
ACE/SPI ROM UF260SPI_UPC01_R_CS_LCS, CLK, MOSI, and MISOPPBUS_AON
Stable at the board-specific nominal value, commonly around 12-13 V on Pro/Max designs
☐
B
Oscilloscope
CHGR_EN_MVR and P3V8AON_PWR_EN, where used
Clean enable transition without repeated pulsing; delay matches the board design
☐
B
DMM and oscilloscope
PP3V8_AON
Approximately 3.8 V, stable; record startup ramp and ripple
☐
C
DMM
All schematic-listed MPMU/SPMU AON and early S2 rails
Each rail reaches its specified nominal value and remains stable
☐
C
Oscilloscope with low-capacitance probe
PMU_CLK32K_SOC
Approximately 32.768 kHz, continuous and with valid logic amplitude
☐
C
DMM or oscilloscope
PMU_CRASH_L or board-equivalent fault output
Inactive/healthy state according to PMU_ONOFF_L, lid-open input, or board-specific wake request
A valid request transition followed by rail sequencing
☐
D
DMM and oscilloscope
AWAKE, S1/S2, CPU/GPU, RAM, I/O, and NAND rail groups
Correct nominal voltages; no collapse or repeated restart
☐
E
Active or low-capacitance oscilloscope probe
SoC reference clock at a safe buffered point
Board-specified frequency, commonly 24 MHz in the reference sequence
☐
E
Oscilloscope
PMU_RESET_L/COLD_RESET*
Held low during prerequisites, then transitions high once without cycling
☐
E
Oscilloscope or logic analyzer
SPI_SOCROM_* or equivalent boot-ROM bus
Boot-time access on chip-select, clock, and data lines
☐
E
Oscilloscope or logic analyzer
SPMI and relevant I2C buses
Transactions present; no rail-clamped or permanently stuck clock/data line
☐
D/E
DMM and oscilloscope
NAND supplies and NAND reset
Correct board-specific voltages; reset releases after supplies stabilize
☐
F
USB-C/PD analyzer
PD negotiation and final contract
Higher-voltage contract appropriate to model and adapter, commonly 20 V; 28 V only where supported
☐
F
DMM and oscilloscope
Adapter input, [diagram]PPBUS_AONPPHV_INT0_AONSWFF200PP3V8_AON R5220Powered-off baseline checks
Disconnect the adapter and battery, discharge the board safely, and document the same meter polarity for every measurement.
PPBUS_AON to ground
Initial and settled resistance, polarity, temperature, and settling time
☐
DMM diode mode
PPBUS_AON, PPDCIN_USBC_AONPP3V8_AONQuick diagnostic flow
Adapter connected
|
+-- No initial VBUS
| +-- Check adapter, cable, connector, CC path, and port-controller auxiliary power
|
+-- Initial VBUS present, no port-controller LDO/ROM activity
| +-- Check controller bias, local LDO, reset, ROM power, and SPI bus
|
+-- Charger ICinput Powerpresent, UpPPBUS_AON [diagram]
Chargermissing/collapsing
IC| (U5200,+-- e.g.,Check ISL9240bus /short/overload, ISL9241charger orbias, Applesense Customnetwork, PMUpower Charger) powered via VDDP / VDDA.
Charger Enters Boost Mode [diagram]
Since VBUS is only 5Vstage, and battery maypath
be|
depleted/disconnected,+-- PPBUS_AON good, PP3V8_AON missing
| +-- Check CHGR_EN_MVR -> delay/buffer -> P3V8AON_PWR_EN -> multiphase regulator
|
+-- PP3V8_AON good, PMU AON/S2 rails or 32 kHz clock missing
| +-- Check MPMU/SPMU inputs, fault signals, oscillator, and exact missing output channel
|
+-- Rail groups good, reset never releases
| +-- Check wake request, PMU prerequisites, PMU communication, and fault inputs
|
+-- Reset releases, no SOCROM/firmware activity
| +-- Check reference clock, SOCROM power/bus, reset integrity, and early SoC prerequisites
|
+-- Early boot activity present, no higher-voltage PD contract
| +-- Check system-to-port-controller communication, CC/PD path, adapter/cable, and firmware state
|
+-- Higher-voltage contract appears, then board resets
+-- Trigger on reset and capture VBUS, charger input, PPBUS_AON, PP3V8_AON, and the Chargerfirst collapsing rail
Interpretation limits
Editor Verification Checklist
Purpose: This section tracks statements that are inferred, generalized across models, based on workshop experience, or not yet tied to primary evidence. It is an editorial checklist, not part of the electrical power sequence itself.
Rule: A plausible explanation is not the same as a verified fact. Until a claim passes the checks below, retain the
[inferred]label, narrow its wording, or remove it.
Status legend
Minimum evidence required for every claim
Claims requiring verification
PP3V3_UPC*_LDO and loads an external SPI ROM before the remaining sequence.
Controller generation, ROM topology, rail name, and port arrangement vary.
Confirm controller part number, local LDO, ROM device, supply, reset, and bus activity for each board family.
☐ Verified boards: ______ ☐ Generalize wording ☐ Remove exact IC
A03
The charger initially operates in PPVDD_AON_MAINPPBUS_AON[diagram]PPVDD_AON_MAINPPBUS_AON is CHGR_EN_MVR P3V8AON_PWR_EN.
🔴designs Stagebut Amay Failureschange &with Troubleshooting
Symptom: 0.00 V / 0.00 Acharger or stuckPMIC atgeneration.
Commonlogic Faults:
FF200PPVDD_AON_MAINPP3V3_UPC0_LDOUF260Stage
BB02
— 3.8V Always-On Rail (PP3V8_AON)
Steps & Signals
[diagram]PPVDD_AON_MAINVDD_MAIN_PWR_GOODPP3V8_AON[diagram]PP3V8_AONPP3V8_AON🔴loads Stageand Bintermediate Failuresregulators &vary; Troubleshooting
a Symptom:net Stuckname atalone 5.0does Vnot /prove 0.01every Alisted –consumer.
Commonnet Faults:
PP3V8_AON non-exclusive
Stage☐ CRewrite
Steps & Signals
[diagram]PP3V8_AONPP1V8_AONPP1V2_AONPP0V8_AONPP3V3_AON[diagram][diagram]🔴 Stage C Failures & Troubleshooting
Symptom: Stuck at 5.0 V / 0.03 A – 0.05 A.
Common Faults:
PP1V8_AON or PP0V8_AON PMU_CLK32K_SOC is continuously present at 32.768 kHz on all supported boards.
Clock gating, state, amplitude, and routing may differ.
Capture frequency, amplitude, duty cycle, and availability across off, attach, DFU, boot, sleep, and running states.
☐ Verified conditions: ______ ☐ Add state qualifier
D01
Power button, lid open, and charger insertion all produce the same effective PMU wake event.
These are different inputs and may enter different firmware or power states.
Capture the relevant PMU inputs and first rail/reset response for each trigger independently.
☐ Separate sequences documented ☐ Generalize wording
D02
The listed AWAKE/S1/S2, CPU/GPU, RAM, and NAND rails start together at one checkpoint.
A diagram may group outputs that actually have measurable internal ordering and dependencies.
Perform a multi-channel scope capture or repeatable single-channel captures using one common trigger. Record first-rise time and stable time for every rail.
☐ Timing captured ☐ Keep grouped without order claim
D03
NAND rail names and nominal values can be generalized across generations.
NAND count, vendor, interface, PMU ownership, and voltage domains vary.
Build a per-board NAND power table including controller/PMU channel, inductor, nominal voltage, enable, power-good/reset, and NAND devices supplied.
☐ Table added ☐ Examples clearly labeled
D04
A particular USB-C current plateau indicates PMU_RESET_L/COLD_RESET* transitions high only after all named rail groups are valid.
The PMU may monitor only selected rails and internal conditions; some rails may start after reset release.
Capture reset with each candidate prerequisite or identify the dependency explicitly in the schematic/PMU documentation.
☐ Dependency proven ☐ Reword to observed order
E03
SOCROM SPI activity proves successful Secure Enclave or boot-ROM verification.
Electrical activity only proves an attempted transaction, not valid content, authentication, or successful execution.
Correlate bus activity with reset behavior, DFU/recovery status, firmware logs, and a known-good ROM comparison where legally and technically appropriate.
☐ Wording limited to bus access ☐ Additional proof attached
E04
The SoC self-test order is RAM → SPMI/I2C → NAND → EEPROM → trackpad/Touch ID.
The reference annotation may be simplified and firmware versions can parallelize or reorder operations.
Use synchronized bus captures, reset/rail captures, firmware logs, or authoritative documentation. Otherwise call this a functional list, not a strict order.
☐ Strict order proven ☐ Reword as unordered checks
F01
The SoC or PMU directly requests the higher-voltage PD contract at checkpoint 19.
The I2C activity is visible, but the exact command source, message, and ownership are not proven by connectivity alone.
Decode the relevant system-to-port-controller transaction or cite controller/firmware documentation.
☐ Protocol decoded ☐ Keep as inferred
F02
Every supported board should negotiate 20 V, or 28 V when connected through MagSafe 3.
Contract depends on model, adapter, cable, battery, port, firmware, and USB-PD/EPR capability.
Record PD analyzer logs for every claimed model/input combination and list expected PDO/EPR behavior separately.
☐ Compatibility table added ☐ Remove universal expectation
F03
AUX_DET proves that the charger has accepted and is using the elevated adapter input.
A detect voltage may prove only threshold detection, not correct regulation, current capability, or selected power path.
Measure AUX_DET, charger input, system bus, battery current, and charger switching behavior together.
☐ Functional meaning proven ☐ Wording narrowed
F04
The charger switches cleanly from boost to buck mode at checkpoint 23.
The controller may use a transitional or mixed buck-boost state; the exact boundary is not established by VBUS alone.
Use a proper differential probe on the relevant switch nodes, capture inductor current if possible, or decode charger mode/status telemetry.
☐ Scope/telemetry verified ☐ Keep functional description only
F05
Successful higher-voltage negotiation means the full power sequence completed.
PD success can occur before NAND, display, peripheral, or operating-system boot succeeds.
Keep this claim rejected unless all later rails, reset, buses, display output, and OS state are independently verified.
☐ Claim removed ☐ Explicit limitation retained
T01
A specific USB-C current value uniquely identifies a failed stage.
Current draw is non-unique and strongly dependent on test configuration and time resolution.
Use current only as supporting evidence. Require at least one rail, clock, reset, bus, or thermal observation before assigning a stage.
☐ Current values labeled as observations ☐ Universal thresholds removed
T02
A component or fault is “common” or “very common.”
Workshop memory and online reports are subject to selection bias.
State the sample size, date range, board families, confirmed repairs, and denominator. Otherwise use “possible” instead of “common.”
☐ Dataset cited ☐ Wording changed to possible
T03
DFU restore is the correct action whenever firmware corruption is suspected.
Restore can erase data and cannot repair missing rails, unstable clocks, damaged NAND, or hardware resets.
Require stable prerequisite rails, clocks, reset, DFU detection, customer authorization/data-risk assessment, and a documented restore error/result.
☐ Preconditions added ☐ Data-loss warning added
Working-board verification record
Duplicate this block orfor shortedevery decouplingcaptured cap).reference board.
Publication gate
Dead☐24MHz/32kHz Crystal.
Stage D — Power-On Request & SSD / AWAKE Rails
Steps & Signals
[diagram][measured] statement links to raw data and includes complete test conditions.
☐ Every [inferred] statement is phrased as an interpretation, not a guaranteed event.
☐ Board-specific net names are not silently presented as universal family names.
☐ Voltage ranges state the tested boards and operating conditions.
☐ Current readings are observations, not standalone fault codes.
☐ “Common fault” language includes a dataset or PMU_SYS_ALIVEexplicit AON_PWR_GOOD[diagram]PP2V5_NAND_AONstatements.
PP1V2_NAND☐ PP0V9_NANDpage revision history summarizes which claims changed and why.
PP1V8_S2RAMPPVDD_SOC_S1🔴 Stage D Failures & Troubleshooting
Symptom: Board stuck in DFU Mode or 5.0 V / 0.05 A - 0.10 A Boot Loop.
Common Faults:
PP2V5_NAND_AONStage E — SoC Core Execution & Firmware Boot
Steps & Signals
[diagram]SOC_RESET_LPMU_RESET_L[diagram]PPVDD_CPU_EPPVDD_CPU_PPPVDD_GPU[diagram][diagram]🔴 Stage E Failures & Troubleshooting
Symptom: Current rises to ~0.15 A – 0.30 A at 5V and shuts off, or loops.
Common Faults:
PPVDD_CPU_PPPVDD_GPUPP1V1_S2RAMStage F — USB-C PD Negotiate (20V Switch) & Buck Mode
Steps & Signals
[diagram][diagram][diagram][diagram]PPVDD_AON_MAINU5200[diagram][diagram]PPVOUT_S0_BKLT🔴 Stage F Failures & Troubleshooting
Symptom: Board boots and works at 5V (slowly), but never switches to 20V, OR shuts off immediately upon 20V switch.
Common Faults:
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.