Skip to main content

Power Sequence

  1. VBUS attach: the CD3217s wake from their own LDOs and negotiate 5 V first, then 20 V once their firmware runs. PPBUS_AON should read around 12.3 V.
  2. PP3V8_AON: a buck from PPBUS_AON, then through the current-sense path into both PMUs.
    At startup only the first phase is active.
    Given the coils on phase 2&3 (`L5840`, `L5820`) are bigger than on phase 1 ('`L5800`), we can assume Phase 1 is the only active phase at startup or when in standby, and either P2/P3 take over when the device is on, or supplement P1.
    The buck controller is an Renesas `RAA225501C` (Apple P/N `353S02645`) - its data sheet is not available (.
  3. AON LDOs from MPMU and SPMU: 1V8_AON, 1V2_AON and 1V5_LDOINT per PMU, plus PP3V3_AON and a 5 V boost (BSTLQ). Charger current is ~30–40 mA at this stage.
  4. Wake event (button, lid, charger): the S2 rails come up, e.g. PP5V_S2, PP3V3_S2, PP1V8_S2, PP1V25_S2, PP0V88_S1, PP0V72_S2_VDD_LOW, PP1V2_AWAKE_PLL, PP0V855_S2SW_CIO, followed by the AWAKE/NAND rails.
  5. SoC starts, SPMI handshake with the PMUs, then S0 rails. This is the part I'm least sure of in detail.
The following information is for an A2338 MacBook Pro M2 (13 inch), and must be verified with some 14" or 16" Pro/Max variant.

    USB-C connection is detected

    The USB-C connector JE700 presents the USBC0_CC1_CONN signal through UF300.

    Initial 5 V USB-C input appears

    The charger supplies approximately 5 V on PPVBUS_USBC0. This is the default USB-C voltage before Power Delivery negotiation.

    USB-C controller auxiliary supply starts

    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_L SPI_UPC01_R_CLK SPI_UPC01_R_MOSI SPI_UPC01_R_MISO

      The initial 5 V reaches the charger input

      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.

      The charger controller becomes operational

      Charger controller U5200 (ISL9240HI) receives its required bias and sensing connections through VDDP, VDDA, CELLand PBUS.

      The charger initially operates in boost mode

      U5200, together with MOSFETs Q5230 and Q5240 and inductor L5230, operates as a boost converter.

      This raises the initial USB-C input sufficiently to establish the system bus.

      The 13 V system bus is established

      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 main voltage-regulator enable is generated

      U5200 activates CHGR_EN_MVR. Through logic device U5340, this produces P3V8AON_PWR_EN.

      The 3.8 V always-on rail starts

      P3V8AON_PWR_EN enables U5700 (RAA225501C).

      U5700 then generates:

        PP3V8_AON

        The PMU always-on and standby LDO rails start

        PP3V8_AON supplies the main PMU U8100 and secondary PMU U7700. The diagram marks the following rails as part of this stage.

        From U8100:

          PP1V8_AON_MPMU PP1V8_AON PP3V3_S2_LDO PP1V2_AWAKE_PLL PP1V2_AON_MPMU PP3V3_AON PP0V855_S2SW_CIO PP3V3_S2SW_SNS PP1V2_S2_CIO PP1V5_LDOINT_MPMU

          From U7700:

            PP1V2_AON_SPMU PP0V72_S2_VDD_LOW PP0V8_S1_VDD_FIXED
              The main PMU crystal oscillator starts

              Crystal Y84A1 starts oscillating and supplies MPMU_XOUT to U8100.

                The 32.768 kHz SoC clock becomes available

                U8100 provides PMU_CLK32K_SOC from its SLEEP_32K output to the M2 SoC U0600.

                  A power-on request is received

                  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 sequence number.

                    The PMUs enable the main SoC and SSD rails

                    U8100 and U7700 enable the switched AWAKE, S1 and S2 rails required by the M2 SoC and onboard NAND storage.

                      PPVDD_AWAKE_PCPU PPVDD_AWAKE_GPU 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_AMPH
                        PP2V58_AWAKE_NAND_VCC PP1V25_AWAKE_NAND_VCCQ PP0V88_AWAKE_NAND_VDD

                        The diagram assigns all these rails to stage 14. It does not establish their exact internal order.

                          The M2 24 MHz reference clock starts

                          Crystal Y0714 provides the 24 MHz reference clock for the M2 SoC.

                            SoC reset is released

                            The main PMU releases PMU_RESET_L, connected to the SoC's COLD_RESET* input.

                            Because the signal is active-low, “released” normally means that it transitions high.

                              The SoC boot ROM is accessed

                              The M2 SoC communicates with SOCROM U1900 (25S64) over SPI:

                                SPI_SOCROM_CS_L SPI_SOCROM_CLK_R SPI_SOCROM_MOSI_R SPI_SOCROM_MISO
                                  Firmware initialization and hardware self-test begin
                                    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:

                                      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
                                        USB-C controller communication is established

                                        The system communicates with UF400 through:

                                          I2C_SMC_UPC_SDA I2C_SMC_UPC_SCL UPC_SMC_I2C_INT_L
                                            The USB-C CC1 connection is processed

                                            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.

                                              USB Power Delivery raises VBUS to 20 V

                                              After successful USB-PD negotiation:

                                                PPVBUS_USBC0 rises from approximately 5 V to 20 V. PPHV_INT0_AONSW also rises to approximately 20 V. The higher voltage reaches PPDCIN_USBC_AON.
                                                  The charger detects the negotiated adapter voltage

                                                  U5200 senses the elevated input through AUX_DET.

                                                    The charger changes to buck mode

                                                    Once the negotiated input voltage is above the required system-bus voltage, U5200 changes from boost operation to buck operation.

                                                      The 13 V bus is maintained in buck mode

                                                      U5200 steps the approximately 20 V USB-C input down to maintain:

                                                        PPBUS_AON at approximately 13 V

                                                        The same system-bus node can also receive power from the battery through Q5265 and PPVBAT_AON.