Skip to main content

Power Sequence

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

Status: Family-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: A2442/A2485 (M1 Pro/Max), A2779/A2780 (M2 Pro/Max), 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.

Important: This is a functional 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 for the board under test.

Evidence labels: [diagram] comes directly from a schematic or power-sequence diagram; [measured] is a working-board observation with the test conditions recorded; [inferred] is a functional interpretation and must not be treated as a guaranteed timing specification.

Safety and measurement rules

  • Use a common logic-board ground for ordinary DMM measurements.
  • Use a 10x high-impedance oscilloscope probe with a short ground spring for low-voltage logic signals.
  • Never attach the ground clip of an earth-referenced bench oscilloscope to a switching node, MOSFET source, bootstrap node, or other non-ground point. Use a suitable differential or isolated probe for charger and multiphase switch nodes.
  • Do not probe crystal pins with a normal high-capacitance probe. Prefer a buffered clock output or test point; otherwise use an active low-capacitance probe.
  • Do not probe PCIe differential pairs with a normal passive probe. For power-sequence diagnosis, check the related power rails, reference clock presence where safely accessible, and reset signal instead.
  • Low resistance on SoC, GPU, RAM, and other sub-1 V rails can be normal. Compare diode-mode or resistance readings with the same board family, polarity, temperature, and capacitor charge state.

Architecture at a glance

Stage Reference checkpoints Expected functional result Primary instrument
A 1-7 Adapter attach, initial VBUS, port-controller startup, charger startup, and establishment of PPBUS_AON USB-C power meter and DMM
B 8-9 P3V8AON_PWR_EN enable chain and stable PP3V8_AON DMM and oscilloscope
C 10-12 MPMU/SPMU always-on rails and the SoC low-frequency clock DMM and oscilloscope
D 13-14 Power-on request accepted; AWAKE, S1/S2, memory, and NAND rail groups begin sequencing Oscilloscope and DMM
E 15-18 SoC reference clock, reset release, SOCROM access, PMU communication, and early firmware self-test Oscilloscope or logic analyzer
F 19-24 Port-controller communication, higher-voltage PD contract, and stable buck-mode system bus USB-C/PD analyzer, DMM, and oscilloscope

The 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 - Adapter attach and always-on system bus

  1. Cable/adapter attachment is 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.
  2. Initial VBUS appears. [diagram]
    A USB-C source normally begins at approximately 5 V before a higher-voltage PD contract is negotiated.
  3. 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.
  4. 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.
  5. The charger controller becomes biased. [diagram]
    The charger IC receives its analog/digital bias and senses adapter, battery, and system-bus conditions.
  6. 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.
  7. 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

  • No initial VBUS: verify the adapter, cable, connector, CC path, and port-controller auxiliary supply before investigating downstream rails.
  • Initial VBUS present but absent after the ingress path: verify input switches, fuse/sense path, corrosion, and the charger-input net.
  • Charger input present but 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

  1. The 3.8 V regulator enable chain becomes valid. [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].
  2. 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

  1. MPMU and SPMU always-on outputs appear. [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.
  2. 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.
  3. 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

  • Check the PMU input rails before condemning a missing PMU output.
  • Check PMU crash/fault signals where available, such as 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

  1. A valid wake or power-on request is received. [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.
  2. 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

  • A missing power-on request is different from a PMU that receives the request but fails to sequence its outputs. Capture both the request and first missing rail.
  • If one NAND rail is missing, check its owning PMU channel, enable, inductor/output path, and resistance to ground before assuming failed NAND.
  • DFU visibility proves that part of the SoC, USB, clock, reset, and firmware path is alive; it does not by itself prove that all NAND or operating-system boot stages are healthy.

Stage E - SoC clock, reset release, and early firmware

  1. The SoC reference oscillator starts. [diagram]
    A reference design shows a separate 24.000 MHz oscillator. Confirm the frequency and test point for the actual board.
  2. SoC reset is released. [diagram]
    PMU_RESET_L or the board-equivalent active-low reset transitions high and releases the SoC COLD_RESET* input.
  3. 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.
  4. 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

  • Reference clock present but reset held low: diagnose PMU prerequisites, fault inputs, missing rail groups, and PMU communication.
  • Reset released but no SOCROM activity: confirm ROM power, chip select, clock, signal integrity, and the SoC-side prerequisites.
  • SOCROM activity followed by a repeating reset: capture the period and identify which rail, reset, or PMU fault changes first.

Stage F - PD negotiation and stable buck-mode operation

  1. The system communicates with the port controller. [diagram]
    The reference design shows I2C/interrupt communication between the system controller and USB-C port controller.
  2. The port controller processes CC/PD communication. [diagram]
    USB-C Power Delivery messaging occurs on the CC line. A proper PD analyzer is more informative than a simple voltage/current display.
  3. VBUS rises to the negotiated higher voltage. [diagram]
    Common USB-C operation is approximately 20 V. A 28 V EPR/MagSafe-capable result applies only to models, adapters, cables, and ports that support it; it is not a universal expectation.
  4. The charger detects the elevated input. [diagram]
    The adapter-detect path, shown as AUX_DET on a reference design, confirms that the higher input is available.
  5. The charger operates in buck mode. [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.
  6. 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

  • Initial 5 V present but no higher-voltage contract: check CC integrity, port-controller power/ROM, system-to-port-controller communication, adapter/cable capability, and firmware state.
  • Higher-voltage contract appears but the board resets: capture adapter VBUS, charger input, 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

  • ☐ Model and board number/revision:
  • ☐ SoC and RAM configuration:
  • ☐ NAND configuration:
  • ☐ Battery connected/disconnected and battery state of charge:
  • ☐ Display, keyboard/trackpad, fans, speakers, and other assemblies connected:
  • ☐ Adapter wattage, PD/EPR capability, cable type, and selected port:
  • ☐ Trigger used: adapter insertion, power button, lid open, DFU command, or other:
  • ☐ Board temperature and starting state:
  • ☐ Oscilloscope model, probe type, attenuation, bandwidth limit, sample rate, and trigger:
  • ☐ DMM model and measurement mode:

Powered checks

Done Stage Instrument Measure/verify Expected result on a working board Record actual result
☐ A USB-C power meter or PD analyzer Initial adapter contract Initial approximately 5 V contract; current is dynamic and test-condition dependent  
☐ A DMM VBUS at connector and both sides of the input protection/sense path No unexplained voltage loss across the path  
☐ A DMM Port-controller auxiliary LDO, such as PP3V3_UPC*_LDO Approximately 3.3 V and stable  
☐ A Oscilloscope or logic analyzer ACE/SPI ROM CS, CLK, MOSI, and MISO Boot-time transaction present; valid logic levels with no stuck line  
☐ A DMM Charger bias and input-detect rails Match the schematic values and remain stable  
☐ A DMM; oscilloscope for transients PPBUS_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 signal polarity  
☐ D Oscilloscope 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, PPBUS_AON, and PP3V8_AON during contract change No collapse or reset while VBUS changes; system rails remain regulated  
☐ F USB-C power meter Current profile from attach through boot and idle Record the complete profile; do not reduce it to a universal single current value  

Powered-off baseline checks

Disconnect the adapter and battery, discharge the board safely, and document the same meter polarity for every measurement.

Done Instrument Measure Record
☐ DMM resistance mode PPBUS_AON to ground Initial and settled resistance, polarity, temperature, and settling time
☐ DMM diode mode PPBUS_AON, PP3V8_AON, PMU AON rails, and NAND rails Forward/reverse polarity readings using the same meter and board state
☐ DMM resistance or diode mode Each low-voltage CPU/GPU/RAM rail Comparison value only; low readings are not automatically shorts

Quick 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 input present, PPBUS_AON missing/collapsing
|   +-- Check bus short/overload, charger bias, sense network, power stage, and battery path
|
+-- 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 first collapsing rail

Interpretation limits

  • A voltage being present does not prove that its ripple, startup ramp, sequencing, or current capability is correct.
  • Bus activity does not prove that the transmitted data or firmware contents are valid.
  • DFU or Recovery visibility does not prove NAND integrity or a complete operating-system boot.
  • A successful 20 V or 28 V contract does not prove that all SoC, display, storage, or peripheral stages completed.
  • Current draw alone is not a unique fault code. Always correlate it with rails, reset, clocks, and bus activity.

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

  • ☐ Unverified - claim currently has no adequate supporting record.
  • ☐ Diagram verified - confirmed directly in a schematic, boardview, or manufacturer document.
  • ☐ Measured once - observed on one known-working board with recorded conditions.
  • ☐ Cross-board verified - confirmed on multiple applicable board numbers or revisions.
  • ☐ Inferred but retained - useful interpretation, explicitly labeled and not presented as fact.
  • ☐ Reword or remove - evidence does not support the current wording.

Minimum evidence required for every claim

  • ☐ Exact Mac model, EMC/model identifier, board number, and PCB revision are recorded.
  • ☐ SoC variant, RAM capacity, and NAND configuration are recorded where relevant.
  • ☐ Source type is recorded: schematic, boardview, datasheet, oscilloscope capture, DMM measurement, USB-C/PD log, repair result, or firmware log.
  • ☐ A schematic claim includes the page/sheet, component designator, and exact net name.
  • ☐ A measured claim includes battery state, connected assemblies, adapter/cable, selected port, trigger event, board temperature, and instrument configuration.
  • ☐ An oscilloscope claim includes probe type, attenuation, bandwidth limit, sample rate, time base, trigger source, and ground/reference method.
  • ☐ A DMM claim includes meter model, measurement mode, polarity, and whether the board was powered or fully discharged.
  • ☐ The raw evidence is attached or linked instead of only recording the author's conclusion.
  • ☐ The claim states whether it applies to one board, one generation, or the complete Pro/Max family.
  • ☐ Conflicting evidence and known exceptions are recorded.

Claims requiring verification

ID Claim to audit Why it is not automatically proven Acceptable verification Editor decision
A01 Every supported model initially receives approximately 5 V before negotiating a higher-voltage contract. USB-C, MagSafe, EPR, battery-only startup, and already-negotiated reconnect behavior may differ. Capture PD logs and VBUS waveforms for each input method and supported generation from a fully off state. ☐ Verified ☐ Add exceptions ☐ Narrow to USB-C
A02 The CD3217/ACE controller always generates a local 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 boost mode to create a 12-13 V PPBUS_AON from 5 V. A diagram annotation establishes design intent for that board, but not every startup state or later charger implementation. Verify input/output voltage relationship, gate-drive/switch-node behavior with a differential probe, controller mode/status where readable, and battery conditions. ☐ Diagram verified ☐ Scope verified ☐ Keep inferred ☐ Add conditions
A04 PPBUS_AON is normally 12.0-13.1 V across the supported family. The nominal value can depend on battery stack, charger state, generation, load, and calibration. Measure multiple working boards under the same battery/adapter/load conditions and cite the schematic nominal value when available. ☐ Verified range: ______ ☐ Board-specific table required
B01 The universal enable path is CHGR_EN_MVR → delay/buffer → P3V8AON_PWR_EN. This path is verified on known designs but may change with charger or PMIC generation. Trace the enable path and logic polarity in each supported schematic; measure both sides of the buffer on a working board. ☐ Verified boards: ______ ☐ Add alternate path
B02 PP3V8_AON directly powers the primary MPMU/SPMU and specific audio/wireless circuits. Downstream loads and intermediate regulators vary; a net name alone does not prove every listed consumer. Use schematic net references or boardview connectivity to enumerate confirmed consumers by board. ☐ Consumer list verified ☐ Remove unverified consumers
B03 Missing PP3V8_AON with enable present implicates the RAA225501 regulator. The fault can also be input/bias loss, a failed external MOSFET, current-sense fault, output short, open inductor/trace, or configuration mismatch. Require input, bias, enable, fault, phase activity, resistance, and output-path checks before naming the controller. ☐ Diagnostic wording is non-exclusive ☐ Rewrite
C01 Generic names such as PP1V2_AON or PP0V8_AON accurately represent every board's PMU outputs. Some boards divide these domains between MPMU/SPMU or use more specific names and different nominal voltages. Create a per-board AON/S2 rail table copied from the applicable schematic. ☐ Table added ☐ Generic names marked as examples
C02 The PMU crystal in the early stage is 24 MHz. The reference drawing separates the PMU low-frequency oscillator from the later SoC 24 MHz reference clock. Read the crystal value/BOM and measure a buffered output. Do not infer frequency from component placement. ☐ Correct frequency documented ☐ 24 MHz claim removed
C03 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 failed NAND or DFU state. Current is affected by battery, port, adapter, connected assemblies, temperature, firmware state, and many unrelated faults. Record complete current/time profiles from multiple known-good and failed boards, then correlate with confirmed rails, reset, DFU visibility, and final repair result. ☐ Evidence set attached ☐ Reword as weak clue ☐ Remove
E01 The SoC reference clock is universally 24.000 MHz and starts at the same point. Clock source, frequency, enable ownership, and accessibility can change. Confirm BOM/schematic value and capture a safe buffered clock point for each generation. ☐ Verified boards: ______ ☐ State as reference example
E02 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 for every captured reference board.

Record ID   Date  
Model   Board number/revision  
SoC/RAM   NAND configuration  
Battery state   Connected assemblies  
Adapter/cable/port   Startup trigger  
Ambient/board temperature   Firmware/macOS state  
Instrument and probe setup  
Raw captures/attachments  
Claims verified  
Exceptions/conflicts found  
Reviewer   Second reviewer  

Publication gate

  • ☐ Every [diagram] statement has an exact board, page/sheet, component, and net reference.
  • ☐ Every [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 has been changed to “possible fault.”
  • ☐ Correlation is not presented as causation.
  • ☐ No bus activity is described as proof of valid data without decoding or corroborating evidence.
  • ☐ Destructive or data-erasing actions include prerequisites and an explicit warning.
  • ☐ At least one second reviewer has checked high-impact diagnostic statements.
  • ☐ The page revision history summarizes which claims changed and why.