PS3 Lost at what to do with PS3 Fat fault finding with syscon

[Kibillcat]

Hello, Im new here and Im hoping that Im creating in right thread, thought posting at existing some very long threads but thought that it would be better here.

Spoiler: Introduction

Few years ago I bought broken PS3 with hoping to fix YLOD, thought it would be easy reflow fix, but as I read more it became like a rabbit hole. It is not that simple. PS3 came without HDD and CELL/BE was delided. (traces are not damaged)

Did a lot of reading about YLOD and I thought I will give a try to replace NEC/TOKIN capacitors, but hesitated and though that it would be better to use syscon to get the error codes, but didint had USB to TTL. But had CH341A programmer and noticed that it could be used as TTL. Though needed some modifications that it would be on 3.3v, didint wanted to risk with 5v and damage something. (This CH341Awas from aliexpress with black color design and recently found out that it has flaw in design and doesnt deliver 3.3v even with jumper). Other than that, I could read error codes.
Really grateful for a lot of tutorials on how to get into syscon.

Today I messed with PS3 whole day and began reading codes, at first I got these codes, probably because I had not connected everything earlier and tried various ways to power on this PS3 (with, without BD, card reader and etc.)
PS3 model: CECHA01
Used only External Access Mode, because I think that was enough to get error codes.

Spoiler: First attempt at error codes reading

>$ ERRLOG GET 00: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 01: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 02: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 03: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 04: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 05: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 06: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 07: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 08: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 09: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 10: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 11: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 12: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 13: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 14: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 15: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 16: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 17: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 18: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 19: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 1A: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 1B: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 1C: 00000000 A0801701 FFFFFFFF
>$ ERRLOG GET 1D: 00000000 A0801601 FFFFFFFF
>$ ERRLOG GET 1E: 00000000 A08014FF FFFFFFFF
>$ ERRLOG GET 1F: 00000000 FFFFFFFF FFFFFFFF

After some searching found "RIP-Felix" message, that it was damaged CPU, because I had tried to reflow and dont know what previous owner did to this PS3 too.
Fault finding YLOD with the SYSCON - First steps and Error reporting

After some more testing and trying to boot again PS3 and reading error codes I got different ones:

Spoiler: Second attempt

>$ ERRLOG GET 00: 00000000 A0213013 FFFFFFFF
>$ ERRLOG GET 01: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 02: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 03: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 05: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 04: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 06: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 07: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 08: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 09: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 10: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 11: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 12: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 13: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 14: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 15: 00000000 A0202120 FFFFFFFF
>$ ERRLOG GET 16: 00000000 A0213013 FFFFFFFF

Kinda got excited and thought that it will be fixable, either easy method after some researching or the hard one by replacing HDMI chip.
Tutorial/Research - NEC/TOKIN Capacitors Replacement - YLOD FIX

After finding out that HDMI chip might be bad, I decided to try disconnecting card reader ribbon and then BD drive and see what kind of errors I would get out of curiosity:

Spoiler: Third attempt

>$ ERRLOG GET 00: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 01: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 02: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 03: 00000000 A0213013 FFFFFFFF

First disconnected card readers, checked errors, got errors mentioned above. Connected everything back, got back to "A0202120" errors. Disconnected BD, got "A080130" errors. Connected everything back - "A0202120" errors. After that assumed that if something is missing - it will report those errors and went measuring some caps and fuses.

Sadly, all fuses were good, not a single one was blown (used schematics to find fuses and that cap). Cap also wasnt shorted and I began measuring randomly caps and got more confused because I dont have good knowledge at board level repairs. Some measurements that I done with multimeter in diode mode and resistor mode, holding one probe on ground, other on component:

C2513 - 042 OHM
L6201 - few ohms
L6306, C6342, C6344 - 16 OHM
L6305, C6343, C6341 - 77 OHM
C6603 - 17 OHM
C6620 - 38 OHM
Q6600 - maybe bad?

It looks like there are short somewhere, or values have to be like that? But still coils having that small resistance looks weird to me and thinking that there is something wrong at DC-DC conversions and RSX VRMs. After this I got lost and dont know what to do anymore and tried to boot it again and see error codes again and this time, theyre different again:

Spoiler: Fourth attempt

>$ ERRLOG GET 00: 00000000 A0611802 FFFFFFFF
>$ ERRLOG GET 01: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 02: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 03: 00000000 A0611802 FFFFFFFF
>$ ERRLOG GET 04: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 05: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 06: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 07: 00000000 A0801301 FFFFFFFF
>$ ERRLOG GET 08: 00000000 A0611802 FFFFFFFF

And now, Im completely lost.
Does this error "A0801301" "BE PLL Unlick", tells me that something is not connected properly?
Does this error "A0611802" "RSX INIT" fails to start RSX chip?
Should I measure voltages? But have no idea what voltages there should be and should I seat in psu or just connect that small wires connector?
Should I try removing some caps or coils? But that feels like I will be blindly checking and have no I idea what I am doing.
Maybe previous owner tried to jailbreak and failed, bricked it?
MaybeI need hdd with correct OS? Since I dont have original hdd and used one from failed delid attempt. Which was jailbroken. But I doubt it and also I dont know for sure.

I also have CECHJ model ps3 with broken cpu traces of failed delid. Previously worked but would overheat and shut down. Could use some parts for CECHA0 if possible. And bricked L model after failed jailbreaking. Sometimes I choose to make stupid decisions. Also Im planning some day to do error reading on those models just out of curiosity and will be posting here.

Spoiler: Tips for newbies like me:

There are lots of useful guides how to begin reading from syscon but still had some trouble till I began reading from PS3 syscon,
Connect TX to TX, RX to RX. GND to ANY ground, preferably to mounting points, easier.
DIAG mode not needed unless trying to get into internal mode (havent tried). External mode gives error messages, like what I needed but still dont know if it was good enough.
If installing python 3.9.5 not from windows store, before installing disable aliases for it ("manage app execution aliases" type in windows search). Had to do this because it gave me errors from windows store python while installing "pycrypto" I think (cant remember which library).
If using CH341A programmer, MAKE SURE, you check your voltages on TX, RX lines. (You can find on youtube "CH341 Programmer 3.3V Fix | Voltlog #318")
Dont be impatient, dont be stupid like me. Take your time, get right tools, dont rush things or you will break something

 

[Pacorretaco]

Hmm that's an interesting issue, but seems like it didn't get that much attention for some reason.

I suggest you use proper internal commands and tell this story again in the SYSCON diagnosis thread.
https://www.psx-place.com/threads/f...-syscon-first-steps-and-error-reporting.30100

Seems like strange problem but it's so complicated that maybe I didn't understand it.
Your problem is not even a YLOD is it?

You mean when you unplug some peripherals like card reader, the machine no longer YLOD but with random CPU errors?
And with everything attached it's about 1 second YLOD 3013+ 10x 2120?

Those external ERRRLOG commands are not enough. Only useful to quickly see if there's 3034+44xx or other obvious big problems or not.
Besides you didn't even get the full log. Missing errors 0A,0B,0C,0D,0E, and 0F

Do you think you can replicate this YLOD? What did you do exactly to get this problem, and to get rid of it? Could be a some new unrelated problem on top old one.

Do you think your CPU is ok? Was this board reflowed or something? Measure ohms, although I'm pretty sure the OHMs will not tell much.

Maybe a longer history of this machine could help.

Again, good luck, better in the SYSCON thread

 

[Kibillcat]

At first I was afraid to set up external commands, but only later I did it. And I couldnt replicate those errors anymore, most likely damaged CPU. Later on I posted in this thread too and came to conclusion, that CPU is most likely dead. In my post there are pictures of chipped CPU die and more info what was done with this PS3.
Links to this thread posts:
https://www.psx-place.com/threads/f...and-error-reporting.30100/page-75#post-302541
https://www.psx-place.com/threads/f...and-error-reporting.30100/page-75#post-302635
https://www.psx-place.com/threads/f...and-error-reporting.30100/page-75#post-302670
vyktormvmpay25 helped me a bit.

Now to answer some of your questions.

You mean when you unplug some peripherals like card reader, the machine no longer YLOD but with random CPU errors?
And with everything attached it's about 1 second YLOD 3013+ 10x 2120?

It would still give YLOD. After "First attempt" error codes, I disassembled and reassembled console then I began having those error codes (YLOD 3013+ 10x 2120). I dont remember if it was instant or between 1-3 seconds YLOD. After "Second attempt", I disassembled and reassembled console and couldnt get those error codes again and cant remember if during this time IHS slid off CPU.

Do you think you can replicate this YLOD? What did you do exactly to get this problem, and to get rid of it? Could be a some new unrelated problem on top old one.

Basically I just disassembled, reassembled, then again disassembled and reassembled and that gave me different error messages until it began giving only 0xa0801301 and 0xA0611802 error codes. Most likely during those reassemblies I damaged something till I chipped CPU and broke completely.

Do you think your CPU is ok? Was this board reflowed or something? Measure ohms, although I'm pretty sure the OHMs will not tell much.

CPU is chipped a bit. I tried to reflow at 360C but was afraid of doing it and probably didint heated enough. But this was like few years ago before syscon discovery and I tried too many times to get original errors. Unless at first attempt, those were the same errors.

Or CPU was already damaged and would give those random errors, I cant really tell. I should have inspected CPU die at first when I got the console, because I only did when I got last errors. Now its really a big mess and might be misleading on some points, sorry.

Thank you, Pacorretaco.