File:Example device pictures.jpg and Charger stuck at 5V instead of 20V on MacBooks: Difference between pages
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
{{Explanatory Guide | |||
|Type=Circuit | |||
|Difficulty=2. Medium | |||
}} | |||
USB-C MacBooks get charged through their USB-C ports, using USB-C PD standard which allows to deliver high power through a USB-C connector by raising the voltage higher than the regular 5 volts we've been used to on legacy USB ports. This requires a handshake between the laptop and the charger through a dedicated data bus, so that the charger can tell the laptop what its capabilities are, and so the laptop can then request a higher voltage, if available. | |||
*PP3V3_G3H missing due to a short circuit on the input to PP3V3_G3H creation circuit | |||
*Corroded LDO capacitor for PP3V3_G3H around a CD3215. On boards with 4 ports, on right side of board, check under shielding by SSD under the right CD3215 for hidden corroded capacitor. | |||
*PP3V3_G3H missing due to PM_EN_P3V3_G3H missing due to bad ISL9239 | |||
*PP3V3_G3H missing due to CHGR_EN_MVR missing due to bad ISL9240. ISL9240 is not available for purchase. Donor would be required. Watch this troubleshooting video on similar 15" model (A1990) https://www.youtube.com/watch?v=HJ2jyo7pAmE | |||
*PPVIN_G3H_P3V3G3H missing due to a short to ground, check D6902 if PP3V3_G3H voltage drops lower than 3.4V after fixing PPVIN_G3H_P3V3G3H short | |||
*Bad CD3215 | |||
*Bad CD3215 ROM chip (U2890) | |||
*Corroded probe points on the data lines between ROM chip and CD3215 | |||
*Corroded resistors around ROM chip (U2890 or UB090) affecting communication between ROM chip and CD3215 | |||
*Corrupted T2 firmware (when applicable) | |||
If the issue is a bad CD3215, one way to get an idea, is to see which does not boot loop. When you plug the charger in with the USB-C current meter, it will turn on for 2-3 seconds, then turn off and turn on again. Whichever port doesn't boot loop usually has an associated CD3215 that is bad. Also, the bad CD3215 will occasionally get hotter than the rest. | |||
CD3215s are chips made by Texas Instruments specifically for Apple, and are likely custom versions of their TPS65986 chip. Texas Instruments do not sell them, so replacement chips must be taken off donor boards. | |||
There are multiple revisions of them, CD3215B, CD3215C, ... They are not compatible with each other, so make sure that you always replace a CD3215 with one from the same revision. | |||
Troubleshooting CD3215s: | |||
*Check presence of PP3V3_G3H, required to power the chip | |||
*Check presence of all 4 LDOs (3.3V, 1.8V, 2, 1.1V) | |||
*If an LDO is missing, check for short | |||
*If no short, and only the 1.1V LDO is missing, it can be because the CD3215 can't load its firmware. Typically this also makes that USB port to not bootloop. Two options: | |||
**It is the master CD3215, directly connected to the SPI ROM. In that case, check continuity of SPI bus signals, possibly look at them with a scope while applying power to the board | |||
**It is the slave CD3215, not directly connected to the SPI ROM. In that case, it will request firmware to the other CD3215 through UART port (UPC_XX_UART_TX and UPC_XX_UART_RX). In that case, it is possible that the other CD3215 is bad | |||
*If other LDOs are missing but no short, replace the CD3215 | |||
*Once all CD3215s have all LDOs up, then it's a matter of talking to the SMC. Check I2C bus signals for activity. | |||
*Can also be a dead / bad ISL9239 | |||
T2 firmware can also cause the machine to be stuck at 5V. It is however, important to rule out other possible causes for the issue before re-flashing T2 firmware. Typically machines that have corrupted T2 firmware will be stuck at 5V 0.0A and typically will have PPBUS present and PP3v3_S5 missing. PP5V_S5 will often be present. T2 firmware can be re-flashed via Apple Configurator 2, however this will erase data in most cases. Try a "soft" re-flash first by clicking Advanced Options > Revive Device in Apple Configurator 2. |
Revision as of 09:33, 27 October 2023
Charger stuck at 5V instead of 20V on MacBooks | |
---|---|
Type | Circuit |
Device(s) | |
Difficulty | ◉◉◌◌ Medium |
USB-C MacBooks get charged through their USB-C ports, using USB-C PD standard which allows to deliver high power through a USB-C connector by raising the voltage higher than the regular 5 volts we've been used to on legacy USB ports. This requires a handshake between the laptop and the charger through a dedicated data bus, so that the charger can tell the laptop what its capabilities are, and so the laptop can then request a higher voltage, if available.
- PP3V3_G3H missing due to a short circuit on the input to PP3V3_G3H creation circuit
- Corroded LDO capacitor for PP3V3_G3H around a CD3215. On boards with 4 ports, on right side of board, check under shielding by SSD under the right CD3215 for hidden corroded capacitor.
- PP3V3_G3H missing due to PM_EN_P3V3_G3H missing due to bad ISL9239
- PP3V3_G3H missing due to CHGR_EN_MVR missing due to bad ISL9240. ISL9240 is not available for purchase. Donor would be required. Watch this troubleshooting video on similar 15" model (A1990) https://www.youtube.com/watch?v=HJ2jyo7pAmE
- PPVIN_G3H_P3V3G3H missing due to a short to ground, check D6902 if PP3V3_G3H voltage drops lower than 3.4V after fixing PPVIN_G3H_P3V3G3H short
- Bad CD3215
- Bad CD3215 ROM chip (U2890)
- Corroded probe points on the data lines between ROM chip and CD3215
- Corroded resistors around ROM chip (U2890 or UB090) affecting communication between ROM chip and CD3215
- Corrupted T2 firmware (when applicable)
If the issue is a bad CD3215, one way to get an idea, is to see which does not boot loop. When you plug the charger in with the USB-C current meter, it will turn on for 2-3 seconds, then turn off and turn on again. Whichever port doesn't boot loop usually has an associated CD3215 that is bad. Also, the bad CD3215 will occasionally get hotter than the rest.
CD3215s are chips made by Texas Instruments specifically for Apple, and are likely custom versions of their TPS65986 chip. Texas Instruments do not sell them, so replacement chips must be taken off donor boards.
There are multiple revisions of them, CD3215B, CD3215C, ... They are not compatible with each other, so make sure that you always replace a CD3215 with one from the same revision.
Troubleshooting CD3215s:
- Check presence of PP3V3_G3H, required to power the chip
- Check presence of all 4 LDOs (3.3V, 1.8V, 2, 1.1V)
- If an LDO is missing, check for short
- If no short, and only the 1.1V LDO is missing, it can be because the CD3215 can't load its firmware. Typically this also makes that USB port to not bootloop. Two options:
- It is the master CD3215, directly connected to the SPI ROM. In that case, check continuity of SPI bus signals, possibly look at them with a scope while applying power to the board
- It is the slave CD3215, not directly connected to the SPI ROM. In that case, it will request firmware to the other CD3215 through UART port (UPC_XX_UART_TX and UPC_XX_UART_RX). In that case, it is possible that the other CD3215 is bad
- If other LDOs are missing but no short, replace the CD3215
- Once all CD3215s have all LDOs up, then it's a matter of talking to the SMC. Check I2C bus signals for activity.
- Can also be a dead / bad ISL9239
T2 firmware can also cause the machine to be stuck at 5V. It is however, important to rule out other possible causes for the issue before re-flashing T2 firmware. Typically machines that have corrupted T2 firmware will be stuck at 5V 0.0A and typically will have PPBUS present and PP3v3_S5 missing. PP5V_S5 will often be present. T2 firmware can be re-flashed via Apple Configurator 2, however this will erase data in most cases. Try a "soft" re-flash first by clicking Advanced Options > Revive Device in Apple Configurator 2.
File history
Click on a date/time to view the file as it appeared at that time.
Date/Time | Thumbnail | Dimensions | User | Comment | |
---|---|---|---|---|---|
current | 12:22, 22 October 2023 | 1,920 × 1,080 (299 KB) | ASRepairs (talk | contribs) |
You cannot overwrite this file.
File usage
More than 100 pages use this file. The following list shows the first 100 pages that use this file only. A full list is available.
- Alienware M18x R2
- Anycubic Kobra Max
- Anycubic Kossel Linear Plus
- Anycubic Photon S
- Aspire 5057g
- Aspire E5-571G
- Aspire E5-773G
- Aspire V3-772g
- Asus A75V/K75V
- Asus L406M
- Asus N550J
- Avatar Whoop VTX
- Chromebook R11
- Epson XP-215/217
- GTX 1060
- GTX 1070
- GTX 1070Ti
- GTX 1080
- GTX 1080Ti
- GTX 970
- Galaxy S10
- Galaxy S22 Ultra
- Galaxy Tab S3
- IPad 5
- IPad 6
- IPad 7
- IPad Air
- IPad Air 4
- IPad Pro 10.5
- IPad Pro 12.9 1st Gen
- IPad Pro 12.9 2nd Gen
- IPad Pro 12.9 3rd Gen
- IPad Pro 12.9 4th Gen
- IPad Pro 12.9 5th Gen
- IPad Pro 9.7
- IPhone 11 Pro
- IPhone 12
- IPhone 14
- IPhone 14 Pro
- IPhone 15 Pro
- IPhone 7
- IPhone 7 Plus
- IPhone 8
- IPhone 8 Plus
- IPhone SE 2020
- IdeaPad Yoga 13ALC6
- MacBook Air A1466
- MacBook Air A1932
- MacBook Air A2179
- MacBook Air A2337
- MacBook Pro A1502
- MacBook Pro A1706
- MacBook Pro A1707
- MacBook Pro A1708
- MacBook Pro A1989
- MacBook Pro A1990
- MacBook Pro A2141
- MacBook Pro A2159
- MacBook Pro A2289
- MacBook Pro A2338
- MacBook Pro A2442
- Nintendo 3DS
- P30 Pro
- Pixel 5a
- PlayStation 5
- Playstation 4
- Playstation 4 Pro
- Playstation 4 Slim
- RTX 2060
- RTX 2070
- RTX 2080
- RTX 2080Ti
- RTX 3060
- RTX 3060Ti
- RTX 3070
- RTX 3070Ti
- RTX 3080
- RTX 3080Ti
- RTX 3090
- RTX 3090Ti
- RX 460
- RX 470
- RX 480
- RX 560
- RX 570
- RX 580
- RX 590
- Samsung UE Series
- Sony Bravia KDL-40W2000
- Thinkpad T420
- Thinkpad T480
- Thinkpad T490
- Thinkpad W541
- Toshiba 4610-1NR
- TravelMate 270
- VivoBook F505/X505
- VivoBook S551LA
- VivoBook S551LB
- WH-1000XM3
- WH-1000XM4
View more links to this file.