Editing Syscon Error Codes
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
== Description == | == Description == | ||
[[SC EEPROM|Syscon memory]] | [[SC EEPROM|Syscon memory]] contains a table of size 0x100 bytes intended to store error codes, every error code is composed by 4 bytes + another 4 bytes for its timestamp, in total the table can store 32 errors. When the table is full of errors and a new error needs to be stored syscon deletes the oldest<br> | ||
== How to get the syscon error log == | == How to get the syscon error log == | ||
If the PS3 still boots to the XMB and is able to install and run | If the PS3 still boots up to the XMB and is able to install and run apps you can use programs like the ones mentioned at top of [[Platform_ID#Apps|Platform ID]] page<br> | ||
If the PS3 | If the PS3 doesnt boots is still posible to retrieve the syscon error log by connecting a PC to syscon UART port using a "USB to TTL UART adapter" and running the command '''errlog'''. There is also the command '''clearerrlog''' to empty the error table (handy to prevent confusions with old error codes that could be cummulated along the months/years and not related with the actual problem) | ||
== Error log format == | == Error log format == | ||
There are 2 error log formats that depends of the syscon type: for [[Mullion]], or for [[Sherwood]] | There are 2 error log formats that depends of the syscon type: for [[Mullion]], or for [[Sherwood]]<br> | ||
The error codes and the timestamps are stored in little endian (right to left)<br> | The error codes and the timestamps are stored in little endian (right to left)<br> | ||
The timestamps are in J2000 format (number of elapsed seconds since 2000/1/1 12:00:00). | The timestamps are in J2000 format (number of elapsed seconds since 2000/1/1 12:00:00). It can be converted as an standared unix epoch and then summed 30 years - 12 hours (or 946684800 seconds). See [https://stackoverflow.com/questions/35763357/conversion-from-unix-time-to-timestamp-starting-in-january-1-2000 1]<br> | ||
If the battery was empty or removed when the error was triggered | If the battery was empty or removed when the error was triggered the timestamp is recorded as FFFFFFFF<br> | ||
If the battery is replaced but the time is not configured | If the battery is replaced but the time is not configured under GameOS (either manualy or by network) it seems the errorlog stores timestamps starting with a date around 2005/12/31 00:00:00 (0x0B488680)<!-- this needs confirmation--><br> | ||
More info about | More info about errorlog timestamp formats and loops in the [[Talk:Syscon_Error_Codes | Talk page]]<br> | ||
*[https://www.epochconverter.com/ Unix epoch] starts counting at 1970/1/1 00:00:00 | *[https://www.epochconverter.com/ Unix epoch] starts counting at 1970/1/1 00:00:00 | ||
*[https://en.wikipedia.org/wiki/Julian_year_%28astronomy%29#Epochs J2000 epoch] starts counting at 2000/1/1 12:00:00 | *[https://en.wikipedia.org/wiki/Julian_year_%28astronomy%29#Epochs J2000 epoch] starts counting at 2000/1/1 12:00:00 | ||
Line 40: | Line 40: | ||
000037F0 E5 DE 38 16 DD D4 5C 16 C4 AC 6C 16 EA C7 6D 16 | 000037F0 E5 DE 38 16 DD D4 5C 16 C4 AC 6C 16 EA C7 6D 16 | ||
}} | }} | ||
*In the | *In the errorlog sample above: | ||
** | **Errorlog looped at least 1 time (1 errorcode FFFFFFFF) | ||
**Timestamps are valid, and the time was configured | **Timestamps are valid, and the time was configured | ||
**Contains errors: A080<span style="background:#bbbbff;"> 1 </span><span style="background:#ff8080;"> 001 </span>, A080</span><span style="background:#bbbbff;"> 1 </span><span style="background:#ff8080;"> 004 </span>, A009</span><span style="background:#bbbbff;"> 3 </span><span style="background:#ff8080;"> 004 </span> | **Contains errors: A080<span style="background:#bbbbff;"> 1 </span><span style="background:#ff8080;"> 001 </span>, A080</span><span style="background:#bbbbff;"> 1 </span><span style="background:#ff8080;"> 004 </span>, A009</span><span style="background:#bbbbff;"> 3 </span><span style="background:#ff8080;"> 004 </span> | ||
Line 131: | Line 131: | ||
== Error code format == | == Error code format == | ||
The error codes follows the format: '''<span style="background:#000000; color:#ffffff;"> A </span><span style="background:#909090; color:#ffffff;"> R </span><span style="background:#ffff80;"> ST </span><span style="background:#bbbbff;"> C </span><span style="background:#ff8080;"> ERR </span>''', where: | The error codes follows the format: '''<span style="background:#000000; color:#ffffff;"> A </span><span style="background:#909090; color:#ffffff;"> R </span><span style="background:#ffff80;"> ST </span><span style="background:#bbbbff;"> C </span><span style="background:#ff8080;"> ERR </span>''', where: | ||
*'''<span style="background:#000000; color:#ffffff;"> A </span>''' (Fixed) | |||
**'''A''' = This is always "A" | |||
*'''<span style="background:#909090; color:#ffffff;"> R </span>''' (Reserved) | |||
**'''0-E''' = Unknown | |||
**'''F''' = Frequent error (For example, Motherboard Damage/Breakdown, etc.) | |||
*'''<span style="background:#ffff80;"> ST </span>''' (Step Number) | |||
**'''00-7F''' = Step Number of the Power On Sequence (POS). This is the Power On Self Test (POST) process. If successful, the BOOT process begins, which loads the OS. | |||
**'''80''' = Static State (Power ON). The console completed the POST and was in a static state. The error happened when the PS3 was powered on. You can get an error with Step No. 80 if your error occurs in game. For example, 80 1002 errors can happen if your NEC/TOKINs are going bad. | |||
**'''90''' = Static State (Power OFF). The error happened when the PS3 was powering off. For example, if a problem causes the system to hang while shutting down the console will beep before powering off. An error with step no. 90 will be recorded in the errorlog. | |||
**'''A0''' = Immediately after SYSCON reset. A reset pulse is sent to the console's main chipset to coordinate and synchronize them. If an error occurs immediately after SYSCON reset, it means it occurred before anything else can happen. For example, if the CPU is completely dead it will not respond to the reset pulse and an error will be generated immediately after reset. | |||
*'''<span style="background:#bbbbff;"> C </span>''' (Category) | |||
**'''1''' = System Error | |||
**'''2''' = Fatal Error | |||
**'''3''' = Boot Error | |||
**'''4''' = Data Error | |||
*'''<span style="background:#ff8080;"> ERR </span>''' (Error) | |||
**Any number in hex | |||
---- | ---- | ||
Examples:<br> | |||
<span style="background:#000000; color:#ffffff;">A</span><span style="background:#909090; color:#ffffff;">0</span><span style="background:#ffff80;">80</span><span style="background:#bbbbff;">1</span><span style="background:#ff8080;">002</span> | <span style="background:#000000; color:#ffffff;">A</span><span style="background:#909090; color:#ffffff;">0</span><span style="background:#ffff80;">80</span><span style="background:#bbbbff;">1</span><span style="background:#ff8080;">002</span> | ||
*System Error 002 ([[RSX]] VRAM Power Fail) which occurred while the System was successfully powered On. | *System Error 002 ([[RSX]] VRAM Power Fail) which occurred while the System was successfully powered On. | ||
*1002 errors are known to be caused by | *1002 errors are known to be caused by bad NEC/TOKINs, but may not be the only cause. See Error Code section below for more details. | ||
<span style="background:#000000; color:#ffffff;">A</span><span style="background:#909090; color:#ffffff;">0</span><span style="background:#ffff80;">40</span><span style="background:#bbbbff;">3</span><span style="background:#ff8080;">034</span> | <span style="background:#000000; color:#ffffff;">A</span><span style="background:#909090; color:#ffffff;">0</span><span style="background:#ffff80;">40</span><span style="background:#bbbbff;">3</span><span style="background:#ff8080;">034</span> | ||
*Fatal Booting Error 034 ([[RSX]]/[[CELL BE|CELL]] Communication Error) which occurred at step no. 40 | *Fatal Booting Error 034 ([[RSX]]/[[CELL BE|CELL]] Communication Error) which occurred at step no. 40, before the Power On Sequence completed. | ||
*3034 errors are | *3034 errors are known to be caused by BGA Defects (among other issues). See Error Code section below for more details. | ||
While the Reserved Area and Step Number can be useful to figure out when the error occurred and how frequent it is, the last four numbers are the most important for figuring out what the error means. So the following Error Code section will only list the last 4 numbers (category + error). | |||
== Error codes == | == Error codes == | ||
Line 207: | Line 170: | ||
**Other nearby components of the power block | **Other nearby components of the power block | ||
Speculation:<br> | |||
1001 errors happen when the system encounters an unexpected shutdown. They often occur in testing, when the console is turned on/off a lot, instead of graceful shutdown. They have been associated with other errors, but there doesn't appear to be any single cause. | |||
1001 errors | |||
The hypothesis that this error is associated with insufficient Filtering on CPU's core voltage (VDDC) has not been confirmed. There is a range of voltage ripple/noise that "should" cause errors before it gets so bad it causes a [[CELL BE|CELL]] VDDC Power Failure (3003). There are numerous SMD components involved in filtering, but the main concern are the NEC/TOKIN Proadlizers (capacitors). 1002 errors are the fingerprint of bad tokins on the GPU, but 1001 has not been shown to have the same association with the CPU's filter. However, a connection is strongly suspected. | |||
==== 1002 (Power RSX) ==== | ==== 1002 (Power RSX) ==== | ||
Line 221: | Line 181: | ||
**Other nearby components of the power block | **Other nearby components of the power block | ||
This error | This error has been associated with insufficient Filtering on '''RSX_VDDC''' power line. There is a range of voltage ripple/noise that will cause this error before it gets so bad it causes an RSX_VDDC Power Failure (3004). YLOD's causing 1002's range in duration from 2 seconds to only occurring during intense games. <br> | ||
<br> | <br> | ||
There are | There are numerous SMD components involved in filtering, but the main concern are the NEC/TOKIN Proadlizers (capacitors). 1002 errors are the fingerprint of bad tokins. | ||
==== 1004 (Power AC/DC) ==== | ==== 1004 (Power AC/DC) ==== | ||
*Components Involved: | *Components Involved: | ||
**[[Power Supply]] | **[[Power Supply]] | ||
==== 1103 (Thermal | ==== 1103 (Thermal) ==== | ||
*Components Involved: | *Components Involved: | ||
** | **See: [[Thermal]] | ||
==== 1200 (Thermal CELL) ==== | ==== 1200 (Thermal CELL) ==== | ||
Line 261: | Line 207: | ||
**[[RSX]] | **[[RSX]] | ||
GPU Overheat. This is the same as error 1200 above, except it's for the GPU. The same repair steps apply, except it's Temperature Monitor Chip is IC2101 | GPU Overheat. This is the same as error 1200 above, except it's for the GPU. The same repair steps apply, except it's Temperature Monitor Chip is IC2101. | ||
==== 1203 (Thermal CELL VR) ==== | ==== 1203 (Thermal CELL VR) ==== | ||
Line 268: | Line 214: | ||
**[[Thermal#Temperature_Monitors|Temperature Monitors]] | **[[Thermal#Temperature_Monitors|Temperature Monitors]] | ||
Some PS3 motherboards ([[TMU-520]], [[COK-001]], [[COK-002]]), have a temperature monitor located somewhere in the CELL power block. The other retail PS3 motherboard models doesnt meassures the temperature of the CELL VR | |||
Some PS3 motherboards ([[TMU-520]], [[COK-001]], [[COK-002]]), have a temperature monitor located somewhere in the CELL power block. The other retail PS3 motherboard models | |||
All the PS3 temperature monitor chips have a internal thermal sensor integrated + 2 pins for an optional external sensor. The temperature monitors for CELL and RSX are configured to use the external sensor, but this one for CELL VR probably uses the internal | All the PS3 temperature monitor chips have a internal thermal sensor integrated + 2 pins for an optional external sensor. The temperature monitors for CELL and RSX are configured to use the external sensor, but this one for CELL VR probably uses the internal | ||
Line 285: | Line 229: | ||
This error is specific for [[COK-001]]/[[CXD2953AGB]] (with full PS2 hardware compatibility, EE+GS) or [[COK-002]]/[[CXD2972GB]] (with partial PS2 hardware compatibility, GS only) | This error is specific for [[COK-001]]/[[CXD2953AGB]] (with full PS2 hardware compatibility, EE+GS) or [[COK-002]]/[[CXD2972GB]] (with partial PS2 hardware compatibility, GS only) | ||
==== 1301 | ==== 1301 ==== | ||
[[CELL BE|CELL]] PLL | |||
==== 14FF ==== | |||
Check stop | |||
==== 1601 ==== | |||
BE Livelock Detection | |||
==== 1601 | |||
Speculation: | Speculation: | ||
If a YLOD turns into a GLOD after reball/reflow then 1601 (with or without 1701) could mean the [[RSX]] RAM was damaged. This is a loose association based on a few user reports. | If a YLOD turns into a GLOD after reball/reflow then 1601 (with or without 1701) could mean the [[RSX]] RAM was damaged. This is a loose association based on a few user reports. | ||
==== 1701 | ==== 1701 ==== | ||
[[CELL BE|CELL]] attention. | |||
A user get this error code with a damaged hard drive. He was transfering some games via FTP, and his console turned off with Ylod. When he tried to turn on again, he get a Glod. Problem was fixed just changing the HDD. | |||
==== 1802 ==== | |||
[[RSX]] init | |||
==== 1802 | |||
==== 1900 (RTC Voltage) ==== | ==== 1900 (RTC Voltage) ==== | ||
Line 362: | Line 256: | ||
==== 1902 (RTC Access) ==== | ==== 1902 (RTC Access) ==== | ||
RTC access | RTC access | ||
---- | ---- | ||
Line 382: | Line 261: | ||
=== Fatal Errors === | === Fatal Errors === | ||
---- | ---- | ||
*This | *This error codes seems to be repeated up to 3 times for 3 special cases, as example, errors 2'''0'''03, 2'''1'''03, 2'''2'''03 are related to southbridge, the only thing that changes in the error code is the second digit (located inmediatly after the category). If at some point we find what means that digit we can join the wiki page sections together (with titles: "2001 & 2101", "2002 & 2102", "2003 & 2103", etc...) | ||
==== 2001 (CELL) ==== | ==== 2001 (CELL) ==== | ||
Line 405: | Line 283: | ||
==== 2013 (Clock CELL, RSX, South Bridge) ==== | ==== 2013 (Clock CELL, RSX, South Bridge) ==== | ||
Clock Generator Error (IC5004) | Clock Generator Error (IC5004) | ||
==== 2020 (HDMI) ==== | ==== 2020 (HDMI) ==== | ||
HDMI Error (IC2502) | HDMI Error (IC2502) | ||
==== 2022 (DVE) ==== | ==== 2022 (DVE) ==== | ||
DVE Error (IC2406, CXM4024R MultiAV controller for analog out) | DVE Error (IC2406, CXM4024R MultiAV controller for analog out) | ||
==== 2024 (AV) ==== | ==== 2024 (AV) ==== | ||
This error tends to cause a delayed Yellow Light Of Death (10s - 1min). Sometimes described as a Green Light Of Death (GLOD) or Red Light Of Death (RLOD). | This error tends to cause a delayed Yellow Light Of Death (10s - 1min). Sometimes described as a Green Light Of Death (GLOD) or Red Light Of Death (RLOD). | ||
2124 and 2024 errors | 2124 and 2024 errors have been fixed by replacing both the AV and HDMI encoders. One user reported 2024/2124 errors resolved by replacing the HDMI encoder. Another removed the HDMI encoder and tested the console without it. That console primarily filled the errorlog with 2124 errors, but a few 2024's as well. So it is unclear if 2124 is specific to the HDMI Encoder or AV Encoder. It seems it could be either. | ||
==== 2030 (Thermal Sensor, CELL) ==== | ==== 2030 (Thermal Sensor, CELL) ==== | ||
Line 446: | Line 299: | ||
**[[CELL BE|CELL]] | **[[CELL BE|CELL]] | ||
**[[CELL BE|CELL]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC1101 on [[COK-001]]) | **[[CELL BE|CELL]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC1101 on [[COK-001]]) | ||
Speculation: 2030-33 errors reported in case of dodgy PWR/EJT daughter board. | Speculation: 2030-33 errors reported in case of dodgy PWR/EJT daughter board. | ||
Line 455: | Line 306: | ||
**[[RSX]] | **[[RSX]] | ||
**[[RSX]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC2101 on [[COK-001]]) | **[[RSX]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC2101 on [[COK-001]]) | ||
==== 2033 (Thermal Sensor, South Bridge) ==== | ==== 2033 (Thermal Sensor, South Bridge) ==== | ||
Line 461: | Line 311: | ||
**[[South Bridge]] | **[[South Bridge]] | ||
**[[South Bridge]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC3101 on [[COK-001]]) | **[[South Bridge]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC3101 on [[COK-001]]) | ||
==== 2101 (CELL) ==== | ==== 2101 (CELL) ==== | ||
[[CELL BE|CELL]] (IC1001) | [[CELL BE|CELL]] (IC1001) | ||
==== 2102 (RSX) ==== | ==== 2102 (RSX) ==== | ||
[[RSX]] (IC2001) | [[RSX]] (IC2001) | ||
==== 2103 (South Bridge) ==== | ==== 2103 (South Bridge) ==== | ||
Line 491: | Line 329: | ||
This error has been resolved by a number of users who had a short on F6001. It is important to note that something usually causes that fuse to blow, like a short. So it's important to troubleshoot the board to find and repair the shorting component before replacing the fuse. Otherwise the new one will blow too. | This error has been resolved by a number of users who had a short on F6001. It is important to note that something usually causes that fuse to blow, like a short. So it's important to troubleshoot the board to find and repair the shorting component before replacing the fuse. Otherwise the new one will blow too. | ||
One user, who resolved this error on his C model PS3, noted "very short YLOD. Error code shows 2110[...]Some earlier code shows 1001 and 1002." The 1001 & 1002 errors he noted in the log before the 2110 appeared may have been a clue that C6019 | One user, who resolved this error on his C model PS3, noted "very short YLOD. Error code shows 2110[...]Some earlier code shows 1001 and 1002." The 1001 & 1002 errors he noted in the log before the 2110 appeared may have been a clue that C6019 was deteriorating. Further investigation is needed to confirm this hypothesis, however. In his case, C6019 was shorting and caused F6001 to blow. This short overloaded F6001 and cut power to many Subsystems, such as the HDD, USB ports, South bridge, CPU, GPU, etc. | ||
One particularly noteworthy component is IC6020, which supplys +3.3v_MK_Vdd to the clock generator (IC5001). When F6001 blows, a 02 2110 is generated. A step number of 02 is very early in the power on sequence (POS), which explains why 2110 is triggered instead of another error code. Since the clock generator is critical for timing, it is one of the first things the SYSCON checks during the POS. | One particularly noteworthy component is IC6020, which supplys +3.3v_MK_Vdd to the clock generator (IC5001). When F6001 blows, a 02 2110 is generated. A step number of 02 is very early in the power on sequence (POS), which explains why 2110 is triggered instead of another error code. Since the clock generator is critical for timing, it is one of the first things the SYSCON checks during the POS. | ||
Line 498: | Line 335: | ||
==== 2111 (Clock CELL) ==== | ==== 2111 (Clock CELL) ==== | ||
Clock Generator Error (IC5003) | Clock Generator Error (IC5003) | ||
==== 2112 (Clock CELL) ==== | ==== 2112 (Clock CELL) ==== | ||
Clock Generator Error (IC5002) | Clock Generator Error (IC5002) | ||
==== 2113 (Clock CELL, RSX, South Bridge) ==== | ==== 2113 (Clock CELL, RSX, South Bridge) ==== | ||
Clock Generator Error (IC5004) | Clock Generator Error (IC5004) | ||
==== 2120 (HDMI) ==== | |||
HDMI Error (IC2502) | |||
A0202120/A0213013 error combinations are common. They appear to be related to VDDIO. IC6301 is involved in the formation of +1.7V_MISC, which amonge other things provides input power to the DC-DC converters that output +1.2V_YC_RC_VDDIO, +1.5V_YC_RC_VDDA, +1.2V_SB_VDDC and +1.2V_SB_VDDR. Lack of voltage to these DC/DC converters downstream of IC6301 suggests F6302 has blown. A number of people have fixed these 2120/3013 errors by finding shorts at or near C6320 and replacing Fuse F6302. But there are many other SMD nearby that might cause these fuses to blow. So you will need to track the source of the short and fix it, or the fuse will just blow again. | |||
A bad thermistor (TH2501) has been reported to cause A0002120. | |||
A0802120 and A0902120 errors may be related to the actual HDMI transmitter (IC2502). Or they can be caused by BGA/Bump defects affecting VDDIO, on the RSX or CELL. BGA defects on the RSX VDDIO pads have been confirmed with a pressure test to have caused 2120 errors. | |||
==== 2122 (DVE) ==== | |||
====2122 (DVE)==== | |||
DVE Error (IC2406, CXM4024R MultiAV controller for analog out) | DVE Error (IC2406, CXM4024R MultiAV controller for analog out) | ||
====2124 (AV) ==== | ==== 2124 (AV) ==== | ||
This error tends to cause a delayed Yellow Light Of Death (10s - 1min). Sometimes described as a Green Light Of Death (GLOD) or Red Light Of Death (RLOD). | This error tends to cause a delayed Yellow Light Of Death (10s - 1min). Sometimes described as a Green Light Of Death (GLOD) or Red Light Of Death (RLOD). | ||
2124 and 2024 errors have been fixed by replacing both the AV and HDMI encoders. One user reported 2024/2124 errors resolved by replacing the HDMI encoder. Another removed the HDMI encoder and tested the console without it. That console primarily filled the errorlog with 2124 errors, but a few 2024's as well. So it is unclear if 2124 is specific to the HDMI Encoder or AV Encoder. It seems it could be either. | 2124 and 2024 errors have been fixed by replacing both the AV and HDMI encoders. One user reported 2024/2124 errors resolved by replacing the HDMI encoder. Another removed the HDMI encoder and tested the console without it. That console primarily filled the errorlog with 2124 errors, but a few 2024's as well. So it is unclear if 2124 is specific to the HDMI Encoder or AV Encoder. It seems it could be either. | ||
====2130 (Thermal Sensor, CELL)==== | ==== 2130 (Thermal Sensor, CELL) ==== | ||
*Components Involved: | *Components Involved: | ||
**[[CELL BE|CELL]] | **[[CELL BE|CELL]] | ||
** [[CELL BE|CELL]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC1101 on [[COK-001]]) | **[[CELL BE|CELL]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC1101 on [[COK-001]]) | ||
====2131 (Thermal Sensor, RSX)==== | ==== 2131 (Thermal Sensor, RSX) ==== | ||
*Components Involved: | *Components Involved: | ||
** [[RSX]] | **[[RSX]] | ||
**[[RSX]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC2101 on [[COK-001]]) | **[[RSX]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC2101 on [[COK-001]]) | ||
====2133 (Thermal Sensor, South Bridge)==== | ==== 2133 (Thermal Sensor, South Bridge) ==== | ||
*Components Involved: | *Components Involved: | ||
** [[South Bridge]] | **[[South Bridge]] | ||
**[[South Bridge]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC3101 on [[COK-001]]) | **[[South Bridge]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC3101 on [[COK-001]]) | ||
==== 2203 ([[South Bridge]]) | ==== 2203 (South Bridge) ==== | ||
[[South Bridge]] Error (IC3001) | |||
---- | ---- | ||
===Fatal Boot Errors=== | === Fatal Boot Errors === | ||
---- | ---- | ||
====3000==== | ==== 3000 ==== | ||
Power Failure | Power Failure | ||
====3001==== | ==== 3001 ==== | ||
12v Power Failure | 12v Power Failure | ||
Usually this caused by a bad Power Supply Unit (PSU). | Usually this caused by a bad Power Supply Unit (PSU). | ||
Alternatively, a failure on the 12v_main line can cause it. Check fuses, capacitors, resistors, and | Alternatively, a failure on the 12v_main line can cause it. Check fuses, capacitors, resistors, and IC's on the 12v line. Measure resistance of the large 2 prong 12v connector on the motherboard. It should read in the Kilo ohms range if there is sufficient separation. Otherwise you may have a short somewhere on the line. | ||
====3002==== | ==== 3002 ==== | ||
Power Failure | Power Failure | ||
====3003 | ==== 3003 ==== | ||
VDDC [[CELL BE|CELL]] Power Failure | |||
This error will occur in the case of a PWR failure on the main core voltage of the CPU | This error will occur in the case of a PWR failure on the main core voltage of the CPU. For example, if the filtering capacitors (NEC/TOKIN's) are severely damaged. There are other SMD's in that filter, so it could be related to them as well. | ||
==== 3004 ==== | |||
VDDC [[RSX]] Power Failure | |||
This error will occur in the case of a PWR failure on the main core voltage of the GPU. For example, if the filtering capacitors (NEC/TOKIN's) are severely damaged. There are other SMD's in that filter, so it could be related to them as well. | |||
==== 3010 ==== | |||
====3010==== | |||
[[CELL BE|CELL]] Error | [[CELL BE|CELL]] Error | ||
Observation: A user triggered this error by injecting 3.3V into PWRGD (power good) of IC6103 (NCP5318 CPU Buck Controller). It generated error 20 1001 and 20 3010. | |||
A user triggered this error by injecting 3.3V into PWRGD (power good) of IC6103 (NCP5318 CPU Buck Controller). It generated error 20 1001 and 20 3010. | |||
==== 3011 ==== | |||
====3011==== | |||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====3012 ==== | ==== 3012 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====3013==== | ==== 3013 ==== | ||
BE_SPI DI/DO ERROR | BE_SPI DI/DO ERROR | ||
Line 630: | Line 427: | ||
One person reported A0202120/A0213013 when his CPU substrate (interposer) was cracked in half by a failed delid attempt. | One person reported A0202120/A0213013 when his CPU substrate (interposer) was cracked in half by a failed delid attempt. | ||
==== 3020 ==== | |||
[[CELL BE|CELL]] | |||
==== | ==== 3030 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
==== 3031 ==== | |||
==== | |||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
==== 3032 ==== | |||
[[CELL BE|CELL]] Error | |||
====3032==== | |||
[[CELL BE|CELL]] | |||
+1.2v_YC_RC_VDDIO PWR Fail? | |||
====3033==== | ==== 3033 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
==== 3034 ==== | |||
[[CELL BE|CELL]] / [[RSX]] Communication Error | |||
This is the most common error seen in early Phat model PS3's with the hottest 90nm [[RSX]] and [[CELL BE|CELL]] processors. It is the hallmark of a BGA defect (such as a cracked solder ball). It is by no means limited to the early models, however. These arrors have been seen in every model of PS3 with varying frequency. The most reliable consoles appear to be those with a CPU/GPU of smaller manufacturing process, such as the Super Slim (SS) models (42xx and later) which have a 45nm [[CELL BE|CELL]] and 28nm [[RSX]]. The least reliable are the PS2 Backwards Compatable A-E Models, which have 90nm [[RSX]]/[[CELL BE|CELL]]. | |||
[[CELL BE|CELL]] / [[RSX]] / [[ | |||
The root cause is mechanical fatigue due to thermal cycling. The materials used to contruct the motherboard and processors have different properties. For example, the cooefficient of thermal expansion for FR4 Fiberglass used in the Motherboard and Processor Substrate is different than that of the copper BGA pads, which is different than that of the Lead-Free solder used to join them. This means they will expand and contract at different rates as the chip heats up and cools down, which applies shearing force to the BGA. Over many thermal cycle this deforms the solder balls and cause a defect (Such as a solder crack, torn trace, or the ball may pull away from the pad). | |||
3034 is triggered when the voltage or data lines connecting the CPU/GPU are broken. There is often a data error (4XXX) that also appears, but not always. The most common cause is a BGA defect on the [[RSX]], which usually requires a reball/reflow to repair. Something about the [[RSX]] construction or workload causes it to fail more frequently, but the CPU can fail too. However, it's not always a BGA defect. The bumps on either chip can fail, Flex IO traces (the data lines that connect the CPU/GPU) can be broken/scratched, or accumulated damage from wear and tear (electromigration) can also cause this error. The true percentage of consoles with BGA defects that can be fixed with a reball/reflow is unknown. However, there is evidence to suggest that the underfill used to reinforce the CPU/GPU die and [[RSX]] Ram bumps was not as effective when the PS3 was manufactured. This could explain many of the consoles who's reball fails prematurely afterwards. | |||
If a reflow/reball of both the CPU/GPU fails, then the chip is beyond repair and needs replaced. The [[RSX]] can be replaced with the same model without modification. It can be replaced with a different model using a modchip that injects the correct [[RSX]] ID during boot. This has been nicknamed a "Frankenstein Mod." Since they are married to each other, the CPU can only be replaced if also replacing the chipset (NAND/NOR and SYSCON Chips). Since the CPU can't as easily be replaced, a dead CPU is usually considered unrepairable. | |||
==== 3035 ==== | |||
[[CELL BE|CELL]] and [[RSX]] | |||
==== 3036 ==== | |||
====3036==== | |||
[[CELL BE|CELL]] and [[RSX]] | [[CELL BE|CELL]] and [[RSX]] | ||
==== 3037==== | ==== 3037 ==== | ||
[[CELL BE|CELL]] and [[RSX]] | [[CELL BE|CELL]] and [[RSX]] | ||
==== 3038 ==== | |||
====3038==== | |||
[[CELL BE|CELL]] and [[RSX]] | [[CELL BE|CELL]] and [[RSX]] | ||
====3039==== | ==== 3039 ==== | ||
[[CELL BE|CELL]] and [[RSX]] | [[CELL BE|CELL]] and [[RSX]] | ||
==== 3040 ==== | |||
====3040==== | |||
Flash | Flash | ||
---- | |||
=== Data Errors === | |||
---- | |||
*This error codes seems to be repeated up to 5 times for 5 special cases, as example, errors 4'''0'''01, 4'''1'''01, 4'''2'''01, 4'''3'''01, 4'''4'''01 are related to CELL, the only thing that changes in the error code is the second digit (located inmediatly after the category). If at some point we find what means that digit we can join the wiki page sections together (with titles: "4001, 4101, 4201, 4301, 4401", etc...) | |||
===Data Errors=== | |||
---- | |||
*This error codes seems to be repeated up to 5 times for 5 special cases, as example, errors 4'''0'''01, 4'''1'''01, 4'''2'''01, 4'''3'''01, 4'''4'''01 are related to CELL, the only thing that changes in the error code is the second digit (located | |||
====4001==== | ==== 4001 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4002==== | ==== 4002 ==== | ||
[[RSX]] | [[RSX]] | ||
====4003==== | ==== 4003 ==== | ||
Southbridge | Southbridge | ||
====4011==== | ==== 4011 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4101==== | ==== 4101 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4102==== | ==== 4102 ==== | ||
[[RSX]] | [[RSX]] | ||
====4103==== | ==== 4103 ==== | ||
Southbridge | Southbridge | ||
====4111==== | ==== 4111 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4201==== | ==== 4201 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4202==== | ==== 4202 ==== | ||
[[RSX]] | [[RSX]] | ||
====4203==== | ==== 4203 ==== | ||
Southbridge | Southbridge | ||
====4211==== | ==== 4211 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4212==== | ==== 4212 ==== | ||
[[RSX]] | [[RSX]] | ||
====4221==== | ==== 4221 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4222==== | ==== 4222 ==== | ||
[[RSX]] | [[RSX]] | ||
====4231==== | ==== 4231 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
==== 4261==== | ==== 4261 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4301==== | ==== 4301 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4302==== | ==== 4302 ==== | ||
[[RSX]] | [[RSX]] | ||
==== 4303==== | ==== 4303 ==== | ||
Southbridge | Southbridge | ||
====4311==== | ==== 4311 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4312==== | ==== 4312 ==== | ||
[[RSX]] | [[RSX]] | ||
====4321==== | ==== 4321 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4322==== | ==== 4322 ==== | ||
[[RSX]] | [[RSX]] | ||
====4332==== | ==== 4332 ==== | ||
[[RSX]] | [[RSX]] | ||
====4341==== | ==== 4341 ==== | ||
[[CELL BE|CELL]] | [[CELL BE|CELL]] | ||
====4401 | ==== 4401 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4402 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4403 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4411 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4412 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4421 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4422 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4432 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
==== | ==== 4441 ==== | ||
[[CELL BE|CELL]] or [[RSX]] | [[CELL BE|CELL]] or [[RSX]] | ||
{{Hardware Modification}}<noinclude>[[Category:Main]]</noinclude> | |||
{{Hardware Modification}}<noinclude> | |||
[[Category:Main]] | |||
</noinclude> |