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

Kleon1876 said:
So I just did the error dump and got the following. Appears the same two codes. What do they mean?

===================================
ERR 00: 00000000 A0A02031 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0A02031 FFFFFFFF
ERR 03: 00000000 A0022110 FFFFFFFF
ERR 04: 00000000 A0A02031 FFFFFFFF
ERR 05: 00000000 A0022110 FFFFFFFF
ERR 06: 00000000 A0A02031 FFFFFFFF
ERR 07: 00000000 A0A02031 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0A02031 FFFFFFFF
ERR 10: 00000000 A0A02031 FFFFFFFF
ERR 11: 00000000 A0A02031 FFFFFFFF
ERR 12: 00000000 A0A02031 FFFFFFFF
ERR 13: 00000000 A0022110 FFFFFFFF
ERR 14: 00000000 A0A02031 FFFFFFFF
ERR 15: 00000000 A0A02031 FFFFFFFF
ERR 16: 00000000 A0022110 FFFFFFFF
ERR 17: 00000000 A0A02031 FFFFFFFF
ERR 18: 00000000 A0022110 FFFFFFFF
ERR 19: 00000000 A0A02031 FFFFFFFF
===================================

So after doing some research, I understand the 2031 error to be "thermal sensor error ic2101". What does this mean? What is ic2101 mean?
Also the 22110 error means "clock generator error ic5001". Same problem what does the clock generator mean and ic5001? My guess ic5001 is something on the pcb that's faulty?
Click to expand...

So based on your error, looks like your timebase chip has gone bad or missing the correct voltage

https://www.psdevwiki.com/ps3/Timebases#ICS_ICS9214DGLFT_.28IC_CLOCK_GEN_RAMBUS_XDR_28-TSSOP.29 - IC5001

This chip basically keeps the RAMBUS in sync (equivalent to the pci bus) with the cpu,rsx etc. Can cause a GLOD and is known to fail on the old models.
 
Kleon1876 said:
So after doing some research, I understand the 2031 error to be "thermal sensor error ic2101". What does this mean? What is ic2101 mean?
Also the 22110 error means "clock generator error ic5001". Same problem what does the clock generator mean and ic5001? My guess ic5001 is something on the pcb that's faulty?

UPDATE: I used the schematics pdf (below) for SEM-001 ( I need one for DIA-001) and identified the chips for ic5001 and ic2101. It should be noted that this specific board has been reballed (not sure if I was successful without killing the chip) and also had all the necks (both sides) replaced and a bridged (total of 8 bridges, 2x rsx top, 2x rsx bottom, 2x cpu top and 2x cpu bottom).
Click to expand...

Its possible the reheat killed the timebase chip or was dead originally. As i have said, GLOD faults dont register any errors.

And the fact it crashes when in safe mode points to this an issue.
 
Kleon1876 said:
Where? I can't find the diagram for DIA-001. Where exactly is it in the repository?

here is a good breakdown of the diagram for cechg model pcb SEM-001
http://psx-core.ru/_ld/5/512_sm-ps3-0093e-02.pdf

now if only someone can point me in the direction of this but for DIA-001
Click to expand...

There is no leaked DIA-001 diagrams, so you will be out of luck.

What im doing at the moment is recording a working DIA-001,002 board testpoints - voltages and resistance. So i can add to the repo to help diag further.
 
Kleon1876 said:
UPDATE: I used the schematics pdf (below) for SEM-001 ( I need one for DIA-001) and identified the chips for ic5001 and ic2101. It should be noted that this specific board has been reballed (not sure if I was successful without killing the chip) and also had all the necks (both sides) replaced and a bridged (total of 8 bridges, 2x rsx top, 2x rsx bottom, 2x cpu top and 2x cpu bottom).
Click to expand...

Do a google search 'cok-002 service manual', this will be the correct manual
 
db260179 said:
So based on your error, looks like your timebase chip has gone bad or missing the correct voltage

https://www.psdevwiki.com/ps3/Timebases#ICS_ICS9214DGLFT_.28IC_CLOCK_GEN_RAMBUS_XDR_28-TSSOP.29 - IC5001

This chip basically keeps the RAMBUS in sync (equivalent to the pci bus) with the cpu,rsx etc. Can cause a GLOD and is known to fail on the old models.
Click to expand...

so interesting you mention GLOD. this cechg DIA-001 started out as ylod. I did a poor mans reflow using heatfun no IR preheater. And replaced one nec. Hit the power bottom and gOT GLOD. the controller wouldn't sync just keep blinking or freeze. So I continued removing one nec at a time and replacing with tantlums. Still GLOD. I eventually took all but one nec on the cpu side, bridged the rsx bottom side and still GLOD. I was messing with the wifi/usb pcb ribbon to motherboard while in GLOD Mode when suddenly it YLOD and has been instant YLOD ever since. I reballed (using preheater, stencil, jig, all the mentioned goodies in the reball section) I replaced the last nec and and bridged both rsx and cpu both bottom and top and still YLOD. then I dumped the error codes and the above is what it showed. What are your thoughts? Did I short anything when messing with the ribbon cable? Have I screwed up and shorted the rails when replacing the necs? Could have I messed up the bridging on the necs or is it what it shows per the error code?

also it's awesome that you are recording test points for DIA-001. I'm sure it will help me. Hopefully it's out soon. Thank you.
 
db260179 said:
Its possible the reheat killed the timebase chip or was dead originally. As i have said, GLOD faults dont register any errors.

And the fact it crashes when in safe mode points to this an issue.
Click to expand...
Hey, perhaps you confused my username with kleon, because I said about crashing safe mode , also console might have power outage during update or bluray got disconnected due to the connector clip missing.
Cheers
 
@db260179 Also, I have a CECHK03(dia-002) that was acting as if it was stuck in internal mode(plug in power and triple beep, red blinking light), the syscon (tx rx etc) points seemed untouched, i soldered my ttl there, went in internal mode, found 2 mismatches, fixed them and now it's ylod, with code A0232102, now, that code according to the thread means "A0232102 - IC6301 faulty (1.5v RSX_VDDIO) or in that area" but i would appreciate some guidance as i do not know which components to test and how to test them(what values are they supposed to be? Any help would be greatly appreciated.(Also the error log from syscon didnt show a ylod which is weird and probably had never yloded before?)
>$ auth
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
sum:0x0100
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ r 3900 100
r 3900 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF BF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 50 21 FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF
FF 03 C8 78 FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
02 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF 50 74

[mullion]$
>$ w 39fe 50 73
w 39fe 50 73
w complete!
[mullion]$
>$ r 3900 100
r 3900 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF BF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 50 21 FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF
FF 03 C8 78 FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
02 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF 50 73

[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ errlog
errlog
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0xffffffff
ofst[ 4]:err_code:0xa0801001, clock:0x13944a56 2010/05/29 21:57:42
ofst[ 8]:err_code:0xa0801001, clock:0xffffffff
ofst[ 12]:err_code:0xa0801001, clock:0xffffffff
ofst[ 16]:err_code:0xa0801001, clock:0xffffffff
ofst[ 20]:err_code:0xa0801001, clock:0x16711ab7 2011/12/06 18:25:59
ofst[ 24]:err_code:0xa0801001, clock:0x16977d16 2012/01/04 21:11:50
ofst[ 28]:err_code:0xa0801001, clock:0x169820df 2012/01/05 08:50:39
ofst[ 32]:err_code:0xa0801001, clock:0x16ca9e79 2012/02/12 15:59:53
ofst[ 36]:err_code:0xa0801001, clock:0xffffffff
ofst[ 40]:err_code:0xa0801001, clock:0x1893709c 2013/01/24 04:10:04
ofst[ 44]:err_code:0xa0801001, clock:0x1af6905b 2014/05/02 17:20:27
ofst[ 48]:err_code:0xa0a02031, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 702 times
Shutdown: 649 times
Power-on: 78day 15hour 07min 20sec
[mullion]$
>$ version
version
v1.4.4_k2
[mullion]$
>$ hversion
hversion
CokE10
>$ fantbl
fantbl
*** Invalid Argument ***
[mullion]$
>$ fantbl get 0
fantbl get 0
fancon No:00
P0: TempD:0.0(0x0000) - TempU:74.0(0x4a00) duty:20%(0x33)
P1: TempD:62.50(0x3e80) - TempU:75.0(0x4b00) duty:21%(0x36)
P2: TempD:63.0(0x3f00) - TempU:76.0(0x4c00) duty:22%(0x39)
P3: TempD:63.50(0x3f80) - TempU:77.0(0x4d00) duty:23%(0x3b)
P4: TempD:64.0(0x4000) - TempU:78.0(0x4e00) duty:24%(0x3e)
P5: TempD:64.50(0x4080) - TempU:79.0(0x4f00) duty:25%(0x40)
P6: TempD:65.0(0x4100) - TempU:80.0(0x5000) duty:26%(0x43)
P7: TempD:65.50(0x4180) - TempU:81.0(0x5100) duty:28%(0x48)
P8: TempD:66.0(0x4200) - TempU:82.0(0x5200) duty:29%(0x4a)
P9: TempD:66.50(0x4280) - TempU:83.0(0x5300) duty:31%(0x50)
P10: TempD:67.0(0x4300) - TempU:84.0(0x5400) duty:33%(0x55)
P11: TempD:67.50(0x4380) - TempU:85.0(0x5500) duty:35%(0x5a)
P12: TempD:68.0(0x4400) - TempU:86.0(0x5600) duty:40%(0x66)
P13: TempD:72.0(0x4800) - TempU:87.0(0x5700) duty:50%(0x80)
P14: TempD:79.50(0x4f80) - TempU:88.0(0x5800) duty:60%(0x99)
P15: TempD:80.0(0x5000) - TempU:91.0(0x5b00) duty:100%(0xff)
P16: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P17: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P18: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P19: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
[mullion]$
>$ fantbl get 1
fantbl get 1
fancon No:01
P0: TempD:0.0(0x0000) - TempU:80.0(0x5000) duty:20%(0x33)
P1: TempD:69.0(0x4500) - TempU:81.0(0x5100) duty:21%(0x36)
P2: TempD:69.50(0x4580) - TempU:82.0(0x5200) duty:22%(0x39)
P3: TempD:70.0(0x4600) - TempU:83.0(0x5300) duty:23%(0x3b)
P4: TempD:70.50(0x4680) - TempU:84.0(0x5400) duty:24%(0x3e)
P5: TempD:71.0(0x4700) - TempU:85.0(0x5500) duty:25%(0x40)
P6: TempD:71.50(0x4780) - TempU:86.0(0x5600) duty:26%(0x43)
P7: TempD:72.0(0x4800) - TempU:87.0(0x5700) duty:28%(0x48)
P8: TempD:72.50(0x4880) - TempU:88.0(0x5800) duty:29%(0x4a)
P9: TempD:73.0(0x4900) - TempU:89.0(0x5900) duty:31%(0x50)
P10: TempD:73.50(0x4980) - TempU:90.0(0x5a00) duty:33%(0x55)
P11: TempD:74.0(0x4a00) - TempU:91.0(0x5b00) duty:35%(0x5a)
P12: TempD:74.50(0x4a80) - TempU:92.0(0x5c00) duty:40%(0x66)
P13: TempD:75.0(0x4b00) - TempU:93.0(0x5d00) duty:50%(0x80)
P14: TempD:81.50(0x5180) - TempU:94.0(0x5e00) duty:60%(0x99)
P15: TempD:82.0(0x5200) - TempU:97.0(0x6100) duty:100%(0xff)
P16: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P17: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P18: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P19: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
[mullion]$
>$ eepcsum
epcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ r 3d00 100
r 3d00 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF BF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00

[mullion]$
>$ w 3dfe ff 40
w 3dfe ff 40
w complete!
[mullion]$
>$ r 3d00 100
r 3d00 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF BF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 40

[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
Addr:0x00003dfe should be 0x40ff
Addr:0x00003ffe should be 0x00ff
>$ exit

C:\Users\Kostaslgr7\Desktop\ps3syscon-master>python ps3_syscon_uart_script.py COM5 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 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$
 
I believe DB is working on something for the dia-001/002 boards. His post is a couple of posts above. I'm in the same boat. I have dumped the error codes but not sure how to test and what to test.
Also according to the error chart, 2101 says BE error code which I'm assuming is the cpu because it also says the chip in question is labeled ic1001 which per the schematics from cok-002 board is the cpu. Possible nec tokins maybe or it could be a bad cpu. Not sure.

Kostaslgr7 said:
@db260179 Also, I have a CECHK03(dia-002) that was acting as if it was stuck in internal mode(plug in power and triple beep, red blinking light), the syscon (tx rx etc) points seemed untouched, i soldered my ttl there, went in internal mode, found 2 mismatches, fixed them and now it's ylod, with code A0232102, now, that code according to the thread means "A0232102 - IC6301 faulty (1.5v RSX_VDDIO) or in that area" but i would appreciate some guidance as i do not know which components to test and how to test them(what values are they supposed to be? Any help would be greatly appreciated.(Also the error log from syscon didnt show a ylod which is weird and probably had never yloded before?)
>$ auth
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
sum:0x0100
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ r 3900 100
r 3900 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF BF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 50 21 FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF
FF 03 C8 78 FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
02 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF 50 74

[mullion]$
>$ w 39fe 50 73
w 39fe 50 73
w complete!
[mullion]$
>$ r 3900 100
r 3900 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF BF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
40 50 21 FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF 00 FF FF FF FF FF FF FF FF FF FF FF FF
FF 03 C8 78 FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
02 00 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF 50 73

[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ errlog
errlog
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
ofst[ 60]:err_code:0xffffffff, clock:0xffffffff
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xffffffff, clock:0xffffffff
ofst[ 80]:err_code:0xffffffff, clock:0xffffffff
ofst[ 84]:err_code:0xffffffff, clock:0xffffffff
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xffffffff, clock:0xffffffff
ofst[ 96]:err_code:0xffffffff, clock:0xffffffff
ofst[100]:err_code:0xffffffff, clock:0xffffffff
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xffffffff, clock:0xffffffff
ofst[116]:err_code:0xffffffff, clock:0xffffffff
ofst[120]:err_code:0xffffffff, clock:0xffffffff
ofst[124]:err_code:0xffffffff, clock:0xffffffff
ofst[ 0]:err_code:0xa0801001, clock:0xffffffff
ofst[ 4]:err_code:0xa0801001, clock:0x13944a56 2010/05/29 21:57:42
ofst[ 8]:err_code:0xa0801001, clock:0xffffffff
ofst[ 12]:err_code:0xa0801001, clock:0xffffffff
ofst[ 16]:err_code:0xa0801001, clock:0xffffffff
ofst[ 20]:err_code:0xa0801001, clock:0x16711ab7 2011/12/06 18:25:59
ofst[ 24]:err_code:0xa0801001, clock:0x16977d16 2012/01/04 21:11:50
ofst[ 28]:err_code:0xa0801001, clock:0x169820df 2012/01/05 08:50:39
ofst[ 32]:err_code:0xa0801001, clock:0x16ca9e79 2012/02/12 15:59:53
ofst[ 36]:err_code:0xa0801001, clock:0xffffffff
ofst[ 40]:err_code:0xa0801001, clock:0x1893709c 2013/01/24 04:10:04
ofst[ 44]:err_code:0xa0801001, clock:0x1af6905b 2014/05/02 17:20:27
ofst[ 48]:err_code:0xa0a02031, clock:0xffffffff
[mullion]$
>$ becount
becount
Bringup : 702 times
Shutdown: 649 times
Power-on: 78day 15hour 07min 20sec
[mullion]$
>$ version
version
v1.4.4_k2
[mullion]$
>$ hversion
hversion
CokE10
>$ fantbl
fantbl
*** Invalid Argument ***
[mullion]$
>$ fantbl get 0
fantbl get 0
fancon No:00
P0: TempD:0.0(0x0000) - TempU:74.0(0x4a00) duty:20%(0x33)
P1: TempD:62.50(0x3e80) - TempU:75.0(0x4b00) duty:21%(0x36)
P2: TempD:63.0(0x3f00) - TempU:76.0(0x4c00) duty:22%(0x39)
P3: TempD:63.50(0x3f80) - TempU:77.0(0x4d00) duty:23%(0x3b)
P4: TempD:64.0(0x4000) - TempU:78.0(0x4e00) duty:24%(0x3e)
P5: TempD:64.50(0x4080) - TempU:79.0(0x4f00) duty:25%(0x40)
P6: TempD:65.0(0x4100) - TempU:80.0(0x5000) duty:26%(0x43)
P7: TempD:65.50(0x4180) - TempU:81.0(0x5100) duty:28%(0x48)
P8: TempD:66.0(0x4200) - TempU:82.0(0x5200) duty:29%(0x4a)
P9: TempD:66.50(0x4280) - TempU:83.0(0x5300) duty:31%(0x50)
P10: TempD:67.0(0x4300) - TempU:84.0(0x5400) duty:33%(0x55)
P11: TempD:67.50(0x4380) - TempU:85.0(0x5500) duty:35%(0x5a)
P12: TempD:68.0(0x4400) - TempU:86.0(0x5600) duty:40%(0x66)
P13: TempD:72.0(0x4800) - TempU:87.0(0x5700) duty:50%(0x80)
P14: TempD:79.50(0x4f80) - TempU:88.0(0x5800) duty:60%(0x99)
P15: TempD:80.0(0x5000) - TempU:91.0(0x5b00) duty:100%(0xff)
P16: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P17: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P18: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P19: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
[mullion]$
>$ fantbl get 1
fantbl get 1
fancon No:01
P0: TempD:0.0(0x0000) - TempU:80.0(0x5000) duty:20%(0x33)
P1: TempD:69.0(0x4500) - TempU:81.0(0x5100) duty:21%(0x36)
P2: TempD:69.50(0x4580) - TempU:82.0(0x5200) duty:22%(0x39)
P3: TempD:70.0(0x4600) - TempU:83.0(0x5300) duty:23%(0x3b)
P4: TempD:70.50(0x4680) - TempU:84.0(0x5400) duty:24%(0x3e)
P5: TempD:71.0(0x4700) - TempU:85.0(0x5500) duty:25%(0x40)
P6: TempD:71.50(0x4780) - TempU:86.0(0x5600) duty:26%(0x43)
P7: TempD:72.0(0x4800) - TempU:87.0(0x5700) duty:28%(0x48)
P8: TempD:72.50(0x4880) - TempU:88.0(0x5800) duty:29%(0x4a)
P9: TempD:73.0(0x4900) - TempU:89.0(0x5900) duty:31%(0x50)
P10: TempD:73.50(0x4980) - TempU:90.0(0x5a00) duty:33%(0x55)
P11: TempD:74.0(0x4a00) - TempU:91.0(0x5b00) duty:35%(0x5a)
P12: TempD:74.50(0x4a80) - TempU:92.0(0x5c00) duty:40%(0x66)
P13: TempD:75.0(0x4b00) - TempU:93.0(0x5d00) duty:50%(0x80)
P14: TempD:81.50(0x5180) - TempU:94.0(0x5e00) duty:60%(0x99)
P15: TempD:82.0(0x5200) - TempU:97.0(0x6100) duty:100%(0xff)
P16: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P17: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P18: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
P19: TempD:255.75(0xffff) - TempU:255.75(0xffff) duty:100%(0xff)
[mullion]$
>$ eepcsum
epcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ r 3d00 100
r 3d00 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF BF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00

[mullion]$
>$ w 3dfe ff 40
w 3dfe ff 40
w complete!
[mullion]$
>$ r 3d00 100
r 3d00 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF BF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 40

[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
Addr:0x00003dfe should be 0x40ff
Addr:0x00003ffe should be 0x00ff
>$ exit

C:\Users\Kostaslgr7\Desktop\ps3syscon-master>python ps3_syscon_uart_script.py COM5 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 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$
Click to expand...
 
Im curious about an small detail a bit weird from your report, is not a question for you but for all in general, incase someone knows why is happening this
Kostaslgr7 said:
>$ eepcsum
epcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
sum:0xc000
Addr:0x00003dfe should be 0xffff40ff
Addr:0x00003ffe should be 0x00ff
>$ r 3d00 100
r 3d00 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF BF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00

[mullion]$
>$ w 3dfe ff 40
w 3dfe ff 40
w complete!
[mullion]$
>$ r 3d00 100
r 3d00 100
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF BF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 40

[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56b6
Addr:0x000034fe should be 0x985b
Addr:0x000039fe should be 0x7350
Addr:0x00003dfe should be 0x40ff
Addr:0x00003ffe should be 0x00ff
Click to expand...
In the first eepcsum command syscon was telling that "Addr:0x00003dfe should be 0xffff40ff", but thats not correct because that csums are only 2 bytes lenght, and syscon is displaying a value of 4 bytes

In the next commands you fixed it correctly by writing 0xFF40... and as can be seen at the last command the csum is reported correctly after that with a lenght of 2 bytes in the line "Addr:0x00003dfe should be 0x40ff"

In short... you only wrote 2 bytes from the 4 suggested by syscon (0x40ff instead of 0xffff40ff)... because what syscon was displaying looks weird

------------------
Now by reading your report i understand the process, you did it correctly (confirmed by syscon in the last eepcsum command)
But im wondering if the way how it was displayed it could be considered a bug of syscon firmware ?... or if there is another reason im missing that could explain why syscon was displaying a csum of 4 bytes instead of 2 ?
 
Last edited:
Kostaslgr7 said:
@db260179 Also, I have a CECHK03(dia-002) that was acting as if it was stuck in internal mode(plug in power and triple beep, red blinking light), the syscon (tx rx etc) points seemed untouched, i soldered my ttl there, went in internal mode, found 2 mismatches, fixed them and now it's ylod, with code A0232102, now, that code according to the thread means "A0232102 - IC6301 faulty (1.5v RSX_VDDIO) or in that area" but i would appreciate some guidance as i do not know which components to test and how to test them(what values are they supposed to be? Any help would be greatly appreciated.(Also the error log from syscon didnt show a ylod which is weird and probably had never yloded before?)

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

[mullion]$
>$
Click to expand...

Your issue looks like a failed Power IC chip - https://www.ebay.com/itm/5x-NEW-Pow...OP-15pin-Chipset-SN-105233-DBTR-/230821648200

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

Check the voltages on this chip when it powers on based on the component manual.

The sem-001 service manual for this chip will be the same so use that as a reference.

You will find that chip on the bottom near to the RSX.

Check any capacitors around that area for high resistance, usually in the millions reading is bad. Check for shorts as well.

To do this is very easy, negative on GND and postive on a power pin in buzz mode (multimeter) on the chip - if buzzes then there is a short, possible capacitor fault.

Work in progress images for DIA-002 - only resistance checks for now

https://ibb.co/YW3cSTL
https://ibb.co/FKCd1M1
 
Last edited:
So here is an update.

I have a SEM-001 which had GLOD. I have removed RSX bottom 2 tokins, havent replaced them with tantlums yet. I dumped the error codes originally and i got the following.

===================================
ERR 00: 00000000 A0213013 FFFFFFFF
ERR 01: 00000000 A0213013 FFFFFFFF
ERR 02: 00000000 A0213013 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0213013 FFFFFFFF
ERR 11: 00000000 A0213013 FFFFFFFF
ERR 12: 00000000 A0213013 FFFFFFFF
ERR 13: 00000000 A0213013 FFFFFFFF
ERR 14: 00000000 A0213013 FFFFFFFF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
BE_SPI DI/DO ERROR - CELL not communicating to syscon via
SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible
shorts on the line, check C4001 and trailing caps. Possible CELL dead?
ERR 17: 00000000 A0403034 FFFFFFFF
Poor BGA solder connections for RSX
( you will see errors like - [POWERSEQ] Error :
BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
ERR 18: 00000000 A0404411 FFFFFFFF
Poor BGA solder connections for RSX
( you will see errors like - [POWERSEQ] Error :
BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
ERR 19: 00000000 A0402101 FFFFFFFF
???????????????????
===================================

after this, I decided to remove the RSX to reball.
I dumped the error codes without the rsx on and still missing the two necs on the bottom of the pcb. Got the following error codes.
===================================
ERR 00: 00000000 A0093003 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0A02030 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0213013 FFFFFFFF
ERR 11: 00000000 A0213013 FFFFFFFF
ERR 12: 00000000 A0213013 FFFFFFFF
ERR 13: 00000000 A0213013 FFFFFFFF
ERR 14: 00000000 A0213013 FFFFFFFF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
ERR 17: 00000000 A0213013 FFFFFFFF
ERR 18: 00000000 A0213013 FFFFFFFF
ERR 19: 00000000 A0213013 FFFFFFFF
===================================

As you can see 3013 persisted even tho no RSX. My theory is its either RSX related, or has nothing to do with RSX (maybe because necs are missing). New errors popped up tho 3003, 2031 and 2030. since I removed the RSX. My guess 3003, 2031, 2030 are RSX related error. I also screwed up some tiny capacitors that came off near the RSX. I'll post a picture of the PCB next. What are your thoughts to help narrow down these errors to a specific part?

Also, where did my original errors go when I hadn't removed the RSX including 4411, 3035 and 2101. All i did was remove the RSX...and some tiny components next to the rsx.

and I think I killed the cpu when I was deliding it up scratching it.
 

Attachments

  • 38AF762A-D209-409E-BE29-568701BC203C.jpeg
    38AF762A-D209-409E-BE29-568701BC203C.jpeg
    1.1 MB · Views: 158
  • 0A102F65-880C-4D3A-833D-2E1D0B5DF634.jpeg
    0A102F65-880C-4D3A-833D-2E1D0B5DF634.jpeg
    1.6 MB · Views: 158
  • 576DF743-3B08-486F-B689-EA17672FF9C5.jpeg
    576DF743-3B08-486F-B689-EA17672FF9C5.jpeg
    2 MB · Views: 134
  • E96878A9-0656-4A79-99DE-F3DA990BFB01.jpeg
    E96878A9-0656-4A79-99DE-F3DA990BFB01.jpeg
    1.8 MB · Views: 136
  • 99CA2B7B-E423-4A0B-ADA3-E741765A74CD.jpeg
    99CA2B7B-E423-4A0B-ADA3-E741765A74CD.jpeg
    1.7 MB · Views: 129
Last edited:
Kleon1876 said:
So here is an update.

I have a SEM-001 which had GLOD. I have removed RSX bottom 2 tokins, havent replaced them with tantlums yet. I dumped the error codes originally and i got the following.

===================================
ERR 00: 00000000 A0213013 FFFFFFFF
ERR 01: 00000000 A0213013 FFFFFFFF
ERR 02: 00000000 A0213013 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0213013 FFFFFFFF
ERR 11: 00000000 A0213013 FFFFFFFF
ERR 12: 00000000 A0213013 FFFFFFFF
ERR 13: 00000000 A0213013 FFFFFFFF
ERR 14: 00000000 A0213013 FFFFFFFF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
BE_SPI DI/DO ERROR - CELL not communicating to syscon via
SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible
shorts on the line, check C4001 and trailing caps. Possible CELL dead?
ERR 17: 00000000 A0403034 FFFFFFFF
Poor BGA solder connections for RSX
( you will see errors like - [POWERSEQ] Error :
BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
ERR 18: 00000000 A0404411 FFFFFFFF
Poor BGA solder connections for RSX
( you will see errors like - [POWERSEQ] Error :
BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
ERR 19: 00000000 A0402101 FFFFFFFF
???????????????????
===================================

after this, I decided to remove the RSX to reball.
I dumped the error codes without the rsx on and still missing the two necs on the bottom of the pcb. Got the following error codes.
===================================
ERR 00: 00000000 A0093003 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0A02030 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0213013 FFFFFFFF
ERR 11: 00000000 A0213013 FFFFFFFF
ERR 12: 00000000 A0213013 FFFFFFFF
ERR 13: 00000000 A0213013 FFFFFFFF
ERR 14: 00000000 A0213013 FFFFFFFF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
ERR 17: 00000000 A0213013 FFFFFFFF
ERR 18: 00000000 A0213013 FFFFFFFF
ERR 19: 00000000 A0213013 FFFFFFFF
===================================

As you can see 3013 persisted even tho no RSX. My theory is its either RSX related, or has nothing to do with RSX (maybe because necs are missing). New errors popped up tho 3003, 2031 and 2030. since I removed the RSX. My guess 3003, 2031, 2030 are RSX related error. I also screwed up some tiny capacitors that came off near the RSX. I'll post a picture of the PCB next. What are your thoughts to help narrow down these errors to a specific part?

Also, where did my original errors go when I hadn't removed the RSX including 4411, 3035 and 2101. All i did was remove the RSX...and some tiny components next to the rsx.
Click to expand...

The old errors don't go away unless you clear them manually. Having 3031 AFTER 3003-2031-2030 means you had them already.
A0A0 -error after syscon reset (just after plugged in) , 2030/2031 thermal sensor error (maybe I2C bus error-- missing pullup resistors?)
A009 - error in power off state , 3003 power fail... i have no clue what it may be -- a bringup log may be help.
Luckily you can find the schematic for that model if you look around.
 
Yeah I'm missing some resistors for sure. I can't access bring up log because I'm using the GUI not the cmd.

CodeKiller said:
The old errors don't go away unless you clear them manually. Having 3031 AFTER 3003-2031-2030 means you had them already.
A0A0 -error after syscon reset (just after plugged in) , 2030/2031 thermal sensor error (maybe I2C bus error-- missing pullup resistors?)
A009 - error in power off state , 3003 power fail... i have no clue what it may be -- a bringup log may be help.
Luckily you can find the schematic for that model if you look around.
Click to expand...
 
I have looked through the pages on this thread and can't seem to find a step by step for bringup log. Can someone point me in the right direction?
 
Kleon1876 said:
I have looked through the pages on this thread and can't seem to find a step by step for bringup log. Can someone point me in the right direction?
Click to expand...
Assuming you already connected to the syscon and into internal mode, the command "bringup" will immediately boot the ps3 and start outputting the boot log.

To get previous boot error codes, simply type "errorlog". This will only output the codes, though, not the full log.

I'm pretty sure the documentation in the github page has a full list of commands....
 
I don't know how to get it into internal mode using CMD on Windows 7. I tried reading on it, but the diag/gnd thing confuses me. I hope someone puts out a video guide for dummys like me.

Here is my situation,

I have a DIA-001 which originally had YLOD. I started messing with the necs and after replacing one single nec on the bottom of RSX i got GLOD. I kept on removing necs and replacing them and GLOD. I even removed a NEC and tried powering on but got GLOD without a nec or tantlums. Then i was messing around with the wifi/usb ribbon while powered on into GLOD and got a sudden YLOD. It's been YLOD ever since. Then I decided to remove all necs and bridge both sides per the guide. Still ylod i reballed the RSX and found out about this thread. Dumped the error codes using the GUI not CMD and got the following error codes

===================================
ERR 00: 00000000 A0A02031 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0A02031 FFFFFFFF
ERR 03: 00000000 A0022110 FFFFFFFF
ERR 04: 00000000 A0A02031 FFFFFFFF
ERR 05: 00000000 A0022110 FFFFFFFF
ERR 06: 00000000 A0A02031 FFFFFFFF
ERR 07: 00000000 A0A02031 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0A02031 FFFFFFFF
ERR 10: 00000000 A0A02031 FFFFFFFF
ERR 11: 00000000 A0A02031 FFFFFFFF
ERR 12: 00000000 A0A02031 FFFFFFFF
ERR 13: 00000000 A0022110 FFFFFFFF
ERR 14: 00000000 A0A02031 FFFFFFFF
ERR 15: 00000000 A0A02031 FFFFFFFF
ERR 16: 00000000 A0022110 FFFFFFFF
ERR 17: 00000000 A0A02031 FFFFFFFF
ERR 18: 00000000 A0022110 FFFFFFFF
ERR 19: 00000000 A0A02031 FFFFFFFF
===================================

presuming my reball was a fail I saw 2031 error and 2110 persist through. 2031 specifically said possibly dioades issue on RSX which i figured meant a dead RSX (possible or maybe i screwed up the reball and killed it) either way, i proceeded thinking maybe if I replace the RSX it might change the error codes. I removed the RSX and got the following error codes wihtout turning on the console resulting in YLOD :

===================================
ERR 00: 00000000 A0A02031 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0022110 FFFFFFFF
ERR 03: 00000000 A0A02031 FFFFFFFF
ERR 04: 00000000 A0A02031 FFFFFFFF
ERR 05: 00000000 A0A02031 FFFFFFFF
ERR 06: 00000000 A0022110 FFFFFFFF
ERR 07: 00000000 A0A02031 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0A02031 FFFFFFFF
ERR 10: 00000000 A0022110 FFFFFFFF
ERR 11: 00000000 A0A02031 FFFFFFFF
ERR 12: 00000000 A0022110 FFFFFFFF
ERR 13: 00000000 A0A02031 FFFFFFFF
ERR 14: 00000000 A0A02031 FFFFFFFF
ERR 15: 00000000 A0A02031 FFFFFFFF
ERR 16: 00000000 A0022110 FFFFFFFF
ERR 17: 00000000 A0A02031 FFFFFFFF
ERR 18: 00000000 A0A02031 FFFFFFFF
ERR 19: 00000000 A0022110 FFFFFFFF
===================================

then I figured, let me turn it on, get the YLOD without an RSX on the PCB. I got the ylod, turned off from the rear switch, turned back on, and dumped the codes...resulting in this.

===================================
ERR 00: 00000000 A0A02031 FFFFFFFF
ERR 01: 00000000 A0022110 FFFFFFFF
ERR 02: 00000000 A0A02031 FFFFFFFF
ERR 03: 00000000 A0A02031 FFFFFFFF
ERR 04: 00000000 A0022110 FFFFFFFF
ERR 05: 00000000 A0A02031 FFFFFFFF
ERR 06: 00000000 A0A02031 FFFFFFFF
ERR 07: 00000000 A0A02031 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0A02031 FFFFFFFF
ERR 10: 00000000 A0A02031 FFFFFFFF
ERR 11: 00000000 A0A02031 FFFFFFFF
ERR 12: 00000000 A0022110 FFFFFFFF
ERR 13: 00000000 A0A02031 FFFFFFFF
ERR 14: 00000000 A0022110 FFFFFFFF
ERR 15: 00000000 A0A02031 FFFFFFFF
ERR 16: 00000000 A0A02031 FFFFFFFF
ERR 17: 00000000 A0A02031 FFFFFFFF
ERR 18: 00000000 A0022110 FFFFFFFF
ERR 19: 00000000 A0A02031 FFFFFFFF
===================================

i figured that now I should rebal the rsx. I had another rsx (which might be dead but i figured i try it anyway, its missing a resistor). I rebaled it onto the PCB, turned it on, got YLOD, turned off the power using switch, back on, had a steady red light, and dumped error codes using GUI. got the following:

===================================
ERR 00: 00000000 A0022110 FFFFFFFF
ERR 01: 00000000 A0022110 FFFFFFFF
ERR 02: 00000000 A0022110 FFFFFFFF
ERR 03: 00000000 A0022110 FFFFFFFF
ERR 04: 00000000 A0022110 FFFFFFFF
ERR 05: 00000000 A0022110 FFFFFFFF
ERR 06: 00000000 A0022110 FFFFFFFF
ERR 07: 00000000 A0022110 FFFFFFFF
ERR 08: 00000000 A0022110 FFFFFFFF
ERR 09: 00000000 A0022110 FFFFFFFF
ERR 10: 00000000 A0A02031 FFFFFFFF
ERR 11: 00000000 A0022110 FFFFFFFF
ERR 12: 00000000 A0A02031 FFFFFFFF
ERR 13: 00000000 A0A02031 FFFFFFFF
ERR 14: 00000000 A0A02031 FFFFFFFF
ERR 15: 00000000 A0022110 FFFFFFFF
ERR 16: 00000000 A0A02031 FFFFFFFF
ERR 17: 00000000 A0022110 FFFFFFFF
ERR 18: 00000000 A0A02031 FFFFFFFF
ERR 19: 00000000 A0A02031 FFFFFFFF
===================================

so...it looks like either the RSX has nothing to do with this, or maybe its dead has everything to do without unless i get a for sure working RSX and try. Or it could be I screwed up the bridging with the Necs etc. At this point i'm trying to narrow down the error codes and if related to RSX specifically. I have an additional DIA-001 untoched with Ylod with the following dump:
===================================
ERR 00: 00000000 A0403034 2641F959
ERR 01: 00000000 A0404322 2641F959
ERR 02: 00000000 A0403034 2641F92B
ERR 03: 00000000 A0404322 2641F92B
ERR 04: 00000000 A0403034 22920A9F
ERR 05: 00000000 A0404322 22920A9F
ERR 06: 00000000 A0403034 1CB46132
ERR 07: 00000000 A0404322 1CB46132
ERR 08: 00000000 A0403034 1CB46124
ERR 09: 00000000 A0404322 1CB46123
ERR 10: 00000000 A0403034 1CB45F18
ERR 11: 00000000 A0404322 1CB45F18
ERR 12: 00000000 A0403034 1B6C438D
ERR 13: 00000000 A0404322 1B6C438D
ERR 14: 00000000 A0403034 1B683B33
ERR 15: 00000000 A0404322 1B683B33
ERR 16: 00000000 A0403034 1B62F16D
ERR 17: 00000000 A0404322 1B62F16D
ERR 18: 00000000 A0403034 1B5DC82E
ERR 19: 00000000 A0404322 1B5DC82E

Given its straight YLOD and untouched, i figure it RSX related (3034/4322) for sure. I have a feeling if I do a proper reflow it will come to life. I'm contemplating if I should reflow, see if RSX is working, and then attempt a full blown reball and see if I'm succefful which would confirm 3034 /4322 to be RSX related (given i dont kill the chip). I think that's my next move. What are your thoughts? and what do you think about my original DIA with with the 2031/2110 error. Any feedback would be appreciated. I'm just hoping to help narrow the errors down.





marciolsf said:
Assuming you already connected to the syscon and into internal mode, the command "bringup" will immediately boot the ps3 and start outputting the boot log.

To get previous boot error codes, simply type "errorlog". This will only output the codes, though, not the full log.

I'm pretty sure the documentation in the github page has a full list of commands....
Click to expand...
 
Just a quick question. What success rate do you have if you try to fix only by completing reball on slim boards untouched? If you feel confident with your method, those errors should be very similar. Slims are easy to reball then phat models. This diagnostic tool is more likely to be sure that after delid and new thermal won't sort 3034/4322(21)or anything related to cpu/gpu.
Before this 2015 started to reball and delid cpu/gpu slims and all fixed. When they fail is for sure my problem and didn't pay attention to something. This diagnostic tool helped me to avoid all measurements on motherboard.
If boards are untouched should be easy fix on any phat/slim by now.
If you don't feel confident with reball, test more slims, then take time to test phats.
By delid I mean both gpu and cpu, after reball don't start any ps3 with old thermal paste under ihs. Up to 3000 even rsx must be delided when is out of board. On most cpu with grey silicone can be delided. White silicone in 2500 models can not be delided.
 
Last edited:
Been lurking around this thread for a while.

Recently bought YLOD PS3 CECHC just for fun.

This are errors I'm getting:

[SSM]Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404422
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.

What should I do now? Or it's reball and pray it works case.
 
You must log in or register to reply here.

Similar threads

Back
Top