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

[RIP-Felix]

I noticed some of the tokins soldering strips came up easily, like they had fatigued or not been soldered on well. Shipping could have exacerbated a fatigued tokins solder joint. Also, I mentioned another user pointed out that thermal expansion cycles on such a large capacitor could fatigue those joints over time. That could be a possible point of failure.

I did note the resistance went up by a few mOhms after removing the tokins. Was 2.3 before, 2.6 somewhere in between, and now without them it's up to 2.9Ohms. Although, I don't really expect the resistance to go down if a solder joint was fatiguing. I did notice flux residue from the reball in and around the tokins, even between the +/GND rail, and I know that can reduce the resistance. Maybe that's all it is.

 

[RIP-Felix]

Oh BTW @squeept . Have a look at what the board looks like after cleaning flux residue off.

Spoiler: Flux residue Before/After

I cleaned it all off today after seeing the corrosion in the copper perimeter in the last photo. Keep using that ultrasonic cleaner and IPA my friend.

 

[RIP-Felix]

PS3 #7 - Part 12
(Last TaPol Array added to RSX + additional parasitic board to see what happens adding even more capacitance)
...continued from par 11 here.​

Here's the results of the last TaPol array on the RSX:

Spoiler: SYSCON, 4 TaPol Arrays added to RSX (All tokins replaced with 18x ETPSF270M6E)

80 1004 occurred when I flipped the PWR rocker off while the console was on. Haven't seen that one again. 80 1002 YLOD occurred while installing game data for NBA live 2012. RSX noise at idle was 50-60mVpp and the CPU bad waveform was mostly gone. 80 1002 YLOD happened again while rebuilding the HDD. Last one was in the menu of NBA live. I decided to try using the "brigup" command in the SYSCON to see if I can tease out more information from the "lasterrlog" and was able to record more of the startup sequence and shutdown sequence during the YLOD event. Notice that it say's "Power Fail RS". That must mean Reality Synthesizer. So that confirms the 1002 is the RSX for sure.

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ lasterrlog
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48916d  2005/12/31 00:46:37
[mullion]$
>$ errlog
errlog
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xa0801002, clock:0xffffffff
ofst[ 36]:err_code:0xa0801002, clock:0xffffffff
ofst[ 40]:err_code:0xa0801002, clock:0xffffffff
ofst[ 44]:err_code:0xa0801002, clock:0xffffffff
ofst[ 48]:err_code:0xa0801002, clock:0xffffffff
ofst[ 52]:err_code:0xa0801002, clock:0xffffffff
ofst[ 56]:err_code:0xa0801002, clock:0xffffffff
ofst[ 60]:err_code:0xa0801002, clock:0xffffffff
ofst[ 64]:err_code:0xa0801002, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
[mullion]$
>$ bringup
bringup
Do nothing. (FatalOff State)
>$ lasterrlog
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
[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.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
POWER Button released
[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
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b4892a3  2005/12/31 00:51:47
[mullion]$
>$ errlog
errlog
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xa0801002, clock:0xffffffff
ofst[ 40]:err_code:0xa0801002, clock:0xffffffff
ofst[ 44]:err_code:0xa0801002, clock:0xffffffff
ofst[ 48]:err_code:0xa0801002, clock:0xffffffff
ofst[ 52]:err_code:0xa0801002, clock:0xffffffff
ofst[ 56]:err_code:0xa0801002, clock:0xffffffff
ofst[ 60]:err_code:0xa0801002, clock:0xffffffff
ofst[ 64]:err_code:0xa0801002, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
[mullion]$
>$

Spoiler: O-Scope, 4 TaPol Arrays added to RSX (All tokins replaced with 18x ETPSF270M6E)

At this point I started to think that maybe I need more capacitance. So I decided to try the Parasite technique. So I whipped these up:

Spoiler: SYSCON, 3x 2R5TPE470M7 TaPol Parasite (YLOD in menu of NBA Live 2012)

Added 3x 2R5TPE470M7 TaPol on a parasite board to the RSX. It didn't make the console any more stable. No change really. Still YLOD in menus of NBA LIve 2012, normal stress. Basically a Random YLOD.

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ bringup
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48befd  2005/12/31 04:01:01
[mullion]$
>$ errlog
errlog
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xa0801002, clock:0xffffffff
ofst[ 48]:err_code:0xa0801002, clock:0xffffffff
ofst[ 52]:err_code:0xa0801002, clock:0xffffffff
ofst[ 56]:err_code:0xa0801002, clock:0xffffffff
ofst[ 60]:err_code:0xa0801002, clock:0xffffffff
ofst[ 64]:err_code:0xa0801002, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
[mullion]$
>$

Spoiler: SYSCON, 3x EEFSX0D471E4 AlPol Parasite on RSX (Less stable than TaPol)

Added 3x EEFSX0D471E4 AlPol on a parasite board to the RSX. It seemed to increase the noise and make the colsole less stable. More Delayed YLODs. When it did get to the game, it YLOD in menu like before. Didn't seem to help, in fact it seemed to be counter productive.

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ Auth
Auth successful
>$ lasterrlog
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48e824  2005/12/31 06:56:36
[mullion]$
>$ errlog
errlog
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xa0801002, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
[mullion]$
>$ 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 -> 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48e824  2005/12/31 06:56:36
[mullion]$ [SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
>$ lasterrlog
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48ec90  2005/12/31 07:15:28
[mullion]$
>$ errlog
errlog
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xa0801002, clock:0xffffffff
ofst[ 72]:err_code:0xa0801002, clock:0xffffffff
ofst[ 76]:err_code:0xa0801002, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
[mullion]$
>$

Spoiler: O-Scope, 3x 2R5TPE470M7 TaPol Parasite on RSX

Spoiler: O-Scope, 3x 2EEFSX0D471E4 AlPol Parasite on RSX

So at this point I'm thinking that the CPU tokins must be the problem here. They must be interfering, preventing the RSX noise from falling further. So I decided to try adding the TaPol parasite in parallel with the CPU tokins. So all four tokins + the TaPol parasite:

Spoiler: SYSCON, 4 TaPol Arrays added to RSX + 1 CPU Parasitic

Made the system barely more stable. It still YLOD in the same place in menu of NBA LIve 2012. It seems to get there more consistantly, but if there is an improvment it's a small one. I didn't get many delayed YLOD, they were about as often as they were with just 4 TaPol arrays witout the parasites.

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ lasterrlog
lasterrlog
Last Error Code:0xa0801002, Time:0x0b488987  2005/12/31 00:12:55
[mullion]$
>$ errlog
errlog
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xa0801002, clock:0xffffffff
ofst[ 84]:err_code:0xa0801002, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0801002, clock:0xffffffff
ofst[ 96]:err_code:0xa0801002, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
ofst[ 64]:err_code:0xa0801002, clock:0x0b4887e2  2005/12/31 00:05:54
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888e6  2005/12/31 00:10:14
ofst[ 72]:err_code:0xa0801002, clock:0x0b488987  2005/12/31 00:12:55
[mullion]$
>$ 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 -> 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b488d3d  2005/12/31 00:28:45
[mullion]$
>$

Spoiler: O-Scope, 3x 2R5TPE470M7 TaPol Parasite on CPU

The noise does seem a little better. I'm not sure if it's significant though.

At the target plateau the bad waveforem wasn't there...

...but I found it shows up more consistantly on the first plateau after the poweup spike. It is smaller by about 10mVpp. So the parasie is having an effect, but I think the bad tokins need to go.

I know that's alot, so here is the Results Table to sum it up:

At this point I'm thinking that the CPU tokins need to come off. But before I do I want to try a Tokin parasite. I have some new old stock tokins I can try. Until then...

Continued in part 13 here...

 

[Ricochet90]

I used to follow this thread back in 2019 but it became way too complicated for me, anyway congrats for continuing the research about this topic, please keep it going!

 

[squeept]

@RIP-Felix And that's no-clean flux, so imagine what the crap from AliExpress does after 10 years. Leaked capacitor electrolyte is worse by far, so I cringe at everyone selling recapped Game Gear and Sega CD 1 systems after they cleaned the leaks up with a q-tip and called it a day. That stuff gets in all the vias, and it sits under the chips melting the board away. It's downright criminal that people sell those without putting them through a cleaner.

I think some of my theories are starting to look promising again. I also want to point out the visual inspection shows those ones you popped the top off look perfect with no burning at the edges (I assume the burn marks are where the self healing mechanism activated). I remember popping the tops off the bad sets and finding one set was perfect, and one set later was burnt to a crisp. And I've still never found one that was out of spec for capacitance or ESR. That's further evidence to me that something weird physical is going on. And I think that's the final nail in the coffin for saying that if they looked burned, they were bad. It's completely unrelated to the burn marks.

And since you're more of the physics fella here... with that wire length, switching frequency, and the time constant (is that what I'm thinking of? IS IT?) ....are those actually even "in" the circuit? This is the question I had when people were putting electrolytics on a foot long wire outside of the shielding.

 

[RIP-Felix]

@RIP-Felix...And since you're more of the physics fella here... with that wire length, switching frequency, and the time constant (is that what I'm thinking of? IS IT?) ....are those actually even "in" the circuit? This is the question I had when people were putting electrolytics on a foot long wire outside of the shielding.

Sure, the noise reduction will be diminished simply because it's easier for the current to bypass the parasite and take an easier path to ground through the shorter array. The way I like to think of it is like water flowing through a channel. The wider the channel the more water can flow. So the shorter and more direct the path, the easier current will flow. Also the wider the channel the more water (current) can flow. So yes, they are in circuit, but no it's not ideal. I used 22AWG solid core, which is much thicker than the resistor legs on the arrays. So if the resistor legs were posing any sort of "narrow channel" that was allowing excess noise to "overflow the banks" and "flood" the console, then the excess water would "spill over" the parasite instead. It's like an emergency spill way in a reservoir. However, if the parasitic inductance of the long wires present too large a barrier, it's like placing the spillway up too high. It'll just spill over the banks and flood the town instead. At that point they are basically out of circuit.

What I don't know is if the parasite is "too high" to work (basically not in circuit like you say). I mean, the scope seems to suggest that the benefit is negligible, so either they aren't in curcuit or we're going significantly above the 4800uF sweet spot and the noise is getting worse because of it.

PS3#7 - Part 13
(Parasites galore)
...continued from part 12 here.
​

I tried a adding a tokin parasite to the RSX. This was in addition to the 3x 470uF TaPol parasite added to the CPU. So now both RSX and CPU should have around 6000uF. I even added a second + conductor just to give it the best chance of working.

Spoiler: SYSCON, 1x NOS TOKIN Parasite on RSX (30s YLOD)

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ lasterrlog
lasterrlog
Last Error Code:0xa0801002, Time:0x0b496a1a  2005/12/31 16:11:06
[mullion]$
>$ errlog
errlog
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xa0801002, clock:0xffffffff
ofst[104]:err_code:0xa0801002, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
ofst[ 64]:err_code:0xa0801002, clock:0x0b4887e2  2005/12/31 00:05:54
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888e6  2005/12/31 00:10:14
ofst[ 72]:err_code:0xa0801002, clock:0x0b488987  2005/12/31 00:12:55
ofst[ 76]:err_code:0xa0801002, clock:0x0b488d3d  2005/12/31 00:28:45
ofst[ 80]:err_code:0xa0801002, clock:0x0b4967a3  2005/12/31 16:00:35
ofst[ 84]:err_code:0xa0801002, clock:0x0b49692e  2005/12/31 16:07:10
ofst[ 88]:err_code:0xa0801002, clock:0x0b496951  2005/12/31 16:07:45
ofst[ 92]:err_code:0xa0801002, clock:0x0b496a1a  2005/12/31 16:11:06
[mullion]$
>$ 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 -> 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
[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)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b496be5  2005/12/31 16:18:45
[mullion]$
>$

Spoiler: O-Scope, 3x 2RTPE470M7 TaPol on CPU & NOS TOKIN on RSX (startup is noisier, 30s YLOD)

Not much improvement if any. Actually when zoomed out there was more variable noise. It would often be like those below, then have periods of chaotic 100mV signals on the RSX and the CPU would move over to the bad waveform, but very briefly.

So the RSX noise was more variable and would fluctuate from 60mV to 70, then 100 briefly, and back to 60. The YLOD was delayed now (10s - 5mins). Most of the time it would YLOD in about 30s. So that's worse than the previous results.

Anyway, I think that concludes the parasites. I'm really hoping a bad CPU tokin is spoiling the bunch otherwise I'll have to rethink using these 270uF caps. I will remove the parasites and begin the CPU tokins next.

Continued in part 14 here...

 

[Kevstah2004]

https://www.psdevwiki.com/ps3/images/6/67/DIA-002_-_1-876-912-22_(CECHJ,_CECHK)_-_FRONT.jpg
https://www.psdevwiki.com/ps3/images/2/21/DIA-002_-_1-876-912-22_(CECHJ,_CECHK)_-_BACK.jpg
DIA-002, has 0E108 left & 0E128 right top side & the reverse on the under side
0E128 left, 0E108 right so they marry up on both sides?

1200uF/470=2
3x470=1410
or
2x470=940+330=1270
to cover 1 1200uF?

&

1000uF/470=2
3x330=990
or
2x330+470=1130

or are both sides of the board counted as 4800uF & 4000uF or just 4400uF?

4800/470=10
10x470=4700
or
9x470=4230+2x330=4890

4000/470=8
9x470=4230
8x470+330=4090

4400/470=9
9x470+330=4560
8x470=3760+2x330=4420

 

[RIP-Felix]

PS3 #7 - Part 14.
(L6202 Replaced)
...continued from part 13 here.​

Well I know I said I was going to move onto the CPU tokins, but I got to thinking about the L in RLC. If you recall it was damaged in shipping. It's resistance was fine, but I don't have any other way to test it. There's no Henery setting on my multimeter. We were just hoping the damage was cosmetic. I decided this morning that I should try replacing it just in case. So PS3#1's carcass comes in hand again for a donor inductor. While I did have to use hot air to get them off and on again, I don't think I stressed the too board much.

I should mention that I removed the parasites for this test. So it's back to just having all the RSX tokins replaced with 18x 270uF TaPol.

The results are pretty clear. The noise was cut in half, the larger and smaller peaks are now just 1 uniform size, and the only time I get larger spikes is during the periodic square wave signals that occurs when the RSX is idling. I didn't experience any YLODs during O-Scope probing and only got an 80 1002 to occur in the menu of NBA Live 2010, but it made it a significant bit further than all the other attempts. This was a noticeable improvement, but it is still not stable by any means.

Spoiler: SYSCON, L6202 Replaced + 4 TaPol Arrays on RSX (Random YLOD)

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ 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 -> 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b488c54  2005/12/31 00:24:52
[mullion]$
>$ errlog
errlog
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xa0801002, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
ofst[ 64]:err_code:0xa0801002, clock:0x0b4887e2  2005/12/31 00:05:54
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888e6  2005/12/31 00:10:14
ofst[ 72]:err_code:0xa0801002, clock:0x0b488987  2005/12/31 00:12:55
ofst[ 76]:err_code:0xa0801002, clock:0x0b488d3d  2005/12/31 00:28:45
ofst[ 80]:err_code:0xa0801002, clock:0x0b4967a3  2005/12/31 16:00:35
ofst[ 84]:err_code:0xa0801002, clock:0x0b49692e  2005/12/31 16:07:10
ofst[ 88]:err_code:0xa0801002, clock:0x0b496951  2005/12/31 16:07:45
ofst[ 92]:err_code:0xa0801002, clock:0x0b496a1a  2005/12/31 16:11:06
ofst[ 96]:err_code:0xa0801002, clock:0x0b496be5  2005/12/31 16:18:45
ofst[100]:err_code:0xa0801002, clock:0x0b488c54  2005/12/31 00:24:52
[mullion]$
>$

Spoiler: O-Scope, L6202 Replaced + 4x TaPol Arrays on RSX

Maybe I should revisit the Parasites again, now that the inductor is fixed. Perhaps they would stand a better chance of working now. They are easy enough to install, so I think I'll give them one last shot...

EDIT: I added the 3x TaPol Parasite onto the RSX and it made the signal more variable again. It does that jumping from 30 to 70 to 100mV thing again. I think the long conductors are adding inductance that is messing with the tuning. Also it's significantly above the sweet spot of 4800uF. IDK, but the console seems quite unstable. It made it about as far into NBA Live as it did before before YLOD with the 80 1002 again.

Spoiler: SYSCON, RSX Inductor repared + TaPol arrays + Parasite

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\HTPC>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ 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 -> 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48a55b  2005/12/31 02:11:39
[mullion]$
>$ errlog
errlog
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xa0801002, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
ofst[ 64]:err_code:0xa0801002, clock:0x0b4887e2  2005/12/31 00:05:54
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888e6  2005/12/31 00:10:14
ofst[ 72]:err_code:0xa0801002, clock:0x0b488987  2005/12/31 00:12:55
ofst[ 76]:err_code:0xa0801002, clock:0x0b488d3d  2005/12/31 00:28:45
ofst[ 80]:err_code:0xa0801002, clock:0x0b4967a3  2005/12/31 16:00:35
ofst[ 84]:err_code:0xa0801002, clock:0x0b49692e  2005/12/31 16:07:10
ofst[ 88]:err_code:0xa0801002, clock:0x0b496951  2005/12/31 16:07:45
ofst[ 92]:err_code:0xa0801002, clock:0x0b496a1a  2005/12/31 16:11:06
ofst[ 96]:err_code:0xa0801002, clock:0x0b496be5  2005/12/31 16:18:45
ofst[100]:err_code:0xa0801002, clock:0x0b488c54  2005/12/31 00:24:52
ofst[104]:err_code:0xa0801002, clock:0x0b48a55b  2005/12/31 02:11:39
[mullion]$
>$

]

Spoiler: O-Scope, RSX L6202 Replaced + 4x arrays + Parasite

The target plateau during startup shows basicly the same signal as before, but once it gets to idling there is a regular signal that starts to generate more noise. I'm thinking it maybe the clock? IDK, but I've seen it before and it only shows up when the system is booted up, si I couldn't really test the signal noise for YLOD consoles during that time. I was only able to capture it for a working console. Here's what it looks like on this console.

...And here it is on PS3#3 a working stock console

Spoiler: PS3#3 Working_Idle_RSX&CPU2

And here is the more variable noise that kinda jumps around...

In the Target plateau it just looks like it did before adding the parasite. I didn't take a pic since it looked the same. So here is the one from before...

Continued in next post...

 

[RIP-Felix]

PS3 #7 - Part 15
(First CPU NEC/TOKIN removed, C6141)
...continued from previous post.​

This was the best result yet. The console boots fine and was able to play about 15 minutes of NBA LIve 2010, actual gameplay instead of dying in menu like previous attempts. After about 15 mins it gave the old 80 1002 again. Clearly the CPU noise is carrying through to the RSX and causing issues. I say this because the RSX noise halved from 60mVpp to 30mVpp! The only change was to remove a CPU tokin!!!

So here we have @squeept's theory about bad tokins spoiling the bunch. But to expand on that theory this result shows it doesn't even need to be on the RSX, it can be on the CPU too. There are no visual clue as to which one is bad either, they all appeared fine. No scorching in the corners on any of the tokins.

The scratch on the bottom left one is from my dental pick. That's the one I removed for this test, so the other 3 are undamaged and the results are valid. Removing the plastic doesn't affect their performance, it just make shorting easier.

Spoiler: SYSCON, 1 CPU TOKIN removed (C6141)

I used "bringup" to start the console. I like that I get more information in the "lasterrlog" after the console experiences a YLOD when I use the SYSCON to start the console, so that's why I'm doing it this way. This time I use a "powerstate" command to see what's on. I did it again after starting NBA Live 2010 just to see if that PCI power OFF was because I was in menu and not in game. It's the same regardless. I'm not sure what connects to the PCI or if it's just an unused feature. Anyway, I then started a game of basketball and let the computer play itself. I like this method for stress testing, because it allows me to do other things while the test is working. Each game lasts 30 minutes and they made it to half time when the YLOD occurred (80 1002), so that's about 15 minutes into the test. That's much further than all previous tests made it. They never even got into a game, they all died in the menu while I was selecting the teams and setting the computer to play itself. So this is the best result yet!

Microsoft Windows [Version 10.0.18363.1316]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\Users\HTPC>CD C:\Users\HTPC\Desktop\PS3\SYSCON

C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM4 CXRF
>$ AUTH
Auth successful
>$ errlog
errlog
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xa0801002, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
ofst[ 64]:err_code:0xa0801002, clock:0x0b4887e2  2005/12/31 00:05:54
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888e6  2005/12/31 00:10:14
ofst[ 72]:err_code:0xa0801002, clock:0x0b488987  2005/12/31 00:12:55
ofst[ 76]:err_code:0xa0801002, clock:0x0b488d3d  2005/12/31 00:28:45
ofst[ 80]:err_code:0xa0801002, clock:0x0b4967a3  2005/12/31 16:00:35
ofst[ 84]:err_code:0xa0801002, clock:0x0b49692e  2005/12/31 16:07:10
ofst[ 88]:err_code:0xa0801002, clock:0x0b496951  2005/12/31 16:07:45
ofst[ 92]:err_code:0xa0801002, clock:0x0b496a1a  2005/12/31 16:11:06
ofst[ 96]:err_code:0xa0801002, clock:0x0b496be5  2005/12/31 16:18:45
ofst[100]:err_code:0xa0801002, clock:0x0b488c54  2005/12/31 00:24:52
ofst[104]:err_code:0xa0801002, clock:0x0b48a55b  2005/12/31 02:11:39
ofst[108]:err_code:0xa0801002, clock:0x0b48b68c  2005/12/31 03:25:00
[mullion]$
>$ 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 -> 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
>$ powerstate
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 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
[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
powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE
[mullion]$
>$ powerstate
WmDiscOpr_ShutterOnEvent
WmDiscOpr_InsertDiscEvent
WmDiscOpr_PushDiscEvent
WmDiscOpr_PushDiscEvent
WmDiscOpr_ShutterOffEvent
WmDiscOpr_ShutterOnEvent
WmDiscOpr_ChuckOnEvent
[SERV NVS] READ CMD
powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE
[mullion]$
>$ lasterrlog
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b489f31  2005/12/31 01:45:21
[mullion]$
>$ errlog
errlog
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xa0801002, clock:0xffffffff
ofst[124]:err_code:0xa0801002, clock:0xffffffff
ofst[  0]:err_code:0xa0801002, clock:0xffffffff
ofst[  4]:err_code:0xa0801002, clock:0xffffffff
ofst[  8]:err_code:0xa0801002, clock:0xffffffff
ofst[ 12]:err_code:0xa0801002, clock:0xffffffff
ofst[ 16]:err_code:0xa0801004, clock:0x0b4887e6  2005/12/31 00:05:58
ofst[ 20]:err_code:0xa0801002, clock:0x0b488c11  2005/12/31 00:23:45
ofst[ 24]:err_code:0xa0801002, clock:0x0b48916d  2005/12/31 00:46:37
ofst[ 28]:err_code:0xa0801002, clock:0x0b4892a3  2005/12/31 00:51:47
ofst[ 32]:err_code:0xa0801002, clock:0x0b48bcd5  2005/12/31 03:51:49
ofst[ 36]:err_code:0xa0801002, clock:0x0b48befd  2005/12/31 04:01:01
ofst[ 40]:err_code:0xa0801002, clock:0x0b48e35d  2005/12/31 06:36:13
ofst[ 44]:err_code:0xa0801002, clock:0x0b48e46c  2005/12/31 06:40:44
ofst[ 48]:err_code:0xa0801002, clock:0x0b48e5a1  2005/12/31 06:45:53
ofst[ 52]:err_code:0xa0801002, clock:0x0b48e6cd  2005/12/31 06:50:53
ofst[ 56]:err_code:0xa0801002, clock:0x0b48e824  2005/12/31 06:56:36
ofst[ 60]:err_code:0xa0801002, clock:0x0b48ec90  2005/12/31 07:15:28
ofst[ 64]:err_code:0xa0801002, clock:0x0b4887e2  2005/12/31 00:05:54
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888e6  2005/12/31 00:10:14
ofst[ 72]:err_code:0xa0801002, clock:0x0b488987  2005/12/31 00:12:55
ofst[ 76]:err_code:0xa0801002, clock:0x0b488d3d  2005/12/31 00:28:45
ofst[ 80]:err_code:0xa0801002, clock:0x0b4967a3  2005/12/31 16:00:35
ofst[ 84]:err_code:0xa0801002, clock:0x0b49692e  2005/12/31 16:07:10
ofst[ 88]:err_code:0xa0801002, clock:0x0b496951  2005/12/31 16:07:45
ofst[ 92]:err_code:0xa0801002, clock:0x0b496a1a  2005/12/31 16:11:06
ofst[ 96]:err_code:0xa0801002, clock:0x0b496be5  2005/12/31 16:18:45
ofst[100]:err_code:0xa0801002, clock:0x0b488c54  2005/12/31 00:24:52
ofst[104]:err_code:0xa0801002, clock:0x0b48a55b  2005/12/31 02:11:39
ofst[108]:err_code:0xa0801002, clock:0x0b48b68c  2005/12/31 03:25:00
ofst[112]:err_code:0xa0801002, clock:0x0b489f31  2005/12/31 01:45:21
[mullion]$
>$

Spoiler: O-Scope, 1 CPU TOKIN removed (C6141)

Here's the startup sequence. Looks to have the least noise yet...

Here's the target plateau. You can see that the RSX noise has been halved from 60mVpp to 30mVpp. Also notice that the CPU noise here has increased from about 20mV to 30mV. That makes sense, we did remove a tokins after all. It seems counterintuitive that removing 1200uF of capacitance on the CPU would cause the RSX noise to decrease by half, but still cause the CPU noise to increase. However, we've been speculating that a bad tokin can spoil the bunch, and this is the first result to support that idea. The last thing I want to mention about the target plateau is that it's been consistently showing the good CPU waveform for the last few tests, regardless of the fact that the "bad waveform" can still be found and the console still experiences YLODs...

So I've started to look at the 1st plateau after the voltage spike. This has been the most consistent place to find the bad waveform, if it can be found. You can see that the CPU's bad waveform has actually decreased from 50mV to 40mVpp. The CPU parasite test did show about 40mVpp bad CPU waveform here too, so the CPU noise reduced as much by removing a tokin as it did by adding a 1647uF TaPol parasite. Only this time it didn't cause the RSX noise to have large/small peaks....

Spoiler: 4 TaPol Arrays added to RSX (All tokins replaced with 18x ETPSF270M6E)

Sorry, I didn't get a capture of the Bad waveform on the 1st plateau in this test, but the variance when zoomed out usually equals it. SO here's that instead. You can see that at the target plateau, it's significantly lower and the "good waveform."

Also note the small/large peaks. When I removed the CPU tokin only the small peak remains.

Spoiler: O-Scope, 3x 2R5TPE470M7 TaPol Parasite on CPU (Bad CPU waveform)

Here is the regular signal I've been talking about. It shows up at idle...

This time I got smart and decided to measure the interval between signals and it's 60Hz. That's a tell tale sign that it's the NTSC video signal.

My guess is that it's the frame being processed. That explains why the noise is less in between. The frame is being drawn on screen and the processors are not doing anything. Then when the the noise increases and becomes variable the RSX is working hard to deliver the next frame to the frame buffer. Then it waits again for the next job. IDK if that's exactly how it works, but the fact that these are occuring at a regulat 60Hz interval has to be related to the NTSC video standard. I wonder if someone with a PAL console were willing to measure this as well, if they would get 50Hz? That would confirm it.

I had a look back at PS3#3, a working stock console, and this signal was 60Hz as well. So this is clearly a video signal timed to the NTSC standard. It's not just a one console fluke.

Spoiler: PS3#3 60Hz Signal

Continued in part 16 here...

 

[squeept]

Where's the daily drip? I needs my fix.

 

[RIP-Felix]

Went deep looking into JTAG for your frankeinstein swap, had to drown the ensuing headache with beer. Also, I got tired of posting after each and every change, so I've just been focusing on completing the CPU changes one by one. Don't worry, I'm taking notes and all the pic. Just got the SYSCON off the 3rd TaPol install. Next up is the last tokin removal. I'm getting kinda worried as the console isn't stable yet. Keeps YLOD in game with the same 801002. We'll see after the last tokin comes out. Here's the table summary, it's more friendly to look at anyway.

 

[MYS]

Interesting to know how the SYSCON would show with all the Tokin changed to Tantalum cap (470uf). I had 3 BC PS3 with all Tokin changed to Tantalum cap (470uf x 32 pcs) and all are working quite well (at the moment), but not sure if such changes would slowly kill off the processor and gpu due to "noise". The other PS3 which is non-BC died to YLOD after 8 months of changing all the Tokin to Tantalum cap, which I do not know the reason as I don't have the equipment to check SYSCON. I tried replacing the Tantalum to Tokin I bought off Aliexpress and the system worked for a month plus and it died again (YLOD). Hope your result would share some light to the failure I encountered so i can bring that unit back into working condition (maybe).
Btw, what is the part number of the Tapol you are using? Could you provide the link to the site you bought them from?

 

[RIP-Felix]

Sounds like a BGA problem to me. $5 TTL USB to serial cable is all you need. Cheap and powerful, the SYSCON is...hrmmm! If you look back a few pages you'll find the model numbers and links to the caps I got. To be clear, I'm testing them out on a reballed console with confirmed bad tokins.

 

[MYS]

Ok, will try to look for the link. Thank you.

For SYSCON, I doubt I would know how to troubleshoot it. I am also suspecting the solder joint of either the processor or gpu. But I think it would be too much for me to do a re-ball.... I had trouble even trying to get the solder paste to "stick" when I replace the Tokin so I don't have any confidence I can get the processor to go back into place after removing it. lol....

Most interesting is the Oscilloscopes reading of the voltage, it might tell us if changing the Tokin would hurt the system in the long run.

 

[squeept]

Most interesting is the Oscilloscopes reading of the voltage, it might tell us if changing the Tokin would hurt the system in the long run.

I'm a man of science, so I have no problem admitting when I was wrong. I now believe the increase in noise/voltage that I saw when replacing them was due to my poor technique with the probes and reading the voltage at the wrong "plateau." Disregard anything I said about that until we have a few more data points.

The last board in my spreadsheet is also now experiencing A0801001 with the regular 3034 after I reballed it. It has damn near perfect signals on both lines. So, I think the 1001, 1002, and 1004 don't necessarily mean bad TOKIN, but if you have bad TOKIN you will definitely have one of those codes.

Thirdly, @RIP-Felix there is a very good chance that the board now has a crack on the CPU considering the damage it took. If it's still unstable after you finish all of the replacement, then send it back and I'll reball the CPU and send it back double boxed. Or if I can fix your board when I get to it, I'll trade you back.

 

[MYS]

@squeept Ya, let's wait for more result to confirm. I just want to know if changing all Tokin is good or bad for the system before I change them all back to the Tokin I got from Aliexpress (reflowing using cheap hot air gun is a headache for me as I have limited skill on this). Do you have a good reflow equipment to recommend (the setting as well)? Might try to do a re-ball on the PS3 since if it is beyond repair (slight chance?) after @RIP-Felix complete his analysis.

BTW, you guys are great.

 

[Sampsonay]

Tantalum may be better because it has lower ESR in the higher frequencies. Here, this graph compares the ESR of your AlPol caps to the tantalum that SONY initially used (2R5TPF470M6L 6mOhm 470uF TaPol) before switching to AlPol.

Spoiler

View attachment 30889
I'd go with the EEFLX0E331R4 if choosing between the ones you listed. The 330uF allows you to get closer to the ideal 4800uF target at 5280uF for 16x of them...and the ESR would be lower too (4.5 / 16 = 0.281mOhms). They should last longer and be able to handle higher ripple because of that, but any noise or ripple above 12MHz will not perform as well as tantalum. BTW, the NEC/TOKINs are quite good, they have low ESR into the HF also. Even better than TaPol, which is why they are still the best option. Basically, HF noise gets coupled into the circuit from the processor, which has to get past the MLCC Bypass caps first. Once the noise gets to the AlPol Bulk filter caps, it will have a see a higher ESR and heat the cap more than a TaPol would. A-E models still have an array of 36x 0.1uF MLCC bypass caps on the CPU. They were later removed with the switch to 65nm Cell_BE and decrease from 3 switch mode converters to 2. So my guess is that the 65nm Cell had much less noise, pulled significantly less current, and required fewer noisy switching VRM. That allowed them to remove some of the HF bypass caps. All of which reduced cost. The tokins job got easier as the current being drawn across them was smaller, and thus the ripple would be smaller.

I am a bit curious, do we know if the ripple current in the original PS3 ever actually hits those high frequencies? And if so, can that cause the ESR of those capacitors i used to sky rocket well beyond their rating on paper?

Today i found another really nice looking capacitor online, its model is "EEF-GY0E681R" and is 2.5v, 680uF, 3mOhms, and 10.2A ripple current. I am considering using 16 of these in future systems, rather than 30 of those EEF-LX0E331R4 caps.

Would be interested in any thoughts you have on this. I'm also curious how those caps stack up against Sony's.

 

[RIP-Felix]

3mOhms / 0.375mOhms = 8 caps. That's 5440uF or 13% over the ideal amount. It's not too far above, so I wouldn't think that's a problem. As for how they stack up to sony's caps, just paste the model number into panasonic's characteristics viewer. Those caps are better upto 13MHz, then the tantalum outshines the aluminum into the higher frequencies.

Again, the reason that matters is because of higher frequency harmonics from the switch mode ripple, coupled HF noise from other parts of the motherboard and your environment (cell phone towers, TV signals, even LED lights), and induced HF noise from the load (processors). These noise sources are HF and can interfere with the singals that the processors are sending, so they need to be filtered. That's what MLCC bypass caps are for. They are all over the CPU/RSX to keep them noise free. However the tokins were VERY good at removing them also. So if we don't use tokins, then we are allowing more HF noise past. Tantalum is better than Aluminum for HF. However, a low ESR in the HF range is important because the caps will last longer. Basically they heat up more if their resistance to HF noise is higher. Tantalum won't heat up as much as AlPol will. Using allumpinum, you might need more MLCC bypassing...

I'm still unconvinced that we don't need to add more HF bypass caps in addition to TaPol caps, to make up the difference between TaPol and the tokins they're replacing.

 

[RIP-Felix]

PS3 #7 - 16
(Final Results on the Tokin removals and TaPol array)
...continued from part 15 here.​

I'll skip to the results. From what I can tell, the O-scope is saying everything is fine. That the TaPol array is working well and the noise is well controlled. If I saw this result on a console, I would say it's tokins were fine. But that pesky 80 1002 error is still randomly killing the console for no apparent reason?! I still have some ideas, but let's backup and document the story so far.

I'm not going to cover everything or post every picture and SYSCON, just some example to make the points I think are worth mentioning.

Spoiler: Working Unmodified Console for Reference

Notice that the axis are zoomed in on 20mV/Div in this startup sequence. I started defaulting to 50mV/Div later. Anyway, this would look much thinner at 50mV/Div. Keep that in mind.

Here is the 60Hz signal. First notice how little noise there is on the signal. Also, I want you to pay attention to the length of time between signals. This working console has 6-7ms signal followed by 10ms plateau before the next signal. The pulses where the noise is larger I'm calling "during signal" noise and the plateau between signals I'm calling the "between signal" noise. The length of time between the signals is 16.67ms (1/60 of a second or 60Hz). Here's my crackpot assertion, I purpose this "signal" is the current frame being processed (NTSC). The time between signals is just unused idle time. The work is done during the signal. This will become important once you see the other pics. I've noticed the signal length increase with more noise on the RSX. I think that is because the noise is causing data mismatches that the CPU/RSX have to re-process in order to finish each frame. So the more noise the more mismatches, likewise the longer the "during signal" and shorter the idle time "between signal." So the between signals idle time is kinda like a buffer (or life meter). If the noise is too high, there are so many mismatches that it takes too long to process a frame and the next frame needs processed before the last frame was finished. When there is no more idle time between signals = YLOD!

Notice how low the noise is. RSX = 10mVpp, Cell = 40mVpp. No bad waveform.

Spoiler: PS3#7: Original Damaged State

You can see there is excessive ripple and noise. The startup sequence has a noticeably fat signal compared to the cpu. Bad wave form on both the CPU (yellow) and GPU (Blue). I couldn't get a pic of the 60Hz signal because it starts after the startup sequence and the console had a 4.5s YLOD. I don't recall if that was long enough for it to show up. Unfortunately in subsequent tests where I could have gotten a pic of it, I was too focused on the target plateau and ripple voltage. There were a number of tests where I could have gotten a pic of the 60Hz signal but didn't. I'm kicking myself now that I've found something interesting in the length of time between signals.

Bad wave forms...

Spoiler: PS3#7: Inductor & All RSX Tokins Replaced with 18x ETPSF270M6E 270uF 2.5v 6mOhm TaPol

Startup sequence looks much better, albeit a bit noisy...

60Hz signal has much more noise than a stock working console and the idle time between signals is about 3-4ms vs 10ms on the stock console. So the signals are taking 14-15ms when they should be taking about 6-7ms. If my crackpot idea is correct, then the noise is causing enough data mismatches to double the processing time of each frame...and that's at idle, not in game. Once you put the console under load and test it's processing ability, I'd expect that's not enough room to prevent a YLOD. And it wasn't. The YLOD occured in the menuu of a game and while rebuilding the HDD from a previous YLOD. So the system was quite unstable like this.

Spoiler: PS3#7: All CPU Tokins replaced with 18x ETPSF270M6E 270uF 2.5v 6mOhm TaPol

GPU Noise looks good on startup, best I'd seen yet...

Idle time between signals increased to 8ms, but the noise between signals still looks to be significantly higher than the stock working console. The console still YLODs in game, but seems to do better. It's still not stable.

The target plateau noise is much lower, but still not as good as the stock working console with it's NEC/TOKINs. I'm starting to think that these TaPol caps are just not up to the task. Or that there is something else that's causing a power failure on the RSX that has nothing to do with the bulk filter. Perhaps dodgy VRM or MOSFET. Maybe a Tantalum filtering caps on the memory or VDDIO voltages...IDK. Gremlins, basically!

The last board in my spreadsheet is also now experiencing A0801001 with the regular 3034 after I reballed it. It has damn near perfect signals on both lines. So, I think the 1001, 1002, and 1004 don't necessarily mean bad TOKIN, but if you have bad TOKIN you will definitely have one of those codes.

Thirdly, @RIP-Felix there is a very good chance that the board now has a crack on the CPU considering the damage it took. If it's still unstable after you finish all of the replacement, then send it back and I'll reball the CPU and send it back double boxed. Or if I can fix your board when I get to it, I'll trade you back.

Yes, I'm beginning to think there is something else going on here. Gremlin VRM or leppercons dancing on the die...IDK. What I do know is that the SYSCON says...

[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
Wait WmMcCom_DeadEvent timeout
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
lasterrlog
Last Error Code:0xa0801002, Time:0x0b48a55b  2005/12/31 02:11:39

I would be curious to find out what your 1001 error triggers? I assume that "RS" stands for Reality Synthesizer, but it could be the Reset Signal too. You need internal command access for this and the console needs to be turned on with "bringup" command so the syscon is logging in the backround. Then after the YLOD type "lasterrlog" and it'll give you the full readout like the above.

I still want to try removing all the 270uF TaPol B case caps and using those SoulKilla PCB's with 470uF TaPol caps. These...

Spoiler: SoulKilla 3xTantalum PCB

However, I noticed that the - rails don't line up perfectly...

...and the + rails don't have plating down the edge.

I still think I can make them work though. With the 1.9mm height caps I got they are 2.9mm thick, which is perfect to fit under the RF shield without touching. Also, the double thick copper planes are more than enough to handle the current.

I'm going to try attaching these with the larger tantalum caps, just to silence that stupid voice in me whining, "but you didn't use the caps the OP recommended."

Continued in part 17 here...

 

[Kleon1876]

This right? All tokens replaced by one in the cpu. Bridged the gpu on the bottom. Still ylod