PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

Yes I did. All 4 XDR light up and so does the CPU. Unfortunately that doesn't help me much. That could mean the issue lies under the CPU, BGA to XDR is broken (IDK if console was dropped or not. Don't think @squeept said). He said it was a warranty return IIRC, which means it was working when he sold it to begin with? So maybe in shipping the banging broke a BGA. IDK, I haven't had time to investigate further. If it were an XDR module that would be fairly quick to replace. But I don't see any obvious reason to suspect them. It's looking at a CPU reball at least, and possibly full XDR replacement too.

I'm procrastinating!

I sleuthed my way back to the sheet by checking the date you sent me your address, then running backwards in the thread to around then and found you reposted my diagnostic sheet for it on your post on page 152. No drops!

edit: Still can't believe that console had 7 days on it. Legitimately may have been from that Air Force cluster.
 
hi. i was getting red light and shutdown in god of war 3 in intro. checked syscon gave me error 1001 changed 1 of cell side nec tokins with 4 470Uf capacıtors. this solved the issue but playing after 30 minutes or so gave the same error. so i changed other cell side nec tokins with 4 same 470uf capacitor. weirdly i got delayed ylod. help me please :drunk:
 
I have repaired a CECHH model with a0a02031 errors. And replacing thermal sensor IC does fix the console.

My syscon logs for reference:
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[ERROR]: 0xa0502131
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.1.0 (Build ID: 2709,28222, Build Data: 2007-12-05_13:32:28)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[ERROR]: 0xa0802031
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
>$
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[mullion]$ [ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[mullion]$
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[mullion]$ [ERROR]: 0xa0802131
>$
[mullion]$
>$
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SSM] *** Unrecoverable FATAL ERROR by thermal***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0802131
[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff

So if you see multiple 2031 or 2131 spit out when doing bringup, that's likely is the thermal sensor error. By the way, thermal sensor is powered even in standby mode(red led on). This makes it easy to probe to see if anything obviously wrong without heatsink or fan.
Thank you for the reply.

I think i found a way to attach the log for reference.

I will give the sensor a go and report back later.
13c0bd4cdafee04e05323b40190b6d2f.jpg


Sent from my XQ-CT54 using Tapatalk
 
I have repaired a CECHH model with a0a02031 errors. And replacing thermal sensor IC does fix the console.

My syscon logs for reference:
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[ERROR]: 0xa0502131
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.1.0 (Build ID: 2709,28222, Build Data: 2007-12-05_13:32:28)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[ERROR]: 0xa0802031
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
>$
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[mullion]$ [ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[mullion]$
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[mullion]$ [ERROR]: 0xa0802131
>$
[mullion]$
>$
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SSM] *** Unrecoverable FATAL ERROR by thermal***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0802131
[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff

So if you see multiple 2031 or 2131 spit out when doing bringup, that's likely is the thermal sensor error. By the way, thermal sensor is powered even in standby mode(red led on). This makes it easy to probe to see if anything obviously wrong without heatsink or fan.
How do you replace it?

Enviado desde mi moto e6 play mediante Tapatalk
 
Good question. I couldn't find an ADT7461A sensor as mentioned on the wiki on either board (A0 and A1) so i replaced what looked like a thermal sensor just by the RSX but error still persists. Either got the wrong sensor or just happened to grab another faulty one [emoji1745]

Sent from my XQ-CT54 using Tapatalk
 
Yes I did. All 4 XDR light up and so does the CPU. Unfortunately that doesn't help me much. That could mean the issue lies under the CPU, BGA to XDR is broken (IDK if console was dropped or not. Don't think @squeept said). He said it was a warranty return IIRC, which means it was working when he sold it to begin with? So maybe in shipping the banging broke a BGA. IDK, I haven't had time to investigate further. If it were an XDR module that would be fairly quick to replace. But I don't see any obvious reason to suspect them. It's looking at a CPU reball at least, and possibly full XDR replacement too.

I'm procrastinating!

I think mine have a similar problem most likely a broken BGA. It might be also a broken BGA in the clock line because the position of them is more vulnerable and a reball should fix it But I don't have a BGA machine unfortunately.
 
Good question. I couldn't find an ADT7461A sensor as mentioned on the wiki on either board (A0 and A1) so i replaced what looked like a thermal sensor just by the RSX but error still persists. Either got the wrong sensor or just happened to grab another faulty one [emoji1745]

Sent from my XQ-CT54 using Tapatalk
The thermal sensor on RSX should be pin compatbile across FAT models AFAIK. For my case, I grabbed even a donor slim model's thermal sensor and checked the pin description that matches the one I have in CECHH, so solder it on and it works. There's one thing that thermal sensor across RSX/CELL/SB isn't interchanable because their I2C address is different. So make sure you grab a donor thermal sensor of RSX and solder it to RSX, not the other chip. Posting a picture might help.
 
Find a donor board, check the datasheet especially pin description, if it matches, it is likely to be interchangeable.
There is a way to get more error codes, more than 20?
I use GUI syscon error codes

Enviado desde mi moto e6 play mediante Tapatalk
 
Hey ! After long time I decided to back to repairing PS3. Here are some error codes, that may help anyone, which I had and successfully repair, or not.
1002 – Faulty Nec on RSX side
3032 – faulty IC6304 (COK 002 board)
4003/4034 – bad solder on IC6305
A0802203 – Scratched CPU on corner while deliding
3013/2120 - Broken pads on the motherboard under CPU (COK 002 board)
3010 – Failed delid attempt, scratched CPU
4002/4034 – RSX reballing - works
4421/4034 – Cell reballing – works
3040 – GLOD, starship chip fail In error logs, but I think that someone had bricked this console while uptading OFW or patching to CFW (SEM 001 board)
No error – Console didn't see the hard drive, bad TH3280 (VER 001 board)
I think, when CPU is scratched there could be some different errors, in case which trace was broken.
I have also a problem. I bought CECHC04, connect syscon and standard 4002/3034, so I decided to put there a 65nm RSX. I did all the modifications, and I got an error :
0xa0404441
0xa0403034
Okay, so I thought there could be BGA problem under CELL, so I reballed it too, and nothing changes. Somebody earlier must working on this board, because IC6304 and IC6303 desoldered from motherboard when I reballed RSX. When this error didn't change I decided to put another 65nm RSX (also working) and… nothing, still 4441/3034. Ok, I thought that CPU can be damaged (3 small capacitors under were not in straight line) so I decided to change CPU, Syscon and flash memory from another board, but this won't change anything, still 3034/4441. Here is the full log from bringup:
Code:
> bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>
[POWERSEQ] Error : BitTraining BE:RRAC:RX4:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404441
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Could this be a problem between comunnication on CPU and SB ? All of the fuses are okay, I don't see any shorts on the board. I read, that TX6 and RX4 are traces beetwen Cell and southbridge, but where to start search ? Could this be also bga defect under southbridge ?
Have a nice day ! ;)
 
Hey ! After long time I decided to back to repairing PS3. Here are some error codes, that may help anyone, which I had and successfully repair, or not.
1002 – Faulty Nec on RSX side
3032 – faulty IC6304 (COK 002 board)
4003/4034 – bad solder on IC6305
A0802203 – Scratched CPU on corner while deliding
3013/2120 - Broken pads on the motherboard under CPU (COK 002 board)
3010 – Failed delid attempt, scratched CPU
4002/4034 – RSX reballing - works
4421/4034 – Cell reballing – works
3040 – GLOD, starship chip fail In error logs, but I think that someone had bricked this console while uptading OFW or patching to CFW (SEM 001 board)
No error – Console didn't see the hard drive, bad TH3280 (VER 001 board)
I think, when CPU is scratched there could be some different errors, in case which trace was broken.
I have also a problem. I bought CECHC04, connect syscon and standard 4002/3034, so I decided to put there a 65nm RSX. I did all the modifications, and I got an error :
0xa0404441
0xa0403034
Okay, so I thought there could be BGA problem under CELL, so I reballed it too, and nothing changes. Somebody earlier must working on this board, because IC6304 and IC6303 desoldered from motherboard when I reballed RSX. When this error didn't change I decided to put another 65nm RSX (also working) and… nothing, still 4441/3034. Ok, I thought that CPU can be damaged (3 small capacitors under were not in straight line) so I decided to change CPU, Syscon and flash memory from another board, but this won't change anything, still 3034/4441. Here is the full log from bringup:
Code:
> bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
>
[POWERSEQ] Error : BitTraining BE:RRAC:RX4:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404441
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Could this be a problem between comunnication on CPU and SB ? All of the fuses are okay, I don't see any shorts on the board. I read, that TX6 and RX4 are traces beetwen Cell and southbridge, but where to start search ? Could this be also bga defect under southbridge ?
Have a nice day ! ;)

3034 is BE error
4441 is SB error
BE:RRAC:RX4:GLOBAL1:RX_STATUS
This means bad communication between two.
Since you reballed CPU, logically next step should be SB. Unless something is messed with CPU pads.
 
There is a way to get more error codes, more than 20?
I use GUI syscon error codes

Enviado desde mi moto e6 play mediante Tapatalk
Can I ask what's the purpose for getting more error codes? The syscon will keep the error codes in a ring table and overwrite the oldest one.
 
Can I ask what's the purpose for getting more error codes? The syscon will keep the error codes in a ring table and overwrite the oldest one.
Check other things like if I had error 3034 or dead RSX.
Before I get the error codes even USB uart, I removed all nec/tokens, maybe cause the error?

Enviado desde mi moto e6 play mediante Tapatalk
 
Check other things like if I had error 3034 or dead RSX.
Before I get the error codes even USB uart, I removed all nec/tokens, maybe cause the error?

Enviado desde mi moto e6 play mediante Tapatalk
You don't need more than 20 error codes to see if it's 3034. If you got one, your RSX probably needs a reball or replace. If you think the previous errors could be mistakes, then clear the error code from syscon uart and bringup the console again, then check the error codes again.
 
You don't need more than 20 error codes to see if it's 3034. If you got one, your RSX probably needs a reball or replace. If you think the previous errors could be mistakes, then clear the error code from syscon uart and bringup the console again, then check the error codes again.
There is any way to talk with you on DM? I see you got a lot of experience with this

Enviado desde mi moto e6 play mediante Tapatalk
 
You can DM me using the forum, but obviously here in this thread a lot more people has more experience than me.
Ok, but I see you got same errors as me, I searched on internet the fix of the error and nothing

Enviado desde mi moto e6 play mediante Tapatalk
 
Apparently you can buy the thermal sensors from sites like AliExpress or Mauser, in my case I have día 001, my question is with the ad51, any reference of ad51 works on PS3?
f99d1ecd17ade35e8a170e2948436eb3.jpg


Enviado desde mi moto e6 play mediante Tapatalk
 
There is a way to get more error codes, more than 20?
I use GUI syscon error codes

Enviado desde mi moto e6 play mediante Tapatalk

Not with that GUI. Author didn't implement the code in HEX, so it's missing 12 codes. Do they matter? YES, for seeing context of the original error, assuming you didn't erase them by testing the console so many times the original errors were replaced with the current issue. This error history is useful for building a story of what's been leading up to the current issue.

Anyway, the proper method is to UART in manually in a comand terminal, or power shell, or whatever. Then all 32 errors are easily retrieved.
 
Not with that GUI. Author didn't implement the code in HEX, so it's missing 12 codes. Do they matter? YES, for seeing context of the original error, assuming you didn't erase them by testing the console so many times the original errors were replaced with the current issue. This error history is useful for building a story of what's been leading up to the current issue.

Anyway, the proper method is to UART in manually in a comand terminal, or power shell, or whatever. Then all 32 errors are easily retrieved.
Them I need to use the python CMD?, I use it and I couldn't auth, I going to try, what commands I need to write plus what else can I check to see the status of console

I have a question about your tantalizers, what caps I need to use and those PCBs have the internal jumper between positive and positive?

Enviado desde mi moto e6 play mediante Tapatalk
 

Similar threads

Back
Top