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

[Rissy]

So with a bit more messing last night, I discovered that the artifacts only come out on 1080p AND when the HDMI is plugged into the TV via an HDMI switched splitter I use (The other consoles don't do this). When I connect to the one of the TV HDMI ports directly, there are no artifacts at all, only the random sparkling happens, and this only happens on 1080p, not 1080i. Weirder and weirder. I'd have to open up the console to start pressing on stuff like you're suggesting. I'd already tried lightly wiggling the HDMI port, and also tried giving it a good blow through, but this doesn't change anything. I think if it was the port on the console, then it would affect 1080i too. I can't explain why only 1080p is affected....?!

When you say BGA fault, is that balling on the RSX you mean? I thought that was more typical of a 90nm rather than the 65nm (in the slim at least) which will be the chip used in this 2103A model.

Well I feel a bit silly now. I've just discovered that the 2103A with the sparkling effects on-screen, and previously with flashing green random artifacts on-screen was actually a sub standard HDMI cable. I've now changed this out for a much nicer gold plated one, and hey presto, perfect video output even on 1080p! I think I might have gotten that sub standard one with the PS3 in the first place. Now there's a proper high quality one there, and it's done the trick. All consoles now displaying perfectly. Very pleased it was something stupid and not requiring surgery!


Sent from my iPhone using Tapatalk

 

[Ormas]

Hello, I bought a cok-002 ylod motherboard that's missing it's daughterboard from ebay with hopes that one day I could get it fixed. I need someones expert opinion on whether this board is worth fixing. When I first pulled the error log from the syscon, it shows some 1001 and 1004 codes, then it changes to nothing but 1701 codes. Then I decided to do two bringup tests and it gave me 4402 and 3034 on both tests. Anybody have any ideas on what's going on here? Could the 1001s and 1004s have happened due to a faulty psu? What could have caused the 1701s? And why is it now giving 4402s and 3034s? I don't know anything about the history of this ps3. It arrived to me with a partially bent metal-shielding and the board is slightly warped on one side where the shielding is bent. It doesn't look like this board was ever worked on. No obvious signs that the rsx was reflowed. Anyways, here is the error log and the bringups. Along with the becount.

>$ errlog
errlog
ofst[ 72]:err_code:0xffffffff, clock:0x166592c6  2011/11/28 00:31:02
ofst[ 76]:err_code:0xa0801004, clock:0x16b20a74  2012/01/25 00:33:56
ofst[ 80]:err_code:0xa0801001, clock:0x16b5a591  2012/01/27 18:12:33
ofst[ 84]:err_code:0xa0801001, clock:0x16b72e3e  2012/01/28 22:07:58
ofst[ 88]:err_code:0xa0801001, clock:0x16f2abab  2012/03/14 01:06:51
ofst[ 92]:err_code:0xa0801001, clock:0x16f807ba  2012/03/18 02:40:58
ofst[ 96]:err_code:0xa0801001, clock:0x16f8e09a  2012/03/18 18:06:18
ofst[100]:err_code:0xa0801001, clock:0x171c5fab  2012/04/14 16:17:47
ofst[104]:err_code:0xa0801001, clock:0x1724970e  2012/04/20 21:52:14
ofst[108]:err_code:0xa0801001, clock:0x173f55d0  2012/05/11 04:45:04
ofst[112]:err_code:0xa0801004, clock:0x17408472  2012/05/12 02:16:18
ofst[116]:err_code:0xa0801001, clock:0x1742f0a0  2012/05/13 22:22:24
ofst[120]:err_code:0xa0801001, clock:0x174c0e30  2012/05/20 20:18:56
ofst[124]:err_code:0xa0801701, clock:0xffffffff
ofst[  0]:err_code:0xa0801701, clock:0xffffffff
ofst[  4]:err_code:0xa0801701, clock:0xffffffff
ofst[  8]:err_code:0xa0801701, clock:0xffffffff
ofst[ 12]:err_code:0xa0801701, clock:0xffffffff
ofst[ 16]:err_code:0xa0801701, clock:0xffffffff
ofst[ 20]:err_code:0xa0801701, clock:0xffffffff
ofst[ 24]:err_code:0xa0801701, clock:0xffffffff
ofst[ 28]:err_code:0xa0801701, clock:0xffffffff
ofst[ 32]:err_code:0xa0801701, clock:0xffffffff
ofst[ 36]:err_code:0xa0801701, clock:0xffffffff
ofst[ 40]:err_code:0xa0801701, clock:0xffffffff
ofst[ 44]:err_code:0xa0801701, clock:0xffffffff
ofst[ 48]:err_code:0xa0801701, clock:0xffffffff
ofst[ 52]:err_code:0xa0801701, clock:0xffffffff
ofst[ 56]:err_code:0xa0801701, clock:0xffffffff
ofst[ 60]:err_code:0xa0801701, clock:0xffffffff
ofst[ 64]:err_code:0xa0801701, clock:0xffffffff
ofst[ 68]:err_code:0xa0801701, clock:0xffffffff
ofst[ 72]:err_code:0xa0404402, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404402, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff

>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[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
Press Ctrl+C to exit
>$ lasterrlog
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0: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]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0403034, Time:0xffffffff
[mullion]$

>$ 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
Press Ctrl+C to exit
>$ errlog
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0: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]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

>$ becount
becount
Bringup : 394 times
Shutdown: 138 times
Power-on: 5day 20hour 23min 32sec
[mullion]$

 

[RIP-Felix]

Well I feel a bit silly now. I've just discovered that the 2103A with the sparkling effects on-screen, and previously with flashing green random artifacts on-screen was actually a sub standard HDMI cable. I've now changed this out for a much nicer gold plated one, and hey presto, perfect video output even on 1080p! I think I might have gotten that sub standard one with the PS3 in the first place. Now there's a proper high quality one there, and it's done the trick. All consoles now displaying perfectly. Very pleased it was something stupid and not requiring surgery!


Sent from my iPhone using Tapatalk

Thank you for the update, I'll add it to the spreadsheet. These are good reports of common issues we dont get alot of reports about, since something simple is often sorted out before asking for help. And thuse we collect more difficult issues and don't get a good sense of normal issue people run into. And it's interesting to hear you getting similar aftifacting from a bad hdmi cable, that would otherwise have BGA/Bump alarm bells ringing in our minds. We have been condituoned! Aparently YLOD PTSD.

 

[RIP-Felix]

Hello, I bought a cok-002 ylod motherboard that's missing it's daughterboard from ebay with hopes that one day I could get it fixed. I need someones expert opinion on whether this board is worth fixing. When I first pulled the error log from the syscon, it shows some 1001 and 1004 codes, then it changes to nothing but 1701 codes. Then I decided to do two bringup tests and it gave me 4402 and 3034 on both tests. Anybody have any ideas on what's going on here? Could the 1001s and 1004s have happened due to a faulty psu? What could have caused the 1701s? And why is it now giving 4402s and 3034s? I don't know anything about the history of this ps3. It arrived to me with a partially bent metal-shielding and the board is slightly warped on one side where the shielding is bent. It doesn't look like this board was ever worked on. No obvious signs that the rsx was reflowed. Anyways, here is the error log and the bringups. Along with the becount.

>$ errlog
errlog
ofst[ 72]:err_code:0xffffffff, clock:0x166592c6  2011/11/28 00:31:02
ofst[ 76]:err_code:0xa0801004, clock:0x16b20a74  2012/01/25 00:33:56
ofst[ 80]:err_code:0xa0801001, clock:0x16b5a591  2012/01/27 18:12:33
ofst[ 84]:err_code:0xa0801001, clock:0x16b72e3e  2012/01/28 22:07:58
ofst[ 88]:err_code:0xa0801001, clock:0x16f2abab  2012/03/14 01:06:51
ofst[ 92]:err_code:0xa0801001, clock:0x16f807ba  2012/03/18 02:40:58
ofst[ 96]:err_code:0xa0801001, clock:0x16f8e09a  2012/03/18 18:06:18
ofst[100]:err_code:0xa0801001, clock:0x171c5fab  2012/04/14 16:17:47
ofst[104]:err_code:0xa0801001, clock:0x1724970e  2012/04/20 21:52:14
ofst[108]:err_code:0xa0801001, clock:0x173f55d0  2012/05/11 04:45:04
ofst[112]:err_code:0xa0801004, clock:0x17408472  2012/05/12 02:16:18
ofst[116]:err_code:0xa0801001, clock:0x1742f0a0  2012/05/13 22:22:24
ofst[120]:err_code:0xa0801001, clock:0x174c0e30  2012/05/20 20:18:56
ofst[124]:err_code:0xa0801701, clock:0xffffffff
ofst[  0]:err_code:0xa0801701, clock:0xffffffff
ofst[  4]:err_code:0xa0801701, clock:0xffffffff
ofst[  8]:err_code:0xa0801701, clock:0xffffffff
ofst[ 12]:err_code:0xa0801701, clock:0xffffffff
ofst[ 16]:err_code:0xa0801701, clock:0xffffffff
ofst[ 20]:err_code:0xa0801701, clock:0xffffffff
ofst[ 24]:err_code:0xa0801701, clock:0xffffffff
ofst[ 28]:err_code:0xa0801701, clock:0xffffffff
ofst[ 32]:err_code:0xa0801701, clock:0xffffffff
ofst[ 36]:err_code:0xa0801701, clock:0xffffffff
ofst[ 40]:err_code:0xa0801701, clock:0xffffffff
ofst[ 44]:err_code:0xa0801701, clock:0xffffffff
ofst[ 48]:err_code:0xa0801701, clock:0xffffffff
ofst[ 52]:err_code:0xa0801701, clock:0xffffffff
ofst[ 56]:err_code:0xa0801701, clock:0xffffffff
ofst[ 60]:err_code:0xa0801701, clock:0xffffffff
ofst[ 64]:err_code:0xa0801701, clock:0xffffffff
ofst[ 68]:err_code:0xa0801701, clock:0xffffffff
ofst[ 72]:err_code:0xa0404402, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404402, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff

>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[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
Press Ctrl+C to exit
>$ lasterrlog
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0: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]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0403034, Time:0xffffffff
[mullion]$

>$ 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
Press Ctrl+C to exit
>$ errlog
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0: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]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

>$ becount
becount
Bringup : 394 times
Shutdown: 138 times
Power-on: 5day 20hour 23min 32sec
[mullion]$

Thanks for posting that info, very helpful.

My guess would be that there was a fall resulting in BGA damage and GLOD. Forcing the console off caused the 1001/1004s. Timestamps stop right when the 1701 appeared. That's when they opened it and broke the suction on the paste. A BGA defect is sensitive to pressure changes, so it going to 1701 after that isnt suprising. And eventually making it all the way to 3034 isnt either.

Now, that's just one hypothesis that may fit the evidence. Clues like whether or not the paste was original or all the RF shield screws were there and unscratched may suggest if anyone dug that deep. If not they may have attempted a PSU replacment, got frustrated a threw the console resulting in the warping...

Point is were just speculating about the cause. So you could try a pressure test to see if it boots or changes behavior. If so a reball may fix it until the RSX dies. Or you could have it frankied. There is a possabikity with drop damage the CPU BGA is damaged too, which would be PITA to have to reball, but it's doable.

Otherwise, this looks like a typical GPU failure common on these 90nm RSX models.

 

[Rissy]

Thank you for the update, I'll add it to the spreadsheet. These are good reports of common issues we dont get alot of reports about, since something simple is often sorted out before asking for help. And thuse we collect more difficult issues and don't get a good sense of normal issue people run into. And it's interesting to hear you getting similar aftifacting from a bad hdmi cable, that would otherwise have BGA/Bump alarm bells ringing in our minds. We have been condituoned! Aparently YLOD PTSD.

One is pleased to be of service


Sent from my iPhone using Tapatalk

 

[Ormas]

Point is were just speculating about the cause. So you could try a pressure test to see if it boots or changes behavior. If so a reball may fix it until the RSX dies. Or you could have it frankied. There is a possabikity with drop damage the CPU BGA is damaged too, which would be PITA to have to reball, but it's doable.

I tried the pressure test and the ylod disappeared. It didn't give me any errors and looked like it was booting through the syscon, but it wasn't displaying anything. So it probably is a glod/rsx problem like you said. Now I gotta figure out if I should get it reballed or frankied. Thank you for the help!

 

[BadaBoomBadaBing]

That's not short, that's normal. The CPU and GPU core voltages (VDDC) are low impedance, meaning they normally read somewhere between 2 and 5 ohms when healthy.

Damn I didn't receive an email notification for your reply, sorry for the delay. I've shelved the console since my last post. It was throwing 3033 and 3034 codes which went back to 1002 after redoing the capacitors for the 200000th time.

I've been defeated

Thanks for your assistance regardless. This has been a good learning experience.

 

[RIP-Felix]

Damn I didn't receive an email notification for your reply, sorry for the delay. I've shelved the console since my last post. It was throwing 3033 and 3034 codes which went back to 1002 after redoing the capacitors for the 200000th time.

I've been defeated

Thanks for your assistance regardless. This has been a good learning experience.

Would you please post the errorlog? Are you sure about the 3033? What step number (full code not just the last 4 digits).

3034 is confirmation of a GPU fault ATP. Doing and redoing the caps is a hampster wheel. The 1002's are likely because the caps are not good or installed properly. But even if they were, the 3034 is intermittently showing up because of thermomechanical stresses and changes in impeedance that briefly allow it to pass bittraining, a calibration procedure for CPU/SB/GPU communication in which changes in impeedance can have a large effect on the whether or not it completes sucessfully. Just heating the console can be enough to get it to pass. Which is why hairdryer tricks worked, the soldering iron and caps do the same. And pressure from flexing the board.

In short, PS3 be hard bro.

 

[BadaBoomBadaBing]

Would you please post the errorlog? Are you sure about the 3033? What step number (full code not just the last 4 digits).

3034 is confirmation of a GPU fault ATP. Doing and redoing the caps is a hampster wheel. The 1002's are likely because the caps are not good or installed properly. But even if they were, the 3034 is intermittently showing up because of thermomechanical stresses and changes in impeedance that briefly allow it to pass bittraining, a calibration procedure for CPU/SB/GPU communication in which changes in impeedance can have a large effect on the whether or not it completes sucessfully. Just heating the console can be enough to get it to pass. Which is why hairdryer tricks worked, the soldering iron and caps do the same. And pressure from flexing the board.

In short, PS3 be hard bro.

Sorry, it's been a hot minute and I got confused about the error code. It was a 4002 and 3034.

Here is the full log:

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[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
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[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]: 0xa0404002
Press Ctrl+C to exit
>$ shutdown
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xa0231002, clock:0xffffffff
ofst[ 32]:err_code:0xa0231002, clock:0xffffffff
ofst[ 36]:err_code:0xa0231002, clock:0xffffffff
ofst[ 40]:err_code:0xa0231002, clock:0xffffffff
ofst[ 44]:err_code:0xa0231002, clock:0xffffffff
ofst[ 48]:err_code:0xa0101002, clock:0xffffffff
ofst[ 52]:err_code:0xa0231002, clock:0xffffffff
ofst[ 56]:err_code:0xa0231002, clock:0xffffffff
ofst[ 60]:err_code:0xa0404002, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0901001, clock:0xffffffff
ofst[ 72]:err_code:0xa0404002, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0231002, clock:0xffffffff
ofst[ 84]:err_code:0xa0231002, clock:0xffffffff
ofst[ 88]:err_code:0xa0093004, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0404002, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0404002, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0404002, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0404002, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[  0]:err_code:0xa0404002, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0404002, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0404002, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff

I think you're spot on about the heat from changing reworking the capacitors. I now realize these 2 codes seem to disappear after messing with the capacitors, and now the console hasn't been touched in days they're back.

 

[AdriHime]

can syscon logs be cleared through software or only using the script?

 

[ShazAu]

Hi, can you please help me diagnose my PS3SS model CECH-4202C? I was playing some GT5 and it randomly powered off after completing a race. Now it won't turn back on.
Here is what is happening:

• Connect power cable to wall, get red standby light.
• Press power button, green light will come on for 10 or more seconds, no display output
• PS3 will power itself off, no standby light.

Initially I thought it was a power supply fault and started there but Reddit showed me the Syscon way and here I am! Here's the errorlog:

>$ errlog
00000000
# CODE     CLOCK
# A0805FFF 2DB5E95C
# A0805FFF 2DB5E682
# A0805FFF 2DB5E544
# A0805FFF 2DB5E352
# A0805FFF 2DB5E319
# A0801601 2DB5E2CB
# A0801701 2DB5E2CA
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

Here's the output from the other commands shown in the video:

>$ bringup
00000000
# [SSM] Bringup Start.
# [PowSeq] Error:A101
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
OK 00000000
# [PowSeq] Error:A101
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ version
00000000
# Sherwood Version = 2.21.0

I don't have an option for becount so I wasn't able to include it. Any help would be appreciated. Thanks

 

[RIP-Felix]

I don't have an option for becount so I wasn't able to include it. Any help would be appreciated. Thanks

r 800 8

post the output here and I'll tell you.

I think that's a CPU or GPU fault. Like a BGA defect if there was a fall, delid attempt, rough handling. Or accumulated electromigration damage. Thank you for the report. Can you provide any more context or history about the console?

• What else have you tried? New HDD, safe mode options?
  
• Is there any case damage and has it been opened before (is the seal intact)? If opened, what was done. Paste, rework, etc.

 

[ShazAu]

Hi,
This was still factory sealed, I imagine it would have A LOT of power on hours, it was previously used by the public in a community complex. I can't imagine it saw much rough handling though. The case was a bit dusty and faded but no big scratches or anything and the CD door still works well. It hadn't been used for a year or so, I recently got it out and played a few hours on it and it just shut itself off during gameplay.

I did previously try starting it in safe mode but I couldn't get it to work. I haven't tried another hard disk but I did try starting it without a hard disk installed.

>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 09 9C 09 78 00 89 D5 92

 

[moflih.morad]

Hi guys am new to this forum, after having new hopes watching Felix on Youtube
first i regret ps3s i've tossed away .....

i got another ps3 COK-002 PAL
i connected the Syscon as prescribed, and got to internal mode.
One error filled the entire errlog
ofst[108]:err_code:0xa0a02031, clock:0xffffffff
and so on.
- According to devWiki its related to RSX Thermal
becount ---------------------------------------------------
Bringup : 3389 times
Shutdown: 1973 times
Power-on: 90day 13hour 01min 55sec
[mullion]$
- seeing that this ps3 worked for 90 days only i did not suspect a BGA problem
according to Felix in this forum
"2130/31 are Thermal monitor voltage issues and is usually register in standby when the thermonitors are powered up and checked. Like if the MB temp was too hot near the thermal monitor, which could indicate a short. Can happen is the monitor is damaged from a reflow for example. Instead of allowing power to switch on the 12v circuit, it refuses to go anyfurther and you get an error in standby after plugging in."
i cleared the errlog, and this time i just flipped the power rocker without bringing up the ps3, and indeed the errlog was full of 2031 err again, so felix was right this error registers immediatly in standby mode.
i ruled out the RSX since this ps3 has low hour count.
now i have a culprit in mind the RSX thermonitor IC2101 and the thermal-check circuit involved
so i checked every resistance in this circuit all good
R4086, R4030, R4031, R4084, R4083, R2101, R2102, R2140.
tested the 3.3v_thermal was good
tested /SYS_THR_ALERT was high
So the circuit was all good no shorts.
the circuit was an SMBus serial communication mastered by the SYSCON and thermonitors as Slaves
psdevwiki.com/ps3/Thermal.
the thermonitor or Sensor of the RSX is a ADT7461A (IC2101) from analog devices i found the Datasheet for it and according to the pinout i have connected my I2C(compatible SMBUS) decoder to
THR_I2C_SDA (for data on pin 7)
THR_I2C_SCL(for clock on pin 8)
and flipped the power rocker
decoder captured stream of Data communication between syscon and 5 devices one of them was not responding to syscon requests with address 0x4D.

according to psdevwiki.com/ps3/Thermal. again this address is given to the RSX thermal sensor.....
so i got the iron out desoldered IC2101 and tried another IC from another junk PS3
Guess what! the error was gone, now the PS3 starts with no YLOD.

YOUR SYSCON KNOWS EXACTLY WHICH SENSOR IS NOT RESPONDING AND RAISE AN ERROR...

 

[RIP-Felix]

>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 09 9C 09 78 00 89 D5 92

2460 bringups | 2424 shutdowns | 104 days of uptime

 

[RIP-Felix]

Bringup : 3389 times
Shutdown: 1973 times
Power-on: 90day 13hour 01min 55sec

...i ruled out the RSX since this ps3 has low hour count.

Hold your horses there wipper snapper! That console has a difference between bringups and shutdowns.

3389 - 1973 = 1416 unaccounted for sessions.

It gets better! We can extrapolate the estimated actual usage time based on the number of stutdowns. Math time!

90 days of recorded use / 1973 recorded sessions = 0.045615813 days/session
0.045615813 days/session X 3389 actual sessions = 154.59 days of estimated actual usage

Right inside the 150-300 day average for 90nm GPU failure.

BUT WAIT! THERE'S MORE!!!

A0 is an error occurring in standby and filling the errorlog, erasing older errors. So you don't know if there was a 3034 before the 2031. Since the PS3 is in an error state, you cant power on. Since you can't power on, The RSX can't initialize. And since the defective GPU can't initialize it can go through BitTraining. Which is when another 3034 would occur. The Power On Self Test doesn't get far enough for use to see if your GPU is ok.

In other words, even if you fix the Thermal monitor issue, there can be a 40 3034 waiting for you.

And it gets better folks!

... I desoldered IC2101 and tried another IC...PS3 starts with no YLOD

Ok. Now this is were I have to advise you manage expectations and think through what you did to remove and replace the Thermal Monitor. It's right next to the RSX isn't it? If you used hot air to remove it, you have essentially performed a "heat test." That can temporarily cause false positive results. So curb your enthusiasm and get to work ruling that out.

Thermal cycle the console under load for 25mins-1 hour to thoroughly heat up. Then turn off for 1 hour to fully cool. Repeat that about 30 times before calling it. My friend used a hot air station directly on the die of a suspected bump defect 90nm RSX and it survived 25 of these thermal cycles before failing again. There is a reason the reflows, reballs, heat tests, towel tricks...all fooled people. For many years.

Be cautiously optimistic, but fully expect that tomorrow it doesn't turn on. Don't go out and sell it working at full price on eBay just to have it fail on the poor sap that buys it.

To be clear. Congratulations on diagnosing and repairing what you diagnosed. So far you have followed the bread crumbs correctly. You just need to take it past the finish line. Kind regards and best of luck to you!

 

[moflih.morad]

Hey Felix great analysis as always been following your guidance on this forum and surely got results, again you are right

After switching on the ps3 for 5min, fan spinning normally there was no image on hdmi nor AV (but tv detects an input)
3 beeps YLOD and following error happened :
ofst[ 0]:err_code:0xa0801701, clock:0x0b48869b 2005/12/31 00:00:27
SYSCON shuts down console seeing BE_ATTENTION signal high and throw 1701
ofst[ 4]:err_code:0xa08014ff, clock:0x0b48869b 2005/12/31 00:00:27
SYSCON indicating the cause as 14FF (Unresolved Checkstop errors)
ofst[ 8]:err_code:0xa0801001, clock:0x0b48869b 2005/12/31 00:00:27
POWER ERROR on CELL, maybe the unexpected shutdown caused by error 1701
ofst[ 12]:err_code:0xa0801701, clock:0x0b48869b 2005/12/31 00:00:27 AGAIN ??? but this time it shows no reason why!
ofst[ 16]:err_code:0xa0022110, clock:0x0b4886cd 2005/12/31 00:01:17 And after that we get a Clock subsystem error!
--------------on POWER on again-----------------------------
ofst[ 20]:err_code:0xa0022110, clock:0xffffffff
ofst[ 24]:err_code:0xa0022110, clock:0xffffffff
ofst[ 28]:err_code:0xa0022110, clock:0xffffffff

PS3 YLOD again (what needs to be done according to Wikidev)
error 2110 (Clock Subsystems) remains while the others not
- Check fuse F6001 (check for the reason why this fuse is blown)
- check 5V_MISC for shorts
- check C6019 or C6020 if they short
- check IC6020 supplys +3.3v_MK_Vdd to the clock generator (IC5001)

...to be continued

PS: i shall never sell a console in this state, or any other, am looking for my ultimate ps3.
PS: for desoldering the IC i used flood method with the solder iron , i didn't use the heat gun, i dont get any result with it, the ps3 seems to sink all the heat no matter how much time a put in it so i did not use it on this one att all, but maybe someone did, because it was not sealed.

 

[ba114]

Just got a CECHA00 in the mail to start tinkering with.
Pulled it down, and whilst it has been opened, the daig points were syscon were untouched.

Pulling it down further it appears to still be on the original thermal paste, there was a lot of dust on the CELL and RSX side of the board.

I hooked up to the syscon and dumped it:

errlog
ofst[ 68]:err_code:0xffffffff, clock:0x1f498785  2016/08/19 09:01:57
ofst[ 72]:err_code:0xa0801002, clock:0x1f49878d  2016/08/19 09:02:05
ofst[ 76]:err_code:0xa0801002, clock:0x1f498794  2016/08/19 09:02:12
ofst[ 80]:err_code:0xa0801002, clock:0x1f49879b  2016/08/19 09:02:19
ofst[ 84]:err_code:0xa0801002, clock:0x1f4987a2  2016/08/19 09:02:26
ofst[ 88]:err_code:0xa0801002, clock:0x1f4987b2  2016/08/19 09:02:42
ofst[ 92]:err_code:0xa0801002, clock:0x1f4987b8  2016/08/19 09:02:48
ofst[ 96]:err_code:0xa0801002, clock:0x1f4987bf  2016/08/19 09:02:55
ofst[100]:err_code:0xa0801002, clock:0x1f4987cf  2016/08/19 09:03:11
ofst[104]:err_code:0xa0801002, clock:0x1f4987e0  2016/08/19 09:03:28
ofst[108]:err_code:0xa0801002, clock:0x1f4987ee  2016/08/19 09:03:42
ofst[112]:err_code:0xa0801002, clock:0x1f4987ff  2016/08/19 09:03:59
ofst[116]:err_code:0xa0801002, clock:0x1f498812  2016/08/19 09:04:18
ofst[120]:err_code:0xa0801002, clock:0x1f498823  2016/08/19 09:04:35
ofst[124]:err_code:0xa0801002, clock:0x1f498835  2016/08/19 09:04:53
ofst[  0]:err_code:0xa0801002, clock:0x1f498847  2016/08/19 09:05:11
ofst[  4]:err_code:0xa0801002, clock:0x1f49886c  2016/08/19 09:05:48
ofst[  8]:err_code:0xa0801002, clock:0x1f5bf6b7  2016/09/02 08:37:11
ofst[ 12]:err_code:0xa0801002, clock:0x1f5d275a  2016/09/03 06:16:58
ofst[ 16]:err_code:0xa0801002, clock:0x1f5d2762  2016/09/03 06:17:06
ofst[ 20]:err_code:0xa0801002, clock:0x1f5d276f  2016/09/03 06:17:19
ofst[ 24]:err_code:0xa0801002, clock:0x1f5d2f7e  2016/09/03 06:51:42
ofst[ 28]:err_code:0xa0801002, clock:0x1f5d2fa1  2016/09/03 06:52:17
ofst[ 32]:err_code:0xa0801002, clock:0x1f5d3008  2016/09/03 06:54:00
ofst[ 36]:err_code:0xa0093004, clock:0x2b42c229  2022/12/31 09:49:29
ofst[ 40]:err_code:0xa0093004, clock:0x2d523799  2024/02/04 11:55:05
ofst[ 44]:err_code:0xa0093004, clock:0x2d5237a7  2024/02/04 11:55:19
ofst[ 48]:err_code:0xa0093004, clock:0x2d8eb154  2024/03/21 08:50:28
ofst[ 52]:err_code:0xa0093004, clock:0x2d8eb159  2024/03/21 08:50:33
ofst[ 56]:err_code:0xa0093004, clock:0x2d8eb163  2024/03/21 08:50:43
ofst[ 60]:err_code:0xa0093004, clock:0x2d8eb390  2024/03/21 09:00:00
ofst[ 64]:err_code:0xa0093004, clock:0x2dc4ac55  2024/05/01 07:31:33

So it starts with a lot of a0801002 errors which kind of looks like maybe the tokins, but then i assume the owner before me tried the device 6 years later and its now throwing an RSX power error a0093004 much earlier in the boot sequence. cofirmed with a bringup command

bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004
bringup
Do nothing. (FatalDown State)
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
bringup
Do nothing. (FatalOff State)

Am i on the right path to say the first place to start on this device is to replace the tokins based on this?

A certain range of voltage ripple and noise can trigger this error before it becomes severe enough to cause an RSX_VDDC Power Failure (3004).

 

[repofmady]

hello i am brand new to this following felix's windows guide on youtube. i have gotten as far as changing 3961 and then attempting to get into internal mode. i am having a similar problem to chiefhunnablunts on page 13/14 where i get 'scopen response invalid' when attempting to auth after putting in cxrf. i tried the thing of turning off/on again, gnd is definitely connected to diag, what am i doing wrong thanks

it's a COK-002 from a cechc03

anyone know about this? i just redid the solder joints and getting the same error. im getting the right lights and beeps as shown in the vid, it successfully set the 3961 value

 

[Ganjo]

What MB revisions were those?

The missing cap was a COK-001
PS6001 was on the COK-002

Also, Is there a way to clear syscon logs? Ive been searching and found nothing. Some people said errlogclr or errlog clear but nothing I found works