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

[vyktormvmpay25]

Hi, I repaired a Dia-002,PS3. It had a fault code of 2102 and it had ylod.
I reballed RSX and CELL. I cleared the error log and restarted the device and then turned it off. The device was no longer giving an error code.
The device is now always green and working, the hdd led appears briefly at the beginning but then does not appear.
The device can work in a continuous green light without ever shutting down, the processors come up to 77 degrees.
My problem is that the device does not display, there is no signal constantly.I changed the hdmi chip, all voltages without interference, I changed th2501, there is no error code, but the device does not display.
At the beginning, I reset the screen by pressing the power button, it still does not work, there is no image from the av port.I do not know about the history of the device, do you think there may be a problem with nor flash?

During few tests on 2 dia002 and 3 dia001 few months back got different errors and I've recovered 3 from 5 but I couldn't understand why cell in those work so hot, even with 40nm rsx imo apart from researching those units won't worth time investing. Everyone is free to choose.
I could not drop easy with 30 % fan under 68 after 30 minutes. On one of last cok002 was like 65 Celsius. Idk how heat affects our cell /rsx during rework process.

 

[christian3411]

During few tests on 2 dia002 and 3 dia001 few months back got different errors and I've recovered 3 from 5 but I couldn't understand why cell in those work so hot, even with 40nm rsx imo apart from researching those units won't worth time investing. Everyone is free to choose.
I could not drop easy with 30 % fan under 68 after 30 minutes. On one of last cok002 was like 65 Celsius. Idk how heat affects our cell /rsx during rework process.

I absolutely agree with your views. I should not waste time for these devices. I had the overheating problem you mentioned on a Sem-001 motherboard. Strangely, after the rework, there was some change in the cell resistance. I started the console, but the device was turning itself off after 45 minutes due to overheating. As a solution, I created a new fan profile for cell/rsx and overwritten it on syscon.

 

[k1netic]

Good. Input side is figured out. Now you just need to find the short downstream that caused the fuse to blow.


Those caps would test short in circuit if any of those MOSFETs are short. You tested "All" components out of circuit? Meaning the MOSFETs too? Cuz my first guess is one of them burned out.

Injecting voltage would be the easiest way to figure out which component is causing the short, but if you can't do that try using diode mode on your multimeter to measure the voltage drop across the MOSFET. Otherwise you willl have to remove them 1-by-1 to figure out where the short is. If it's not there, you will have to keep hunting downstream. 1.7V_MISC serves as power for multiple MOSFETs later on, YC_RC_VDDA, YC_RC_VDDIO, SB_VDDC, GX_VDDC, and more. Any one of them could short to ground (unlikely though).

Removing R6374/R6375 (unsure which is which on the board but I guess it doesn't matter) has eliminated the short across the MOSFETs and capacitors in parallel in that area. So with 1 resistor still in place the short is gone. I removed both and both tested 33ohms, so unsure if they could be faulty while reading the correct resistance?

Putting just one resistor back on the board, replacing fuse 6302, and replacing capacitor c6320 and the console boots up to xmb.

I won't be stress testing yet as I'm now waiting for resistors to be delivered, I assume running the console with one missing is a problem down the road waiting to happen.

I do have a working donor cech-k02 here, I took fuse 6001 from it and the capacitor from the same location as c6320 to repair the cech-c02, but couldn't find a service manual for it to point me in the right direction for a resistor of 33ohms and correct case size. Any hints for that? Then I can put the c02 back together and replace the parts on the k02 later...

 

[Timbo9876]

Got a CECHG03, console has been opened before. The console boots up and at this stage I decided to do a Syscon dump using PS3 advanced tools.

Dump is as follows

Firmware Version: 4.89 (build 50740)
Platform ID: CokC12
Product Code: 00 87
Product Sub Code: 00 05
Hardware Config: 4E00FFFF0007FCFF
Syscon Fimware Version: 0D52.0001000200030002 (EEPROM: 0001000200030002)
Bringup Count: 1059, Shutdown Count: 666
Runtime: 55 Days, 4 Hours, 45 Minutes, 56 Seconds
Error Log
01: A0801001 Sat May 21 13:18:41 2022
02: A0801001 Sat May 21 13:01:40 2022
03: A0801001 Sat Nov 11 12:22:47 2017
04: A0801001 Thu Jan 15 19:33:29 2015
05: A0801001 Sun Nov 23 13:05:06 2014
06: A0801001 Tue Nov 18 14:35:58 2014
07: A08014FF Fri Sep 26 21:35:15 2014
08: A0801701 Fri Sep 26 21:35:15 2014
09: A0801001 Fri Sep 26 21:17:53 2014
10: A08014FF Fri Sep 26 21:17:53 2014
11: A0801001 Sat Jul 5 00:10:53 2014
12: A08014FF Sat Jul 5 00:10:52 2014
13: A0801001 Sun Apr 20 23:20:20 2014
14: A0801001 Thu Jan 9 00:34:53 2014
15: A08014FF Sat Jan 4 17:38:08 2014
16: A0801701 Sat Jan 4 17:38:08 2014
17: A0902120 Wed Jan 1 23:22:34 2014
18: A0801001 Wed Jan 1 23:22:34 2014
19: A0801001 Fri Nov 15 23:08:51 2013
20: A0801001 Mon Aug 26 21:35:01 2013
21: A0801001 Wed Dec 19 21:49:21 2012
22: A0801001 Fri Dec 31 23:59:59 1999
23: A08014FF Wed Dec 19 21:46:30 2012
24: A0801001 Sat Sep 15 16:55:45 2012
25: A0801002 Fri Sep 14 11:29:06 2012
26: A0801001 Wed Sep 12 21:13:49 2012
27: A0801001 Mon Sep 10 22:35:40 2012
28: A0801001 Tue Jun 19 23:41:46 2012
29: A0801002 Wed May 30 23:46:22 2012
30: A0801001 Sat May 5 11:10:19 2012
31: A0801001 Thu Apr 5 22:44:14 2012
32: FFFFFFFF Thu Apr 5 14:25:23 2012

So A08014FF seems concerning? Any one know what this might mean? Check stop? Also 1002 RSX possible tokin failure?

 

[RIP-Felix]

Got a CECHG03, console has been opened before. The console boots up and at this stage I decided to do a Syscon dump using PS3 advanced tools.

Dump is as follows

Firmware Version: 4.89 (build 50740)
Platform ID: CokC12
Product Code: 00 87
Product Sub Code: 00 05
Hardware Config: 4E00FFFF0007FCFF
Syscon Fimware Version: 0D52.0001000200030002 (EEPROM: 0001000200030002)
Bringup Count: 1059, Shutdown Count: 666
Runtime: 55 Days, 4 Hours, 45 Minutes, 56 Seconds
Error Log
01: A0801001 Sat May 21 13:18:41 2022
02: A0801001 Sat May 21 13:01:40 2022
03: A0801001 Sat Nov 11 12:22:47 2017
04: A0801001 Thu Jan 15 19:33:29 2015
05: A0801001 Sun Nov 23 13:05:06 2014
06: A0801001 Tue Nov 18 14:35:58 2014
07: A08014FF Fri Sep 26 21:35:15 2014
08: A0801701 Fri Sep 26 21:35:15 2014
09: A0801001 Fri Sep 26 21:17:53 2014
10: A08014FF Fri Sep 26 21:17:53 2014
11: A0801001 Sat Jul 5 00:10:53 2014
12: A08014FF Sat Jul 5 00:10:52 2014
13: A0801001 Sun Apr 20 23:20:20 2014
14: A0801001 Thu Jan 9 00:34:53 2014
15: A08014FF Sat Jan 4 17:38:08 2014
16: A0801701 Sat Jan 4 17:38:08 2014
17: A0902120 Wed Jan 1 23:22:34 2014
18: A0801001 Wed Jan 1 23:22:34 2014
19: A0801001 Fri Nov 15 23:08:51 2013
20: A0801001 Mon Aug 26 21:35:01 2013
21: A0801001 Wed Dec 19 21:49:21 2012
22: A0801001 Fri Dec 31 23:59:59 1999
23: A08014FF Wed Dec 19 21:46:30 2012
24: A0801001 Sat Sep 15 16:55:45 2012
25: A0801002 Fri Sep 14 11:29:06 2012
26: A0801001 Wed Sep 12 21:13:49 2012
27: A0801001 Mon Sep 10 22:35:40 2012
28: A0801001 Tue Jun 19 23:41:46 2012
29: A0801002 Wed May 30 23:46:22 2012
30: A0801001 Sat May 5 11:10:19 2012
31: A0801001 Thu Apr 5 22:44:14 2012
32: FFFFFFFF Thu Apr 5 14:25:23 2012

So A08014FF seems concerning? Any one know what this might mean? Check stop? Also 1002 RSX possible tokin failure?

Test an intense game. Probe the tokins with an o-scope if you have one.

What I suspect is that the tokins are marginal. They could cause a checkstop if the noise interferes with the wrong data packet. I'm not 100% convinced that Marginal tokins can cause this.

So I suggest checking to see if you can trigger a YLOD from an intense game, record the error, and if it's a 1001 or 1002, then you can be reasonably sure it's the tokins. The 1701/14FF could suggest something more, or suggest a larger connection between tokins and these errors than previously known.

I would like to see the scope images, but if you don't have one, oh well.

 

[Timbo9876]

Test an intense game. Probe the tokins with an o-scope if you have one.

What I suspect is that the tokins are marginal. They could cause a checkstop if the noise interferes with the wrong data packet. I'm not 100% convinced that Marginal tokins can cause this.

So I suggest checking to see if you can trigger a YLOD from an intense game, record the error, and if it's a 1001 or 1002, then you can be reasonably sure it's the tokins. The 1701/14FF could suggest something more, or suggest a larger connection between tokins and these errors than previously known.

I would like to see the scope images, but if you don't have one, oh well.

Hi Felix,

Could you point me in the direction of buying a scope that's up to the job of creating the image required.

 

[Timbo9876]

Hi Felix,

Could you point me in the direction of buying a scope that's up to the job of creating the image required.

Also could you send me the link to your de-lid tutorial,

Many thanks

 

[TYRANT]

No, just an ohm test to see if the resistance on the voltage line seems off. You can do this without power. Prefferably when the board is cool. Short is bad, open is bad. Otherwise, it doesn't reveal much. I don't think there's a missing voltage or SYSCON wouldn't let the console boot.

Also, the chips wont burn without HS. The'll overheat and then the system powers off with an error. They don't burn out. This is a protection feature.

Hi RIP-Felix, i have tested my 2 boards like you suggested me (comparing all the values).
I didn' found short or oper circuit.
Also i retrieved the syscon using your guide.
Here the results

(first before nec tokin replace using PS3 Advance Toolstet)

Firmware Version: 4.84 (build 50696)
Platform ID: CokF10
Product Code: 00 85
Product Sub Code: 00 08
Hardware Config: 4E00FFFF0307BCBF
Syscon Fimware Version: 065D.0000000000000000 (EEPROM: 0000000000000000)

Bringup Count: 2447, Shutdown Count: 2418
Runtime: 121 Days, 21 Hours, 55 Minutes, 20 Seconds

Error Log
01: A0802124 Sun Jan 1 00:00:31 2006
02: A0802124 Sun Jan 1 00:00:31 2006
03: A0801002 Sun Jan 1 00:00:30 2006
04: A0802124 Sun Jan 1 00:00:01 2006
05: A0801002 Sun Jan 1 00:00:00 2006
06: A0802124 Sun Jan 1 19:48:25 2006
07: A0801002 Sun Jan 1 19:48:24 2006
08: A0802124 Sun Jan 1 19:47:44 2006
09: A0802124 Sun Jan 1 19:47:43 2006
10: A0801002 Sun Jan 1 19:47:43 2006
11: A0802124 Sun Jan 1 00:02:44 2006
12: A0802124 Sun Jan 1 00:02:43 2006
13: A0801002 Sun Jan 1 00:02:43 2006
14: A0802124 Sun Jan 1 00:01:11 2006
15: A0802124 Sun Jan 1 00:01:11 2006
16: A0801002 Sun Jan 1 00:01:10 2006
17: A0802124 Sun Jan 1 00:00:23 2006
18: A0801002 Sun Jan 1 00:00:22 2006
19: A0802124 Sun Jan 1 00:00:01 2006
20: A0801002 Sun Jan 1 00:00:00 2006
21: A0802124 Sun Jan 1 01:42:16 2006
22: A0801002 Sun Jan 1 01:42:16 2006
23: A0802022 Sun Jan 1 01:41:52 2006
24: A0802124 Sun Jan 1 01:08:44 2006
25: A0801002 Sun Jan 1 01:08:44 2006
26: A0802022 Sun Jan 1 01:08:16 2006
27: A0802124 Sun Jan 1 00:47:24 2006
28: A0802124 Sun Jan 1 00:47:24 2006
29: A0801002 Sun Jan 1 00:47:23 2006
30: A0802022 Sun Jan 1 00:47:10 2006
31: A0802124 Sun Jan 1 00:42:37 2006
32: FFFFFFFF Fri Dec 31 23:59:59 1999

(last using your guide with uart adapter)

ERRLOG GET 00 00000000 A0802124 0B49D81F
ERRLOG GET 01 00000000 A0802124 0B49D81F
ERRLOG GET 02 00000000 A0801002 0B49D81E
ERRLOG GET 03 00000000 A0802124 0B49D801
ERRLOG GET 04 00000000 A0801002 0B49D800
ERRLOG GET 05 00000000 A0802124 0B4AEE89
ERRLOG GET 06 00000000 A0801002 0B4AEE88
ERRLOG GET 07 00000000 A0802124 0B4AEE60
ERRLOG GET 08 00000000 A0802124 0B4AEE5F
ERRLOG GET 09 00000000 A0801002 0B4AEE5F
ERRLOG GET 0A 00000000 A0802124 0B49D8A4
ERRLOG GET 0B 00000000 A0802124 0B49D8A3
ERRLOG GET 0C 00000000 A0801002 0B49D8A3
ERRLOG GET 0D 00000000 A0802124 0B49D847
ERRLOG GET 0E 00000000 A0802124 0B49D847
ERRLOG GET 0F 00000000 A0801002 0B49D846
ERRLOG GET 10 00000000 A0802124 0B49D817
ERRLOG GET 11 00000000 A0801002 0B49D816
ERRLOG GET 12 00000000 A0802124 0B49D801
ERRLOG GET 13 00000000 A0801002 0B49D800
ERRLOG GET 14 00000000 A0802124 0B49EFF8
ERRLOG GET 15 00000000 A0801002 0B49EFF8
ERRLOG GET 16 00000000 A0802022 0B49EFE0
ERRLOG GET 17 00000000 A0802124 0B49E81C
ERRLOG GET 18 00000000 A0801002 0B49E81C
ERRLOG GET 19 00000000 A0802022 0B49E800
ERRLOG GET 1A 00000000 A0802124 0B49E31C
ERRLOG GET 1B 00000000 A0802124 0B49E31C
ERRLOG GET 1C 00000000 A0801002 0B49E31B
ERRLOG GET 1D 00000000 A0802022 0B49E30E
ERRLOG GET 1E 00000000 A0802124 0B49E1FD
ERRLOG GET 1F 00000000 FFFFFFFF FFFFFFFF

It seems thal all errors are the same in the same order.
I'm starting to think that the real problem is the rsx.

 

[VSpeed]

@vyktormvmpay25 is the SB Sensei. I've never tried the SB UART myself. I'm also curious if there's more to it than just using the same code/procedure as the SYSCON (which i doubt). So I second the call for a tutorial. Victor, you feel like revealing your SB Code-fu?

That's interesting. I've had something similar happen to me, where the HDMI setting don't persist after shutting down. It would prompt me there was a HDMI device detected and ask If I wanted to switch to it. I say yes and setup 1080p to my HDTV. No problem. That session works fine. But it'd prompt me to do the same on the very next boot, as if it can't remember those settings. I didn't think anything of it, and now I can't even remember which PS3 it was.

I wonder where the AV/HDMI configuration is stored? Probably NAND/NOR. I do know I/O from the HDMI/AV controllers needs to pass through the RSX over the FlexIO to the SB, where it can then be directed to the Starship2 Flash controller for storage. It still has to go through the SB to get to the HDD if that's where the config is stored. So either way, if there's an issue on the BGA/Bumps affecting VDDIO, but not necessarily the FlexIO, then you can conceivably get 2120/2020 errors. I hate to say it, but I don't think we can rule out the RSX BGA. I do know we often see 2120/2020 associated with 3034/4XXX errors. This may be why.

You could try replacing the HDMI encoder just to rule it out. Then reball.

Glad you got the 2110 sorted. C6019 again? Yeah, maybe you have stumbled on a common issue there...or just crap luck.

I can confirm the C6019 or C6020 theory as they are in parallel. I have a COK-002 that stopped working. I didn't had the FT232RL yet, so I replaced the RSX tokins and got it to power on for a couple of minutes and just died again. I then waited for the serial adapter to arrive and now that I have read the error log, it is showing code 1001 and then 2110 (no 1002). I checked both caps and one is working like a resistor (140 ohms) and not reading any capacitance. So this overloaded the F6001 fuse which died.

 

[RIP-Felix]

Hi RIP-Felix, i have tested my 2 boards like you suggested me (comparing all the values).
I didn' found short or oper circuit.
Also i retrieved the syscon using your guide.
Here the results

(first before nec tokin replace using PS3 Advance Toolstet)

Firmware Version: 4.84 (build 50696)
Platform ID: CokF10
Product Code: 00 85
Product Sub Code: 00 08
Hardware Config: 4E00FFFF0307BCBF
Syscon Fimware Version: 065D.0000000000000000 (EEPROM: 0000000000000000)

Bringup Count: 2447, Shutdown Count: 2418
Runtime: 121 Days, 21 Hours, 55 Minutes, 20 Seconds

Error Log
01: A0802124 Sun Jan 1 00:00:31 2006
02: A0802124 Sun Jan 1 00:00:31 2006
03: A0801002 Sun Jan 1 00:00:30 2006
04: A0802124 Sun Jan 1 00:00:01 2006
05: A0801002 Sun Jan 1 00:00:00 2006
06: A0802124 Sun Jan 1 19:48:25 2006
07: A0801002 Sun Jan 1 19:48:24 2006
08: A0802124 Sun Jan 1 19:47:44 2006
09: A0802124 Sun Jan 1 19:47:43 2006
10: A0801002 Sun Jan 1 19:47:43 2006
11: A0802124 Sun Jan 1 00:02:44 2006
12: A0802124 Sun Jan 1 00:02:43 2006
13: A0801002 Sun Jan 1 00:02:43 2006
14: A0802124 Sun Jan 1 00:01:11 2006
15: A0802124 Sun Jan 1 00:01:11 2006
16: A0801002 Sun Jan 1 00:01:10 2006
17: A0802124 Sun Jan 1 00:00:23 2006
18: A0801002 Sun Jan 1 00:00:22 2006
19: A0802124 Sun Jan 1 00:00:01 2006
20: A0801002 Sun Jan 1 00:00:00 2006
21: A0802124 Sun Jan 1 01:42:16 2006
22: A0801002 Sun Jan 1 01:42:16 2006
23: A0802022 Sun Jan 1 01:41:52 2006
24: A0802124 Sun Jan 1 01:08:44 2006
25: A0801002 Sun Jan 1 01:08:44 2006
26: A0802022 Sun Jan 1 01:08:16 2006
27: A0802124 Sun Jan 1 00:47:24 2006
28: A0802124 Sun Jan 1 00:47:24 2006
29: A0801002 Sun Jan 1 00:47:23 2006
30: A0802022 Sun Jan 1 00:47:10 2006
31: A0802124 Sun Jan 1 00:42:37 2006
32: FFFFFFFF Fri Dec 31 23:59:59 1999

(last using your guide with uart adapter)

ERRLOG GET 00 00000000 A0802124 0B49D81F
ERRLOG GET 01 00000000 A0802124 0B49D81F
ERRLOG GET 02 00000000 A0801002 0B49D81E
ERRLOG GET 03 00000000 A0802124 0B49D801
ERRLOG GET 04 00000000 A0801002 0B49D800
ERRLOG GET 05 00000000 A0802124 0B4AEE89
ERRLOG GET 06 00000000 A0801002 0B4AEE88
ERRLOG GET 07 00000000 A0802124 0B4AEE60
ERRLOG GET 08 00000000 A0802124 0B4AEE5F
ERRLOG GET 09 00000000 A0801002 0B4AEE5F
ERRLOG GET 0A 00000000 A0802124 0B49D8A4
ERRLOG GET 0B 00000000 A0802124 0B49D8A3
ERRLOG GET 0C 00000000 A0801002 0B49D8A3
ERRLOG GET 0D 00000000 A0802124 0B49D847
ERRLOG GET 0E 00000000 A0802124 0B49D847
ERRLOG GET 0F 00000000 A0801002 0B49D846
ERRLOG GET 10 00000000 A0802124 0B49D817
ERRLOG GET 11 00000000 A0801002 0B49D816
ERRLOG GET 12 00000000 A0802124 0B49D801
ERRLOG GET 13 00000000 A0801002 0B49D800
ERRLOG GET 14 00000000 A0802124 0B49EFF8
ERRLOG GET 15 00000000 A0801002 0B49EFF8
ERRLOG GET 16 00000000 A0802022 0B49EFE0
ERRLOG GET 17 00000000 A0802124 0B49E81C
ERRLOG GET 18 00000000 A0801002 0B49E81C
ERRLOG GET 19 00000000 A0802022 0B49E800
ERRLOG GET 1A 00000000 A0802124 0B49E31C
ERRLOG GET 1B 00000000 A0802124 0B49E31C
ERRLOG GET 1C 00000000 A0801002 0B49E31B
ERRLOG GET 1D 00000000 A0802022 0B49E30E
ERRLOG GET 1E 00000000 A0802124 0B49E1FD
ERRLOG GET 1F 00000000 FFFFFFFF FFFFFFFF

It seems thal all errors are the same in the same order.
I'm starting to think that the real problem is the rsx.

No, what I meant was to use the bringup command to start the console. It will log the startup sequence and there "might" be something useful in there.

Note after typing bringup and hitting enter, the log will stop. But there is more info beyond that. Hit enter again and it'll display what has happend since then. Copy all that and post here.

Edit:
Regardless, I think you have a GLOD. This will require a reball (if you're lucky) or replacment RSX (more likely). It could also be the CPU. Possably firmware, but I doubt it

 

[TYRANT]

No, what I meant was to use the bringup command to start the console. It will log the startup sequence and there "might" be something useful in there.

Note after typing bringup and hitting enter, the log will stop. But there is more info beyond that. Hit enter again and it'll display what has happend since then. Copy all that and post here.

Edit:
Regardless, I think you have a GLOD. This will require a reball (if you're lucky) or replacment RSX (more likely). It could also be the CPU. Possably firmware, but I doubt it

Here the results oth the commands bringup, powerstate and becount.

>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

>$ powerstate
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# ATA :ON
# PCI :OFF
# PCIex:OFF
# RSX :ON
# GDDR :ON
# XDR :ON
# EURUS:ON
# SB :ON

>$ becount
F0000003
# [UCMD] Unknown command.

 

[sandungas]

Btw, the best you can do by now is to use the command "clearerrorlog", there is a list of commands here if you are curious of how many things can be checked
https://www.psdevwiki.com/ps3/Syscon_Firmware#Internal_commands

In general i would say that is better to keep a record of the old errorlogs, but only if the PS3 is working fine, and only after making a backup of them (for forensic study incase is needed later, and incase the error codes varyes a lot)
But in your case you already backuped them (by publishing your errorlog in the forum), and that PS3 is repeating the same 3 errors all the times
The problem of your current errorlog is the timestamps are not real, so you dont really know when happened that error codes, maybe the problem was already solved and you are looking at error codes that was recorded months ago

The best way to confirm the timestamps by now is either... by figuring why the helll your PS3 is not recording the real timestamps (after you replaced he battery), or clearing the errorlog and wait to see if a new one is recorded in the next days

 

[TYRANT]

Btw, the best you can do by now is to use the command "clearerrorlog", there is a list of commands here if you are curious of how many things can be checked
https://www.psdevwiki.com/ps3/Syscon_Firmware#Internal_commands

In general i would say that is better to keep a record of the old errorlogs, but only if the PS3 is working fine, and only after making a backup of them (for forensic study incase is needed later, and incase the error codes varyes a lot)
But in your case you already backuped them (by publishing your errorlog in the forum), and that PS3 is repeating the same 3 errors all the times
The problem of your current errorlog is the timestamps are not real, so you dont really know when happened that error codes, maybe the problem was already solved and you are looking at error codes that was recorded months ago

The best way to confirm the timestamps by now is either... by figuring why the helll your PS3 is not recording the real timestamps (after you replaced he battery), or clearing the errorlog and wait to see if a new one is recorded in the next days

I extracted the syscon log again after the bringup command:

>$ errlog
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)
# CODE CLOCK
# A0801200 0B649DEC
# A0802124 0B49D81F
# A0802124 0B49D81F
# A0801002 0B49D81E
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 0B4AEE89
# A0801002 0B4AEE88
# A0802124 0B4AEE60
# A0802124 0B4AEE5F
# A0801002 0B4AEE5F
# A0802124 0B49D8A4
# A0802124 0B49D8A3
# A0801002 0B49D8A3
# A0802124 0B49D847
# A0802124 0B49D847
# A0801002 0B49D846
# A0802124 0B49D817
# A0801002 0B49D816
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 0B49EFF8
# A0801002 0B49EFF8
# A0802022 0B49EFE0
# A0802124 0B49E81C
# A0801002 0B49E81C
# A0802022 0B49E800
# A0802124 0B49E31C
# A0802124 0B49E31C
# A0801002 0B49E31B
# A0802022 0B49E30E

The first error line is changed (again error 1002).
(i have saved all the error logs that i had extracted avery time, and saved them in order and wrote on a txt file everything i made everytime).
Thanks for the command list link.

 

[sandungas]

I extracted the syscon log again after the bringup command:

>$ errlog
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)
# CODE CLOCK
# A0801200 0B649DEC
# A0802124 0B49D81F
# A0802124 0B49D81F
# A0801002 0B49D81E
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 0B4AEE89
# A0801002 0B4AEE88
# A0802124 0B4AEE60
# A0802124 0B4AEE5F
# A0801002 0B4AEE5F
# A0802124 0B49D8A4
# A0802124 0B49D8A3
# A0801002 0B49D8A3
# A0802124 0B49D847
# A0802124 0B49D847
# A0801002 0B49D846
# A0802124 0B49D817
# A0801002 0B49D816
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 0B49EFF8
# A0801002 0B49EFF8
# A0802022 0B49EFE0
# A0802124 0B49E81C
# A0801002 0B49E81C
# A0802022 0B49E800
# A0802124 0B49E31C
# A0802124 0B49E31C
# A0801002 0B49E31B
# A0802022 0B49E30E

The first error line is changed (again error 1002).
(i have saved all the error logs that i had extracted avery time, and saved them in order and wrote on a txt file everything i made everytime).
Thanks for the command list link.

The error with timestamp 0B649DEC is new, right ?
Im not sure how you did it, but it seems this new timestamp is real, compare the hex value with the others

The timestamps starting with 0B49xxxx was converted by the PS3 advanved tools app into dates around Sun Jan 1 00:00:00 2006
And the new timestamp starting with 0B64xxx is way higher (probably several years higher, i guess is real)

What you did to fix this problem ?, is the kind of weird thing that i would like to understand


-------
Edit:
Never minds... i think the new timestamp is not so high, the first byte of a valid timestamp from 2022 needs to be bigger than 0B

 

[RIP-Felix]

I extracted the syscon log again after the bringup command:

>$ errlog
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)
# CODE CLOCK
# A0801200 0B649DEC
# A0802124 0B49D81F
# A0802124 0B49D81F
# A0801002 0B49D81E
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 0B4AEE89
# A0801002 0B4AEE88
# A0802124 0B4AEE60
# A0802124 0B4AEE5F
# A0801002 0B4AEE5F
# A0802124 0B49D8A4
# A0802124 0B49D8A3
# A0801002 0B49D8A3
# A0802124 0B49D847
# A0802124 0B49D847
# A0801002 0B49D846
# A0802124 0B49D817
# A0801002 0B49D816
# A0802124 0B49D801
# A0801002 0B49D800
# A0802124 0B49EFF8
# A0801002 0B49EFF8
# A0802022 0B49EFE0
# A0802124 0B49E81C
# A0801002 0B49E81C
# A0802022 0B49E800
# A0802124 0B49E31C
# A0802124 0B49E31C
# A0801002 0B49E31B
# A0802022 0B49E30E

The first error line is changed (again error 1002).
(i have saved all the error logs that i had extracted avery time, and saved them in order and wrote on a txt file everything i made everytime).
Thanks for the command list link.

Actually the new error is 1200 (CPU overheat). Were you testing without fan on?

I recommend you do as @sandungas suggested and clear the errorlog. I forget if the command is clearerrlog or clearerrorlog.

This way you know that any new error is indeed new.

Unless I had seen more 1200's in your log, I wouldn't think the issue is just an overheating cpu. I'd have thought you'd mention a loud fan before the shutdown. So I don't think that explains your GLOD.

The bringup string looks fine. The console should be displaying. Last ditch effort you could try is replacing the HDMI encoder. If that's not it, then I'm thinking you have no choice than replace the RSX, but that's not really worth it on an L model. Not unless you have data you want to get off.

 

[TYRANT]

Actually the new error is 1200 (CPU overheat). Were you testing without fan on?

I recommend you do as @sandungas suggested and clear the errorlog. I forget if the command is clearerrlog or clearerrorlog.

This way you know that any new error is indeed new.

Unless I had seen more 1200's in your log, I wouldn't think the issue is just an overheating cpu. I'd have thought you'd mention a loud fan before the shutdown. So I don't think that explains your GLOD.

The bringup string looks fine. The console should be displaying. Last ditch effort you could try is replacing the HDMI encoder. If that's not it, then I'm thinking you have no choice than replace the RSX, but that's not really worth it on an L model. Not unless you have data you want to get off.

Yesterday when i used the bringup command i forgot to fix properly the board to the cooling heater with the screws.
When i used the bring command the console started and then shut down after about 30 sec.
I thout it was a normal procedure fot that command, because when i dumped again the syscon i got confused the last error (was 1200 but i confused with 1002) but it was a security shut down caused by a overheat.

So even that error it's by my fault, the console can generate new error code if some problem occour.

I tried to clear the error log, but the command clearerrlog report me an error ([UCMD] Unknow command).


All the error date stamp are right, because i didn't changed the internal battery for several years until last week (when i opened the console for the first time and than set the current date).


I can try to change the hdmi encoder taking it from the other board (what is the best way to remove/replace it?).

In any case if this doesn't resolv the problem, like RIP-Felix say, i think that the last chance is to rebal/replace the RSX.

But for the same price as the repair i can buy a working used ps3.

 

[M4j0r]

@RIP-Felix you might be interested in this:

, it maps the CELL POR Phase 2 to the Syscon sequence numbers.

Phase 0 and 1 can't be mapped to the HIG since they're different - let me quote myself:

I just discovered that the CELL SPI is already active in POR Phase 1 (where the security/pll init happens). The HIG specifies that the SPI interface is not active until Phase 2, but Syscon waits for attention and then sends the PLL data in Phase 1 (that's what I use to overclock CELL). Interestingly it happens in the step where it says that the PLL and security settings are read from the internal fuses. Well, the PLL data is loaded from Syscon, does that mean you can do the same for the security data?

 

[RIP-Felix]

I tried to clear the error log, but the command clearerrlog report me an error ([UCMD] Unknow command).

Try clearerrorlog then.

All the error date stamp are right, because i didn't changed the internal battery for several years until last week (when i opened the console for the first time and than set the current date).

Wait, how? You can't set the time unless you can see? I thought you said that it was GLOD? As in, no video.

I can try to change the hdmi encoder taking it from the other board (what is the best way to remove/replace it?).

In any case if this doesn't resolv the problem, like RIP-Felix say, i think that the last chance is to rebal/replace the RSX.

But for the same price as the repair i can buy a working used ps3.

Yeah, IMO it would be cheaper and easier to buy a replacment console. The only reason to go to that much trouble is if there were saves, pictures, or videos that are very important to you.

 

[RIP-Felix]

@RIP-Felix you might be interested in this:
View attachment 37923
, it maps the CELL POR Phase 2 to the Syscon sequence numbers.

Phase 0 and 1 can't be mapped to the HIG since they're different - let me quote myself:

Firmware sequence begins after POR. I've seen errors from NAND with step number 60ish. I can check later to get specifics, but I'm pretty sure that POR ends after BitTraining (step 40). So the Firmware sequence begins sometime after that. Errors after 40 are therefore related to issues with SS2, NAND, or HDD. The HIG is only takling about it so far as it's related to the CELL. So that cytology probably makes sense. But the SYSCON has a few more checks before it can safely access the bootloader.

 

[TYRANT]

Try clearerrorlog then.


Wait, how? You can't set the time unless you can see? I thought you said that it was GLOD? As in, no video.


Yeah, IMO it would be cheaper and easier to buy a replacment console. The only reason to go to that much trouble is if there were saves, pictures, or videos that are very important to you.

Already tried with clearerrorlog, but same result.
The strange thing is that i have tried some other commands, but everytime i got the same response at the end:

>$ bsn
F0000003
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

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

>$ becount
F0000003
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

>$ disp_err
F0000003
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

>$ boardconfig
F0000003
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

For the error log, i just compared the first that i have made (when the ps3 can reach the xmb) with all the dates, and the last one (made with an uart adapter because i can't see nothing on both video output).
The errors are the same in the same order.

I'm trying to fix my ps3, because i like learn new things and try to repair things by my self (if is it possible).