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

[Pacorretaco]

First time posting logs over here, finally!! lol

Well, I mentioned somewhere that I had a couple of mobos having GLOD issues, those that @RIP-Felix and @vyktormvmpay25 call "special GLOD". I didn't find anything wierd (until now) on these mobos, it wasn't the Panasonic HDMI this time provoking this GLOD, and I have to mention, these two act different.
A doubt that I have is if powerstate only shows you the stages that the CELL turned on, or if it's really trying to show you everything that should be running without issue, because I get WLAN: ON even when the console is turned off, and both are missing the wifi module. If this is a false positive, it really sucks. Because I don't know if both SB are dead, or if some of the ram modules are, this due the string I get on becount "![ERROR]: 0xb000200d (FATAL) XDR Link not initilized."

Well, to summary this: MSX/GLOD/turns off at 45 seconds without red light after boot.

becount: #![ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.

Spoiler: MSX

>$ ERRLOG
00000000
# CODE CLOCK
# A0801005 FFFFFFFF No energy abruptly
# A0801004 FFFFFFFF Power AC/DC 1004
# A0805FFF FFFFFFFF Turns off by itself 5FFF
# A0003001 FFFFFFFF 12v Power Failure 3001
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 264717AE
# A0805FFF 26471768
# A0805FFF 26431EDA
# A0805FFF 26431EA3
# A0805FFF 261783C8
# A0805FFF 26177860
# A0805FFF 261777DA
# A0805FFF 2617775A
# A0805FFF 2477716B
# A0805FFF 2477711F



>$ ERRLOG
00000000
# CODE CLOCK
# A0801200 FFFFFFFF
# A0801005 FFFFFFFF
# A0801004 FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 264717AE
# A0805FFF 26471768
# A0805FFF 26431EDA
# A0805FFF 26431EA3
# A0805FFF 261783C8
# A0805FFF 26177860
# A0805FFF 261777DA
# A0805FFF 2617775A
# A0805FFF 2477716B

>$ becount
F0000003
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [UCMD] Unknown command.

>$ bringup
00000000
# [SSM] Bringup Start.

>$
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.2.0
#!(Build ID: 4809,49233,
#!Build Date: 2012-06-12_21:19:37)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!

>$ powerstate
FFFFFFFF Answer length
>$ powerstate
00000000
#!0000
#!0000
#!
#!PTC_DUMP
#!0000
#!0000
#!0000
#!0000
#!0000
# ATA :ON
# PCI :OFF
# PCIex:OFF
# RSX :ON
# GDDR :ON
# XDR :ON
# EURUS:ON
# SB :ON
# LAN :ON
# WLAN :ON
OK 00000000
#!0000
#!0000
#!0a0c
#!0a70
#!0000
#!0000
#!09c3
#!0a2e
#!0000
#!0000
#!09d0
#!0a31
#!0000
#!0000
#!09c5
#!0a31
#!0000
#!0000
#!09cd
#!0a34
#!0000
#!0000
#!0a0f
#!0a73
#!0000
#!0000
#!09f5
#!0a5a
#!0000
#!0000
#!09f2
#!0a54
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!09eb
#!0a52
#!0000
#!0000
#!09f5

>$
00000000
#!0a5c
#!0000
#!0000
#!09bd
#!0a24
#!0000
#!0000
#!09ca
#!0a31
#!0000
#!0000
#!09c7
#!0a31
#!0000
#!0000
#!09e1
#!0a42
#!0000
#!0000
#!09d4
#!0a38
#!0000
#!0000
#!09eb
#!0a4c
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0a0a
#!0a74
#!0000
#!0000
#!09e5
#!0a4d
#!0000
#!0000
#!09e4
#!0a4f
#!0000
#!0000
#!09e1
#!0a50
#!0000
#!0000
#!09eb
#!0a54
#!0000
#!0000
#!0a12
#!0a78
#!0000
#!0000
#!09d9
#!0a39
#!0000
#!0000
#!0a0b
#!0a72
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0a19
#!0a80
#!0000
#!0000
#!0a16
#!0a7d
#!0000
#!0000
#!09da
#!0a43
#!0000
#!0000
#!09e6
#!0a52
#!0000
#!0000
#!09e0
#!0a3e
#!0000
#!0000
#!0a23
#!0a93
#!0000
#!0000
#!0a12
#!0a78
#!0000
#!0000
#!0a25
#!0a92
#!0000
#!0000
#!0000
#!0000
#!
#!MIC_DUMP
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!3200000000000000
#!0000000000000000
#!0000000000000000
#!0000000fffffff80
#!0000000000012000
#!0000000000100000
#!8000000000000000
#!0000000000000000
#!0800000000000000
#!0800000000000000
#!0000000000000000
#!0000000000000000
#!ffc0000000000000
#!6040000000000000
#!00e0000000000000
#!6284055ad6b00000
#!5d70000000000000
#!7180021000000000
#!0a963d6000000000
#!edd61229594ba6b4
#!0000000000000000
#!1b87000000000000
#!0481000000000000
#!0100000000000000
#!c800000000000000
#!0000000000000000
#!0000100000000000
#!0000000000000000
#!1b87000000000000
#!0481000000000000
#!0100000000000000
#!c800000000000000
#!0000000000000000
#!0000100000000000
#!0000000000000000
#!6040000000000000
#!00e0000000000000
#!6284055ad6b00000
#!5d70000000000000
#!7180021000000000
#!0a963d6000000000
#!edd61229594ba6b4
#!0000000000000000
#!8000000000000000
#!0000000000000000
#!0800000000000000
#!0800000000000000
#!0000000000000000
#!0000000000000000
#!ffc0000000000000
#!0611017000000000
#!4000000000000000
#!7cfe000000000000
#!e1c0000000000000
#!0000000000000000
#!0000000000000000
#!0000fd4000000000
#!0000028000000000
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!0000000000000013
#!0000000000000000
#!
#!XIO_DUMP
#!0001
>$ errlog
00000000

# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0801200 FFFFFFFF
# A0801200 FFFFFFFF
# A0801005 FFFFFFFF
# A0801004 FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 264717AE
# A0805FFF 26471768
# A0805FFF 26431EDA

>$
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.2.0
#!(Build ID: 4809,49233,
#!Build Date: 2012-06-12_21:19:37)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.
#!ITC_DUMP
#!0000

PQX/GLOD/Infinite green light until turn off.

becount: #![ERROR]: 0xb000200d (FATAL) XDR Link not initilized.

Spoiler: PQX

Auth successful
>$ errlog
00000000
# CODE CLOCK
# A0801200 FFFFFFFF 1200 (Thermal CELL)
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF Turns off by itself 5FFF
# A0801005 FFFFFFFF
# A0801002 FFFFFFFF 1002 (Power RSX)
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF 12v Power Failure 3001
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 0F5BBB47
# A0805FFF 0F5BBA7F
# A0805FFF 0E8F81EB
# A0805FFF 0E8F745A
# A0805FFF 0DCF1FEF
# A0805FFF 0DCF1F2E
# A0805FFF 0DCF1A78
# A0805FFF 0DCED6E3
# A0805FFF 0DCED5C3
# A0805FFF 0DCED53C
# A0805FFF 0DCED4B2
# A0805FFF 0DCED415
# A0805FFF 0DCDF454
# A0805FFF 0DCDF3BB
# A0805FFF 0DCDF26E
# A0801601 0DC82D03 BE Livelock Detection 1601
# A0801701 0DC82D02 BE Livelock Detection 1701
# A0802031 0CFBCE91 2031 (Thermal Sensor, RSX)
# A0402131 0CF51B37 2131 (Thermal Sensor, RSX)
# A0402130 0CF51B37 2130 (Thermal Sensor, CELL)
# A0402131 0CF51B34

>$ powerstate
00000000
# ATA :OFF
# PCI :OFF
# PCIex:OFF
# RSX :OFF
# GDDR :OFF
# XDR :OFF
# EURUS:OFF
# SB :OFF
# LAN :OFF
# WLAN :ON

>$ bringup
00000000
# [SSM] Bringup Start.

>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# [UCMD] Unknown command.

>$ powerstate
00000000
# ATA :ON
# PCI :OFF
# PCIex:OFF
# RSX :ON
# GDDR :ON
# XDR :ON
# EURUS:ON
# SB :ON
# LAN :ON
# WLAN :ON

>$ becount
F0000003
# [UCMD] Unknown command.

>$ shutdown
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

>$ becount
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![ERROR]: 0xb000200d (FATAL) XDR Link not initilized.
#!ITC_DUMP
#!0000
#!0000
#!0000
# [UCMD] Unknown command.
NG F0000003
#!0000
#!0000
--------------------------------------------
>$ errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0801005 FFFFFFFF
# A0801002 FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 0F5BBB47
# A0805FFF 0F5BBA7F
# A0805FFF 0E8F81EB
# A0805FFF 0E8F745A
# A0805FFF 0DCF1FEF
# A0805FFF 0DCF1F2E
# A0805FFF 0DCF1A78
# A0805FFF 0DCED6E3
# A0805FFF 0DCED5C3
# A0805FFF 0DCED53C
# A0805FFF 0DCED4B2
# A0805FFF 0DCED415
# A0805FFF 0DCDF454
# A0805FFF 0DCDF3BB
# A0805FFF 0DCDF26E
# A0801601 0DC82D03
# A0801701 0DC82D02
# A0802031 0CFBCE91
# A0402131 0CF51B37
# A0402130 0CF51B37

>$ bringup
00000000
# [SSM] Bringup Start.

>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# [UCMD] Unknown command.

Something to notice, both have almost the same errors on that XDR stage, but they act different. I wanted to change those SBs but it seems rams could be the issue mainly (which they're northbdrige in this case), so what do you thing people?

BTW, both RSX/CELL on both mobos warm like normal. When I had a GLOD due that HDMI chip being damaged, I had no boot on CELL, and question would be, why this fault blocked the CELL?

Nice to see you "peeking into the matrix" as you say, hehehehe. Well done. I'm sure it wasnt that hard.

GLOD is normally not as easy to troubleshoot, but you have one of the cases where the syscon has indeed identified and reported the issue.

XDR Link not initialized:
You have a problem between the CPU and the XDR Ram (Ram next to CPU)... This is known to cause a big GLOD yes.

It could be one or more of the ram modules, it could be the CPU itself or somewhere in between, one of their connections.
We have seen this as a result of delid damage for example, where people end up scratching the traces on the CPU corner that go to the XDR RAM... Obviously getting this error.

Good luck

 

[Dynamik1]

The 80 1802 is an RSX initialization error (1802) occuring during the power on state (step# 80). I wrote some about it here. Your log called it, "RSX Interrupt : Detected!"It even provides details, "RSX SY_IES register (0x0008) = 0x4000." @M4j0r @sandungas are the programming gurus, I'm not sure about memory addresses and such. So manybe they can provide more insight about what it's complaining about there.

When 1802s occur at step# 20, I associate them with a dead RSX. That's because step# 20 is when the RSX is first initialized. If it doesn't initialize then, it's dead. However, your 1802 is only occuring after the console has booted (step# 80) and is associated with the BE Attention (1701) alarm raised when a Checkstop error (14FF) occured. That makes sense because the CPU couldn't continue with it's process when the RSX interrupt occured.

We've seen this error a lot. The common story between them was the console was on at the time the YLOD occurred. All subsequent attempt to start the console resulted in a GLOD with subsequent 1601/1701 errors, or a YLOD within 2 seconds. SYSCON errors usually show one A0801601/A0801701 occurring at the same timestamp, followed thereafter by 3034/4xxx errors for all subsequent attempts to PWR it on. Or it'll GLOD and throw more 1701/1601's or 14FF's. I think this means there is a precarious BGA defect teetering on the edge of breaking and it'll soon switch back to 3034/4xxx like the others. But that's a guess.

Since your 3034/4432 errors appeared just as predicted, I would suspect the RSX has either bad BGA/bumps or died. We can test that theory by ohm testing the following voltage lines and seeing if they all check out...

These were taken from a board that's currently working, althought not thoroughly tested.

If any of those read close to a short, then you'll need to remove and replace the RSX. If they all test fine, you may be able to fix it with a reball. Just ohm test the RSX off the board to be sure it hasn't died before balling it. But if you have to remove the RSX anyway, you may as well just replace the 90nm RSX with a more reliable 65nm or 40nm (now that we know how to do it).

@RIP-Felix, many thanks for the very quick response. i have finally got around to measuring the values on my board and the measurements are as follows:

RSX_VDDIO - 76.3 Ohms
FBVDDQ - 140.1 Ohms
RSX_PLL - 5.82 Ohms
RSX_VDDC - 4.3 Ohms
VDDR - .592 K Ohms (a bit worrying maybe?)
YC_RC_VDDIO - 12.8 Ohms
BE_VDDC 6.6 Ohms
VDD_MEM - 16.1 Ohms
BE_PLL - 6.47 M Ohms
Mc2_VDDIO - 37.8 Ohms
VDDA - (right side) - 4.1 Ohms (left side) - 4.2 Ohms

So the only main ones that stand out are:

RBVDDQ, RSX_VDDC, VDDR, BD_VDDC, BE_PLL and MC2_VDDIO

BTW my board is a COK-002 so don't know if the resistance might be different as the main chip on the far left that i'm guessing does the PS1/PS2 emulation has a black chip instead. Or does this still co-inside with a faulty RSX?

I do appreciate all the information you have provided and would appreciate more info, i would really like to get this fixed even if i was to get the mod chip done instead for reliability.

If it is a faulty RSX, would you recommend anyone to do the job and how much roughly would it cost?. I would love to do it myself but at the moment i cant spend lots of money on a BGA reballing station yet and never done it before so wouldn't want to mess things up. plus i have now possibly 7 Backward Compatible PS3s plus a couple of non BC models that all would need to have this job done. I would not want to throw these pieces for gold dust in the skip plus i would want to keep them for the family and maybe sell a couple. (i'm a bit of a PS3 PHAT console hoarder lol)

Thanks you again for all of your kind wisdom. I wish i knew as much about these as you do (maybe you could teach me LOL)

 

[Workz_777]

@RIP-Felix, many thanks for the very quick response. i have finally got around to measuring the values on my board and the measurements are as follows:

RSX_VDDIO - 76.3 Ohms
FBVDDQ - 140.1 Ohms
RSX_PLL - 5.82 Ohms
RSX_VDDC - 4.3 Ohms
VDDR - .592 K Ohms (a bit worrying maybe?)
YC_RC_VDDIO - 12.8 Ohms
BE_VDDC 6.6 Ohms
VDD_MEM - 16.1 Ohms
BE_PLL - 6.47 M Ohms
Mc2_VDDIO - 37.8 Ohms
VDDA - (right side) - 4.1 Ohms (left side) - 4.2 Ohms

So the only main ones that stand out are:

RBVDDQ, RSX_VDDC, VDDR, BD_VDDC, BE_PLL and MC2_VDDIO

BTW my board is a COK-002 so don't know if the resistance might be different as the main chip on the far left that i'm guessing does the PS1/PS2 emulation has a black chip instead. Or does this still co-inside with a faulty RSX?

I do appreciate all the information you have provided and would appreciate more info, i would really like to get this fixed even if i was to get the mod chip done instead for reliability.

If it is a faulty RSX, would you recommend anyone to do the job and how much roughly would it cost?. I would love to do it myself but at the moment i cant spend lots of money on a BGA reballing station yet and never done it before so wouldn't want to mess things up. plus i have now possibly 7 Backward Compatible PS3s plus a couple of non BC models that all would need to have this job done. I would not want to throw these pieces for gold dust in the skip plus i would want to keep them for the family and maybe sell a couple. (i'm a bit of a PS3 PHAT console hoarder lol)

Thanks you again for all of your kind wisdom. I wish i knew as much about these as you do (maybe you could teach me LOL)

Will be interesting what Felix makes of your readings, one thing you don't have is any 0.01Ω readings so that's good. A dead RSX would read 0.01Ω for (RSX_VDDC).

 

[marciolsf]

Ok, so I've been doing some digging on that RSX_VDDR line. Just out of curiosity, I tracked down the voltage path -- this is supposed to be feeding 1.2V... but in my case, it isn't, i'm only getting about 10mv or so.

I then tracked the line (thanks to @RIP-Felix 's diagrams, which saved me a ton of time), all the way back to Pin 1 of IC6003, which generates +5V_Misc. The documentation for COK-001 says that JL9644 should be a test point for +5_Misc, but in my board, all those 5 resistors (R6037, 6042, 6048, 6049 and 6046) are not present... so maybe that explains why that test point too, is only getting ~10mv. I then tested pin 1 of IC6003, and that also only outputs 10mv.

In the schematics, the powergood pin on IC6003 isn't connected. Is there anything else maybe that isn't activating this chip? For some reason, it's just not generating the +5V it should, so maybe syscon is telling it not to? I don't see how, but I haven't attempted to track that connection down yet.

 

[RIP-Felix]

@RIP-Felix, many thanks for the very quick response. i have finally got around to measuring the values on my board and the measurements are as follows:

RSX_VDDIO - 76.3 Ohms
FBVDDQ - 140.1 Ohms
RSX_PLL - 5.82 Ohms
RSX_VDDC - 4.3 Ohms
VDDR - .592 K Ohms (a bit worrying maybe?)
YC_RC_VDDIO - 12.8 Ohms
BE_VDDC 6.6 Ohms
VDD_MEM - 16.1 Ohms
BE_PLL - 6.47 M Ohms
Mc2_VDDIO - 37.8 Ohms
VDDA - (right side) - 4.1 Ohms (left side) - 4.2 Ohms

So the only main ones that stand out are:

RBVDDQ, RSX_VDDC, VDDR, BD_VDDC, BE_PLL and MC2_VDDIO

BTW my board is a COK-002 so don't know if the resistance might be different as the main chip on the far left that i'm guessing does the PS1/PS2 emulation has a black chip instead. Or does this still co-inside with a faulty RSX?

I do appreciate all the information you have provided and would appreciate more info, i would really like to get this fixed even if i was to get the mod chip done instead for reliability.

If it is a faulty RSX, would you recommend anyone to do the job and how much roughly would it cost?. I would love to do it myself but at the moment i cant spend lots of money on a BGA reballing station yet and never done it before so wouldn't want to mess things up. plus i have now possibly 7 Backward Compatible PS3s plus a couple of non BC models that all would need to have this job done. I would not want to throw these pieces for gold dust in the skip plus i would want to keep them for the family and maybe sell a couple. (i'm a bit of a PS3 PHAT console hoarder lol)

Thanks you again for all of your kind wisdom. I wish i knew as much about these as you do (maybe you could teach me LOL)

Recheck RSX_PLL. 5.82 Ohms is bad, but maybe you meant to write 5.82k. If that is reading anything less than the kilo ohms range, that explains your 1802. At which point there are 2 possabilities. Either the RSX is dead or the voltage line that feeds RSX_PLL is bad. You can test with a multimeter to see if it gets voltage when you power on. If not, then you can try replacing the VRM (driver and MOSFET). And checking nearby SMD's for shorts. Otherwise the RSX needs replaced.

MC2_VDDIO is sus as well. Double check it.

 

[RIP-Felix]

Ok, so I've been doing some digging on that RSX_VDDR line. Just out of curiosity, I tracked down the voltage path -- this is supposed to be feeding 1.2V... but in my case, it isn't, i'm only getting about 10mv or so.

I then tracked the line (thanks to @RIP-Felix 's diagrams, which saved me a ton of time), all the way back to Pin 1 of IC6003, which generates +5V_Misc. The documentation for COK-001 says that JL9644 should be a test point for +5_Misc, but in my board, all those 5 resistors (R6037, 6042, 6048, 6049 and 6046) are not present... so maybe that explains why that test point too, is only getting ~10mv. I then tested pin 1 of IC6003, and that also only outputs 10mv.

In the schematics, the powergood pin on IC6003 isn't connected. Is there anything else maybe that isn't activating this chip? For some reason, it's just not generating the +5V it should, so maybe syscon is telling it not to? I don't see how, but I haven't attempted to track that connection down yet.

• Those resistors have "XX" next to them, indicating they are not supposed to be populated. So that's fine.
  
• Sabotaging +5v_MISC (SW_0) revealed a 02 2110. So that's one of the first things the SYSCON switches on after turning on. If you're getting that error then you will not get VDDR, because the IC's that produce it aren't powered. VDDR is formed by SW_5_B later in the power on sequence. Interestingly, when we sabotaged +1.7v_MISC, which is what powers Q6200, the MOSFET that produces +1.2V_RSX_VDDR, we didn't get an error code. We got "Fatal Error Requested by OS. "lvl0 not found." I just realized I forgot to add SW_5_B to the list and we haven't sabotaged it yet. So I need to add that one to the list.

So to summarize:
VDDR will only form after you power on the console. And it will only do so if the power on sequence makes it as far as SW_5_B.

 

[marciolsf]

• Those resistors have "XX" next to them, indicating they are not supposed to be populated. So that's fine.
  
• Sabotaging +5v_MISC (SW_0) revealed a 02 2110. So that's one of the first things the SYSCON switches on after turning on. If you're getting that error then you will not get VDDR, because the IC's that produce it aren't powered. VDDR is formed by SW_5_B later in the power on sequence. Interestingly, when we sabotaged +1.7v_MISC, which is what powers Q6200, the MOSFET that produces +1.2V_RSX_VDDR, we didn't get an error code. We got "Fatal Error Requested by OS. "lvl0 not found." I just realized I forgot to add SW_5_B to the list and we haven't sabotaged it yet. So I need to add that one to the list.

So to summarize:
VDDR will only form after you power on the console. And it will only do so if the power on sequence makes it as far as SW_5_B.

interesting! In my case, Im only getting a 40-3430, so Im making at least that far… but past 02-2110, so presumably +5_misc is getting power. I'll have to try and test it again.

IC6002 is a 30-pin package, and seems to be managing a lot of different things. I've found just a tiny bit of info on the wiki, but no pin out documentation or anything. Most voltages seem to be starting from it.

edit: accidentally posted before i was finished writing.

 

[Workz_777]

interesting! In my case, Im only getting a 40-3430, so Im making at least that far… but past 02-2110, so presumably +5_misc is getting power. I'll have to try and test it again.

IC6002 is a 30-pin package, and seems to be managing a lot of different things. I've found just a tiny bit of info on the wiki, but no pin out documentation or anything. Most voltages seem to be starting from it.

edit: accidentally posted before i was finished writing.

When you had the "2110" was the fuse (F6001) o.k in the end?

 

[marciolsf]

When you had the "2110" was the fuse (F6001) o.k in the end?

I damaged F6001 somehow when I was probing the board… lol. Once I replaced the fuse, the 2110 error was gone. This was a while ago.

 

[marciolsf]

Sigh... one mystery solved, at least. My pocket scope's probe was set to 10x, so the voltages were all getting reported all wrong. Once I adjusted the probe, everything checked out! Starting at mains 12v, all the way down to 1.2V for RSX_VDDR on IC6200.

I'm going to probe around some more, but the main question I had (why is resistance so high on RSX_VDDR?) is at least not related to voltage (I didn't really think it was, but wanted to confirm it anyway).

 

[RIP-Felix]

Sigh... one mystery solved, at least. My pocket scope's probe was set to 10x, so the voltages were all getting reported all wrong. Once I adjusted the probe, everything checked out! Starting at mains 12v, all the way down to 1.2V for RSX_VDDR on IC6200.

I'm going to probe around some more, but the main question I had (why is resistance so high on RSX_VDDR?) is at least not related to voltage (I didn't really think it was, but wanted to confirm it anyway).

What is said resistance?

What voltages did you measure?

 

[mohsen136]

@vyktormvmpay25 but start with the easyest thing first, have you checked all this ?
1) remove/replace the capacitor in between D+ and D-
2) remove/replace the resistors in D+ and D-
3) remove/replace the capacitor in V
4) replace the voltage regulator that feeds the 2 thermal monitors (i dont know where is located though)

--------
Yeah, that 2 resistors R3209, R3208 in the COK-002 is what i meant (not marked in your image), the service manual tells that are 0 ohms ?. Can you check in the service manual if the other 2 resistors you marked in your photo are 0 ohms too ?
So... in total are 4 resistors of 0 ohms ?
Then i guess the same rule applyes to the SC UART lines to the service connector

In the testpads Layout 6 (SUR-001, JTP-001, JSD-001, KTE-001) are a bunch
The 3 missing components very close to the connector, in this photo

After that the lines goes into VIAS (holes), and appears at the other side of the motherboard, convenienty aligned to a hole in the metal shield, next to the connector of the antennas
Is neeed to fix the 4 missing components here

And finally... 2 more, located very close to the SB_Tx and SB_Rx testpads (on top of them in this photo)

Hi, I need a photo up to a radius of 5 cm from this part. I need more capacitors on the right side of the photo of SB-RX & SB-TX
Email:[email protected]
thank you

 

[vyktormvmpay25]

https://www.psdevwiki.com/ps3/Motherboard_Revisions

 

[sandungas]

Hi, I need a photo up to a radius of 5 cm from this part. I need more capacitors on the right side of the photo of SB-RX & SB-TX
Email:[email protected]
thank you

The photos have a great quality, are not made by me, i got them from wiki and painted the "blue spheres" in one of them

Where is your doubt ?, in the last one ?
Note the 2 blue spheres have a very short trace that goes to a little "hole" and a copper square... and at the other side another couple of squares
You just need to drop a blob of solder to join the copper squares

Same stuff in the other photos, the missing components are resistors of value 0 ohms (not capacitors), a resistor of 0 ohms doesnt have resistance, is like a wire... but in this case the distance in between the 2 squares is so small that there is no need to use a wire, the blob of solder i mentioned is enought
Just create the solder blob in one of the squares and "drag" the solder tip in direction to the other square to create the bridge

 

[marciolsf]

What is said resistance?

What voltages did you measure?

I measured all resistances based off of the one diagram you put together (the one for RSX_VDDIO, BE_VDDC, etc). All my resistances checked out ok, except for RSX_VDDR. The chart showed it should've been at 303ohms, but mine read 380ohms.

As for voltages, I measured the circuit from 12V down to IC6200:
* both sides of F6001 - 12V
* JL9645 - 3.3V,
* JL 9644 - 5V
* JL9651 - 1.2V

I also checked the test points around IC6201, but I haven't been able to verify those values, particularly SW_5_A, which is tied to the enable pin. I think I'm getting 3.3V? I didn't write it down, I got interrupted during testing

 

[RIP-Felix]

VDDR looks fine. That chart was based on 1 console. I have more data now and will eventually get back around to updating it with the average (median, since this dataset is skewed), +/- 1 or 2 standard deviations.

People can help by posting their readings at those locations and saying whether the console works or not. The more data the better those estimates get.

 

[vyktormvmpay25]

I'll post one dyn001 if goes well or not. In reball process atm.
Edit
First stage passed

Spoiler

Update 2
Just remember I will work on boards with cell vddc line over or around 3 ohms from now.

Spoiler

It will update 3 as few days back as Akiong (botakompong) refered few more points to check in case of special glod as this board was, or AV - no hdmi. In my case this board was special glod and another board I've pulled rsx was dead cell. Any ic over 4.7 in vddc line for me is definitely defective ic.
Second board was 6,2 ohms and didn't bother to much with rest of measurement I just pulled few logs.
Purpose is to add more data while I work on them, otherwise I don't have time give particular support, only David gets because he streaming those real situations.
Update 3
Text file is log from board that had dead cell with 6.2 ohms on vddc line.
Second is photo from working dyn001 after reball it is as reference to any problems for AV-no hdmi. For special glod just exchange rsx and all should be fine unless there is a problem with cell side.
@RIP-Felix quated you just for data collection.
https://s.go.ro/fd5t7rig

Spoiler

 

[marciolsf]

VDDR looks fine. That chart was based on 1 console. I have more data now and will eventually get back around to updating it with the average (median, since this dataset is skewed), +/- 1 or 2 standard deviations.

People can help by posting their readings at those locations and saying whether the console works or not. The more data the better those estimates get.

I thought the goal of the resistance test was to determine how healthy rsx was. Am I mixing up tests?

The other thing I find curious is that this spot with high resistance is in the same general area that the bit training indicates is having issues. The area is not exactly the same, and the resistance is not that much higher than normal (however small to pool sample), but maybe it's just close enough to throw off the calibration and prevent boot up.

 

[RIP-Felix]

I thought the goal of the resistance test was to determine how healthy rsx was. Am I mixing up tests?

The other thing I find curious is that this spot with high resistance is in the same general area that the bit training indicates is having issues. The area is not exactly the same, and the resistance is not that much higher than normal (however small to pool sample), but maybe it's just close enough to throw off the calibration and prevent boot up.

It's not outside the normal range. Currently I have an average of 380 ohms. So your reading is dead on normal.

 

[marciolsf]

It's not outside the normal range. Currently I have an average of 380 ohms. So your reading is dead on normal.

Excellent! That means my RSX is healthy, which is surprising given the amount of hours I put on this thing. I did replace the termal paste about every 18 months, so I'm guessing that helped.