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

Anyone know what the small rectangular in the pictures is? I knocked two off when I dropped something on them. I've lost one of them but have the other. I think the traces have been torn off as well. Also, are they necessary?
 
Another evening on this. It was going ok then I knocked off two components as mentioned before. Not sure what they are or if the can be left out. I have one but lost the other, if someone could shed some insight that would be appreciated. The images should be in a reply above this. I have since been able to get internal access and can post the results of the in depth error log as well as the bring up results if that would help someone assist me. I have tested the PSU and get in the kΩ on one of the 12V pins and get 5 volts on the two 5 volt pins in the psu so I'm guessing that means it's something on the motherboard resulting in the 2110 I keep getting? Does that sound right? Thanks in advance.
 
Hello everyone, I have a fat PS3 that started to have the yload problem, the famous yellow LED started to gradually decrease the time it remained on, from the SYSCON program it gives me error A0093003
, initially I replaced the capacitors in the CPU and also GPU but unfortunately the error returns, now the power-on time is non-existent as soon as you press the power button it immediately goes into protection
IMG-20240318-153740355.jpg

IMG-20240313-201414223.jpg

IMG-20240313-201323242-HDR.jpg

You must bridge the wire because you replaced all tokins. Just replace the bottom one will be enough.
 
hi, after a reflow (320°C for like 10 minutes) for fixing code A0801002, my ps3 didn't turn on anymore, so checking syscon codes two times it gave me that errors:
===================================
ERR 00: 00000000 A0A02131 FFFFFFFF
ERR 01: 00000000 A0A02131 FFFFFFFF
ERR 02: 00000000 A0A02130 FFFFFFFF
ERR 03: 00000000 A0A02130 FFFFFFFF
ERR 04: 00000000 A0A02131 FFFFFFFF
ERR 05: 00000000 A0A02131 FFFFFFFF
ERR 06: 00000000 A0A02130 FFFFFFFF
ERR 07: 00000000 A0A02130 FFFFFFFF
ERR 08: 00000000 A0A02131 FFFFFFFF
ERR 09: 00000000 A0A02131 FFFFFFFF
ERR 10: 00000000 A0112130 FFFFFFFF
ERR 11: 00000000 A0112130 FFFFFFFF
ERR 12: 00000000 A0902130 FFFFFFFF
ERR 13: 00000000 A0112130 FFFFFFFF
ERR 14: 00000000 A0112131 FFFFFFFF
ERR 15: 00000000 A0A02131 FFFFFFFF
ERR 16: 00000000 A0A02131 FFFFFFFF
ERR 17: 00000000 A0A02130 FFFFFFFF
ERR 18: 00000000 A0A02130 FFFFFFFF
ERR 19: 00000000 A0112130 FFFFFFFF
===================================
and
===================================
ERR 00: 00000000 A0112131 FFFFFFFF
ERR 01: 00000000 A0112130 FFFFFFFF
ERR 02: 00000000 A0112130 FFFFFFFF
ERR 03: 00000000 A0A02131 FFFFFFFF
ERR 04: 00000000 A0A02131 FFFFFFFF
ERR 05: 00000000 A0A02130 FFFFFFFF
ERR 06: 00000000 A0A02130 FFFFFFFF
ERR 07: 00000000 A0112131 FFFFFFFF
ERR 08: 00000000 A0112130 FFFFFFFF
ERR 09: 00000000 A0112131 FFFFFFFF
ERR 10: 00000000 A0112130 FFFFFFFF
ERR 11: 00000000 A0A02131 FFFFFFFF
ERR 12: 00000000 A0A02131 FFFFFFFF
ERR 13: 00000000 A0A02130 FFFFFFFF
ERR 14: 00000000 A0A02130 FFFFFFFF
ERR 15: 00000000 A0A02131 FFFFFFFF
ERR 16: 00000000 A0A02131 FFFFFFFF
ERR 17: 00000000 A0A02130 FFFFFFFF
ERR 18: 00000000 A0A02130 FFFFFFFF
ERR 19: 00000000 A0A02131 FFFFFFFF
===================================
looking for informations seems that i broke temperature sensors of RSX and CELL, do i?
its sure that i also fixed A0801002?
and whats the fix for these errors?

its a DYN-001 CECH-2004A.

1002 is RSX tokins, not sure why you try to reflow it. Maybe you knocked off the temperature sensor or just killed it.
 
Just received CECHA console with YLOD and full list of 3034 errors. I reflowed RSX and console booted, however cannot get signal to the screen via hdmi or AV (GLOD). Now I get full list of errors A0802022 (DVE errors). I already replaced CXM4024R MultiAV controller chip from donor board, but same errors. Do you think that faulty RSX can cause 2022 errors? I am going to replace RSX with 40nm if you don't have any other good ideas to fix this.

SB log shows that console boots just fine, controller syncs etc. Log shows that console has Cell OS SDK4.8.1, am I right that this means firmware is 4.81, thus it supports then 40nm frankenstein mod?

GetAttachmentThumbnail
 
Last edited:
Hi, I have a CECHC with GLOD with multiple A0202120 and some A0802020 error. Fuses, 1.7V_MISC, 1.5V_YC_RC_VDDIO are OK.
any idea?

errlog
ofst[ 12]:err_code:0xffffffff, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 16]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 20]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 24]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 28]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 32]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 36]:err_code:0xa0202120, clock:0x0b51cf8c 2006/01/07 01:02:04
ofst[ 40]:err_code:0xa0802020, clock:0x0b51cf90 2006/01/07 01:02:08
ofst[ 44]:err_code:0xa0802020, clock:0x0b51cf90 2006/01/07 01:02:08
ofst[ 48]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 52]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 56]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 60]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 64]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 68]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 72]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 76]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 80]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 84]:err_code:0xa0202120, clock:0x0b51cfca 2006/01/07 01:03:06
ofst[ 88]:err_code:0xa0802020, clock:0x0b51cfd1 2006/01/07 01:03:13
ofst[ 92]:err_code:0xa0802020, clock:0x0b51cfd1 2006/01/07 01:03:13
ofst[ 96]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[100]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[104]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[108]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[112]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[116]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[120]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[124]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[ 0]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[ 4]:err_code:0xa0202120, clock:0x0b6193f3 2006/01/19 00:04:03
ofst[ 8]:err_code:0xa0802020, clock:0x0b6193f7 2006/01/19 00:04:07

[mullion]$
becount
Bringup : 3789 times
Shutdown: 3164 times
Power-on: 196day 03hour 57min 00sec

[mullion]$
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
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
[ERROR]: 0xa0202120
 
So I'm pretty fearful around electrical stuff so I was wondering if I can to plug anything to the ps3 or screw in the "ground" to anything. My ps3 is a cecha01. If you respond thank you in advance!
 
Just received CECHA console with YLOD and full list of 3034 errors. I reflowed RSX and console booted, however cannot get signal to the screen via hdmi or AV (GLOD). Now I get full list of errors A0802022 (DVE errors). I already replaced CXM4024R MultiAV controller chip from donor board, but same errors. Do you think that faulty RSX can cause 2022 errors? I am going to replace RSX with 40nm if you don't have any other good ideas to fix this.

SB log shows that console boots just fine, controller syncs etc. Log shows that console has Cell OS SDK4.8.1, am I right that this means firmware is 4.81, thus it supports then 40nm frankenstein mod?

GetAttachmentThumbnail
UPDATE. Swapped 40nm rsx and HDMI IC also. Same error codes A0802022 and GLOD. Need to investigate more on DVE/hdmi circuit.
 
Last edited:
Hello everyone. A few years ago I bought a secondhand CECHG04. After some time I decided to take it apart since it was very loud, so I changed the thermal paste and cleaned the dust. When I powered it up after assembly I was welcomed by the nefarious YLOD. I did my due diligence before embarking on this task, the console came apart and back together very nicely, nothing was forced. I took it apart afterwards to try the hair drayer method and indeed the console did boot up into XMB but after a minute or two the YLOD came back.
Now I wanted to take another look at it so I followed the Uart guide to pull up the error codes:
Code:
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0404421, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0404421, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404421, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404421, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404421, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0404421, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0404421, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0404421, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[  0]:err_code:0xa0404421, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0404421, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0404421, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0404421, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404421, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0404421, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0404421, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff

Bringup : 1240 times
Shutdown: 1130 times
Power-on: 119day 20hour 54min 12sec

power on command
Code:
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
Press Ctrl+C to exit
>$
[mullion]$ [SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[POWERSEQ] Error : BitTraining BE:RRAC:RX2: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]: 0xa0404421
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
 
Hi, I bought a CECHG model which wasn't working (YLOD after 6 seconds). The seller said it has been open at least twice, one time having the thermal paste replaced. The CPU and GPU were absolutely caked in thermal paste, so I don't think the guy who did it was very good and thermal paste was low quality. This is my first ps3 I've taken apart but there was this blue foam attached to I think the NEC tokens and some other stuff, idk if that is normal but I don't think I saw it in disassembly videos. Any ideas on what the issue is please?

Code:
ofst[  8]:err_code:0xffffffff, clock:0x0b4f6c05  2006/01/05 05:32:53
ofst[ 12]:err_code:0xa0801002, clock:0x0b4f6c0f  2006/01/05 05:33:03
ofst[ 16]:err_code:0xa0801002, clock:0x0b4f6d06  2006/01/05 05:37:10
ofst[ 20]:err_code:0xa0801002, clock:0x0b4f7381  2006/01/05 06:04:49
ofst[ 24]:err_code:0xa0801002, clock:0x0b4f7394  2006/01/05 06:05:08
ofst[ 28]:err_code:0xa0801002, clock:0x0b4f73d4  2006/01/05 06:06:12
ofst[ 32]:err_code:0xa0801002, clock:0x0b4f7544  2006/01/05 06:12:20
ofst[ 36]:err_code:0xa0801002, clock:0x0b4f755c  2006/01/05 06:12:44
ofst[ 40]:err_code:0xa0801002, clock:0x0b4f758f  2006/01/05 06:13:35
ofst[ 44]:err_code:0xa0801002, clock:0x0b4f76c3  2006/01/05 06:18:43
ofst[ 48]:err_code:0xa0801002, clock:0x0b4f792b  2006/01/05 06:28:59
ofst[ 52]:err_code:0xa0801002, clock:0x0b4f79b9  2006/01/05 06:31:21
ofst[ 56]:err_code:0xa0801002, clock:0x0b4f7a8c  2006/01/05 06:34:52
ofst[ 60]:err_code:0xa0801002, clock:0x0b4f7ad2  2006/01/05 06:36:02
ofst[ 64]:err_code:0xa0801002, clock:0x0b4f7b44  2006/01/05 06:37:56
ofst[ 68]:err_code:0xa0801002, clock:0x0b4f7c41  2006/01/05 06:42:09
ofst[ 72]:err_code:0xa0801002, clock:0x0b4f7ea8  2006/01/05 06:52:24
ofst[ 76]:err_code:0xa0801002, clock:0x0b4f81e3  2006/01/05 07:06:11
ofst[ 80]:err_code:0xa0801002, clock:0x0b4f87df  2006/01/05 07:31:43
ofst[ 84]:err_code:0xa0801002, clock:0x0b4f8c53  2006/01/05 07:50:43
ofst[ 88]:err_code:0xa0801002, clock:0x0b4f8c89  2006/01/05 07:51:37
ofst[ 92]:err_code:0xa0801002, clock:0x0b4f8c95  2006/01/05 07:51:49
ofst[ 96]:err_code:0xa0801002, clock:0x0b4f8cae  2006/01/05 07:52:14
ofst[100]:err_code:0xa0801002, clock:0x0b4f8ce3  2006/01/05 07:53:07
ofst[104]:err_code:0xa0801002, clock:0x0b4f8cee  2006/01/05 07:53:18
ofst[108]:err_code:0xa0801002, clock:0x0b4f8d02  2006/01/05 07:53:38
ofst[112]:err_code:0xa0801002, clock:0x0b4f8d91  2006/01/05 07:56:01
ofst[116]:err_code:0xa0801002, clock:0x0b4f8da5  2006/01/05 07:56:21
ofst[120]:err_code:0xa0801002, clock:0x0b4f8eb6  2006/01/05 08:00:54
ofst[124]:err_code:0xa0801002, clock:0x0b4f909a  2006/01/05 08:08:58
ofst[  0]:err_code:0xa0801002, clock:0x0b4f90a8  2006/01/05 08:09:12
ofst[  4]:err_code:0xa0801002, clock:0x0b4f9178  2006/01/05 08:12:40
[mullion]$

Bringup : 1973 times
Shutdown: 1257 times
Power-on: 81day 02hour 04min 09sec
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
Press Ctrl+C to exit
>$ shutdown
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.9.0 (Build ID: 2398,24722, Build Data: 2007-07-22_15:55:29)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[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 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
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
 
Last edited:
Hello. I have a cechg08 fat console with 3 beeps.
So I got these code errors 3032

where should I start looking for the problem?

Auth successful
> ERRLOG GET 00
00000000 A0313032 FFFFFFFF
> ERRLOG GET 01
00000000 A0313032 FFFFFFFF
> ERRLOG GET 02
00000000 A0313032 FFFFFFFF
> ERRLOG GET 03
00000000 A0313032 FFFFFFFF
> ERRLOG GET 04
00000000 A0313032 FFFFFFFF
> ERRLOG GET 05
00000000 A0313032 FFFFFFFF
> ERRLOG GET 06
00000000 A0313032 FFFFFFFF
> ERRLOG GET 07
00000000 A0313032 FFFFFFFF
> ERRLOG GET 08
00000000 A0313032 FFFFFFFF
> ERRLOG GET 09
00000000 A0313032 FFFFFFFF
> ERRLOG GET 10
00000000 A0313032 FFFFFFFF
> ERRLOG GET 11
00000000 A0313032 FFFFFFFF
> ERRLOG GET 12
00000000 A0313032 FFFFFFFF
> ERRLOG GET 13
00000000 A0313032 FFFFFFFF
> ERRLOG GET 14
00000000 A0313032 FFFFFFFF
> ERRLOG GET 15
00000000 A0313032 FFFFFFFF
> ERRLOG GET 16
00000000 A0313032 FFFFFFFF
> ERRLOG GET 17
00000000 A0313032 FFFFFFFF
> ERRLOG GET 18
00000000 A0313032 FFFFFFFF
> ERRLOG GET 19
00000000 A0313032 FFFFFFFF
>

and

> errlog
errlog
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xa0313032, clock:0xffffffff
ofst[104]:err_code:0xa0313032, clock:0xffffffff
ofst[108]:err_code:0xa0313032, clock:0xffffffff
ofst[112]:err_code:0xa0313032, clock:0xffffffff
ofst[116]:err_code:0xa0313032, clock:0xffffffff
ofst[120]:err_code:0xa0313032, clock:0xffffffff
ofst[124]:err_code:0xa0313032, clock:0xffffffff
ofst[ 0]:err_code:0xa0313032, clock:0xffffffff
ofst[ 4]:err_code:0xa0313032, clock:0xffffffff
ofst[ 8]:err_code:0xa0313032, clock:0xffffffff
ofst[ 12]:err_code:0xa0313032, clock:0xffffffff
ofst[ 16]:err_code:0xa0313032, clock:0xffffffff
ofst[ 20]:err_code:0xa0313032, clock:0xffffffff
ofst[ 24]:err_code:0xa0313032, clock:0xffffffff
ofst[ 28]:err_code:0xa0313032, clock:0xffffffff
ofst[ 32]:err_code:0xa0313032, clock:0xffffffff
ofst[ 36]:err_code:0xa0313032, clock:0xffffffff
ofst[ 40]:err_code:0xa0313032, clock:0xffffffff
ofst[ 44]:err_code:0xa0313032, clock:0xffffffff
ofst[ 48]:err_code:0xa0313032, clock:0xffffffff
ofst[ 52]:err_code:0xa0313032, clock:0xffffffff
ofst[ 56]:err_code:0xa0313032, clock:0xffffffff
ofst[ 60]:err_code:0xa0313032, clock:0xffffffff
ofst[ 64]:err_code:0xa0313032, clock:0xffffffff
ofst[ 68]:err_code:0xa0313032, clock:0xffffffff
ofst[ 72]:err_code:0xa0313032, clock:0xffffffff
ofst[ 76]:err_code:0xa0313032, clock:0xffffffff
ofst[ 80]:err_code:0xa0313032, clock:0xffffffff
ofst[ 84]:err_code:0xa0313032, clock:0xffffffff
ofst[ 88]:err_code:0xa0313032, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>
 
Hello. I have a cechg08 fat console with 3 beeps.
So I got these code errors 3032

where should I start looking for the problem?

Auth successful
> ERRLOG GET 00
00000000 A0313032 FFFFFFFF
> ERRLOG GET 01
00000000 A0313032 FFFFFFFF
> ERRLOG GET 02
00000000 A0313032 FFFFFFFF
> ERRLOG GET 03
00000000 A0313032 FFFFFFFF
> ERRLOG GET 04
00000000 A0313032 FFFFFFFF
> ERRLOG GET 05
00000000 A0313032 FFFFFFFF
> ERRLOG GET 06
00000000 A0313032 FFFFFFFF
> ERRLOG GET 07
00000000 A0313032 FFFFFFFF
> ERRLOG GET 08
00000000 A0313032 FFFFFFFF
> ERRLOG GET 09
00000000 A0313032 FFFFFFFF
> ERRLOG GET 10
00000000 A0313032 FFFFFFFF
> ERRLOG GET 11
00000000 A0313032 FFFFFFFF
> ERRLOG GET 12
00000000 A0313032 FFFFFFFF
> ERRLOG GET 13
00000000 A0313032 FFFFFFFF
> ERRLOG GET 14
00000000 A0313032 FFFFFFFF
> ERRLOG GET 15
00000000 A0313032 FFFFFFFF
> ERRLOG GET 16
00000000 A0313032 FFFFFFFF
> ERRLOG GET 17
00000000 A0313032 FFFFFFFF
> ERRLOG GET 18
00000000 A0313032 FFFFFFFF
> ERRLOG GET 19
00000000 A0313032 FFFFFFFF
>

and

> errlog
errlog
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xa0313032, clock:0xffffffff
ofst[104]:err_code:0xa0313032, clock:0xffffffff
ofst[108]:err_code:0xa0313032, clock:0xffffffff
ofst[112]:err_code:0xa0313032, clock:0xffffffff
ofst[116]:err_code:0xa0313032, clock:0xffffffff
ofst[120]:err_code:0xa0313032, clock:0xffffffff
ofst[124]:err_code:0xa0313032, clock:0xffffffff
ofst[ 0]:err_code:0xa0313032, clock:0xffffffff
ofst[ 4]:err_code:0xa0313032, clock:0xffffffff
ofst[ 8]:err_code:0xa0313032, clock:0xffffffff
ofst[ 12]:err_code:0xa0313032, clock:0xffffffff
ofst[ 16]:err_code:0xa0313032, clock:0xffffffff
ofst[ 20]:err_code:0xa0313032, clock:0xffffffff
ofst[ 24]:err_code:0xa0313032, clock:0xffffffff
ofst[ 28]:err_code:0xa0313032, clock:0xffffffff
ofst[ 32]:err_code:0xa0313032, clock:0xffffffff
ofst[ 36]:err_code:0xa0313032, clock:0xffffffff
ofst[ 40]:err_code:0xa0313032, clock:0xffffffff
ofst[ 44]:err_code:0xa0313032, clock:0xffffffff
ofst[ 48]:err_code:0xa0313032, clock:0xffffffff
ofst[ 52]:err_code:0xa0313032, clock:0xffffffff
ofst[ 56]:err_code:0xa0313032, clock:0xffffffff
ofst[ 60]:err_code:0xa0313032, clock:0xffffffff
ofst[ 64]:err_code:0xa0313032, clock:0xffffffff
ofst[ 68]:err_code:0xa0313032, clock:0xffffffff
ofst[ 72]:err_code:0xa0313032, clock:0xffffffff
ofst[ 76]:err_code:0xa0313032, clock:0xffffffff
ofst[ 80]:err_code:0xa0313032, clock:0xffffffff
ofst[ 84]:err_code:0xa0313032, clock:0xffffffff
ofst[ 88]:err_code:0xa0313032, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>
A0313032 = SB_CLOCK OR INIT ERROR (can be related to the CELL solder balls not making proper connection and will most likely had previous errors like A0403034, A0404401) - check for voltages first!
 
Hi, I bought a CECHG model which wasn't working (YLOD after 6 seconds). The seller said it has been open at least twice, one time having the thermal paste replaced. The CPU and GPU were absolutely caked in thermal paste, so I don't think the guy who did it was very good and thermal paste was low quality. This is my first ps3 I've taken apart but there was this blue foam attached to I think the NEC tokens and some other stuff, idk if that is normal but I don't think I saw it in disassembly videos. Any ideas on what the issue is please?

Code:
ofst[  8]:err_code:0xffffffff, clock:0x0b4f6c05  2006/01/05 05:32:53
ofst[ 12]:err_code:0xa0801002, clock:0x0b4f6c0f  2006/01/05 05:33:03
ofst[ 16]:err_code:0xa0801002, clock:0x0b4f6d06  2006/01/05 05:37:10
ofst[ 20]:err_code:0xa0801002, clock:0x0b4f7381  2006/01/05 06:04:49
ofst[ 24]:err_code:0xa0801002, clock:0x0b4f7394  2006/01/05 06:05:08
ofst[ 28]:err_code:0xa0801002, clock:0x0b4f73d4  2006/01/05 06:06:12
ofst[ 32]:err_code:0xa0801002, clock:0x0b4f7544  2006/01/05 06:12:20
ofst[ 36]:err_code:0xa0801002, clock:0x0b4f755c  2006/01/05 06:12:44
ofst[ 40]:err_code:0xa0801002, clock:0x0b4f758f  2006/01/05 06:13:35
ofst[ 44]:err_code:0xa0801002, clock:0x0b4f76c3  2006/01/05 06:18:43
ofst[ 48]:err_code:0xa0801002, clock:0x0b4f792b  2006/01/05 06:28:59
ofst[ 52]:err_code:0xa0801002, clock:0x0b4f79b9  2006/01/05 06:31:21
ofst[ 56]:err_code:0xa0801002, clock:0x0b4f7a8c  2006/01/05 06:34:52
ofst[ 60]:err_code:0xa0801002, clock:0x0b4f7ad2  2006/01/05 06:36:02
ofst[ 64]:err_code:0xa0801002, clock:0x0b4f7b44  2006/01/05 06:37:56
ofst[ 68]:err_code:0xa0801002, clock:0x0b4f7c41  2006/01/05 06:42:09
ofst[ 72]:err_code:0xa0801002, clock:0x0b4f7ea8  2006/01/05 06:52:24
ofst[ 76]:err_code:0xa0801002, clock:0x0b4f81e3  2006/01/05 07:06:11
ofst[ 80]:err_code:0xa0801002, clock:0x0b4f87df  2006/01/05 07:31:43
ofst[ 84]:err_code:0xa0801002, clock:0x0b4f8c53  2006/01/05 07:50:43
ofst[ 88]:err_code:0xa0801002, clock:0x0b4f8c89  2006/01/05 07:51:37
ofst[ 92]:err_code:0xa0801002, clock:0x0b4f8c95  2006/01/05 07:51:49
ofst[ 96]:err_code:0xa0801002, clock:0x0b4f8cae  2006/01/05 07:52:14
ofst[100]:err_code:0xa0801002, clock:0x0b4f8ce3  2006/01/05 07:53:07
ofst[104]:err_code:0xa0801002, clock:0x0b4f8cee  2006/01/05 07:53:18
ofst[108]:err_code:0xa0801002, clock:0x0b4f8d02  2006/01/05 07:53:38
ofst[112]:err_code:0xa0801002, clock:0x0b4f8d91  2006/01/05 07:56:01
ofst[116]:err_code:0xa0801002, clock:0x0b4f8da5  2006/01/05 07:56:21
ofst[120]:err_code:0xa0801002, clock:0x0b4f8eb6  2006/01/05 08:00:54
ofst[124]:err_code:0xa0801002, clock:0x0b4f909a  2006/01/05 08:08:58
ofst[  0]:err_code:0xa0801002, clock:0x0b4f90a8  2006/01/05 08:09:12
ofst[  4]:err_code:0xa0801002, clock:0x0b4f9178  2006/01/05 08:12:40
[mullion]$

Bringup : 1973 times
Shutdown: 1257 times
Power-on: 81day 02hour 04min 09sec
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
Press Ctrl+C to exit
>$ shutdown
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.9.0 (Build ID: 2398,24722, Build Data: 2007-07-22_15:55:29)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[INFO]: Connecting to Debug Device (SB UART)
[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 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
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

most of the time the 1002 error is due to faulty tokens on the RSX. By removing the old capacitors and putting in tantalum ones you have a good chance of solving the problem. Remember to create bridges between the two positive areas as in the image above. NOTE: for the ground side you must preheat the board, the plate absorbs a lot of heat and you cannot make good soldering with just the soldering iron.
 
Hi everyone, after changing the capacitors I made the connection with a jumper cable, but it gives me these errors

IMG-20240321-100343023.jpg

IMG-20240321-205105566.jpg
ciao, did you by any chance manage to solve it? I have the same error 2120, the fuses are fine. I have two COK-002 boards (but the second one has about ten different errors) with which I can exchange components, I tried changing the capacitors near the F6302 but nothing changed
 
ciao, did you by any chance manage to solve it? I have the same error 2120, the fuses are fine. I have two COK-002 boards (but the second one has about ten different errors) with which I can exchange components, I tried changing the capacitors near the F6302 but nothing changed
Hi, I'm still looking at the moment, I've read that it could be a built-in or something else causing this problem
 
Hello, my ps3 has been turning off during start up for a while now (I press the button, it stays green for a few seconds without image and then it shuts down completely). When that happens, I found out that if I apply a little bit of pressure on the top it somehow turns on normally and I can play just fine afterwads. Usually when I open the PS3 and close it again, the problem goes away for like days or weeks until it inevitably returns. It's pretty random. Can anyone make sense of this? Here's the syscon log:

01: A0805FFF Fri Dec 31 23:59:59 1999
02: A0801601 Fri Dec 31 23:59:59 1999
03: A0801701 Fri Dec 31 23:59:59 1999
04: A0805FFF Fri Dec 31 23:59:59 1999
05: A0805FFF Fri Dec 31 23:59:59 1999
06: A0801601 Wed Jan 4 21:24:31 2006
07: A0801701 Wed Jan 4 21:24:31 2006
08: A0801601 Wed Jan 4 13:49:59 2006
09: A0801701 Wed Jan 4 13:49:59 2006
10: A0801601 Wed Jan 4 13:44:50 2006
11: A0801701 Wed Jan 4 13:44:50 2006
12: A0801601 Wed Jan 4 03:55:11 2006
13: A0801701 Wed Jan 4 03:55:10 2006
14: A0801601 Wed Jan 4 03:53:29 2006
15: A0801701 Wed Jan 4 03:53:29 2006
16: A0805FFF Wed Jan 4 03:47:35 2006
17: A0805FFF Wed Jan 4 03:44:15 2006
18: A0805FFF Wed Jan 4 03:42:59 2006
19: A0801601 Wed Jan 4 03:41:08 2006
20: A0801701 Wed Jan 4 03:41:07 2006
21: A0801601 Wed Jan 4 03:12:55 2006
22: A0801701 Wed Jan 4 03:12:54 2006
23: A0801601 Tue Jan 3 11:45:47 2006
24: A0801701 Tue Jan 3 11:45:47 2006
25: A0805FFF Tue Jan 3 11:44:52 2006
26: A0801601 Mon Jan 2 02:00:28 2006
27: A0801701 Mon Jan 2 02:00:27 2006
28: A0805FFF Mon Jan 2 12:06:29 2006
29: A0805FFF Sun Jan 1 23:27:59 2006
30: A0805FFF Sun Jan 1 23:26:27 2006
31: A0805FFF Sun Jan 1 12:20:30 2006
32: FFFFFFFF Fri Dec 31 23:59:59 1999
 
Just received CECHA console with YLOD and full list of 3034 errors. I reflowed RSX and console booted, however cannot get signal to the screen via hdmi or AV (GLOD). Now I get full list of errors A0802022 (DVE errors). I already replaced CXM4024R MultiAV controller chip from donor board, but same errors. Do you think that faulty RSX can cause 2022 errors? I am going to replace RSX with 40nm if you don't have any other good ideas to fix this.

SB log shows that console boots just fine, controller syncs etc. Log shows that console has Cell OS SDK4.8.1, am I right that this means firmware is 4.81, thus it supports then 40nm frankenstein mod?

GetAttachmentThumbnail

Yes, your FW is high enough to support 40nm RSX. Reflowing a defective RSX to a GLOD is common. It's usually a bad RSX that needs replaced. The reflow wouldn't have lasted long even if it had worked, so the only repair is to replace it. And yes, 2022 errors are easily caused by the RSX BGA/Bumps defects, since many of the IO traces go to the DVE. Same with 2020/2120 and 2024/2120 do for the HDMI transmitter. So they can also be caused by a bad RSX.
 
Another evening on this. It was going ok then I knocked off two components as mentioned before. Not sure what they are or if the can be left out. I have one but lost the other, if someone could shed some insight that would be appreciated. The images should be in a reply above this. I have since been able to get internal access and can post the results of the in depth error log as well as the bring up results if that would help someone assist me. I have tested the PSU and get in the kΩ on one of the 12V pins and get 5 volts on the two 5 volt pins in the psu so I'm guessing that means it's something on the motherboard resulting in the 2110 I keep getting? Does that sound right? Thanks in advance.

There is a service manual for the COK-002. In it you can find wiring shematic and labels for all the SMDs in the console. Please refer to it and tell use which components you knocked off. A picture would be helpful, but until you reach 10 posts on the forum you cannot upload them directly. You will have to use imgur or another picture hosting service and link.

2110 is a clock subsystem error usually stemming from an issue at or around 3.3v/5v Misc. It's very likely caused by whatever SMD you knocked off.
 

Similar threads

Back
Top