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

[nickxab]

Here you can read what's these errors.

ofst[ 0]:err_code:0xa0801701, clock:0x0f67209d 2008/03/09 22:26:37

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#1701_(CELL_BE_ATTENTION)

ofst[ 4]:err_code:0xa0801601, clock:0x0f67209d 2008/03/09 22:26:37

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#1601_(CELL_Livelock_Detection)

ofst[ 8]:err_code:0xa0802203, clock:0x1548e3d3 2011/04/26 02:00:51

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#2203_(South_Bridge)

ofst[ 12]:err_code:0xa0801004, clock:0x1779e4c1 2012/06/24 14:46:25

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#1004_(Power_AC/DC)



I would start from the power supply, it's the easiest of all to start checking.

 

[RGBeter]

Here you can read what's these errors.


https://www.psdevwiki.com/ps3/Syscon_Error_Codes#1701_(CELL_BE_ATTENTION)

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#1601_(CELL_Livelock_Detection)

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#2203_(South_Bridge)

https://www.psdevwiki.com/ps3/Syscon_Error_Codes#1004_(Power_AC/DC)



I would start from the power supply, it's the easiest of all to start checking.

Already checked the codes, but I'll give what I thought of each

1004 I'm assuming was an improper shutdown, already swapped PSU, HDD, wireless card, memory card readers, and even disc drive (I know it won't read anything because daughterboard mismatch but it would still let the system boot or update)

2203 is, pretty useless, just the southbridge didn't have power at some point.

The 1701/1601 is interesting, and points to bad GPU, which is what I'm being led to believe. Southbridge logs show the system boots, there's just no display from AV or HDMI

The only thing this system does not do is sync a controller, or display video from either port.

This is a COK-002 board, so there's a chance a bad GS or video encoders could cause it, maybe the passives that connect them, but I haven't heard any reports of that being an issue, so I'm leaning towards making it a frankie.

 

[nickxab]

Already checked the codes, but I'll give what I thought of each

1004 I'm assuming was an improper shutdown, already swapped PSU, HDD, wireless card, memory card readers, and even disc drive (I know it won't read anything because daughterboard mismatch but it would still let the system boot or update)

2203 is, pretty useless, just the southbridge didn't have power at some point.

The 1701/1601 is interesting, and points to bad GPU, which is what I'm being led to believe. Southbridge logs show the system boots, there's just no display from AV or HDMI

The only thing this system does not do is sync a controller, or display video from either port.

This is a COK-002 board, so there's a chance a bad GS or video encoders could cause it, maybe the passives that connect them, but I haven't heard any reports of that being an issue, so I'm leaning towards making it a frankie.

Mine some days ago refused to work. Some times booted without video signal on both AV and HDMI ports, some times it booted with AV signal only and some other times gave me YLOD. I replaced the capacitors and everything worked fine after that.

Try to test it with some electrolytic capacitors first without to remove the nec tokins, if it works then proceed with the replacement.

 

[LSL]

Hey everyone, ran into a GLOD system earlier today, Syscon codes are pretty much useless but they're here anyway, I also checked diagnostic output from the SB, and from what I see the system just, boots, no complaints, but I have no video output from either AV or HDMI. I inserted both logs, if anybody with advanced knowledge on the PS3 can help me out that would be great. If it is just a bad RSX, I recently got the equipment together, and learned how to swap GPUs on xbox 360, getting a JTAGable falcon running again, so an RSX swap is no issue to me, I just need to know it needs to be done.

Boot Loader SE Version 4.4.0 (Build ID: 5012,49722, Build Date: 2013-03-14_23:53:31)
SDK Version: 440.000
Copyright(C) 2013 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.2, SB:PX1.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.4.0 000 (release build: r49722 2013_03_14_223000)
Copyright 2013 Sony Computer Entertainment Inc.
revision: 49423
date:     Thu Mar 14 23:56:50 JST 2013
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3524KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.4.0
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 49722
lv2(2): build date: 2013/03/15 00:04:17
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0202
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b02 500/650 vpe:ff shd:5f  [4K0349001:1:3:10:7:7:4:f:1][39:2:1:1:1:3:1][0:0:0]

lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2):
lv2(2): ###
lv2(2): ### Software update mode
lv2(2): ###
lv2(2):
lv2(2): mounting the builtin HDD1 : OK
lv2(2): creating the initial system process : OK

ofst[  0]:err_code:0xa0801701, clock:0x0f67209d  2008/03/09 22:26:37
ofst[  4]:err_code:0xa0801601, clock:0x0f67209d  2008/03/09 22:26:37
ofst[  8]:err_code:0xa0802203, clock:0x1548e3d3  2011/04/26 02:00:51
ofst[ 12]:err_code:0xa0801004, clock:0x1779e4c1  2012/06/24 14:46:25

Bringup : 2773 times
Shutdown: 2329 times
Power-on: 216day 21hour 13min 35sec

Can the Sixaxis/Dualshock 3 power up the PS3 and stay connected?
Is the red light on the digital optical output off?
If you are experiencing the above symptoms, you may not have a GLOD, but rather a power failure in the audio/video sector that is responsible for the AV, HDMI, and optical output signals. I have had problems with these symptoms.
When I had a GLOD, the Sixaxis/Dualshock 3 would not connect to the PS3

 

[RGBeter]

Can the Sixaxis/Dualshock 3 power up the PS3 and stay connected?
Is the red light on the digital optical output off?
If you are experiencing the above symptoms, you may not have a GLOD, but rather a power failure in the audio/video sector that is responsible for the AV, HDMI, and optical output signals. I have had problems with these symptoms.
When I had a GLOD, the Sixaxis/Dualshock 3 would not connect to the PS3

The system charges a DS3 just fine, but I can't sync any to it. Also a bit late to ask me to test since I already pulled the RSX since that's what some experienced members in the booter discord server thought the issue was, this PS3s gonna be a Frankie whether it likes it or not now! (So long as the donor 65nm I pull tomorrow lives)

 

[PWG1991]

Hello everyone
My PS3 Fat (ver-001) has the following errors:


>$ errlog 00000000
CODE CLOCK
A0802124 0E8209A2
A0801002 0E8209A1
A0802130 0B49D8D4
A0802031 0B49D8D3
A0802030 0B49D884
A0802031 0B49D884
A0802030 0B49D880
A0802131 0B49D87C
A0802130 0B49D875
A0802131 0B49D871
A0802130 0B49D813
A0802130 0B49D874
A0232131 FFFFFFFF
A0232131 FFFFFFFF
A0232131 FFFFFFFF
A0232131 FFFFFFFF
A0232031 FFFFFFFF
A0802131 0B49D87C
A0802130 0B49D86C
A0802030 0B49D864
A0802030 0B49D863
A0802130 0B49D860
A0802130 0B49D85A
A0802131 0B49D854
A0802131 0B49D850
A0802131 0B49D84B
A0802131 0B49D849
A0802130 0B49D849
A0802130 0B49D848
A0802030 0B49D843
A0802131 0B49D83F

Can errors 2030, 2031, 2130 and 2131 be caused by NEC TOKINS?
What should I do?

Thanks in advance.

 

[LSL]

Hello everyone
My PS3 Fat (ver-001) has the following errors:


>$ errlog 00000000
CODE CLOCK
A0802124 0E8209A2
A0801002 0E8209A1
A0802130 0B49D8D4
A0802031 0B49D8D3
A0802030 0B49D884
A0802031 0B49D884
A0802030 0B49D880
A0802131 0B49D87C
A0802130 0B49D875
A0802131 0B49D871
A0802130 0B49D813
A0802130 0B49D874
A0232131 FFFFFFFF
A0232131 FFFFFFFF
A0232131 FFFFFFFF
A0232131 FFFFFFFF
A0232031 FFFFFFFF
A0802131 0B49D87C
A0802130 0B49D86C
A0802030 0B49D864
A0802030 0B49D863
A0802130 0B49D860
A0802130 0B49D85A
A0802131 0B49D854
A0802131 0B49D850
A0802131 0B49D84B
A0802131 0B49D849
A0802130 0B49D849
A0802130 0B49D848
A0802030 0B49D843
A0802131 0B49D83F

Can errors 2030, 2031, 2130 and 2131 be caused by NEC TOKINS?
What should I do?

Thanks in advance.

https://www.psdevwiki.com/ps3/Syscon_Error_Codes

 

[LSL]

Hey everyone, ran into a GLOD system earlier today, Syscon codes are pretty much useless but they're here anyway, I also checked diagnostic output from the SB, and from what I see the system just, boots, no complaints, but I have no video output from either AV or HDMI. I inserted both logs, if anybody with advanced knowledge on the PS3 can help me out that would be great. If it is just a bad RSX, I recently got the equipment together, and learned how to swap GPUs on xbox 360, getting a JTAGable falcon running again, so an RSX swap is no issue to me, I just need to know it needs to be done.

Boot Loader SE Version 4.4.0 (Build ID: 5012,49722, Build Date: 2013-03-14_23:53:31)
SDK Version: 440.000
Copyright(C) 2013 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.2, SB:PX1.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.4.0 000 (release build: r49722 2013_03_14_223000)
Copyright 2013 Sony Computer Entertainment Inc.
revision: 49423
date:     Thu Mar 14 23:56:50 JST 2013
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3524KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.4.0
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 49722
lv2(2): build date: 2013/03/15 00:04:17
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0202
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b02 500/650 vpe:ff shd:5f  [4K0349001:1:3:10:7:7:4:f:1][39:2:1:1:1:3:1][0:0:0]

lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2):
lv2(2): ###
lv2(2): ### Software update mode
lv2(2): ###
lv2(2):
lv2(2): mounting the builtin HDD1 : OK
lv2(2): creating the initial system process : OK

ofst[  0]:err_code:0xa0801701, clock:0x0f67209d  2008/03/09 22:26:37
ofst[  4]:err_code:0xa0801601, clock:0x0f67209d  2008/03/09 22:26:37
ofst[  8]:err_code:0xa0802203, clock:0x1548e3d3  2011/04/26 02:00:51
ofst[ 12]:err_code:0xa0801004, clock:0x1779e4c1  2012/06/24 14:46:25

Bringup : 2773 times
Shutdown: 2329 times
Power-on: 216day 21hour 13min 35sec

I'm reviewing my PS3 collection, most of which have some kind of problem, and when reviewing one of the CECHA00s the first error since 2020 was 0xa0093004. When I returned the analysis on January 18, the PS3 presented errors 0xa0003001, 0xa0093004, 0xa0801002, 0xa0901001, 0xa0603040. I solved them all!

Now I'm practically in the same situation as you, the PS3 turns on and I have no image on the HDMI port or the AV port, the Sixaxis doesn't even flash the charging LED even though there's 5v on the USB ports. The HDD LED flashes once. There are no errors in Syscon.

Below is the SB log, I saw that it's a little different from yours, probably because mine has a higher firmware. In your log there is the following section that is not in my log:

lv2(2):
lv2(2): ###
lv2(2): ### Software update mode
lv2(2): ###
lv2(2):
lv2(2): mounting the builtin HDD1 : OK

Boot Loader SE Version 4.7.6 (Build ID: 5292,50550, Build Date: 2015-08-11_11:15:27)
SDK Version: 476.000
Copyright(C) 2015 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.1, SB:DX3.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.7.6 000 (release build: r50550 2015_08_10_200000)
Copyright 2015 Sony Computer Entertainment Inc.
revision: 50550
date:     Tue Aug 11 11:17:23 JST 2015
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3492KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.7.6
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50550
lv2(2): build date: 2015/08/11 11:23:37
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b02 500/650 vpe:ff shd:7b  [G2A878400:1:2:b:f:7:3:9:1][16:3:0:0:1:2:1][0:0:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2): creating the initial system process : OK
lv2(2): entering stand-alone mode.
lv2(2): system software: PS3 console mode (game memsize=200MB)
lv2(2): creating the system software process : OK
lv2(2): sys_init: system software process set-up done.
lv2(2): initial system process done.
lv2(2): [system utility]: BD Drive connect error.

The bad thing is that this COK-001 has a lot of oxidized solder joints, there were 2 resistors that deal with the thermal issue that had a problem, but visually they seemed normal.

 

[RGBeter]

I'm reviewing my PS3 collection, most of which have some kind of problem, and when reviewing one of the CECHA00s the first error since 2020 was 0xa0093004. When I returned the analysis on January 18, the PS3 presented errors 0xa0003001, 0xa0093004, 0xa0801002, 0xa0901001, 0xa0603040. I solved them all!

Now I'm practically in the same situation as you, the PS3 turns on and I have no image on the HDMI port or the AV port, the Sixaxis doesn't even flash the charging LED even though there's 5v on the USB ports. The HDD LED flashes once. There are no errors in Syscon.

Below is the SB log, I saw that it's a little different from yours, probably because mine has a higher firmware. In your log there is the following section that is not in my log:

Boot Loader SE Version 4.7.6 (Build ID: 5292,50550, Build Date: 2015-08-11_11:15:27)
SDK Version: 476.000
Copyright(C) 2015 Sony Computer Entertainment Inc.All Rights Reserved.
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.1, SB:DX3.1
Device: PATAC0:Cable Not Connect
Cell OS SDK4.7.6 000 (release build: r50550 2015_08_10_200000)
Copyright 2015 Sony Computer Entertainment Inc.
revision: 50550
date:     Tue Aug 11 11:17:23 JST 2015
skip 2nd initialization step
lv2(0): total memory size: 249MB+640KB
lv2(0): kern memory size:   12MB+640KB (heap:3492KB  page pool:4736KB)
lv2(0): user memory size:  237MB
lv2(2):
lv2(2): Cell OS Lv-2 32 bit version 4.7.6
lv2(2): Copyright 2011 Sony Computer Entertainment Inc.
lv2(2): All Rights Reserved.
lv2(2):
lv2(2): revision: 50550
lv2(2): build date: 2015/08/11 11:23:37
lv2(2): processor: Broadband Engine  Ver 0x0000  Rev 0x0201
lv2(2): PPU:0, Thread:0 is enabled.
lv2(2): PPU:0, Thread:1 is enabled.
lv2(2): rsx:      b02 500/650 vpe:ff shd:7b  [G2A878400:1:2:b:f:7:3:9:1][16:3:0:0:1:2:1][0:0:0]
lv2(2): Available physical SPUs: 6/7
lv2(2): mounting the flash file system : OK
lv2(2): creating the initial system process : OK
lv2(2): entering stand-alone mode.
lv2(2): system software: PS3 console mode (game memsize=200MB)
lv2(2): creating the system software process : OK
lv2(2): sys_init: system software process set-up done.
lv2(2): initial system process done.
lv2(2): [system utility]: BD Drive connect error.

The bad thing is that this COK-001 has a lot of oxidized solder joints, there were 2 resistors that deal with the thermal issue that had a problem, but visually they seemed normal.

Huh, it seems like you're getting further than me with the bootloaders, I'm still stuck at sourcing an RSX to replace mine with, if that doesn't help me, then idk what you can do. Someone suggested the encoders aren't getting power for me earlier in the thread, you should check that out. If nothing works, then just try swapping the RSX.

 

[LSL]

Someone suggested the encoders aren't getting power for me earlier in the thread, you should check that out.

It could be.

I was checking db260179's gitHub and found a file (PS3 - SYSCON Switches and Power On Sequencing.pdf) that shows all the voltage signals of the CECHA.

When checking the voltages, I found the +1.2V_YC_RC_VDDIO (IC6303) shorted to GND.

The problem is that this voltage is interconnected with CELL, RSX, SB, XDR, IC5004 (IC CLOCK GEN RAMBUS XDR) and with several capacitors and resistors, finding out what the problem is will take a long time. Since I am progressing well with this COK-001, I will see if I can find where the problem is with the 4-pin Kelvin method.

Spoiler: Voltage Tree

PSU +5V_EVER

--> /SYSCON_RST (IC6004)
--> +3.3V_THERMAL (IC6009)

--> IC1101
--> IC2101
--> IC3101​

--> +3.3V_EVER (IC6005)

-->Q6311 --> What's happening here?
--> Base Q3501 to Drain +3.3V_MISC --> +3.3V_ESW​

--> +1.8V_EVER (IC6006)
--> +1.8V_VDD_MEM (IC6302/Q6301) (JL9647)​

PSU +12V_MAIN

--> /POW_FAIL (IC6023) (Error A0003001)
--> +12V_BD (Q6010) (JL6064)
--> +5V_ANA (IC2403)
--> +5V_MISC (IC6003/Q6002)

--> +5V_HDD (Q6006/Q6007) (JL6067)
--> +5V_USB (Q6006/Q6008) (JL6057)
--> +5V_BD (Q6010) (JL9658)
--> +3.3V_MK_VDD (IC6020) (JL6053)
--> +3.3V_Bridge (IC6022) (JL6070)
--> +3.3V_DRCG_VDD_DIG_+3.3V1 (IC6605) (JL6360)
--> +3.1V_EEGS_AVDA_DIG_+3.1V1 (IC6600) (JL6359)
--> +1.2V_RSX_VDDR (IC6200) (JL9651)
--> +1.5V_RSX_VDDIO (IC6017) (JL9656)
--> +1.5V_YC_RC_VDDA (IC6304) (JL9655)
--> +1.2V_EEGS_VDD_DIG_+1.2V1 (IC6302) (JL6361)
--> +1.2V_YC_RC_VDDIO (IC6303) (JL9652)
--> +1.2V_SB_VDDC (IC6305) (JL9648)
--> +1.2V_ESW (IC3501) (JL9649)
--> +1.2V_RSX_VDDC, RSX VRM (2 Phase)

--> IC6202 (JL6205/6)
--> IC6203 (JL6207/8)​

--> +1.0V_BE_VDDC, CELL BE VRM (3 phase)

--> IC6104 (JL6109/10)
-->IC6105 (JL6111/12)
-->IC6106 (JL6113/14)​

-->+3.3V_MISC (IC6003/Q6601)

--> +3.3V_SB_VDDIO (Q6004) (JL6058)
--> +3.3V_ESW (Q5303) (JL3551)
--> +2.5V_EEGS_PLLVDD1_DIG_+2.5V1 (IC6601) (JL6357)
--> +2.5V_RDRAM_VDD_DIG_+2.5V3 (IC6607) (JL6358)
--> +2.5V_SB_PLL_VDDC (IC6011) (JL6060)
--> +2.5V_LREG_XCG_500_MEM (IC6013) (JL6054)
--> +1.8V_RSX_PLL_VDD (IC6008) (JL6048)
--> +1.8V_SB_PERI (IC6014) (JL6061)
--> +1.8V_EEGS_VDDIO_DIG_+1.8V1 (IC6603) (JL6355)
--> +1.8V_RDRAM_VCMOS_DIG_+1.8V1 (IC6604) (JL6356)
--> +1.6V_BE_VDDA (IC6007) (JL9654)
--> +1.5V_AVCG_VDDIO (IC6019) (JL6056)
--> +1.5V_Bridge (IC6021) (JL6069)
--> +1.5V_EEGS_VDDO_DIG_+1.5V4 (IC6606) (JL6354)
--> Q6311 (What's happening here?)
--> +1.2V_MC2_VDDIO (IC6012) (JL6063)
--> +1.2V_RSX_VDDC (IC6204) --> DRVON --> ENABLE (IC6202/3)
--> +1.0V_BE_VDDC (IC6107) --> DRVON --> ENABLE (IC6104/5/6)​

--> +1.7V_MISC (IC6301/Q6305) (JL9656)

--> +1.5V_YC_RC_VDDA (Q6308) (JL9655)
--> +1.2V_SB_VDDC (Q6309) (JL9648)
--> +1.2V_SB_VDDR (Q6309) (JL9648)
--> +1.2V_YC_RC_VDDIO (Q6310 ) (JL9652)
--> +1.2V_RSX_VDDR (Q6200) (JL9651)
--> +1.2V_EEGS_VDD_DIG_+1.2V1 (Q6600) (JL6361)
--> +1.2V_ESW (Q3504) (JL9649)​

--> +1.8V_RSX_FBVDDQ (IC6301/Q6304) (JL9657)
--> +1.2V_RSX_VDDC

--> IC6201 (2 Phase Buck Controller)

-->IC6202 (JL6205/6)
-->IC6203 (JL6207/8)​

--> +1.0V_BE_VDDC

--> IC6103 (3 Phase Buck Controller)

--> IC6104 (JL6109/10)
--> IC6105 (JL6111/12)
--> IC6106 (JL6113/14)​

It may have been corrected over time, but yesterday when analyzing a CECHA I noticed the following errors in the location of the component in the voltage tree:

+1.2V_EEGS_VDD_DIG_+1.2V1 (IC6302) > +1.2V_EEGS_VDD_DIG_+1.2V1 (IC6602)
+3.3V_MISC (IC6003/Q6601) > +3.3V_MISC (IC6003/Q6001)
+3.3V_ESW (Q5303) > +3.3V_ESW (Q3503)
+1.8V_RDRAM_VCMOS_DIG_+1.8V1 (IC6604) > This component does not exist

About Q6311 it appears to be a switch for IC6301, I have seen a similar circuit in a Sony Home Theater. Checking Q6311 is important because as it switches some type of signal to IC6301 it may even be one of the causes of error 2120, which coincidentally is an error I have in another CECHA even after having replaced IC2502 (HDMI transmitter)

 

[Fernando Vinicius]

Hello everyone. This is my first post here in the group. I recently acquired a PS3 Fat CECHA-01 backwards compatible. The device had already been opened and touched, but the board is in perfect condition. Visually, there are no flux marks or anything that could indicate rebaling or reflow. The only thing that was done was to change the NECs on one side of the board only. It has a YLOD of approximately 1.5s and it was really a find, especially where I live. Based on the errors that Syscon presents, I believe that it is only the RSX that needs rebaling or replacement. Possibly even a future Frankye. I would also like your opinion because I believe that there are people much more experienced than me, just to indicate if I am on the right track.

These are the Syscon error codes together with the beecount and a bringup

>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 2597 times
Shutdown: 2359 times
Power-on: 106day 08hour 13min 25sec
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
Press Ctrl+C to exit
>$
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$

 

[LSL]

Hello everyone. This is my first post here in the group. I recently acquired a PS3 Fat CECHA-01 backwards compatible. The device had already been opened and touched, but the board is in perfect condition. Visually, there are no flux marks or anything that could indicate rebaling or reflow. The only thing that was done was to change the NECs on one side of the board only. It has a YLOD of approximately 1.5s and it was really a find, especially where I live. Based on the errors that Syscon presents, I believe that it is only the RSX that needs rebaling or replacement. Possibly even a future Frankye. I would also like your opinion because I believe that there are people much more experienced than me, just to indicate if I am on the right track.

These are the Syscon error codes together with the beecount and a bringup

>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 2597 times
Shutdown: 2359 times
Power-on: 106day 08hour 13min 25sec
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
Press Ctrl+C to exit
>$
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$

Error 3034 was probably caused when the Nec-tokin was replaced with tantalum.

You can test this by applying light pressure to side B of the board, which is the side where the BD power supply/driver is located. Press lightly on the area between the CELL and RSX and turn on the PS3. If error 3034 persists, you could heat it for a short period of time, still on side B, the area where the RSX is located.

These are the methods I use when my PS3 shows error 3034.

Maybe other people have more tips

 

[Fernando Vinicius]

Error 3034 was probably caused when the Nec-tokin was replaced with tantalum.

You can test this by applying light pressure to side B of the board, which is the side where the BD power supply/driver is located. Press lightly on the area between the CELL and RSX and turn on the PS3. If error 3034 persists, you could heat it for a short period of time, still on side B, the area where the RSX is located.

These are the methods I use when my PS3 shows error 3034.

Maybe other people have more tips

Ok, I'll try and see if anything changes. Another detail that I noticed now, checking again, was that they only put two 470uf capacitors in place of each NEC. Could this be the case too, since with only two, the capacitance would be insufficient to power both the RSX and the Cell.

 

[RGBeter]

Hello everyone. This is my first post here in the group. I recently acquired a PS3 Fat CECHA-01 backwards compatible. The device had already been opened and touched, but the board is in perfect condition. Visually, there are no flux marks or anything that could indicate rebaling or reflow. The only thing that was done was to change the NECs on one side of the board only. It has a YLOD of approximately 1.5s and it was really a find, especially where I live. Based on the errors that Syscon presents, I believe that it is only the RSX that needs rebaling or replacement. Possibly even a future Frankye. I would also like your opinion because I believe that there are people much more experienced than me, just to indicate if I am on the right track.

These are the Syscon error codes together with the beecount and a bringup

>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 2597 times
Shutdown: 2359 times
Power-on: 106day 08hour 13min 25sec
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
Press Ctrl+C to exit
>$
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$

Classic flexio_id, I know that one all too well. Basically, your system cannot even begin to detect the RSX, and as such shuts down with a bit training error (3034) very quickly in the boot process. Unfortunately it probably needs a new RSX.

 

[Fernando Vinicius]

I'm going to replace the RSX and see if it works. I believe that this should work if no new errors appear afterwards, because there's always that chance.
As for the 470uf capacitors, which only have two where the NECs should be, I'm going to replace them too. From what I've read on the forum, three of these capacitors are needed in place of each NEC, so I could solder two on the top and one on the bottom. Could it be soldered like this? Unfortunately, I don't have access to the RIP-Felix tantalizer here.

 

[Joel_]

Hey guys,
I received a PS3 C with YLOD as a gift. Unfortunately I can't say anything about the background story, as it was a gift from a stranger via the platform "Kleinanzeigen". This is a well-known sales platform in Germany. It's roughly comparable to Facebook Marketplace. The first thing I did before switching it on for the first time was to activate the internal mode of the Syscon and display some data such as the errlog and the becount before I started it for the first time. Then I started it twice with bringup and saved everything and added it here. My question now is if a reball would be enough or is it really confirmed that the 90nm RSX have bad bumbs? The YLOD is 2.33 seconds long.

Syscon:
Errlog: errlog
ofst[ 4]:err_code:0xffffffff, clock:0x193e02ed 2013/06/02 13:19:41
ofst[ 8]:err_code:0xa0403034, clock:0x193e02ed 2013/06/02 13:19:41
ofst[ 12]:err_code:0xa0404411, clock:0x193e02f9 2013/06/02 13:19:53
ofst[ 16]:err_code:0xa0403034, clock:0x193e02f9 2013/06/02 13:19:53
ofst[ 20]:err_code:0xa0404411, clock:0x193e0304 2013/06/02 13:20:04
ofst[ 24]:err_code:0xa0403034, clock:0x193e0304 2013/06/02 13:20:04
ofst[ 28]:err_code:0xa0404411, clock:0x193e041f 2013/06/02 13:24:47
ofst[ 32]:err_code:0xa0403034, clock:0x193e041f 2013/06/02 13:24:47
ofst[ 36]:err_code:0xa0404411, clock:0x1a7eb586 2014/01/31 19:27:02
ofst[ 40]:err_code:0xa0403034, clock:0x1a7eb586 2014/01/31 19:27:02
ofst[ 44]:err_code:0xa0404411, clock:0x1a7eb58e 2014/01/31 19:27:10
ofst[ 48]:err_code:0xa0403034, clock:0x1a7eb58e 2014/01/31 19:27:10
ofst[ 52]:err_code:0xa0404411, clock:0x1a7eb59d 2014/01/31 19:27:25
ofst[ 56]:err_code:0xa0403034, clock:0x1a7eb59d 2014/01/31 19:27:25
ofst[ 60]:err_code:0xa0404411, clock:0x1a7eb7ab 2014/01/31 19:36:11
ofst[ 64]:err_code:0xa0403034, clock:0x1a7eb7ab 2014/01/31 19:36:11
ofst[ 68]:err_code:0xa0404411, clock:0x1a7eb7b4 2014/01/31 19:36:20
ofst[ 72]:err_code:0xa0403034, clock:0x1a7eb7b4 2014/01/31 19:36:20
ofst[ 76]:err_code:0xa0404411, clock:0x1a7ebb75 2014/01/31 19:52:21
ofst[ 80]:err_code:0xa0403034, clock:0x1a7ebb75 2014/01/31 19:52:21
ofst[ 84]:err_code:0xa0404411, clock:0x1a7ebb7d 2014/01/31 19:52:29
ofst[ 88]:err_code:0xa0403034, clock:0x1a7ebb7d 2014/01/31 19:52:29
ofst[ 92]:err_code:0xa0404411, clock:0x1a7ebb85 2014/01/31 19:52:37
ofst[ 96]:err_code:0xa0403034, clock:0x1a7ebb85 2014/01/31 19:52:37
ofst[100]:err_code:0xa0404411, clock:0x1a7ebb8c 2014/01/31 19:52:44
ofst[104]:err_code:0xa0403034, clock:0x1a7ebb8c 2014/01/31 19:52:44
ofst[108]:err_code:0xa0404411, clock:0x1a7ebb91 2014/01/31 19:52:49
ofst[112]:err_code:0xa0403034, clock:0x1a7ebb91 2014/01/31 19:52:49
ofst[116]:err_code:0xa0404411, clock:0x1a7ebb9a 2014/01/31 19:52:58
ofst[120]:err_code:0xa0403034, clock:0x1a7ebb9a 2014/01/31 19:52:58
ofst[124]:err_code:0xa0404411, clock:0x1a7ebba1 2014/01/31 19:53:05
ofst[ 0]:err_code:0xa0403034, clock:0x1a7ebba1 2014/01/31 19:53:05
[mullion]$
Becount: becount
Bringup : 1012 times
Shutdown: 965 times
Power-on: 71day 17hour 43min 40sec
[mullion]$
Bringup: > 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:0x21e2
> shutdown
[POWERSEQ] Error : BitTraining BE:RRAC:RX1: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]: 0xa0404411
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
> bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
> shutdown
[POWERSEQ] Error : BitTraining BE:RRAC:RX1: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]: 0xa0404411
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

 

[Nestorlink]

Hi guys!

I hope you can help me, my patience is running out. My PS3 Fat board COK-02 has not power on for many years, it turns on and off instantly with the red lights flashing. I have done the Syscon tests and it gives me error 3003 all the time. I think I have everything connected correctly even though I am not a professional. The only error I have had is that I have lost some of the mini SMD capacitors and I don't know if that could be the error, i have made bridges. If it were, would you know their values? I am attaching photos.

errlog
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xa0093003, clock:0xffffffff
ofst[124]:err_code:0xa0093003, clock:0xffffffff
ofst[  0]:err_code:0xa0093003, clock:0xffffffff
ofst[  4]:err_code:0xa0093003, clock:0xffffffff
ofst[  8]:err_code:0xa0093003, clock:0xffffffff
ofst[ 12]:err_code:0xa0093003, clock:0xffffffff
ofst[ 16]:err_code:0xa0093003, clock:0xffffffff
ofst[ 20]:err_code:0xa0093003, clock:0xffffffff
ofst[ 24]:err_code:0xa0093003, clock:0xffffffff
ofst[ 28]:err_code:0xa0093003, clock:0xffffffff
ofst[ 32]:err_code:0xa0093003, clock:0xffffffff
ofst[ 36]:err_code:0xa0093003, clock:0xffffffff
ofst[ 40]:err_code:0xa0093003, clock:0xffffffff
ofst[ 44]:err_code:0xa0093003, clock:0xffffffff
ofst[ 48]:err_code:0xa0093003, clock:0xffffffff
ofst[ 52]:err_code:0xa0093003, clock:0xffffffff
ofst[ 56]:err_code:0xa0093003, clock:0xffffffff
ofst[ 60]:err_code:0xa0093003, clock:0xffffffff
ofst[ 64]:err_code:0xa0093003, clock:0xffffffff
ofst[ 68]:err_code:0xa0093003, clock:0xffffffff
ofst[ 72]:err_code:0xa0093003, clock:0xffffffff
ofst[ 76]:err_code:0xa0093003, clock:0xffffffff
ofst[ 80]:err_code:0xa0093003, clock:0xffffffff
ofst[ 84]:err_code:0xa0093003, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0093004, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0093003, clock:0xffffffff
ofst[108]:err_code:0xa0093003, clock:0xffffffff
ofst[112]:err_code:0xa0093003, clock:0xffffffff
[mullion]$

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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093003

I have photos but I don't know why I can't attach them

I found in the manual the capacitor, it is the C6176, the others I said are fine, do not exixten on the plate, when I saw the gaps I thought they were not but everything is ok about it. Its value and specifications are 0.1uf X7R 10v 1005. The problem now is to get it, maybe I can pull one like that from the board in another less important place to check if it starts?

 

[Kibillcat]

I wouldn't be suprised if your European L model has a DIA-001 motherboard, with a 90nm RSX. SONY screwed europe and M models have it, possably other phats too.

Whoa.. thats scummy of Sony..

Interesting, it seems the pressure mod has worked, but you know, have an issue with the CPU capacitors

Sent from my SM-F936B using Tapatalk

Been a while since last update. Finally got time to replace the tokins. Replaced with same one that I had replaced RSX with, 4x330uf per tokin. At first tried one side - still same A0093003 error. Then replaced the other side and bridged positive sides - still same. Then I ordered 470uf and tried to replace - still same. I used hot air at 350C to help me solder caps because my soldering iron just couldnt do it and thought I burned the caps. Tried again but with 300C and further away - still same.
Kind of just gave up, but decided to check few things after just blindly soldering tantalum caps.
When caps soldered on - its shorted to ground, around 2ohm I think. From positive to negative - 2ohms. From negative to negative - same.
Desoldered positive jumper wire - same.
Desoldered all tantulum caps, from both sides and got interesting results. On the CELL side, checking resistance between + and -, its less tham 1ohm. On the opposite side, further away from CELL - its 155k~ ohm. On diode/beep mode value just keeps increasing like charging capacitor.

After that did some research and found Felix post that it should be around 5ohm with soldered caps. And then also checked old units that I got with failed CELL delid attempt:
DIA-002 CECHJ03 is 4.5ohm~
SEM-001 CECHG03 - 5ohm~

So Im thinking, CELL is kinda dead or some other component went bad and everything there is being shorted? Also those capacitors are from aliexpress because it was considerably cheaper and didint wanted to invest too much. So it could also be bad caps. Anyways, more in depth troubleshooting is too much for me. If got any more suggestions what could I try, I will try, because Im giving up.. Dont have that much drive to troubleshoot like used before hahah...

---EDIT---
Ahh.. Sadly I didint read more comments after last time I was here. Went to do unnecessary things and misunderstood some stuff. Interesting conversation was there onward.
Now some stuff are more clearer for me after reading next Felix post. Thank you for not mincing words and providing valuable information. Thank you all.
Anyways, it was just a fun project out of curiosity, to see if I could fix simple issue (at least thats what I thought then) and learn more about PS3. If I could have fixed it for cheap, would have been even better, if not, I still had fun and learned a lot about PS3.

 

[Ganjo]

Hello everyone. This is my first post here in the group. I recently acquired a PS3 Fat CECHA-01 backwards compatible. The device had already been opened and touched, but the board is in perfect condition. Visually, there are no flux marks or anything that could indicate rebaling or reflow. The only thing that was done was to change the NECs on one side of the board only. It has a YLOD of approximately 1.5s and it was really a find, especially where I live. Based on the errors that Syscon presents, I believe that it is only the RSX that needs rebaling or replacement. Possibly even a future Frankye. I would also like your opinion because I believe that there are people much more experienced than me, just to indicate if I am on the right track.

These are the Syscon error codes together with the beecount and a bringup

>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 2597 times
Shutdown: 2359 times
Power-on: 106day 08hour 13min 25sec
[mullion]$
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
Press Ctrl+C to exit
>$
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[mullion]$

403034 is the RSX and has nothing to do with TOKINs unless you created a cold solder joint when replacing them but Ive never had it happen.

Hey guys,
I received a PS3 C with YLOD as a gift. Unfortunately I can't say anything about the background story, as it was a gift from a stranger via the platform "Kleinanzeigen". This is a well-known sales platform in Germany. It's roughly comparable to Facebook Marketplace. The first thing I did before switching it on for the first time was to activate the internal mode of the Syscon and display some data such as the errlog and the becount before I started it for the first time. Then I started it twice with bringup and saved everything and added it here. My question now is if a reball would be enough or is it really confirmed that the 90nm RSX have bad bumbs? The YLOD is 2.33 seconds long.

Syscon:
Errlog: errlog
ofst[ 4]:err_code:0xffffffff, clock:0x193e02ed 2013/06/02 13:19:41
ofst[ 8]:err_code:0xa0403034, clock:0x193e02ed 2013/06/02 13:19:41
ofst[ 12]:err_code:0xa0404411, clock:0x193e02f9 2013/06/02 13:19:53
ofst[ 16]:err_code:0xa0403034, clock:0x193e02f9 2013/06/02 13:19:53
ofst[ 20]:err_code:0xa0404411, clock:0x193e0304 2013/06/02 13:20:04
ofst[ 24]:err_code:0xa0403034, clock:0x193e0304 2013/06/02 13:20:04
ofst[ 28]:err_code:0xa0404411, clock:0x193e041f 2013/06/02 13:24:47
ofst[ 32]:err_code:0xa0403034, clock:0x193e041f 2013/06/02 13:24:47
ofst[ 36]:err_code:0xa0404411, clock:0x1a7eb586 2014/01/31 19:27:02
ofst[ 40]:err_code:0xa0403034, clock:0x1a7eb586 2014/01/31 19:27:02
ofst[ 44]:err_code:0xa0404411, clock:0x1a7eb58e 2014/01/31 19:27:10
ofst[ 48]:err_code:0xa0403034, clock:0x1a7eb58e 2014/01/31 19:27:10
ofst[ 52]:err_code:0xa0404411, clock:0x1a7eb59d 2014/01/31 19:27:25
ofst[ 56]:err_code:0xa0403034, clock:0x1a7eb59d 2014/01/31 19:27:25
ofst[ 60]:err_code:0xa0404411, clock:0x1a7eb7ab 2014/01/31 19:36:11
ofst[ 64]:err_code:0xa0403034, clock:0x1a7eb7ab 2014/01/31 19:36:11
ofst[ 68]:err_code:0xa0404411, clock:0x1a7eb7b4 2014/01/31 19:36:20
ofst[ 72]:err_code:0xa0403034, clock:0x1a7eb7b4 2014/01/31 19:36:20
ofst[ 76]:err_code:0xa0404411, clock:0x1a7ebb75 2014/01/31 19:52:21
ofst[ 80]:err_code:0xa0403034, clock:0x1a7ebb75 2014/01/31 19:52:21
ofst[ 84]:err_code:0xa0404411, clock:0x1a7ebb7d 2014/01/31 19:52:29
ofst[ 88]:err_code:0xa0403034, clock:0x1a7ebb7d 2014/01/31 19:52:29
ofst[ 92]:err_code:0xa0404411, clock:0x1a7ebb85 2014/01/31 19:52:37
ofst[ 96]:err_code:0xa0403034, clock:0x1a7ebb85 2014/01/31 19:52:37
ofst[100]:err_code:0xa0404411, clock:0x1a7ebb8c 2014/01/31 19:52:44
ofst[104]:err_code:0xa0403034, clock:0x1a7ebb8c 2014/01/31 19:52:44
ofst[108]:err_code:0xa0404411, clock:0x1a7ebb91 2014/01/31 19:52:49
ofst[112]:err_code:0xa0403034, clock:0x1a7ebb91 2014/01/31 19:52:49
ofst[116]:err_code:0xa0404411, clock:0x1a7ebb9a 2014/01/31 19:52:58
ofst[120]:err_code:0xa0403034, clock:0x1a7ebb9a 2014/01/31 19:52:58
ofst[124]:err_code:0xa0404411, clock:0x1a7ebba1 2014/01/31 19:53:05
ofst[ 0]:err_code:0xa0403034, clock:0x1a7ebba1 2014/01/31 19:53:05
[mullion]$
Becount: becount
Bringup : 1012 times
Shutdown: 965 times
Power-on: 71day 17hour 43min 40sec
[mullion]$
Bringup: > 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:0x21e2
> shutdown
[POWERSEQ] Error : BitTraining BE:RRAC:RX1: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]: 0xa0404411
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
> bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
> shutdown
[POWERSEQ] Error : BitTraining BE:RRAC:RX1: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]: 0xa0404411
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

The RSX is bad. A reflow might work but it wont work very long. The only way to get a more permanent fix is to put a 40nm on it.

 

[Ganjo]

Anyone have any suggestions for this console? After putting a 40nm on it im getting instant YLOD but it wont drop an error code. I normally swap the TOKINs after I get it booting but they were bad so I had to swap them first.

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

Previous error log info

Bringup : 1451 times
Shutdown: 1359 times
Power-on: 2976day 06hour 29min 25sec


ofst[120]:err_code:0xffffffff, clock:0x10468ab0  2008/08/26 09:34:40
ofst[124]:err_code:0xa0801002, clock:0x10468ab6  2008/08/26 09:34:46
ofst[  0]:err_code:0xa0101001, clock:0x10468ab9  2008/08/26 09:34:49
ofst[  4]:err_code:0xa0801002, clock:0x10468ac0  2008/08/26 09:34:56
ofst[  8]:err_code:0xa0801002, clock:0x10468acf  2008/08/26 09:35:11
ofst[ 12]:err_code:0xa0801002, clock:0x10468ad4  2008/08/26 09:35:16
ofst[ 16]:err_code:0xa0801002, clock:0x10468afb  2008/08/26 09:35:55
ofst[ 20]:err_code:0xa0801002, clock:0x10468b01  2008/08/26 09:36:01
ofst[ 24]:err_code:0xa0801002, clock:0x10468b09  2008/08/26 09:36:09
ofst[ 28]:err_code:0xa0801002, clock:0x10468b0f  2008/08/26 09:36:15
ofst[ 32]:err_code:0xa0801002, clock:0x10468b16  2008/08/26 09:36:22
ofst[ 36]:err_code:0xa0801002, clock:0x10468b1d  2008/08/26 09:36:29
ofst[ 40]:err_code:0xa0101001, clock:0x10468b1f  2008/08/26 09:36:31
ofst[ 44]:err_code:0xa0801002, clock:0x10468b24  2008/08/26 09:36:36
ofst[ 48]:err_code:0xa0101001, clock:0x10468b26  2008/08/26 09:36:38
ofst[ 52]:err_code:0xa0611001, clock:0x10468b28  2008/08/26 09:36:40
ofst[ 56]:err_code:0xa0801002, clock:0x10468b31  2008/08/26 09:36:49
ofst[ 60]:err_code:0xa0801002, clock:0x10468b36  2008/08/26 09:36:54
ofst[ 64]:err_code:0xa0801002, clock:0x10468b3d  2008/08/26 09:37:01
ofst[ 68]:err_code:0xa0801002, clock:0x10468b43  2008/08/26 09:37:07
ofst[ 72]:err_code:0xa0801002, clock:0x10468b49  2008/08/26 09:37:13
ofst[ 76]:err_code:0xa0801002, clock:0x10468b50  2008/08/26 09:37:20
ofst[ 80]:err_code:0xa0801002, clock:0x10468b56  2008/08/26 09:37:26
ofst[ 84]:err_code:0xa0801002, clock:0x10468b5c  2008/08/26 09:37:32
ofst[ 88]:err_code:0xa0801002, clock:0x10468b62  2008/08/26 09:37:38
ofst[ 92]:err_code:0xa0801002, clock:0x10468b69  2008/08/26 09:37:45
ofst[ 96]:err_code:0xa0801002, clock:0x10468b6f  2008/08/26 09:37:51
ofst[100]:err_code:0xa0801002, clock:0x10468b84  2008/08/26 09:38:12
ofst[104]:err_code:0xa0801002, clock:0x10468b8b  2008/08/26 09:38:19
ofst[108]:err_code:0xa0101001, clock:0x10468b8d  2008/08/26 09:38:21
ofst[112]:err_code:0xa0801002, clock:0x10468b94  2008/08/26 09:38:28
ofst[116]:err_code:0xa0801002, clock:0x10468b9b  2008/08/26 09:38:35