PS3 (Research/Experimental) - NEC/TOKIN Capacitors Replacement - YLOD

[doc_gc]

Replace the CPU side TOKINs.

3003 is the next level escalation of 1001. It's more diagnostic of an issue with the CELL VDDC filter than 1001 is. The behavior is consistant with cpu tokins.

It can be realated to the VRM as well, but start with tokins.

Thank you!!
I saw that usually 3003 is coming with 1002 and this probably means NEC caps dead, idk in this case if will fix but will try for sure for a first diagnosis



edit: also, can i ask you to confirm me that there are no schematics for DIA boards around? Tried to search them but no luck, only for COK boards actually

 

[RIP-Felix]

The only schematics that exist in the Obtainable domain are the the COK-00X and SEM-001.

 

[marciolsf]

Amazing this thread is still going strong. Good job @RIP-Felix for still sticking around and helping everyone!

 

[Destroyerr]

Hello everyone!

A few days ago I bought a used PS3 (CECHC04) and right after I got it, I cleaned it (it was very dusty) and replaced the thermal paste (no delid).

After that I installed CFW and tried to play some games from the hdd. But after about 40sec it turns itself off with a beep and the red light starts to flash until I hit the power button, then it stays red and I can turn it on again.
The temperatures shouldn't be an issue as both CPU and RSX are at 65°C or less when this happens.
It happens with Ps2 games aswell as Ps3 games.
As a first fix I tried to replace the old hdd with a new ssd and at first I thought that, this fixed the problem but it just took longer (about 30min) until the same thing happened.

Here is the Syscon error log:

Spoiler: Syscon error log

Bringup Count: 1342, Shutdown Count: 897
Runtime: 125 Days, 17 Hours, 15 Minutes, 52 Seconds

Error Log
01: A0801001 Mon Jan 2 06:04:16 2006
02: A0801002 Sun Jan 1 21:51:54 2006
03: A0801002 Sat Dec 31 07:22:12 2005
04: A0802022 Sat Dec 31 07:18:51 2005
05: A0801002 Sat Dec 31 07:15:57 2005
06: A0802022 Sat Dec 31 07:12:38 2005
07: A0802022 Sat Dec 31 05:18:54 2005
08: A0802022 Sat Dec 31 05:17:42 2005
09: A0802022 Sat Dec 31 05:09:10 2005
10: A0802022 Sat Dec 31 05:08:02 2005
11: A0802022 Sat Dec 31 05:00:53 2005
12: A0802022 Sat Dec 31 04:55:09 2005
13: A0801002 Sat May 11 22:43:41 2024
14: A0801002 Thu May 9 23:33:02 2024
15: A0801002 Thu May 9 23:32:50 2024
16: A0801002 Thu May 9 23:32:21 2024
17: A0801002 Thu May 9 23:20:42 2024
18: A0801002 Tue Feb 20 22:26:40 2024
19: A0801004 Fri Sep 16 23:18:51 2016
20: A0801004 Mon Sep 14 21:45:23 2015
21: A0801004 Fri Sep 11 00:56:28 2015
22: A0801004 Wed Aug 5 14:18:14 2015
23: A0801004 Tue Aug 4 12:45:50 2015
24: A0801001 Sun Jul 19 13:11:30 2015
25: A0801004 Thu Jul 2 12:54:02 2015
26: A0801004 Wed Jul 1 12:51:26 2015
27: A0801004 Sat Jun 27 23:42:38 2015
28: A0801004 Thu Jun 25 13:16:07 2015
29: A0801001 Sun May 3 00:04:46 2015
30: A0801001 Fri May 1 11:17:34 2015
31: A0801001 Fri May 1 02:26:55 2015
32: FFFFFFFF Wed Apr 29 01:44:34 2015

I have read some older posts here and with these error codes the fault should be with the Nec/Tokin capacitors right?
If that is true my best course of action would be to replace the NEC's on the bottom first as they are the most prone to fail, correct?

Thanks in advance!

 

[Francis023]

Hi, is it possible to use the 470uf from donor board? I have super slim donor board and upon checking it has some 470uf.

 

[bass9030]

Hello, I recently bought a PS3 that won't power on due to a YLOD issue and replaced all 4 capacitors on the RSX side with tantalum.
The modding was successful, but due to the low quality tantalum from aliexpress, the PS3 randomly shuts down with YLOD unless I fix the fan speed to 40% via webman.
So I want to order and replace the RIP Felix's Tantalizer PCB, do I have to make a jumper even if I use that PCB? Or does the PCB have a built-in jumper circuit?

 

[Bertus van Zyl]

So I got my tantalum caps from the place I won't name yesterday. After replacing the 2 Tokins for RSX on one side of the board the console booted right up after it initially only stayed on for a second. I'll get me some decent caps from RS-Electronics or LCSC just to be safe though. For now it's stable playing youtube at least, i'll try some gaming later on.

 

[Starship2]

so i think i screwed up. I have a cok001. Had the error 3034. Which i know to be bad solder joints. Before i reflowed using preheater, i decided to delid the CPU. I think i dropped the ball big time and slightly cut into the chip. I am getting error 2001 which corresponds with a bad CPU. here is the log.

how do i replace the CPU? i know that the cpu is married to the mobo. Do i need to replace the correspoding southbridge? I know its possible but i forgot how. Damn im pissed off for cutting into the cpu. I had a lot of games on this ps3. any advice? i want to bring it back to life. I have a stencil to reball the cpu. what else i need.?

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\UsersXXXXXXX>cd c:\python27\scripts
c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXRF
>$ AUTh
Auth successful
>$ 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
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39
:57)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.
ITC_DUMP000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000
PTC_DUMP0000000009cf0a30000000000a5e0ac0000000000a710ae0000000000a690ace00000000
09cb0a290000000009d60a340000000009cf0a30000000000a6b0ace000000000000000000000000
0a4e0ab4000000000a3d0aa900000000099109f3000000000a380aa200000000099a0a0200000000
000000000000000000000000000000000a4d0aaf00000000000000000000000009aa0a0700000000
098c09ef000000000a100a7400000000098909f200000000097a09e300000000098209e600000000
09a40a06000000000a010a6700000000000000000000000009ff0a61000000000a090a6f00000000
09b40a12000000000a2a0a900000000009a90a08000000000a280a89000000000a260a8200000000
0a2d0a9600000000000000000000000009ad0a0f000000000a2e0a8e0000000009fb0a6300000000
098109eb000000000a140a7c000000000a120a7d00000000099e0a05000000000a240a8b00000000
00000000000000000a090a70000000000a020a690000000009af0a12000000000a100a7b00000000
099609fc0000000009a70a0a00000000098f09ef00000000098009e7000000000000000000000000
09cf0a310000000009a30a07000000000a5b0ac6000000000a4f0abd00000000098d09f300000000
099809fb00000000099309fa000000000a5b0ac60000000000000000000000000a7b0add00000000
0a4d0ab20000000009ce0a2f000000000a720adb0000000009e50a450000000009d00a3000000000
0a690acb000000000a7e0ae0000000000000
0000[mullion]$
MIC_DUMP000000000000000000000000000000000000000000000000320000000000000000000000
0000000000000000000000000000000fffffff800000000000012000000000000010000080000000
00000000000000000000000008000000000000000800000000000000000000000000000000000000
00000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d700000
0000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b870000
00000000140002000000000004810000000000000100000000000000c80000000000000000000000
00000000000010000000000000000000000000001b87000000000000140002000000000004810000
000000000100000000000000c8000000000000000000000000000000000010000000000000000000
00000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210
000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000
000000000800000000000000080000000000000000000000000000000000000000000000ffc00000
00000000061101700000000040000000000000007cfe000000000000e1c000000000000000000000
0000000000000000000000000000fd40000000000000028000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000001300000000
00000000
XIO_DUMP000100020009000002110000036c0000000000160000000000000210000710e109410000
000f000f00200000a08000080001e10f000008540c540000000000010bad00000000000000000000
0000000c000c000c000c00580058005800580000000000000000007f007f
>$ shutfown
007f007f44384438443844389309930d9311930b0000006000000000000000000000000000000bad
00000bad002a0bad002c0bad00000000000000000bad3f000bad3f39000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000009ff
0a8f0aa80a9b09fa0a0509ff0a9c000009cf0a5e0a710a6909cb09d609cf0a6b00000a300ac00ae0
0ace0a290a340a300ace000006030603060306030603060306030603060800000000000000000000
00000000000000020000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000a810a7309c20a6d09ce000000000a7e00000a4e0a3d09910a38099a000000000a4d
00000ab40aa909f30aa20a02000000000aaf00000603060306030603060306080608060306080000
00000000000000000002000200000002000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000009d809bd0a4209bd09ae09b409d50a34000009aa098c0a100989
097a098209a40a0100000a0709ef0a7409f209e309e60a060a670000060306030603060306030603
06030603060800000000000000000000000000000000000200000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000000000000a300a3c09e30a5d09d80a580a540a610000
09ff0a0909b40a2a09a90a280a260a2d00000a610a6f0a120a900a080a890a820a96000006030603
06030603060306030603060306080000000000000000000000000000000000020000000000000000
00000000000000000000000000000000shutfown
*** Unknown Command ***
0000[mullion]$ 00000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000001000200090000020c0000036c000000000016000000000000020c00071
0e109410000000f000f00200000a08000080001e00f000008540c540000000000010bad000000000
000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4
4384438443844389309930d9317930d0000000000000000000000000000000000000bad00000bad0
02c0bad002c0bad00000000000000000bad3f000bad3f00000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000
>$ shutdown
0000000000000000000000000000000000000000000000000000000000000000000009de0a5e0a2f
09b60a480a4709d10a57000009ad0a2e09fb09810a140a12099e0a2400000a0f0a8e0a6309eb0a7c
0a7d0a050a8b00000603060306030603060306030603060306080000000000000000000000000000
00000002000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000a3c0a3509e00a4509c909d809bf09b300000a090a0209af0a10099609a7098f098000000a70
0a690a120a7b09fc0a0a09ef09e70000060306030603060306030603060306030608000000000000
00000000000000000000000200000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000a0009d50a900a8609c009c909c60a90000009cf09a30a5b0a4f098d0998
09930a5b00000a310a070ac60abd09f309fb09fa0ac6000006030603060306030603060306030603
06080000000000000000000000000000000000020000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
000000000000000000000000000000000000shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
0aac[ERR_PRINT] serv_cons.c, line 132
[SERV CONSOLE] *** sending error ***
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$

ive fixed all my 3034 errors by replacing nec/tokins. seems like if they cant provide a stable/clean current that this can also trigger 3034's. in all cases it was enough to just replace 2 tokins, didnt ever have to change both sides.

 

[sojogabosta]

Hi guys, new to the forum (at least for this thread)

Bought a Fatboy a while ago and now it's giving the ylod error. It's a CECHL01 Set/2008 (Canadian I guess), was never opened, it boots up, stays normal at xmb and it's not overheating. I noticed the three beeps only with demanding games (L.A. Noire, New Vegas) and with anything with split screen.
I extracted de syscon log and got this:

Spoiler: Syscon log

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

Bringup Count: 1481, Shutdown Count: 1265
Runtime: 52 Days, 23 Hours, 54 Minutes, 1 Seconds

Error Log
01: A0802124  Sun Jan  1 03:46:08 2006
02: A0801002  Sun Jan  1 03:46:07 2006
03: A0802124  Sun Jan  1 01:31:03 2006
04: A0802124  Sun Jan  1 01:31:03 2006
05: A0801002  Sun Jan  1 01:31:02 2006
06: A0802124  Sun Jan  1 00:36:21 2006
07: A0801002  Sun Jan  1 00:36:20 2006
08: A0802124  Sun Jan  1 00:17:45 2006
09: A0802124  Sun Jan  1 00:17:45 2006
10: A0801002  Sun Jan  1 00:17:44 2006
11: A0802124  Sun Jan  1 00:14:40 2006
12: A0802124  Sun Jan  1 00:14:39 2006
13: A0801002  Sun Jan  1 00:14:39 2006
14: A0802124  Sun Jan  1 00:05:38 2006
15: A0802124  Sun Jan  1 00:05:37 2006
16: A0801002  Sun Jan  1 00:05:37 2006
17: A0802124  Fri Jan  6 22:49:27 2006
18: A0801002  Fri Jan  6 22:49:27 2006
19: A0802124  Fri Jan  6 22:35:39 2006
20: A0801002  Fri Jan  6 22:35:39 2006
21: A0802124  Fri Jan  6 22:02:24 2006
22: A0801002  Fri Jan  6 22:02:24 2006
23: A0802124  Fri Jan  6 18:34:56 2006
24: A0802124  Fri Jan  6 18:34:55 2006
25: A0801002  Fri Jan  6 18:34:55 2006
26: A0802124  Fri Jan  6 18:34:03 2006
27: A0802124  Fri Jan  6 18:34:03 2006
28: A0802124  Fri Jan  6 18:34:02 2006
29: A0801002  Fri Jan  6 18:34:02 2006
30: A0802124  Fri Jan  6 18:33:08 2006
31: A0802124  Fri Jan  6 18:33:08 2006
32: FFFFFFFF  Fri Dec 31 23:59:59 1999

Do you guys have any thoughts on it? From my research it's those NEC/Tolkins from the RSX side, but I could be mistaken.

 

[Starship2]

Hi guys, new to the forum (at least for this thread)

Bought a Fatboy a while ago and now it's giving the ylod error. It's a CECHL01 Set/2008 (Canadian I guess), was never opened, it boots up, stays normal at xmb and it's not overheating. I noticed the three beeps only with demanding games (L.A. Noire, New Vegas) and with anything with split screen.
I extracted de syscon log and got this:

Spoiler: Syscon log

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

Bringup Count: 1481, Shutdown Count: 1265
Runtime: 52 Days, 23 Hours, 54 Minutes, 1 Seconds

Error Log
01: A0802124  Sun Jan  1 03:46:08 2006
02: A0801002  Sun Jan  1 03:46:07 2006
03: A0802124  Sun Jan  1 01:31:03 2006
04: A0802124  Sun Jan  1 01:31:03 2006
05: A0801002  Sun Jan  1 01:31:02 2006
06: A0802124  Sun Jan  1 00:36:21 2006
07: A0801002  Sun Jan  1 00:36:20 2006
08: A0802124  Sun Jan  1 00:17:45 2006
09: A0802124  Sun Jan  1 00:17:45 2006
10: A0801002  Sun Jan  1 00:17:44 2006
11: A0802124  Sun Jan  1 00:14:40 2006
12: A0802124  Sun Jan  1 00:14:39 2006
13: A0801002  Sun Jan  1 00:14:39 2006
14: A0802124  Sun Jan  1 00:05:38 2006
15: A0802124  Sun Jan  1 00:05:37 2006
16: A0801002  Sun Jan  1 00:05:37 2006
17: A0802124  Fri Jan  6 22:49:27 2006
18: A0801002  Fri Jan  6 22:49:27 2006
19: A0802124  Fri Jan  6 22:35:39 2006
20: A0801002  Fri Jan  6 22:35:39 2006
21: A0802124  Fri Jan  6 22:02:24 2006
22: A0801002  Fri Jan  6 22:02:24 2006
23: A0802124  Fri Jan  6 18:34:56 2006
24: A0802124  Fri Jan  6 18:34:55 2006
25: A0801002  Fri Jan  6 18:34:55 2006
26: A0802124  Fri Jan  6 18:34:03 2006
27: A0802124  Fri Jan  6 18:34:03 2006
28: A0802124  Fri Jan  6 18:34:02 2006
29: A0801002  Fri Jan  6 18:34:02 2006
30: A0802124  Fri Jan  6 18:33:08 2006
31: A0802124  Fri Jan  6 18:33:08 2006
32: FFFFFFFF  Fri Dec 31 23:59:59 1999

Do you guys have any thoughts on it? From my research it's those NEC/Tolkins from the RSX side, but I could be mistaken.

Im pretty sure that problem is caused by the tokins from RSX. Replace two of them and it should run fine again.

 

[Guzza]

Hi all, I'm looking for advice on what I should attempt, I've Ordered 20x 32V 5A 1608 Fuses to replace F6001, its the only blown fuse found. I'm Ready to blow a few looking for the cause.

The only other component that didn't look great (off colour - corroded?) was Capacitor C6020 22uF 16V 3225, once removed it measures as ~500ohms, the C6019 in parallel measured as expected.

the schematic I snipped and marked up shows this F6001 is on +12V rail supplying Q6002 FDQ7238AS DC-DC converter supplying:-

1. IC6003 "MB39A116APFT-G-JN-ERE1 is a DC-DC switching controller designed for power management applications"
2. +5V_MISC Rail
3. +3.3V_MK_VDD (Via IC6020)
4. +1.5V_RSX_VIDEO (Via IC6017 and Q6012)
5. +5V_BD (Via Q6010)
6. +5V_USB (Via Q6008)
7. +5V_HDD (Via Q6007)

Spoiler: COK-002 Schematic

Spoiler: Syscon

EEPCSUM

*** Unknown Command ***

[mullion]$
eepcsum

Addr:0x000032fe should be 0x528c

Addr:0x000034fe should be 0x7115

sum:0x0100

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
w 3dfe ff 00

w complete!

[mullion]$
ERRLOG

*** Unknown Command ***

[mullion]$
errlog

ofst[ 36]:err_code:0xffffffff, clock:0x0d97d4cd  2007/03/24 12:23:41

ofst[ 40]:err_code:0xa0801001, clock:0x0d97d601  2007/03/24 12:28:49

ofst[ 44]:err_code:0xa0802022, clock:0x0d9a6b77  2007/03/26 11:31:03

ofst[ 48]:err_code:0xa0801001, clock:0x0da4cb7b  2007/04/03 08:23:23

ofst[ 52]:err_code:0xa0801001, clock:0x0da6305e  2007/04/04 09:46:06

ofst[ 56]:err_code:0xa0801001, clock:0x0e2cabb8  2007/07/15 09:56:08

ofst[ 60]:err_code:0xa0802022, clock:0x0e8fb02e  2007/09/28 12:29:34

ofst[ 64]:err_code:0xa0801001, clock:0x0ec7d207  2007/11/10 02:20:55

ofst[ 68]:err_code:0xa0801001, clock:0x0ec91a3b  2007/11/11 01:41:15

ofst[ 72]:err_code:0xa0802022, clock:0x0ec91b4c  2007/11/11 01:45:48

ofst[ 76]:err_code:0xa0801001, clock:0x0ee33cae  2007/11/30 21:27:10

ofst[ 80]:err_code:0xa0801001, clock:0x0eed174a  2007/12/08 08:50:18

ofst[ 84]:err_code:0xa0801001, clock:0x290d1527  2021/10/28 08:00:39

ofst[ 88]:err_code:0xa0801001, clock:0x29128227  2021/11/01 10:47:03

ofst[ 92]:err_code:0xa0022110, clock:0x29128253  2021/11/01 10:47:47

ofst[ 96]:err_code:0xa0022110, clock:0x291282b1  2021/11/01 10:49:21

ofst[100]:err_code:0xa0022110, clock:0x291282ca  2021/11/01 10:49:46

ofst[104]:err_code:0xa0022110, clock:0x291282df  2021/11/01 10:50:07

ofst[108]:err_code:0xa0022110, clock:0x2912832b  2021/11/01 10:51:23

ofst[112]:err_code:0xa0022110, clock:0x29128335  2021/11/01 10:51:33

ofst[116]:err_code:0xa0022110, clock:0x29128389  2021/11/01 10:52:57

ofst[120]:err_code:0xa0022110, clock:0x29128397  2021/11/01 10:53:11

ofst[124]:err_code:0xa0022110, clock:0x291284e7  2021/11/01 10:58:47

ofst[  0]:err_code:0xa0022110, clock:0x29128529  2021/11/01 10:59:53

ofst[  4]:err_code:0xa0022110, clock:0x29472066  2021/12/11 08:40:06

ofst[  8]:err_code:0xa0022110, clock:0x29472080  2021/12/11 08:40:32

ofst[ 12]:err_code:0xa0022110, clock:0x29472086  2021/12/11 08:40:38

ofst[ 16]:err_code:0xa0022110, clock:0xffffffff

ofst[ 20]:err_code:0xa0022110, clock:0xffffffff

ofst[ 24]:err_code:0xa0022110, clock:0xffffffff

ofst[ 28]:err_code:0xa0022110, clock:0xffffffff

ofst[ 32]:err_code:0xa0022110, clock:0xffffffff

ofst[ 36]:err_code:0xa0022110, clock:0xffffffff

[mullion]$

becount

Bringup : 1413 times

Shutdown: 1394 times

Power-on: 167day 23hour 24min 53sec

[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.

Looking at the Syscon, Is this capacitor C6020 possibly my only issue?!?

When my Friend Bought This CECHC02 in 2021 from a second hand charity shop it turned on for 5 - 10 minutes before beeping to death, he gave it to me straight after.

I think the syscon log is pretty complete, prior to 2021 the most recent error was in 2007.

Bringup : 1413 times
Shutdown: 1394 times
Power-on: 167day 23hour 24min 53sec

 

[Starship2]

Readi

Hi all, I'm looking for advice on what I should attempt, I've Ordered 20x 32V 5A 1608 Fuses to replace F6001, its the only blown fuse found. I'm Ready to blow a few looking for the cause.

The only other component that didn't look great (off colour - corroded?) was Capacitor C6020 22uF 16V 3225, once removed it measures as ~500ohms, the C6019 in parallel measured as expected.

the schematic I snipped and marked up shows this F6001 is on +12V rail supplying Q6002 FDQ7238AS DC-DC converter supplying:-

1. IC6003 "MB39A116APFT-G-JN-ERE1 is a DC-DC switching controller designed for power management applications"
2. +5V_MISC Rail
3. +3.3V_MK_VDD (Via IC6020)
4. +1.5V_RSX_VIDEO (Via IC6017 and Q6012)
5. +5V_BD (Via Q6010)
6. +5V_USB (Via Q6008)
7. +5V_HDD (Via Q6007)

Spoiler: COK-002 Schematic

Spoiler: Syscon

EEPCSUM

*** Unknown Command ***

[mullion]$
eepcsum

Addr:0x000032fe should be 0x528c

Addr:0x000034fe should be 0x7115

sum:0x0100

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
w 3dfe ff 00

w complete!

[mullion]$
ERRLOG

*** Unknown Command ***

[mullion]$
errlog

ofst[ 36]:err_code:0xffffffff, clock:0x0d97d4cd  2007/03/24 12:23:41

ofst[ 40]:err_code:0xa0801001, clock:0x0d97d601  2007/03/24 12:28:49

ofst[ 44]:err_code:0xa0802022, clock:0x0d9a6b77  2007/03/26 11:31:03

ofst[ 48]:err_code:0xa0801001, clock:0x0da4cb7b  2007/04/03 08:23:23

ofst[ 52]:err_code:0xa0801001, clock:0x0da6305e  2007/04/04 09:46:06

ofst[ 56]:err_code:0xa0801001, clock:0x0e2cabb8  2007/07/15 09:56:08

ofst[ 60]:err_code:0xa0802022, clock:0x0e8fb02e  2007/09/28 12:29:34

ofst[ 64]:err_code:0xa0801001, clock:0x0ec7d207  2007/11/10 02:20:55

ofst[ 68]:err_code:0xa0801001, clock:0x0ec91a3b  2007/11/11 01:41:15

ofst[ 72]:err_code:0xa0802022, clock:0x0ec91b4c  2007/11/11 01:45:48

ofst[ 76]:err_code:0xa0801001, clock:0x0ee33cae  2007/11/30 21:27:10

ofst[ 80]:err_code:0xa0801001, clock:0x0eed174a  2007/12/08 08:50:18

ofst[ 84]:err_code:0xa0801001, clock:0x290d1527  2021/10/28 08:00:39

ofst[ 88]:err_code:0xa0801001, clock:0x29128227  2021/11/01 10:47:03

ofst[ 92]:err_code:0xa0022110, clock:0x29128253  2021/11/01 10:47:47

ofst[ 96]:err_code:0xa0022110, clock:0x291282b1  2021/11/01 10:49:21

ofst[100]:err_code:0xa0022110, clock:0x291282ca  2021/11/01 10:49:46

ofst[104]:err_code:0xa0022110, clock:0x291282df  2021/11/01 10:50:07

ofst[108]:err_code:0xa0022110, clock:0x2912832b  2021/11/01 10:51:23

ofst[112]:err_code:0xa0022110, clock:0x29128335  2021/11/01 10:51:33

ofst[116]:err_code:0xa0022110, clock:0x29128389  2021/11/01 10:52:57

ofst[120]:err_code:0xa0022110, clock:0x29128397  2021/11/01 10:53:11

ofst[124]:err_code:0xa0022110, clock:0x291284e7  2021/11/01 10:58:47

ofst[  0]:err_code:0xa0022110, clock:0x29128529  2021/11/01 10:59:53

ofst[  4]:err_code:0xa0022110, clock:0x29472066  2021/12/11 08:40:06

ofst[  8]:err_code:0xa0022110, clock:0x29472080  2021/12/11 08:40:32

ofst[ 12]:err_code:0xa0022110, clock:0x29472086  2021/12/11 08:40:38

ofst[ 16]:err_code:0xa0022110, clock:0xffffffff

ofst[ 20]:err_code:0xa0022110, clock:0xffffffff

ofst[ 24]:err_code:0xa0022110, clock:0xffffffff

ofst[ 28]:err_code:0xa0022110, clock:0xffffffff

ofst[ 32]:err_code:0xa0022110, clock:0xffffffff

ofst[ 36]:err_code:0xa0022110, clock:0xffffffff

[mullion]$

becount

Bringup : 1413 times

Shutdown: 1394 times

Power-on: 167day 23hour 24min 53sec

[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.

Looking at the Syscon, Is this capacitor C6020 possibly my only issue?!?

When my Friend Bought This CECHC02 in 2021 from a second hand charity shop it turned on for 5 - 10 minutes before beeping to death, he gave it to me straight after.

I think the syscon log is pretty complete, prior to 2021 the most recent error was in 2007.

Bringup : 1413 times
Shutdown: 1394 times
Power-on: 167day 23hour 24min 53sec

Dont forget to check C6023. I'd guess the readings of measured Caps look fine so far even though that those measurements just show these caps are not shorted. There are other important Values like the capacitance. But lets pretend they are good at this point. Next i would check the Buck Converter Q6002 for shorts, they fail sometimes and put extra load on F6001. If this also shows good readings, replace F6001 and see what happens.
Your DVE Error is something you dont have to worry about yet. i wouldnt pay attention on that one.
Next thing is to see what is going to happen with that 1001 Cell Power error, i dont think its related to the Clock gen problem. It can possibly occur when the console shuts down improperly, yes, but maybe you have to replace some tokins there to make it run again. Keep that in mind if replacing F6001 doesnt bring it back to life. Check Errorcodes again first.

 

[Adriaan Couchez]

Hi, got a cechc04 with ylod.

Can only get into the external mode.

Com pad seems broken from a previous owner who opened up the console and got the syscon.

Anyone got any insight in these errors and if its worth attempting repair.
From what i find these errors could be anything. (cell & rsx)

>$ ERRLOG GET 00
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit

 

[Starship2]

Hi, got a cechc04 with ylod.

Can only get into the external mode.

Com pad seems broken from a previous owner who opened up the console and got the syscon.

Anyone got any insight in these errors and if its worth attempting repair.
From what i find these errors could be anything. (cell & rsx)

>$ ERRLOG GET 00
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0003001 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0A02031 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0093004 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
Press Ctrl+C to exit

first check 12v rail and your psu. you have an 3001 error which shows up if there is anything wrong with 12v supply. further it seems your rsx maybe needs to get new tokins, but first see if 3004 still exists when you figured out why it has that 3001 error.

 

[Adriaan Couchez]

first check 12v rail and your psu. you have an 3001 error which shows up if there is anything wrong with 12v supply. further it seems your rsx maybe needs to get new tokins, but first see if 3004 still exists when you figured out why it has that 3001 error.

Thanks for the insight . I was able to get into internal mode now. (had to replace diag pad).
The 3001 error must have been from the previous owner. I think they maybe didn't connect the psu correctly.

When i try a bringup it only shows the 3004 error.

>$ bringup
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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004
Press Ctrl+C to exit
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

It's weird because it's a bit of a longer YLOD then my other broken ps3 .
Would anyone have an idea about the 3004?

 

[Starship2]

Thanks for the insight . I was able to get into internal mode now. (had to replace diag pad).
The 3001 error must have been from the previous owner. I think they maybe didn't connect the psu correctly.

When i try a bringup it only shows the 3004 error.

>$ bringup
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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093004
Press Ctrl+C to exit
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

It's weird because it's a bit of a longer YLOD then my other broken ps3 .
Would anyone have an idea about the 3004?

we have to be clear if 3001 is an older error or if its actual. that could change things.
what step number do you have? looks like bad rsx tokins to me. try replacing them if you are sure about 3001.

 

[NextJack0325]

Attention All Newcomers:
We are always repeating ourselves answering questions that have been answered ad nauseam. I will use this post as a catch all for future newcomers who need to catch up to the current state of the thread. If you are not willing to read the entire thread before asking for help, at least read the following.

I compiled a shortlist of links to subjects that are particularly important to read. These disscussions and posts will help you understand how to fix your PS3 and how to avoid breaking it. They will also dispel some myths in the process.

• SYSCON Tutorial (Start Here First)
• SYSCON Analysis (what 250 consoles worth of data reveals)
• SB UART Tutorial
• TestBench Firmware (experimental)
  
• What Causes the YLOD?
• Poll: How long do reballs last?
  
• Frequently Asked Questions (FAQ)
• PS3 Sabotage tests (selectively disabling voltages to see what SYSCON error it produces)
  
• list of equipment I use for both SYSCON and DIY reballing/reflowing.
  
• A statistical analysis of the Tantalum YLOD Fix. Basically, how many people have actually fixed their PS3's by replaing the tokins using this tutorial. The next few comments afterwards are worth reading too.
  
• A Retrospective Analysis of the NEC/TOKIN Proadlizer (Part 1)
• A Retrospective Analysis of the NEC/TOKIN Proadlizer (Part 2)
• PS3 Tantalizer - Beta Release (v0.6b). There were other versions before this and I based them off the original PCB by SoulKilla. I intend to improve the design.
  
• Schematics and etc.
• RSX Pinout and Ohm testing.
• CELL BE Pinout
• Southbridge Pinout
  
• Botakompongs Pulse CLK method of Troubleshooting the PS3. This method is a powerful way to troubleshoot a PS3, with simple/cheap tools (an analog multimeter).
  
• The problem of BGA and why SONY should have known better! The following discussion is also quite entertaining.
• Frankenstein Phat PS3 Tutorial allowing a 65nm or 40nm RSX to replace the 90nm RSX on backwards compatible PS3's. Technically it can be used on any PS3 to allow different (pin compatable) RSX revisions to be used. But it finnally allows us to put a reliable RSX in a BC console.
• DIY CPU Deliding Tool that will allow you to safely remove the CPU's IHS and apply new thermal interface compound.
• Replace the IHS after Delidding.
  
• PS3 Power Control Topology (Part 1 - Under Voltage Lock-Out).
• PS3 Power Control Topology (Part 2 - Voltage Regulation & Power Good).
• PS3 Power Control Topology (Part 3 - SYSCON Switches & Power On Sequencing)
• Spoiler: PS3's I've worked on

  • PS3 #1 (Started on SHMUPS forum, then I moved to PSX place on Page 137. Console was destroyed in second reball attempt)
  • PS3 #2 (Started in the same post as PS3 #1. This Reball attempt left 2 RSX BGA pads torn. I repaired it and installed a 65nm RSX (Frankenstein phat ps3 mod). Has been working great since.)
  • PS3 #3 (Working, didn't read discs. BluRay just needed reseated. Used it as a working control for Oscilloscope measurements, to see what good tokins are supposed to look like.)
    
  • PS3 #4 (RSX BGA, traded to @squeept for PS3#7)
  • PS3 #5 (Working, nothing special)
    
  • PS3 #6 (HDMI port)
    
  • PS3 #7 (Reballed, bad Tokin filter charcterized with O-Scope)
    
  • PS3 #8 (Frankenstein/ORBIS Mod)
  • PS3 #9 (P model I bought to harvest 65nm RSX, but it worked and I didn't have the heart to kill it!)
  • PS3 #10 (YLOD, LAN/Optical Port damage.)
    
  • PS3 #11 (Sole 3034, Cell Trace damage. Attempted frankestein mod.)
    
  • PS3 #12 (GLOD, Replaced RSX with a 40nm)
  • PS3 #13 (Frakenstein with a 40nm, with lots of mistakes)
  • PS3 #14 (The Unholy 65nm Frankenstein)
    
  • PS3 #15 (E01 With Genuine Bad Tokins)
  • PS3 #16 (COK-001 w/65nm - GLOD from FW Downgrade?)
  • PS3 Slim #6 - Prototype DEH-2000A-A

I will edit this post as needed.

like SYSCON Tutorial

 

[The GT Army]

So I brought a Ps3 cechc03 untested off eBay for £40 and it had ylod, should my first step be getting access to the syscon error codes?

 

[RIP-Felix]

So I brought a Ps3 cechc03 untested off eBay for £40 and it had ylod, should my first step be getting access to the syscon error codes?

Generally that is advisable, just so you dont waste time chassing red herrings.

But if the YLOD occurs between 1 and 3 seconds after pressing the on pad, then we can guess with fairly high probability it's the GPU. Up to you what you want to do with it from there. If it's sealed it has more resale value, so unless you intend to attempt to repair it, that may be yojr best course of action. If you want to have it frankied, you could attempt to get sys on to see if it's a good candidate, but be careful not to tear the traces on the pads. If you're not confident you could just send it in and let them decided. They may prefer you don't open it.

Really depends on what you hope to do with it?

 

[RIP-Felix]

Hi all, I'm looking for advice on what I should attempt, I've Ordered 20x 32V 5A 1608 Fuses to replace F6001, its the only blown fuse found. I'm Ready to blow a few looking for the cause.

The only other component that didn't look great (off colour - corroded?) was Capacitor C6020 22uF 16V 3225, once removed it measures as ~500ohms, the C6019 in parallel measured as expected.

the schematic I snipped and marked up shows this F6001 is on +12V rail supplying Q6002 FDQ7238AS DC-DC converter supplying:-

1. IC6003 "MB39A116APFT-G-JN-ERE1 is a DC-DC switching controller designed for power management applications"
2. +5V_MISC Rail
3. +3.3V_MK_VDD (Via IC6020)
4. +1.5V_RSX_VIDEO (Via IC6017 and Q6012)
5. +5V_BD (Via Q6010)
6. +5V_USB (Via Q6008)
7. +5V_HDD (Via Q6007)

Spoiler: COK-002 Schematic

Spoiler: Syscon

EEPCSUM

*** Unknown Command ***

[mullion]$
eepcsum

Addr:0x000032fe should be 0x528c

Addr:0x000034fe should be 0x7115

sum:0x0100

Addr:0x00003dfe should be 0x00ff

Addr:0x00003ffe should be 0x00ff
w 3dfe ff 00

w complete!

[mullion]$
ERRLOG

*** Unknown Command ***

[mullion]$
errlog

ofst[ 36]:err_code:0xffffffff, clock:0x0d97d4cd  2007/03/24 12:23:41

ofst[ 40]:err_code:0xa0801001, clock:0x0d97d601  2007/03/24 12:28:49

ofst[ 44]:err_code:0xa0802022, clock:0x0d9a6b77  2007/03/26 11:31:03

ofst[ 48]:err_code:0xa0801001, clock:0x0da4cb7b  2007/04/03 08:23:23

ofst[ 52]:err_code:0xa0801001, clock:0x0da6305e  2007/04/04 09:46:06

ofst[ 56]:err_code:0xa0801001, clock:0x0e2cabb8  2007/07/15 09:56:08

ofst[ 60]:err_code:0xa0802022, clock:0x0e8fb02e  2007/09/28 12:29:34

ofst[ 64]:err_code:0xa0801001, clock:0x0ec7d207  2007/11/10 02:20:55

ofst[ 68]:err_code:0xa0801001, clock:0x0ec91a3b  2007/11/11 01:41:15

ofst[ 72]:err_code:0xa0802022, clock:0x0ec91b4c  2007/11/11 01:45:48

ofst[ 76]:err_code:0xa0801001, clock:0x0ee33cae  2007/11/30 21:27:10

ofst[ 80]:err_code:0xa0801001, clock:0x0eed174a  2007/12/08 08:50:18

ofst[ 84]:err_code:0xa0801001, clock:0x290d1527  2021/10/28 08:00:39

ofst[ 88]:err_code:0xa0801001, clock:0x29128227  2021/11/01 10:47:03

ofst[ 92]:err_code:0xa0022110, clock:0x29128253  2021/11/01 10:47:47

ofst[ 96]:err_code:0xa0022110, clock:0x291282b1  2021/11/01 10:49:21

ofst[100]:err_code:0xa0022110, clock:0x291282ca  2021/11/01 10:49:46

ofst[104]:err_code:0xa0022110, clock:0x291282df  2021/11/01 10:50:07

ofst[108]:err_code:0xa0022110, clock:0x2912832b  2021/11/01 10:51:23

ofst[112]:err_code:0xa0022110, clock:0x29128335  2021/11/01 10:51:33

ofst[116]:err_code:0xa0022110, clock:0x29128389  2021/11/01 10:52:57

ofst[120]:err_code:0xa0022110, clock:0x29128397  2021/11/01 10:53:11

ofst[124]:err_code:0xa0022110, clock:0x291284e7  2021/11/01 10:58:47

ofst[  0]:err_code:0xa0022110, clock:0x29128529  2021/11/01 10:59:53

ofst[  4]:err_code:0xa0022110, clock:0x29472066  2021/12/11 08:40:06

ofst[  8]:err_code:0xa0022110, clock:0x29472080  2021/12/11 08:40:32

ofst[ 12]:err_code:0xa0022110, clock:0x29472086  2021/12/11 08:40:38

ofst[ 16]:err_code:0xa0022110, clock:0xffffffff

ofst[ 20]:err_code:0xa0022110, clock:0xffffffff

ofst[ 24]:err_code:0xa0022110, clock:0xffffffff

ofst[ 28]:err_code:0xa0022110, clock:0xffffffff

ofst[ 32]:err_code:0xa0022110, clock:0xffffffff

ofst[ 36]:err_code:0xa0022110, clock:0xffffffff

[mullion]$

becount

Bringup : 1413 times

Shutdown: 1394 times

Power-on: 167day 23hour 24min 53sec

[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.

Looking at the Syscon, Is this capacitor C6020 possibly my only issue?!?

When my Friend Bought This CECHC02 in 2021 from a second hand charity shop it turned on for 5 - 10 minutes before beeping to death, he gave it to me straight after.

I think the syscon log is pretty complete, prior to 2021 the most recent error was in 2007.

Bringup : 1413 times
Shutdown: 1394 times
Power-on: 167day 23hour 24min 53sec

Yes, very likely the only short. Those larger power caps on 3.3v MISC pull alot of current and experiance flexing due to their size. Ceramic doesn't flex well and they chip/break, their resistance increases then they burn out and then pop that fuse. Sounds like your issue.

Also, what you want are slow blow fuses to prevent them from popping from inrush currents when you first turn on or off the PSU. Just FYI.