Editing Syscon Error Codes

[[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>

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 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)

There are 2 error log formats that depends of the syscon type: for [[Mullion]], or for [[Sherwood]]<br>

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 the timestamp is recorded as FFFFFFFF<br>

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 errorlog timestamp formats and loops in the [[Talk:Syscon_Error_Codes | Talk page]]<br>

*In the errorlog sample above:

**Errorlog looped at least 1 time (1 errorcode FFFFFFFF)

'''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.

'''A0''' = Immediately after SYSCON reset. When you supply/plug-in power, the PS3 is supposed to enter Standby. A solid red LED will illuminate on early "Phat" models, for example. There is a Standby circuit in the PS3 that constantly needs power, so the PS3 can wait for the user to start the console. Sometimes this is called a Vampire circuit, because it uses power even when you're not using the console. Many electronics do this to allow you to turn them on remotely. Otherwise, you would need to physically flip a switch to turn them on.

The PS3 reset circuit consists of the SYSCON and it's Clock generating Crystal, Bluetooth/WIFI Card, Front PWR/EJT and LED panel, and Thermal Monitor ICs. The SYSCON needs to know if you are trying to start the console. Either manually with the PWR button or over Bluetooth using your controller. So those modules need to be powered. It also needs to know that the thermal monitors are functioning properly before it can safely send power to the Southbrige, CPU or GPU. Otherwise, the console would be a fire hazard! Thermal monitors ICs are like the PS3s fire alarms. They are critical safety equipment.  

If there is a Hardware issue anywhere in that circuit, you will get an error immediately after SYSCON reset that will prevent you from even attempting to power on the console. The front LED will flash Red Indefinitely as soon as you plug in the console, instead of giving you a solid RED LED. This is how you know you have an error with the standby circuit. And there will be an associated error logged in the syscon that may help you track it down to the specific component.

5v_MISC powers the reset circuit, which are a collection of SMD/SMT components and IC's that power the above modules. Check the Service manual (If available) for specifics. For example, in the COK-001 service manual you can find the circuit diagram on page 23/45. You can see that IC6005 (a DC/DC converter) is responsible for generating +3.3v_EVER. IC6006 generates +1.8V_EVER, and IC6009 generates +3.3V_THERMAL. These are the main voltages used by the component in the reset circuit, such as the WIFI/Bluetooth card needed to remote start the console by pressing the PS button on the controller.  

The 3-digit error code can repeat in others Categories, but doesn't mean the same thing. System error <span style="background:#ff8080;">001</span> and Fatal error <span style="background:#ff8080;">001</span> don't mean the same thing. <span style="background:#bbbbff;">1</span><span style="background:#ff8080;">001</span> is "BE VRM Power Failure" and <span style="background:#bbbbff;">2</span><span style="background:#ff8080;">001</span> is "BE Error." We wouldn't be able to tell the difference between them if we just referred to the <span style="background:#ff8080;">error</span>. That's not enough information by itself to understand the problem. The <span style="background:#bbbbff;">category</span> gives the <span style="background:#ff8080;">error</span> context. So we use the 4-Digit code <span style="background:#bbbbff;">C</span><span style="background:#ff8080;">ERR</span> to differentiate them from one another.  

Likewise, the <span style="background:#ffff80;">Step Nump (ST)</span> provides context to the 4-Digit code. For example, you can have a CELL VRM Power Failure occur while playing an intense game (Static State, Power on). That would generate an <span style="background:#ffff80;">80</span><span style="background:#bbbbff;">1</span><span style="background:#ff8080;">001</span> (Step number <span style="background:#ffff80;">80</span>). However, you can also get that error when turning the console on, during Power On Sequence Testing (POST), before it even has a chance to start the bootloader, which loads the OS, which in turn let's you load the game. This time it might generate error <span style="background:#ffff80;">10</span><span style="background:#bbbbff;">1</span><span style="background:#ff8080;">001</span>. Step number <span style="background:#ffff80;">10</span> is lower than Step number <span style="background:#ffff80;">80</span>, telling you this <span style="background:#bbbbff;">1</span><span style="background:#ff8080;">001</span> occurred earlier. The <span style="background:#bbbbff;">Categoty</span> + <span style="background:#ff8080;">Error</span> tells you "What" happened. The <span style="background:#ffff80;">Step Number</span> tells you "when" it happened. It's building context that can help you figure out what is causing the error.

It is important to consider the context of the full errorlog. Not just the 4-digit <span style="background:#bbbbff;">C</span><span style="background:#ff8080;">ERR</span>. The reason is because you are attempting to build the case for "Why" it happened! In the previous example, the <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;">001</span> could mean the NEC/TOKIN Proadlizers (a type of capacitor that is part of the CELL CPU's VRM, Voltage Regulation Module) may be at fault. The <span style="background:#000000; color:#ffffff;">A</span><span style="background:#909090; color:#ffffff;">0</span><span style="background:#ffff80;">10</span><span style="background:#bbbbff;">1</span><span style="background:#ff8080;">001</span> can result from other causes simply because there is a larger number of things that can go wrong. It may not be the NEC/TOKINs at all.  

*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.

*Fatal Booting Error 034 ([[RSX]]/[[CELL BE|CELL]] Communication Error) which occurred at step no. 40 (BitTraining), before the Power On Sequence completed.

*3034s are caused by BGA/Bump Defects (among other issues). Experienced PS3 repair technicians have noted that it is almost exclusive to the RSX. While our knowledge of the hardware interface cannot rule out the possibility a CELL BE BGA/Bump defect can cause it, that has been the exception to the rule. Experience and time have shown 3034's are primarily an RSX issue. A repair technician needs to decide which processor to reball/replace based upon the more likely candidate. They have to use discretion.

*3013 errors have been caused by Dead CELL BE CPU.

The following Error Code section will only list the last 4 numbers (category + error). However, remember 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 specific error means, but you still need to figure out what it means in context of your issue. So you can diagnose the error and then fix it.

This error is due to insufficient Filtering on the CPU's core voltage (VDDC) or an unexpected shutdown. There is a range of voltage ripple/noise that 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 NEC/TOKINs on the GPU, but 1001 is not as easy to diagnose. You need to witness the console YLOD under load and see a new 1001 error was generated by it. Otherwise, the 1001 could simply mean the console wasn't shut off properly.

1001 errors can be logged naturally when the system encounters an unexpected shutdown or AC power loss. They often occur in testing, when the console is switched on/off a lot, instead of a graceful shutdown. A0801001 errors by themselves cannot be used as evidence of failing NEC/TOKINs. Such errors are commonly found in the log of perfectly working machines, and are nothing to worry about unless the system is shutting itself off unexpectedly.

A common case where 1001 errors can be misinterpreted is a machine that can power ON, but has graphical artifacts or no video (GLOD). In these cases the console must be forced off using the power rocker at the back of the console (in Phat models), or by pulling the power cord (slim & super slim models), which can cause the 1001. This can also cause 1004 errors. These errors can be ignored if they were not generated under normal circumstances. In the case of a console exhibiting artifacts/GLOD, the bigger issue should be addressed first (typically a GPU issue requiring a reball/replacement). Afterwards, if 1001 errors return during stress testing, then you can diagnose the CPU NEC/TOKINs.

Anecdote: One console with bad CPU NEC/TOKINs exhibited an A0901001 only upon shutdown. It was stable in The Last of Us (strenuous game) and did not seem to have the typical behavior associated with bad NEC/TOKINs. However, it hung in shutdown for an extended period of time, finally issuing the YLOD (3-beeps and flashing red). It needed to be reset before it could be powered on again. Replacing the NEC/TOKINs repaired the issue.

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>

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.

When a console looses AC power, error A0801004 may be generated. A common case where 1004 errors occur is a machine that can power ON, but has graphical artifacts or no video (GLOD). In these cases the console must be forced off using the power rocker at the back of the console (in Phat models), or by pulling the power cord (slim & super slim models). Doing this causes a loss of AC, which can cause the error.

This error can be ignored if it wasn't generated under normal circumstances. Such as a power outtage or accidental unplugging. Since it didn't result from a hardware fault, it's not serious. In the case of a console exhibiting artifacts/GLOD, the bigger issue should be addressed first (typically a GPU issue requiring a reball/replacement). Afterwards, if 1004 errors return, then you can should diagnose the AC/DC line. PSU and it's connection upto the DC-DC converters.

**[[Thermal|CELL temperature monitor]] (only in mullion syscons, the CELL temperature monitor for PS3 slims and superslims cant send this error code)

Syscon have a pad/pin dedicated to this signal, the reason why it was given an official generic name (not indicating who was triggering it) is because this signal can be sent by several components, in the first PS3 models (with mullion syscon ?) it can be sent by CELL, or by the CELL temperature monitor, using the official function names SYS_THR_ALRT or THERMAL_OVERLOAD<br>

But this electrical design is not specific for the PS3, there could be other devices based in the IBM/CELL and developed by sony where this error code is sent by other components and could have more than one CELL... so in general we could say this error code indicates one (or more) of the CELL processors (<abbr title="and maybe other components not present in retail PS3 models">or his temperature monitor chips</abbr>) is overheating

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

==== 1301 ====

[[CELL BE|CELL]] PLL

==== 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]]

*This fatal error codes seems to be repeated up to 3 times for 3 special cases, as example, errors '''20'''03, '''21'''03, and '''22'''03 are related with southbridge, the only thing that changes in the error code is the second digit (located inmediatly after the category 2). If at some point we find what means that second digit we can join the wiki page sections together (with titles: "2001 & 2101", "2002 & 2102", "2003 & 2103", etc...)<br>

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.

I had a short in the cell, in the nec tokin after removing it, changed the error.

Clock Generator Error (IC5002)

==== 2120 (HDMI) ====

HDMI Error (IC2502)

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) ====

==== 2124 (AV) ====

==== 2130 (Thermal Sensor, CELL) ====

**[[CELL BE|CELL]] [[Thermal#Temperature_Monitors|Temperature Monitor]] (IC1101 on [[COK-001]])

==== 2131 (Thermal Sensor, RSX) ====

**[[RSX]]

==== 2133 (Thermal Sensor, South Bridge) ====

**[[South Bridge]]

==== 2203 (South Bridge) ====

[[South Bridge]] Error (IC3001)

==== 2310 ====

=== Fatal Boot Errors ===

==== 3000 ====

==== 3001 ====

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 ====

==== 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. 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 ====

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 ====

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.

==== 3011 ====

==== 3012 ====

==== 3013 ====

==== 3030 ====

==== 3031 ====

==== 3032 ====

[[CELL BE|CELL]] Error

+1.2v_YC_RC_VDDIO PWR Fail?

==== 3033 ====

[[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]].

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 (or new syscon modification) 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.

[[CELL BE|CELL]] and [[RSX]]

==== 3036 ====

==== 3037 ====

==== 3038 ====

==== 3039 ====

==== 3040 ====

=== 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...)

==== 4001 ====

==== 4002 ====

==== 4003 ====

==== 4011 ====

==== 4101 ====

==== 4102 ====

==== 4103 ====

==== 4111 ====

==== 4201 ====

==== 4202 ====

==== 4203 ====

==== 4211 ====

==== 4212 ====

==== 4221 ====

==== 4222 ====

==== 4231 ====

==== 4261 ====

==== 4301 ====

==== 4302 ====

==== 4303 ====

==== 4311 ====

==== 4312 ====

==== 4321 ====

==== 4322 ====

==== 4332 ====

==== 4341 ====

==== 4401 ====

==== 4402 ====

==== 4403 ====

==== 4411 ====

==== 4412 ====

==== 4421 ====

==== 4422 ====

==== 4432 ====

==== 4441 ====

{{Hardware Modification}}<noinclude>[[Category:Main]]</noinclude>