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

[Pacorretaco]

well interestingly enough, i believe i was able to get that knick back where it was supposed to be, as both those errors are now gone and replaced with a 3031 now. this is sure getting interesting.

Hmm, if you notice, yes the 3031 is now "replacing" the 3034 errors but actually that doesn't really mean that those errors are gone.
Because the new 31 3031 is happening "sooner" than the 40 3034 bit training errors. (Prefix 31 vs 40).
In other words it's possible that the 3034 just aren't getting their chance to appear now.

This weird intermittent behavior is puzzling, but one explanation could be yet another type of delid damage (3 in the same board dang). Especially with the RSX, and since it can be seen that it was a battle to wrestle the heatspreader out... Maybe the prying also damaged an already precarious connection under the RSX... This is the most common type of damage but it isn't so obvious or visible.

Vyktor says he prefers doing the delid while RSX totally off the board, for this reason. Everybody has their tricks probably... I put some alcohol and heat to about 80c to soften this "thermal cement"
In any case it's very easy to get "unlucky", and most of the times for no good reason (temperatures already OK most of the time), so I recommend beginners to not even bother delidding RSX. Only CPU needs it in most cases but only with the right tool.

I'm sure many more machines were damaged than saved by "preventative maintenances"... I really doubt these machines are actually failing because of heat problems anyway. RSX is always cool already even in sealed machines, and still can fail or not fail.

Other possibility is that the inner layers of the RSX substrate were damaged too. As you say the top layer doesn't seem to be the problem.

 

[RIP-Felix]

So,
A0404002 = RSX_SPI DI/DO ERROR
A0404102 + A0403034 = Poor BGA solder connections for RSX
A0404411 = ERROR ON RSX SPI (?)

40 3034/4xxx errors all point to RSX/CPU connection issues. Be it BGA, solder bumps, broken traces, internal shorts...whatever is preventing them from communicating. Voltage should be getting to the chips or it would error earlier in the power on sequence than 40. I do find it interesting that your 4002 progressed to a 4102. I suspect that the 102 represents an elevated level of seriousness to the same problem, but we really don't know more than what's on the PDF. We just know those data errors are always associated with the 3034 and that reballing can fix both at the same time, if it works. It won't unless there's a BGA defect. You can have a 3034 without a data error, but I don't recall ever seeing a data error without the 3034.

 

[Bbowes9]

Hmm, if you notice, yes the 3031 is now "replacing" the 3034 errors but actually that doesn't really mean that those errors are gone.
Because the new 31 3031 is happening "sooner" than the 40 3034 bit training errors. (Prefix 31 vs 40).
In other words it's possible that the 3034 just aren't getting their chance to appear now.

This weird intermittent behavior is puzzling, but one explanation could be yet another type of delid damage (3 in the same board dang). Especially with the RSX, and since it can be seen that it was a battle to wrestle the heatspreader out... Maybe the prying also damaged an already precarious connection under the RSX... This is the most common type of damage but it isn't so obvious or visible.

Vyktor says he prefers doing the delid while RSX totally off the board, for this reason. Everybody has their tricks probably... I put some alcohol and heat to about 80c to soften this "thermal cement"
In any case it's very easy to get "unlucky", and most of the times for no good reason (temperatures already OK most of the time), so I recommend beginners to not even bother delidding RSX. Only CPU needs it in most cases but only with the right tool.

I'm sure many more machines were damaged than saved by "preventative maintenances"... I really doubt these machines are actually failing because of heat problems anyway. RSX is always cool already even in sealed machines, and still can fail or not fail.

Other possibility is that the inner layers of the RSX substrate were damaged too. As you say the top layer doesn't seem to be the problem.

Appreciate the detailed response, considering the numerous codes thrown and that being the only area that's damaged, I'm about 90% sure that's causing these errors. The worst part is I actually moved to between the ram chips and the IHS after the failed attempt at the knicked spot. Guess I was a little too late on that.

Appreciate everyone's help!

 

[johs854]

Anyone able to tell me what these errorcodes could mean? its a CECHG04

 

[SkaziChris]

Take a look here first:

github . com / db260179 / ps3syscon

(remove spaces from the address)


A0093004 = RSX_POW_FAIL poweroff state
A0404002 = RSX_SPI DI/DO ERROR
A0403034, A0404402,A0404411 = Poor BGA solder connections for RSX ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )

 

[RIP-Felix]

Anyone able to tell me what these errorcodes could mean? its a CECHG04

Just a quick note. You can hold shift in the CMD terminal and press up to highlight the text. CTRL + C to copy it and then you can paste it into notepad. Then on the top ribbon toolbar there is a "insert" button where you can find "code." That's the easiest way to insert your error codes.

We need more information to piece together the story.

1. What is the console's history? Was it sealed when you got it? What work have you done on it since? Are the Tokins intact? I'm asking about the tokins specifically because error 09 3004 is an RSX VDDC PWR failure and the tokins are part of the filter that provides smooth current/voltage to the RSX core.
2. If you are willing to gain internal access can you post the bringup, becount, and errlog. In that order.

A0093004 = RSX_POW_FAIL poweroff state
A0404002 = RSX_SPI DI/DO ERROR
A0403034, A0404402,A0404411 = Poor BGA solder connections for RSX ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )

Close. 90 is the power off state. He has 09, which is very early in the power on sequence. His would be an instant YLOD (<1s).

While yes, the most common culprit causing 3034/4xxx errors is a BGA defect, it's more accurate to say its an RSX/CPU connection issue. That's because it can be more than the RSX BGA. 95% of the time it is the RSX and maybe 30-60% of the time it's the RSX BGA. But often times it's the RSX RAM or solder BUMP, which require replacement of the RSX. You'll only know for sure after reballing. So the path forward is the same regardless. It's just important to understand that reballing isn't 100%, because it isn't always the BGA. We don't want people to get their hopes up or feel like they wasted their money having the console reballed for nothing. It's a gamble and people should know that going in, so they can manage their expectations.

 

[feng_ye]

Hi. I've been watch this thread for a while and thanks for all the work! I've got error codes from 3 of my boards(2 SEM-001, 1 DIA-001) successfully, which is great.

The DIA-001 board I've got is having 2031 and 2131 errors, according to error code guide it's a RSX thermal sensor(IC2101) error. The error log is:

>$ errlog
errlog
ofst[108]:err_code:0xffffffff, clock:0x28c08b6e  2021/08/31 06:40:46
ofst[112]:err_code:0xa0082131, clock:0x28c08b7a  2021/08/31 06:40:58
ofst[116]:err_code:0xa0902131, clock:0x28c08b7b  2021/08/31 06:40:59
ofst[120]:err_code:0xa0082131, clock:0x28c08b88  2021/08/31 06:41:12
ofst[124]:err_code:0xa0082131, clock:0x28c08b95  2021/08/31 06:41:25
ofst[  0]:err_code:0xa0902131, clock:0x28c08b95  2021/08/31 06:41:25
ofst[  4]:err_code:0xa0a02131, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[  8]:err_code:0xa0a02031, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[ 12]:err_code:0xa0a02031, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[ 16]:err_code:0xa0a02031, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[ 20]:err_code:0xa0a02031, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[ 24]:err_code:0xa0a02031, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[ 28]:err_code:0xa0a02031, clock:0x28c08ba7  2021/08/31 06:41:43
ofst[ 32]:err_code:0xa0082131, clock:0x28c08baa  2021/08/31 06:41:46
ofst[ 36]:err_code:0xa0902131, clock:0x28c08baa  2021/08/31 06:41:46
ofst[ 40]:err_code:0xa0082131, clock:0x28c08bb2  2021/08/31 06:41:54
ofst[ 44]:err_code:0xa0902131, clock:0x28c08bb2  2021/08/31 06:41:54
ofst[ 48]:err_code:0xa0082131, clock:0x28c08bc5  2021/08/31 06:42:13
ofst[ 52]:err_code:0xa0902131, clock:0x28c08bc5  2021/08/31 06:42:13
ofst[ 56]:err_code:0xa0082131, clock:0x28c08bd1  2021/08/31 06:42:25
ofst[ 60]:err_code:0xa0902131, clock:0x28c08bd1  2021/08/31 06:42:25
ofst[ 64]:err_code:0xa0a02131, clock:0xffffffff
ofst[ 68]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 72]:err_code:0xa0a02131, clock:0xffffffff
ofst[ 76]:err_code:0xa0a02131, clock:0xffffffff
ofst[ 80]:err_code:0xa0a02131, clock:0xffffffff
ofst[ 84]:err_code:0xa0a02131, clock:0xffffffff
ofst[ 88]:err_code:0xa0082131, clock:0xffffffff
ofst[ 92]:err_code:0xa0a02131, clock:0xffffffff
ofst[ 96]:err_code:0xa0a02031, clock:0xffffffff
ofst[100]:err_code:0xa0a02031, clock:0xffffffff
ofst[104]:err_code:0xa0a02031, clock:0xffffffff
[mullion]$

And the bringup sequence isn't very interesting. It stops early:

>$ auth
Auth successful
>$ 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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0082131
[ERROR]: 0xa0902131
>$

Luckily on this DIA-001 I can find something wrong with two capacitors seems to be on the power rail of RSX

https://imgur.com/a/mHeb2x9

And according to the service manual, though not DIA-001, the thermal sensor for RSX should be IC2101. On https://www.psdevwiki.com/ps3/Thermal#RSX it says could be a OnSemi or Ti sensor. Later I found this little chip sitting next to RSX:
https://imgur.com/gallery/MThP4cT

My question is, do I need to do any multi-meter for this thermal sensor checking before I order some replacement for the two leaky capcitors? If so, how? After all this is a thermal sensor error but could be well related to power issue. Thanks in advance!

 

[feng_ye]

So I did replace the SMD capacitors(150uf 16V) with some through-hole electrolytic capacitors of 220uf 16V(the best I can find now). Some interesting progress happens.

The YLOD is still there but this time if I call bringup several times, it will eventually enter a long boot sequence(long green light on, then red light blinking). The logs is as follows:

Spoiler: Bringup

>$ 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]: 0xa0512131
[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
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[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
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[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
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

It appears when 2131/2031 error happens too many times, the syscon will just abort the bootloader's booting sequence because it think it's unsafe. This doesn't happen everytime, it will happen after I do bringup several times. I have to confess I didn't have clock battery, or blueray disc drive, or HDD connected but looks like they are all unrelated. I'm still scratching my head figuring out what components/parts went wrong.

 

[Stryder]

Just passing by to thanks you all 4

Paco
Felix
NCS
Vyktor

For all the help you kindly provide for all of us.

Thanks to you it as been my 10th ressurected PS3, time to spare some money for a BGA station.

What I've learn from legit nothing after buying YLOD PS3 while being clueless of how to fix them :

-How to teardown them
-There is ALOT MORE than 2 major revision of PS3 fat
-Nec Tokin ain't always faulty but god those guys suck
-Syscon basic stuff & diagnose YLOD
-How to delid PS3 cell & RSX properly
-How to do proper reflow (so far so good atleast !)
-Install CFW
-Remarry Bluray Drive


I can't thanks you enough for all you've teached me but if by any chance, one day you passes by Strasbourg in France, let me offer you a coffee & some french croissant !

Was my most intense auto-learning month ever.


Love you guys.

 

[RIP-Felix]

So I did replace the SMD capacitors(150uf 16V) with some through-hole electrolytic capacitors of 220uf 16V(the best I can find now). Some interesting progress happens.

The YLOD is still there but this time if I call bringup several times, it will eventually enter a long boot sequence(long green light on, then red light blinking). The logs is as follows:

Spoiler: Bringup

>$ 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]: 0xa0512131
[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
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[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
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[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
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

It appears when 2131/2031 error happens too many times, the syscon will just abort the bootloader's booting sequence because it think it's unsafe. This doesn't happen everytime, it will happen after I do bringup several times. I have to confess I didn't have clock battery, or blueray disc drive, or HDD connected but looks like they are all unrelated. I'm still scratching my head figuring out what components/parts went wrong.

2030-33 have been reported in case of dodgy PWR/EJT daughter board. Try replacing it with another one just in case. Otherwise try soldering the legs of the thermal sensor (IC2101). Also probe the surrounding SMD's for shorts. If neither reveals a problem, try replacing IC2101.

Out of curiosity, how long does it take to YLOD? 10s? 5s?

 

[vyktormvmpay25]

So I did replace the SMD capacitors(150uf 16V) with some through-hole electrolytic capacitors of 220uf 16V(the best I can find now). Some interesting progress happens.

The YLOD is still there but this time if I call bringup several times, it will eventually enter a long boot sequence(long green light on, then red light blinking). The logs is as follows:

Spoiler: Bringup

>$ 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]: 0xa0512131
[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
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[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
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[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
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

It appears when 2131/2031 error happens too many times, the syscon will just abort the bootloader's booting sequence because it think it's unsafe. This doesn't happen everytime, it will happen after I do bringup several times. I have to confess I didn't have clock battery, or blueray disc drive, or HDD connected but looks like they are all unrelated. I'm still scratching my head figuring out what components/parts went wrong.

Ok didn't read full story of that dia001, please use multimeter on power line of rsx vddc and report that resistance values on both cpu and rsx, also have you atemp to delid any of those? I don't suggest pushing any pressure on ic, delid if you feel confident that you don't scratch any of ic surfaces. Ask for advices to delid and read more before any mistakes, we all did it wrong on beginning.
Edit
It looks as thermal panic on both, not to jump on any conclusions but some rsx can die in this case, had different 5 cases that SB debugging was starting and kind of errors were about thermal sensors, all cases been sorted with another rsx even that old defective rsx after reball didn't come with errors after cleaning errlog.

 

[RIP-Felix]

@vyktormvmpay25 would you say that 2030-33 errors are common for later models and that reballing/RSX replacement is the usual fix?

If so, I'll make a note about it in my PDF.

 

[vyktormvmpay25]

@vyktormvmpay25 would you say that 2030-33 errors are common for later models and that reballing/RSX replacement is the usual fix?

If so, I'll make a note about it in my PDF.

Remember those boards with different errors about thermal ic errors, but if reball won't fix and will come back with same errors, different resistance in vddc on board will tell is hardware problem and when SB debugging is starting most often rsx. Now I think he did not delid any of them?
Edit
Earlier errors 17xx/16xx are tied for cpu and I never managed to fix, exchanged cpu set working fine after , even if 1802 said rsx int exchange cpu set fixed board. Can't explain how but seen this in different slim models.
I really like to see people doing different tests on different boards and report problems and fix solutions, is hard enough for me to understand those but I will continue sharing. Not enough knowledge or equipment to know 100 % sure where signals are falling, dame expensive logic analyzer for this bandwidths.

 

[feng_ye]

2030-33 have been reported in case of dodgy PWR/EJT daughter board. Try replacing it with another one just in case. Otherwise try soldering the legs of the thermal sensor (IC2101). Also probe the surrounding SMD's for shorts. If neither reveals a problem, try replacing IC2101.

Out of curiosity, how long does it take to YLOD? 10s? 5s?

Thanks for the quick reply. By the way the motherboard is DIA001 so it doesn't come with a PWR daughter board. There's a small area marked as `TH4001` should be the PWR and EJT module.

Yes I'm thinking of probing the components around this IC2101(marked as T1L, should be TMP441's variant) and the IC pins and compare to the my other boards (SEM-001). So far there're some differences in resistance value if I probe between SCL/SDA and GND. No obvious short found. I'll try digging deeper.

To answer your question, usually when first time from cold boot, it will YLOD in about 1.5 sec just after fan kicks in. However as I mentioned, if I do bringup a few times, it will start a longer boot sequence until YLOD. I used a stopwatch and it is longer than 6.5 sec. Thus the bringup logs are pretty long and a few READCMD happends. And last night I just found a rare 2111 error, along with the usual 2131s, only happened once. Paste the log in case:

Spoiler: Bringup

# First 2111 ERROR
 >$ 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:0x20e7
>$
[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]: 0xa0802131
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[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
[ERR_PRINT] serv_setconf.c, line 1605
[SERV SETCFG] *** sending error ***
[ERROR]: 0xa0802131
[ERROR]: 0xa0902111
[ERROR]: 0xa0902111
[ERROR]: 0xa0902131
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

 

[feng_ye]

Ok didn't read full story of that dia001, please use multimeter on power line of rsx vddc and report that resistance values on both cpu and rsx, also have you atemp to delid any of those? I don't suggest pushing any pressure on ic, delid if you feel confident that you don't scratch any of ic surfaces. Ask for advices to delid and read more before any mistakes, we all did it wrong on beginning.
Edit
It looks as thermal panic on both, not to jump on any conclusions but some rsx can die in this case, had different 5 cases that SB debugging was starting and kind of errors were about thermal sensors, all cases been sorted with another rsx even that old defective rsx after reball didn't come with errors after cleaning errlog.

Thanks that was my first post so here's some background. It's a DIA-001 board with intact seal and no delid no reflow/reball/tokin at all. But the shield was pretty rusty, obviously it was staying in a wrong environment before I bought it! I just replaced two SMD electrolytic capacitors seems blown up, with some ones with slightly bigger capacity.

When you say "use multimeter on power line of rsx vddc and report resistance values on both cpu and rsx", did you mean I do it when the power is on or off? I assume the negative probe goes to the GND right? I can certainly do it when power is off. But if you meant when power on, that'd be tricky to me as the GPU/CPU are actually below the PCB...

About the "death" of RSX, I inspect my bringup log and compared with some usual 3034's logs. It appears my RSX and CELL actually passed the "BitTraining" phase means they can actually talk to each other, in a bare minimal. It reached to a quite late stage of the booting sequence, like this:

[SSM] state: 0105 -> 0400

So what I'm thinking is still finding other issues like power, the death of the thermal sensor, or some connecting components. It's still like shooting in dark but I thought passing the BitTraining part is actually a rather good news.

 

[vyktormvmpay25]

@feng_ye you should just delid as seem to be thermal panic, on both otherwise we don't understand more. If you don't feel comfortable enough, let someone that do it well in your area. All ps3 are older then 8 years so that thermal paste under copper ihs won't stand anymore for any ps3. Apart from 3000 series where cpu is stick with hard adhesive on cpu, rsx I still delid after desolder. All slim start with 2100 rsx I have to desolder in order to delid in good condition.

 

[feng_ye]

@feng_ye you should just delid as seem to be thermal panic, on both otherwise we don't understand more. If you don't feel comfortable enough, let someone that do it well in your area. All ps3 are older then 8 years so that thermal paste under copper ihs won't stand anymore for any ps3. Apart from 3000 series where cpu is stick with hard adhesive on cpu, rsx I still delid after desolder. All slim start with 2100 rsx I have to desolder in order to delid in good condition.

At this point I'm rather staying away from deliding tbh as there could be the external thermal chip or communication issue with the syscon. And I have zero experience delid anything and I see numerous posts even in this thread about damage from deliding. What's the next step you recommend after deliding? Do I have to delid to measure anything?

 

[joesaiditstrue]

Will SYSCON be accessible via CFW eventually? I don't have the equipment to perform the hardware mod unfortunately. I have a 4USB CECHE that YLOD whenever I play demanding games (Killzone 2, GT6, Uncharted 3, Dragon Age: Inquisition)

Less graphically demanding games play just fine

Thanks for any advice

 

[vyktormvmpay25]

Just delid, add new thermal paste on top of both ic die and add back ihs and thermal paste. On rsx ram add high density thermal paste good enough, I use something cheap sa it will matter more ic die. Just assembly unit and leave uart wires on hand, clean old errors and test, if those errors will disappear and come with something else will see next decision. Without delid can't think more, be careful with pressure on that area and mostly not scratch/hit any part.

 

[vyktormvmpay25]

Will SYSCON be accessible via CFW eventually? I don't have the equipment to perform the hardware mod unfortunately. I have a 4USB CECHE that YLOD whenever I play demanding games (Killzone 2, GT6, Uncharted 3, Dragon Age: Inquisition)

Less graphically demanding games play just fine

Thanks for any advice

Hard to say if possible but my opinion by looking at different ports of connection between Cpu, rsx, SB, syscon. Syscon debugging uart port is quite separated in hardware side and not sure really. We have to ask opinion to @sandungas , @M4j0r, @zecoxao.
Probably if there was a way was about to be revealed?
Sony made this kind of hardware mask in my opinion.