This is my method. It works great and safe if you are careful.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?
Nice and thank you for your report this will help more people to understand . Looking to your bump cpu, and will act as thermal error in rsx is something new or seen something similar to botakompong when he had 2131 and he changed cpu set. @RIP-Felix please note that in pdf of strange things.What in the holy moly ps3 world happen to this Cell ?
Had some A0A02031 and A0093003
Is that what we call extreme heat ?
View attachment 34800 View attachment 34801
Welp another board for my BGA training I suppose !
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...
I agree, it's a good sign that you don't have a 3034/4xxx error. I think your RSX is fine. But it could still be overheating. Or the solder could be corroded on the motherboard. You did say it was kept in an inhgospitable place that caused the RF shielding to rust, so it's likely the came conditions caused corrosion on the MB.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:
Code:[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.
Can you explain the YLOD better. Is it actually a single Y led before shutdown and then blinking red? Or does it flash yellow repeatedly before shutting down? The latter is overheating, not a YLOD. That is a relatively easy thing to fix. Does the fan get loud before the shutdown?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
Was that console sealed? If so, I can't imagine a scenario where a natural fault could cause that kind of delamination. That smacks me as a "heat gun special."What in the holy moly ps3 world happen to this Cell ?
Had some A0A02031 and A0093003
Is that what we call extreme heat ?
View attachment 34800 View attachment 34801
Welp another board for my BGA training I suppose !
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.
Ah yes, I forgot about that.We can access some functions, I created an application for that, it's part of the https://www.psx-place.com/threads/release-ps3-advanced-tools.34104/ .
Example output: https://github.com/bucanero/psl1ghtv2_ports/blob/master/sm_error_log/log.txt
Can you explain the YLOD better. Is it actually a single Y led before shutdown and then blinking red? Or does it flash yellow repeatedly before shutting down? The latter is overheating, not a YLOD. That is a relatively easy thing to fix. Does the fan get loud before the shutdown?
Syscon only costs a few dollars. You may need a soldering iron, but even a cheap one will work for the 3 wires you have to solder in. If you don't have the equipment and skill to perform the syscon, then you shouldn't be working on a PS3. You can buy a new one working console for less than it'll cost to fix it.
I know that's a pretty harsh statement, but the PS3 is not like a SNES or N64, some rock solid console that only ever has a blown fuse or bad capacitor. No, a PS3 YLOD is 90% of the time going to to required about $300 in equipment to fix (minimum). More than it's worth to most people. The chances you have an easy fix are less than 7%!. So my advice is to sell it for parts and buy another. Only attempt to fix it if you like electronics repair and are willing to pay for the education ahead of you, which most likely includes destroying a few consoles in the process.
EDIT: It sounds like your problem could be the NEC/TOKINs or overheating. Overheating is easy. NEC/TOKINs are not!
@joesaiditstrueAh yes, I forgot about that.
Any guide on how to install it? I'm a noob when it comes to CFW and homebrew on PS3. I mostly just fix the hardware and stick to OFW.
@joesaiditstrue
You can find a precompiled version (debug pkg) with the "Get Syscon Info" support here: https://workupload.com/file/yExhQFXdsFy .
@M4j0r this is a nice utility! I'm going to make a note about it in my SYSCON tutorial. Thanks.![]()
Here's the log file from my SYSCON chip. What do these say about my YLODs?
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
What in the holy moly ps3 world happen to this Cell ?
Had some A0A02031 and A0093003
Is that what we call extreme heat ?
View attachment 34800 View attachment 34801
Welp another board for my BGA training I suppose !
BTW, I have never seen a 90nm RSX console such as yours with so much use! 559 days of use is well over the 150-300 days we usually see the YLOD occur on A-H models. I was curious if the console had ever been refirbished by SONY, in case they installed a 65nm or 40nm RSX in there. However your SYSCON Firmware Revision is consistant previous dumps of a stock COK-002's CXR713120-202GB SYSCON chip. So that can't be it.
I'm curious...How long have you had this console? Is it sealed? Was it sealed when you got it? Has it ever been refirbished? Have you done routine maintenance on it (change thermal pasted, deliding, blowing the dust out, etc)? I honestly didn't think any 90nm RSX could last that long. Your console is definitely the exception to the rule!
Given how much use it has seen, It seems more likely the PSU really could be the issue. Or even the tokins. You have the right kind of errors and YLOD for that diagnosis.
I bought it on ebay 1 year after PS3 launched. Most of those hours are indeed from me haha. Yes it was sealed (I've taken it apart many times to clean it out and repaste)
239 days in is right on schedule for YLOD in 90nm RSX consoles. The electrolytic capacitors in the console will fall -20% capacitance in 250-330 days of use ballpark (6000-8000 hours). However, I'm not sure what model you have?anybody able to help me with this error log system yellow lights when playing intense games
Firmware Version: 4.82 (50677)
Platform ID: CokE10
Hardware Config: 4E00FFFF0107BCBF
Syscon Fimware Version: 0E69.0001000400040002 (0001000400040002)
Bringup Count: 2837, Shutdown Count: 2743
Runtime: 239 Days, 2 Hours, 55 Minutes, 36 Seconds
Error Log
01: A0802203 Mon Aug 17 13:54:07 2020
02: A0801002 Mon Aug 17 13:54:07 2020
03: A0801002 Fri Aug 14 15:31:07 2020
04: A0801002 Sun Jul 5 09:51:11 2020
05: A0801002 Sat Jul 4 08:43:34 2020
06: A0801002 Mon Jun 29 12:29:21 2020
07: A0802022 Sun Nov 24 05:38:37 2019
08: A0802022 Sun Nov 24 05:38:35 2019
09: A0802022 Sun Nov 24 05:37:29 2019
10: A0802022 Sun Nov 24 05:35:16 2019
11: A0802022 Sun Nov 24 05:34:33 2019
12: A0802022 Sun Nov 24 05:26:21 2019
13: A0802022 Sun Nov 24 05:25:30 2019
14: A0802022 Sun Nov 24 05:23:26 2019
15: A0802022 Sun Nov 24 05:22:41 2019
16: A0802022 Sun Nov 24 05:19:20 2019
17: A0802022 Sun Nov 24 05:15:02 2019
18: A0801001 Fri Dec 31 23:59:59 1999
19: A0801001 Thu Feb 4 09:14:22 2010
20: A0801001 Fri Dec 31 23:59:59 1999
21: FFFFFFFF Fri Dec 31 23:59:59 1999
22: FFFFFFFF Fri Dec 31 23:59:59 1999
23: FFFFFFFF Fri Dec 31 23:59:59 1999
24: FFFFFFFF Fri Dec 31 23:59:59 1999
25: FFFFFFFF Fri Dec 31 23:59:59 1999
26: FFFFFFFF Fri Dec 31 23:59:59 1999
27: FFFFFFFF Fri Dec 31 23:59:59 1999
28: FFFFFFFF Fri Dec 31 23:59:59 1999
29: FFFFFFFF Fri Dec 31 23:59:59 1999
30: FFFFFFFF Fri Dec 31 23:59:59 1999
31: FFFFFFFF Fri Dec 31 23:59:59 1999
32: FFFFFFFF Fri Dec 31 23:59:59 1999