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

Shawn Shakir · Oct 8, 2022

alty75 said:
If it was off an KTE then there is a high possibility that it was foobarred prior to lifting it to use elsewhere

Yeah, replaced it with another 40NM pull, console now boots!

Blackbrew · Oct 12, 2022

Thank you guys for great info in this thread.
is it common for error A0403034 to be the only error reported in the log ?

board COK-001
syscon
version: v1.0.0_k1
revision: 0B8E

Pacorretaco · Oct 12, 2022

Blackbrew said:
Thank you guys for great info in this thread.
is it common for error A0403034 to be the only error reported in the log ?

board COK-001
syscon
version: v1.0.0_k1
revision: 0B8E

Thats actually a very good question.

And theres a trick. You have a COK-001 board with a 201GB syscon yes?
You also provided syscon version and revision because indeed, I think this is important too.

I think the lone 3034 in the log is simply a primitive behavior of the early SYSCON.
Later, in the newer models, the 3034 will be accompanied by a 4xxx error for more detail. But the underlying problem may be the same, just logged in different ways.
You need to use bringup for more details.

So to answer your question... Yes it is common, but only in the oldest boards.
Otherwise no. 3034 alone is not common.
I wonder if somebody could find a lone 3034 in a board "other than" COK-001.

Cheers

Blackbrew · Oct 12, 2022

Pacorretaco said:
Thats actually a very good question.

And theres a trick. You have a COK-001 board with a 201GB syscon yes?
You also provided syscon version and revision because indeed, I think this is important too.

I think the lone 3034 in the log is simply a primitive behavior of the early SYSCON.
Later, in the newer models, the 3034 will be accompanied by a 4xxx error for more detail. But the underlying problem may be the same, just logged in different ways.
You need to use bringup for more details.

So to answer your question... Yes it is common, but only in the oldest boards.
Otherwise no. 3034 alone is not common.
I wonder if somebody could find a lone 3034 in a board "other than" COK-001.

Cheers

Thank you for your reply,
yes this is one of my oldest CECHB00 20GB version.

> 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:0x20e2
> lasterrlog
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
> shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

errlog
ofst[100]:err_code:0xffffffff, clock:0x1d8f1f8f 2015/09/18 19:16:31
ofst[104]:err_code:0xa0403034, clock:0x1d8f1f92 2015/09/18 19:16:34
ofst[108]:err_code:0xa0403034, clock:0x1d8f1f96 2015/09/18 19:16:38
ofst[112]:err_code:0xa0403034, clock:0x1d8f1f99 2015/09/18 19:16:41
ofst[116]:err_code:0xa0403034, clock:0x1d8f1f9d 2015/09/18 19:16:45
ofst[120]:err_code:0xa0403034, clock:0x1d8f1fa1 2015/09/18 19:16:49
ofst[124]:err_code:0xa0403034, clock:0x1d8f1fa4 2015/09/18 19:16:52
ofst[ 0]:err_code:0xa0403034, clock:0x1d8f1fa7 2015/09/18 19:16:55
ofst[ 4]:err_code:0xa0403034, clock:0x1d8f1faa 2015/09/18 19:16:58
ofst[ 8]:err_code:0xa0403034, clock:0x1d8f1fad 2015/09/18 19:17:01
ofst[ 12]:err_code:0xa0403034, clock:0x1d8f1fb0 2015/09/18 19:17:04
ofst[ 16]:err_code:0xa0403034, clock:0x1d8f1fb4 2015/09/18 19:17:08
ofst[ 20]:err_code:0xa0403034, clock:0x1d8f1fdc 2015/09/18 19:17:48
ofst[ 24]:err_code:0xa0403034, clock:0x1d8f2278 2015/09/18 19:28:56
ofst[ 28]:err_code:0xa0403034, clock:0x1d8f236c 2015/09/18 19:33:00
ofst[ 32]:err_code:0xa0403034, clock:0x1d8f23a2 2015/09/18 19:33:54
ofst[ 36]:err_code:0xa0403034, clock:0x1d8f23b4 2015/09/18 19:34:12
ofst[ 40]:err_code:0xa0403034, clock:0x1d8f23c4 2015/09/18 19:34:28
ofst[ 44]:err_code:0xa0403034, clock:0x1d8f23ce 2015/09/18 19:34:38
ofst[ 48]:err_code:0xa0403034, clock:0x1d8f23d2 2015/09/18 19:34:42
ofst[ 52]:err_code:0xa0403034, clock:0x1d8f23d8 2015/09/18 19:34:48
ofst[ 56]:err_code:0xa0403034, clock:0x1d8f23e3 2015/09/18 19:34:59
ofst[ 60]:err_code:0xa0403034, clock:0x1d8f2416 2015/09/18 19:35:50
ofst[ 64]:err_code:0xa0403034, clock:0x1d8f2603 2015/09/18 19:44:03
ofst[ 68]:err_code:0xa0403034, clock:0x1d8f260b 2015/09/18 19:44:11
ofst[ 72]:err_code:0xa0403034, clock:0x1d8f2610 2015/09/18 19:44:16
ofst[ 76]:err_code:0xa0403034, clock:0x28c0cbfc 2021/08/31 11:16:12
ofst[ 80]:err_code:0xa0403034, clock:0x2ad02f3f 2022/10/05 12:04:15
ofst[ 84]:err_code:0xa0403034, clock:0x2ad02f56 2022/10/05 12:04:38
ofst[ 88]:err_code:0xa0403034, clock:0x2ad02f70 2022/10/05 12:05:04
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
[mullion]$

DeadEnd · Oct 12, 2022

Blackbrew said:
Thank you guys for great info in this thread.
is it common for error A0403034 to be the only error reported in the log ?

board COK-001
syscon
version: v1.0.0_k1
revision: 0B8E

Yes, I had one like that not too long ago and it booted after baking the board at 90 C.

Blackbrew · Oct 12, 2022

DeadEnd said:
Yes, I had one like that not too long ago and it booted after baking the board at 90 C.

Man !! I just watched your video few days ago by YT recommendations, still wondering about your DIY rework station, it would make a very nice winter afternoon project

if you care to share details.
as for baking the board , im too nervous to do it..

RIP-Felix · Oct 12, 2022

The lone 3034 I believe happens when the refrence voltage is where the defect occurs. Whereas you get data errors and 3034 when a data line is affected.

EDIT: Because I sense paco will want evidence, here is the result from sabotaging the RSX FlexIO reference voltage...

SW_5_B
--> Enable Pin 3 (IC6200)

--> Gate Pin 4 (Q6200) --> +1.2V_RSX_VDDR (JL9651)

--> If lifted = A0403034 (BitTraining RSX:RRAC:BX0:BX:FlexIO_ID)

alty75 · Oct 12, 2022

Paco is right. Boards with the 201GB SYSCON will only produce 3034 without any other error code like later SYSCON revisions that will throw a 4XXX and or a 2120 with the 3034

DeadEnd · Oct 13, 2022

RIP-Felix said:
The lone 3034 I believe happens when the refrence voltage is where the defect occurs. Whereas you get data errors and 3034 when a data line is affected.

EDIT: Because I sense paco will want evidence, here is the result from sabotaging the RSX FlexIO reference voltage...

SW_5_B
--> Enable Pin 3 (IC6200)

--> Gate Pin 4 (Q6200) --> +1.2V_RSX_VDDR (JL9651)

--> If lifted = A0403034 (BitTraining RSX:RRAC:BX0:BX:FlexIO_ID)

Small clarification. It throws FlexIO_ID step only when it's unhappy about RSX revision or missing VDDR. Normally it doesn't complain about that. So in the case of a bga/internal issue can produce a lone 3034, but at a different bittraining step.

Pacorretaco · Oct 13, 2022

RIP-Felix said:
The lone 3034 I believe happens when the refrence voltage is where the defect occurs. Whereas you get data errors and 3034 when a data line is affected.

EDIT: Because I sense paco will want evidence, here is the result from sabotaging the RSX FlexIO reference voltage...

SW_5_B
--> Enable Pin 3 (IC6200)

--> Gate Pin 4 (Q6200) --> +1.2V_RSX_VDDR (JL9651)

--> If lifted = A0403034 (BitTraining RSX:RRAC:BX0:BX:FlexIO_ID)

Well, but the thing is that you sabotaged an old COK-001 board with an old Syscon, didnt you?

I believe if you do the same exact sabotage on a newer board, you will get 3034 + 4002 (for FLEXIO_ID)...

RIP-Felix · Oct 13, 2022

It was the easiest way to test what a lack of voltage would do. I wasn't going to have him try slicing individual FlexIO traces to see what error it throw when you take out RX0's voltage refrence line. I suspect the bittraining error would be different. It's just impractical.

Tony359 · Oct 19, 2022

Hello all - can someone please direct me to some instructions on how to decode the timestamp of syscon error codes? I'm diagnosing a COK-002 which shows potentially harmless 1001 codes but I wanted to see if I could see from the codes when that happened.

Thank you!

Edit: found the solution myself. In Internal mode I get all the details I need! Thanks anyways!

Timbo9876 · Oct 20, 2022

I have recently bought a COK-001 (CECHA00) Backwards Compatible PS3 of Ebay.

I have used PS3 pro tools to obtain the Syscon error log which can be found below. The console boots but before i clean it out and referbish it i like to see if there has ever been a fatal error. The two codes i have found are 1200 (CPU over heat) and a 2022 which i have no idea what this actually is. My question is, is it likely this been recovered from a serious fault or do I have nothing to worry about?

Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 2078, Shutdown Count: 1699
Runtime: 180 Days, 14 Hours, 40 Minutes, 53 Seconds
Error Log
01: A0801200 Tue May 11 10:47:20 2010
02: A0802022 Fri Dec 5 06:00:55 2008
03: A0802022 Fri Dec 5 06:00:55 2008
04: A0802022 Fri Dec 5 06:00:55 2008
05: A0802022 Fri Dec 5 06:00:55 2008
06: A0802022 Wed Dec 3 05:39:45 2008
07: A0802022 Wed Dec 3 05:39:45 2008
08: A0802022 Wed Dec 3 05:39:45 2008
09: A0802022 Wed Dec 3 05:39:45 2008
10: A0802022 Tue Dec 2 17:35:36 2008
11: A0802022 Tue Dec 2 17:35:36 2008
12: A0802022 Tue Dec 2 17:35:36 2008
13: A0802022 Tue Dec 2 17:35:36 2008
14: A0802022 Tue Dec 2 17:00:28 2008
15: A0802022 Tue Dec 2 17:00:28 2008
16: A0802022 Tue Dec 2 17:00:28 2008
17: A0802022 Tue Dec 2 17:00:28 2008
18: A0802022 Mon Dec 1 15:25:28 2008
19: A0802022 Mon Dec 1 15:25:28 2008
20: A0802022 Mon Dec 1 15:25:28 2008
21: A0802022 Mon Dec 1 15:25:28 2008
22: A0802022 Mon Nov 24 10:13:56 2008
23: A0802022 Mon Nov 24 10:13:55 2008
24: A0802022 Mon Nov 24 10:13:55 2008
25: A0802022 Mon Nov 24 10:13:55 2008
26: A0802022 Fri Nov 21 13:09:24 2008
27: A0802022 Fri Nov 21 13:09:24 2008
28: A0802022 Fri Nov 21 13:09:24 2008
29: A0802022 Fri Nov 21 13:09:24 2008
30: A0802022 Thu Nov 20 12:07:56 2008
31: A0802022 Thu Nov 20 12:07:56 2008
32: FFFFFFFF Thu Nov 20 12:07:56 2008

sandungas · Oct 21, 2022

Timbo9876 said:
I have recently bought a COK-001 (CECHA00) Backwards Compatible PS3 of Ebay.

I have used PS3 pro tools to obtain the Syscon error log which can be found below. The console boots but before i clean it out and referbish it i like to see if there has ever been a fatal error. The two codes i have found are 1200 (CPU over heat) and a 2022 which i have no idea what this actually is. My question is, is it likely this been recovered from a serious fault or do I have nothing to worry about?

Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 2078, Shutdown Count: 1699
Runtime: 180 Days, 14 Hours, 40 Minutes, 53 Seconds
Error Log
01: A0801200 Tue May 11 10:47:20 2010
02: A0802022 Fri Dec 5 06:00:55 2008
03: A0802022 Fri Dec 5 06:00:55 2008
04: A0802022 Fri Dec 5 06:00:55 2008
05: A0802022 Fri Dec 5 06:00:55 2008
06: A0802022 Wed Dec 3 05:39:45 2008
07: A0802022 Wed Dec 3 05:39:45 2008
08: A0802022 Wed Dec 3 05:39:45 2008
09: A0802022 Wed Dec 3 05:39:45 2008
10: A0802022 Tue Dec 2 17:35:36 2008
11: A0802022 Tue Dec 2 17:35:36 2008
12: A0802022 Tue Dec 2 17:35:36 2008
13: A0802022 Tue Dec 2 17:35:36 2008
14: A0802022 Tue Dec 2 17:00:28 2008
15: A0802022 Tue Dec 2 17:00:28 2008
16: A0802022 Tue Dec 2 17:00:28 2008
17: A0802022 Tue Dec 2 17:00:28 2008
18: A0802022 Mon Dec 1 15:25:28 2008
19: A0802022 Mon Dec 1 15:25:28 2008
20: A0802022 Mon Dec 1 15:25:28 2008
21: A0802022 Mon Dec 1 15:25:28 2008
22: A0802022 Mon Nov 24 10:13:56 2008
23: A0802022 Mon Nov 24 10:13:55 2008
24: A0802022 Mon Nov 24 10:13:55 2008
25: A0802022 Mon Nov 24 10:13:55 2008
26: A0802022 Fri Nov 21 13:09:24 2008
27: A0802022 Fri Nov 21 13:09:24 2008
28: A0802022 Fri Nov 21 13:09:24 2008
29: A0802022 Fri Nov 21 13:09:24 2008
30: A0802022 Thu Nov 20 12:07:56 2008
31: A0802022 Thu Nov 20 12:07:56 2008
32: FFFFFFFF Thu Nov 20 12:07:56 2008

Have you checked if it outputs good video and audio by the MultiAV connector ?, the error 2022 is related with the DVE controller (CXM4024R)

alty75 · Oct 21, 2022

I've had it with other codes on a sherwood system and the fix has been RSX NEC's

A0801002/2022/2024

RSX NEC Caps - All errors together in the log.

1

RIP-Felix · Oct 21, 2022

Timbo9876 said:
I have recently bought a COK-001 (CECHA00) Backwards Compatible PS3 of Ebay.

I have used PS3 pro tools to obtain the Syscon error log which can be found below. The console boots but before i clean it out and referbish it i like to see if there has ever been a fatal error. The two codes i have found are 1200 (CPU over heat) and a 2022 which i have no idea what this actually is. My question is, is it likely this been recovered from a serious fault or do I have nothing to worry about?

Platform ID: Cok14
Product Code: 00 83
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 2078, Shutdown Count: 1699
Runtime: 180 Days, 14 Hours, 40 Minutes, 53 Seconds
Error Log
01: A0801200 Tue May 11 10:47:20 2010
02: A0802022 Fri Dec 5 06:00:55 2008
03: A0802022 Fri Dec 5 06:00:55 2008
04: A0802022 Fri Dec 5 06:00:55 2008
05: A0802022 Fri Dec 5 06:00:55 2008
06: A0802022 Wed Dec 3 05:39:45 2008
07: A0802022 Wed Dec 3 05:39:45 2008
08: A0802022 Wed Dec 3 05:39:45 2008
09: A0802022 Wed Dec 3 05:39:45 2008
10: A0802022 Tue Dec 2 17:35:36 2008
11: A0802022 Tue Dec 2 17:35:36 2008
12: A0802022 Tue Dec 2 17:35:36 2008
13: A0802022 Tue Dec 2 17:35:36 2008
14: A0802022 Tue Dec 2 17:00:28 2008
15: A0802022 Tue Dec 2 17:00:28 2008
16: A0802022 Tue Dec 2 17:00:28 2008
17: A0802022 Tue Dec 2 17:00:28 2008
18: A0802022 Mon Dec 1 15:25:28 2008
19: A0802022 Mon Dec 1 15:25:28 2008
20: A0802022 Mon Dec 1 15:25:28 2008
21: A0802022 Mon Dec 1 15:25:28 2008
22: A0802022 Mon Nov 24 10:13:56 2008
23: A0802022 Mon Nov 24 10:13:55 2008
24: A0802022 Mon Nov 24 10:13:55 2008
25: A0802022 Mon Nov 24 10:13:55 2008
26: A0802022 Fri Nov 21 13:09:24 2008
27: A0802022 Fri Nov 21 13:09:24 2008
28: A0802022 Fri Nov 21 13:09:24 2008
29: A0802022 Fri Nov 21 13:09:24 2008
30: A0802022 Thu Nov 20 12:07:56 2008
31: A0802022 Thu Nov 20 12:07:56 2008
32: FFFFFFFF Thu Nov 20 12:07:56 2008

A few users have reported these 802022 errors in the logs of (apparently) perfectly working consoles. IMO, the concern is the overheating CPU, which is easy enough to fix. Test and see if the console is stable. And if so, i wouldn't worry about it.

sandungas · Oct 22, 2022

RIP-Felix said:
A few users have reported these 802022 errors in the logs of (apparently) perfectly working consoles. IMO, the concern is the overheating CPU, which is easy enough to fix. Test and see if the console is stable. And if so, i wouldn't worry about it.

I was thinking about this before and there is a couple of details that worths to be discussed, what confuses me a bit is the MultiAV connector pinout doesnt have any pin that could be used as an "input"
Lets say... is an unidirectional communication, and the PS3 doesnt really knows if there is a TV at the other side

In other words... i think the syscon is not going to generate an error if you boot the PS3 with the MultiAV video option enabled but without a TV connected at the other side of the cable
Mostly because when you are using the MultiAV video output the PS3 doesnt knows anything about "outside" of the PS3

*In a HDMI connection this is way different, the syscon->HDMI controller "scans" for the TV specs... and i guess it could generate some syscon error codes

Timbo9876 · Oct 22, 2022

RIP-Felix said:
A few users have reported these 802022 errors in the logs of (apparently) perfectly working consoles. IMO, the concern is the overheating CPU, which is easy enough to fix. Test and see if the console is stable. And if so, i wouldn't worry about it.

Console is a little high on the CPU (console needs to be running on 37 percent fan speed to keep the temps under 68 degrees on the CPU when running TLOU). I played the first two chapters with no issues at all, I will check to see if its been opened down to the MB, if not its just a thermal paste change, if it has I will reevaluate the situation as I see it.

Timbo9876 · Oct 22, 2022

sandungas said:
Have you checked if it outputs good video and audio by the MultiAV connector ?, the error 2022 is related with the DVE controller (CXM4024R)

No, I will check and report back

sandungas · Oct 23, 2022

Timbo9876 said:
No, I will check and report back

Check also the XMB video settings (to disable the multiAV output ?), and after some experiments remember to dump the syscon error log again
We need to check the dates to figure if is still triggering errors 2022

Im not sure if the timestamps of your errorlog are real, but we can compare them with your previous post to find if are new

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

Shawn Shakir

Member

Blackbrew

Member

Pacorretaco

Member

Blackbrew

Member

DeadEnd

Senior Member

Blackbrew

Member

RIP-Felix

Senior Member

alty75

Member

DeadEnd

Senior Member

Pacorretaco

Member

RIP-Felix

Senior Member

Tony359

Member

Timbo9876

Member

sandungas

alty75

Member

RIP-Felix

Senior Member

sandungas

Timbo9876

Member

Timbo9876

Member

sandungas

Similar threads