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

RIP-Felix said:
Yes. The Remote sense line on the CPU thermal monitor cannot read the thermal diode inside the die. Replace the thermal moitor and check the resistors/cap.
View attachment 41905
If that doesn't do it, then the CPU needs reballed. And if that doesnt work, then the thermal diode inside it is dead and the CELL is gone.
Click to expand...
I've reballed the CPU, and the error codes 3010 and 3032 are gone. But still, it does not boot.


Code: 
===================================
ERR 00: 00000000 A0111B01 FFFFFFFF
ERR 01: 00000000 A0111B01 FFFFFFFF
ERR 02: 00000000 A0111B01 FFFFFFFF
ERR 03: 00000000 A0111B01 FFFFFFFF
ERR 04: 00000000 A0111B01 FFFFFFFF
ERR 05: 00000000 A0111B01 FFFFFFFF
ERR 06: 00000000 A0111B01 FFFFFFFF
ERR 07: 00000000 A0111B01 FFFFFFFF
ERR 08: 00000000 A0111B01 FFFFFFFF
ERR 09: 00000000 A0111B01 FFFFFFFF
ERR 10: 00000000 A0111B01 FFFFFFFF
ERR 11: 00000000 A0111B01 FFFFFFFF
ERR 12: 00000000 A0111B01 FFFFFFFF
ERR 13: 00000000 A0111B01 FFFFFFFF
ERR 14: 00000000 A0111B01 FFFFFFFF
ERR 15: 00000000 A0111B01 FFFFFFFF
ERR 16: 00000000 A0111B01 FFFFFFFF
ERR 17: 00000000 A0111B01 FFFFFFFF
ERR 18: 00000000 A0111B01 FFFFFFFF
ERR 19: 00000000 A0111B01 FFFFFFFF
===================================
 
Only advice on this is that you can try solder tristate to gnd. 40 seconds it could be on bad patch.
If that stays on more than one minute I'll check voltage to xdr memory or something else with those controllers for memory on cell side too.
It could be cell side deformation on motherboard corner left side down to xdr
Usually I reball both cell /rsx with dia001 /002 and ver001 board.
Always pain boards.
Worth try dump nor and see if any errors apart from ros0/1.
 
Sorry if this was asked before and is lost in the middle of the thread. Can someone tell me what case codes (either in or mm) or sizes of caps I should look for for tantalum caps replacements?
 
TheBusinessRabbit said:
Sorry if this was asked before and is lost in the middle of the thread. Can someone tell me what case codes (either in or mm) or sizes of caps I should look for for tantalum caps replacements?
Click to expand...

Found it.

I have a few questions though. I have a syscon A0801002 on my CECHC that according to db260179's ps3syscon project on Github is

"A0801002 = RSX Power on VRAM failure (Potential NEC tokins issue and VCC)"

I take I should just try starting to replace the NEC/Tokins caps near the RSX, and leave the CPU ones aline for now, no?

Also, I'm a bit confused. The guide says the original are 1200uF on FAT. Doesn't that mean it that here:

cok-001-3-jpg.19116


We should be seeing 6 of thodse buggers intead of 4? Or am I thinking that wrong?

Finally:

"*32 Tantalum Capacitors "330/470uF - 2.5V/6.3V - Rated"

Does any combination here works? Someone in this thread suggested Panassics 2R5TPE470M9. Those are 470 uF and 2.5V. Shouldn't they be 6.3V? Thank you for any help.
 
TheBusinessRabbit said:
Found it.

I have a few questions though. I have a syscon A0801002 on my CECHC that according to db260179's ps3syscon project on Github is

"A0801002 = RSX Power on VRAM failure (Potential NEC tokins issue and VCC)"

I take I should just try starting to replace the NEC/Tokins caps near the RSX, and leave the CPU ones aline for now, no?

Also, I'm a bit confused. The guide says the original are 1200uF on FAT. Doesn't that mean it that here:

cok-001-3-jpg.19116


We should be seeing 6 of thodse buggers intead of 4? Or am I thinking that wrong?

Finally:

"*32 Tantalum Capacitors "330/470uF - 2.5V/6.3V - Rated"

Does any combination here works? Someone in this thread suggested Panassics 2R5TPE470M9. Those are 470 uF and 2.5V. Shouldn't they be 6.3V? Thank you for any help.
Click to expand...

Read this.
 
M4SH said:
I've reballed the CPU, and the error codes 3010 and 3032 are gone. But still, it does not boot.


Code: 
===================================
ERR 00: 00000000 A0111B01 FFFFFFFF
ERR 01: 00000000 A0111B01 FFFFFFFF
ERR 02: 00000000 A0111B01 FFFFFFFF
ERR 03: 00000000 A0111B01 FFFFFFFF
ERR 04: 00000000 A0111B01 FFFFFFFF
ERR 05: 00000000 A0111B01 FFFFFFFF
ERR 06: 00000000 A0111B01 FFFFFFFF
ERR 07: 00000000 A0111B01 FFFFFFFF
ERR 08: 00000000 A0111B01 FFFFFFFF
ERR 09: 00000000 A0111B01 FFFFFFFF
ERR 10: 00000000 A0111B01 FFFFFFFF
ERR 11: 00000000 A0111B01 FFFFFFFF
ERR 12: 00000000 A0111B01 FFFFFFFF
ERR 13: 00000000 A0111B01 FFFFFFFF
ERR 14: 00000000 A0111B01 FFFFFFFF
ERR 15: 00000000 A0111B01 FFFFFFFF
ERR 16: 00000000 A0111B01 FFFFFFFF
ERR 17: 00000000 A0111B01 FFFFFFFF
ERR 18: 00000000 A0111B01 FFFFFFFF
ERR 19: 00000000 A0111B01 FFFFFFFF
===================================
Click to expand...
If you have ruled out the thermal monitor, the external sense line resistors and cap, and the CPU's BGA...then I'm afraid the internal diode inside the cell is dead. Cell is a goner and you are SOL. Now I would be extremely interested to see if anyone finds another solution, but this is the most solid conclusion from available evidence about this error.
 
Ps3 Fat DIA-001 -xxxx0524145E

Code: 
C:\Users\Administrator>C:\Users\Administrator\Desktop\ps3syscon-master\Linux\ps3
_syscon_uart_script.py COM5 CXRF
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$  becount
becount
Bringup : 843 times
Shutdown: 714 times
Power-on: 37day 21hour 52min 15sec
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[  4]:err_code:0xffffffff, clock:0x0b488707  2005/12/31 00:02:15
ofst[  8]:err_code:0xffffffff, clock:0x0b4887b9  2005/12/31 00:05:13
ofst[ 12]:err_code:0xa0801004, clock:0x0b4887fb  2005/12/31 00:06:19
ofst[ 16]:err_code:0xa0801004, clock:0xffffffff
ofst[ 20]:err_code:0xa0801004, clock:0xffffffff
ofst[ 24]:err_code:0xa0801004, clock:0xffffffff
ofst[ 28]:err_code:0xa0801004, clock:0xffffffff
ofst[ 32]:err_code:0xa0801004, clock:0xffffffff
ofst[ 36]:err_code:0xa0801004, 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:0xa0801004, clock:0xffffffff
ofst[ 84]:err_code:0xa0801004, clock:0xffffffff
ofst[ 88]:err_code:0xa0801002, clock:0xffffffff
ofst[ 92]:err_code:0xa0003001, clock:0xffffffff
ofst[ 96]:err_code:0xa0003001, clock:0xffffffff
ofst[100]:err_code:0xa0003001, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0801004, clock:0xffffffff
ofst[112]:err_code:0xa0801004, clock:0xffffffff
ofst[116]:err_code:0xa0801004, clock:0xffffffff
ofst[120]:err_code:0xa0801004, clock:0xffffffff
ofst[124]:err_code:0xa0801004, clock:0xffffffff
ofst[  0]:err_code:0xa0801004, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$ Bringup
Bringup
*** Unknown Command ***
[mullion]$
Press Ctrl+C to exit
>$ 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:0x20e7
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
Press Ctrl+C to exit
>$ bringup
[SERV NVS] READ CMD

Boot Loader SE Version 2.0.0 (Build ID: 2655,27256, Build Data: 2007-10-26_12:10
:58)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[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 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
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SERV THERM] Thermal Error Detected!
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SERV THERM] *** NO COMMTAG SPECIFIED YET. ***
[ERROR]: 0xa0801200
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
(*
 
Last edited:
bennieboy777 said:
CECH-2001A

System was given to me cheap, but it is in remarkably good shape. Its blue ray drive didn't work when I bought it, but the rest of the system did. I was able to install cfw, so the temps were well controlled. It was about a month after purchase when it ylod for the first time.

The ylod happens a few seconds after pressing the button. If I keep recycling the power, it eventually heats up a little bit and starts. It will stay on the menu for a long time at this point. Below is a picture of my sys con errors:
ubDXvEY


Pic wouldn't attach for some reason: but it's a consecutive list of 11 A0801002 errors, one A08014FF, and 11 more A0801002.

I've decided to order some replacements for the nec/tokins, because it only throws the 1002 error. I'm just curious how the system is able to boot after recycling the ylod?

Any help would be greatly appreciated! Otherwise, I will report back with success or failure after replacing one or more nec/tokins
Click to expand...

I replaced just one of the NEC/TOKINs on the side of the motherboard opposite where the chips face. I used (4) 370uf caps. The system booted up first try! I would post pics of the install but it's not my cleanest soldering job.
The system needs a new fan, so I'm going to order that. The only other problem with this slim is the blue ray drive.
I will post an update if the NEC/TOKIN replacement doesn't take in the long-term. But if I started getting the 1002 again in the future, I should just replace more of them?
 
bennieboy777 said:
I replaced just one of the NEC/TOKINs on the side of the motherboard opposite where the chips face. I used (4) 370uf caps. The system booted up first try! I would post pics of the install but it's not my cleanest soldering job.
The system needs a new fan, so I'm going to order that. The only other problem with this slim is the blue ray drive.
I will post an update if the NEC/TOKIN replacement doesn't take in the long-term. But if I started getting the 1002 again in the future, I should just replace more of them?
Click to expand...

EDIT: I meant to say 330uf caps.

Would it be a bad idea to replace all of the NEC/TOKIN caps this way ahead of time?
 
1200 is cell overheating
2130 is cell thermal censor error
2131-2031 is rsx thermal censor error

Okay. Recently, web pages are always translated into Chinese for no apparent reason.

Do you know where the temperature sensor is on the motherboard?
 
PS3 FAT DIA-001 -xxxx00615535

Code: 
C:\Users\Administrator>C:\Users\Administrator\Desktop\ps3syscon-master\Linux\ps
_syscon_uart_script.py COM5 CXRF
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ becount
becount
Bringup : 342 times
Shutdown: 233 times
Power-on: 7day 13hour 53min 59sec
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0404401, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0404401, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0404401, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404401, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404401, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404401, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0404401, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0404401, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0404401, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[  0]:err_code:0xa0404401, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0404401, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0404401, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0404401, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404401, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0404401, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$ 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:0x20e7
Press Ctrl+C to exit
>$ bringup
[POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404401
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
 
Last edited:
I bought a PS3 with the description saying it had the YLOD. I got the items needed to use the SYSCON and after a few hours i got it work and these are the error codes that it gave me.

>$ ERRLOG GET 00
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0801002 0DC8F1B6
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0801002 0DC8F0F1
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0801002 0DC8F0E3
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0801002 0B488A3D
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0801002 0B488A2D
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801002 0B488680
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801002 282363EA
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801002 20C1DBB7
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801002 20C1DB76
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0801002 1DCEE928
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801002 1DCEE8AA
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801002 1D214DFB
Press Ctrl+C to exit

I looked up on google and also the psdevwiki and the A0801002 usually means that the NEC/TOKINs are bad. I wanted to come here and ask for confirmation and to see what my next steps should be.
 
T3MP3STA said:
I bought a PS3 with the description saying it had the YLOD. I got the items needed to use the SYSCON and after a few hours i got it work and these are the error codes that it gave me.

>$ ERRLOG GET 00
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0801002 0DC8F1B6
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0801002 0DC8F0F1
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0801002 0DC8F0E3
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0801002 0B488A3D
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0801002 0B488A2D
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801002 0B488680
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0801002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801002 282363EA
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801002 20C1DBB7
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801002 20C1DB76
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0801002 1DCEE928
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801002 1DCEE8AA
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801002 1D214DFB
Press Ctrl+C to exit

I looked up on google and also the psdevwiki and the A0801002 usually means that the NEC/TOKINs are bad. I wanted to come here and ask for confirmation and to see what my next steps should be.
Click to expand...
I'm not going to pretend to be an expert, but I explained my situation on the previous page. I had the A0801002 syscon error and I replaced one of my NEC/TOKINs and my system has been working fine since.

On an unrelated note, I have a fat PS3 that doesn't get any PWM signal through the grey wire for the fan. I've "fixed" this by installing a hardware fan override controller. I control the fan speeds manually with a knob on the back of the console.
I would really like to figure out WHY I get no signal from the grey wire. I find this issue interesting, and I've asked countless people about it on different forums to no avail. If anyone has any ideas, I'd love to track down the source of this issue.
 
bennieboy777 said:
I'm not going to pretend to be an expert, but I explained my situation on the previous page. I had the A0801002 syscon error and I replaced one of my NEC/TOKINs and my system has been working fine since.

On an unrelated note, I have a fat PS3 that doesn't get any PWM signal through the grey wire for the fan. I've "fixed" this by installing a hardware fan override controller. I control the fan speeds manually with a knob on the back of the console.
I would really like to figure out WHY I get no signal from the grey wire. I find this issue interesting, and I've asked countless people about it on different forums to no avail. If anyone has any ideas, I'd love to track down the source of this issue.
Click to expand...

What did you replace the NEC/TOKIN with? and what tools did you use?
 
I want to ask a question, when l got my first sem-001 ps3 it has a broken cell and today I bought a dia-002 motherboard ps3 with A0061002 and A0093003 errors and because they are mostly nec issues I want to replace them.
Can I use the Nec tokıns from my sem-001 motherboard and how can I harvest them without breaking them up on my sem-001 ?
 
You must log in or register to reply here.

Similar threads

Back
Top