PS3 CECH-C02 (BC) 2110 Error

[TwitTheNit]

I recently got a Backwards Compatible (CECH-C02) Playstation 3 that is not in the best condition. I have opened it and checked the syscon log, and i am getting error code 2110. Looking at the syscon errors on psdev wiki it seems to be a fuse of some sort has blown, and/or a general motherboard short/fault.

I would like to know if there are any specific components that could be causing this error and also just wanted to post the syscon logs here.

ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xa0022110, clock:0xffffffff
ofst[112]:err_code:0xa0022110, clock:0xffffffff
ofst[116]:err_code:0xa0022110, clock:0xffffffff
ofst[120]:err_code:0xa0022110, clock:0xffffffff
ofst[124]:err_code:0xa0022110, clock:0xffffffff
ofst[  0]:err_code:0xa0022110, clock:0xffffffff
ofst[  4]:err_code:0xa0022110, clock:0xffffffff
ofst[  8]:err_code:0xa0022110, clock:0xffffffff
ofst[ 12]:err_code:0xa0022110, clock:0xffffffff
ofst[ 16]:err_code:0xa0022110, clock:0xffffffff
ofst[ 20]:err_code:0xa0022110, clock:0xffffffff
ofst[ 24]:err_code:0xa0022110, clock:0xffffffff
ofst[ 28]:err_code:0xa0022110, clock:0xffffffff
ofst[ 32]:err_code:0xa0022110, clock:0xffffffff
ofst[ 36]:err_code:0xa0022110, clock:0xffffffff
ofst[ 40]:err_code:0xa0022110, clock:0xffffffff
ofst[ 44]:err_code:0xa0022110, clock:0xffffffff
ofst[ 48]:err_code:0xa0022110, clock:0xffffffff
ofst[ 52]:err_code:0xa0022110, clock:0xffffffff
ofst[ 56]:err_code:0xa0022110, clock:0xffffffff
ofst[ 60]:err_code:0xa0022110, clock:0xffffffff
ofst[ 64]:err_code:0xa0022110, clock:0xffffffff
ofst[ 68]:err_code:0xa0022110, clock:0xffffffff
ofst[ 72]:err_code:0xa0022110, clock:0xffffffff
ofst[ 76]:err_code:0xa0022110, clock:0xffffffff
ofst[ 80]:err_code:0xa0022110, clock:0xffffffff
ofst[ 84]:err_code:0xa0022110, clock:0xffffffff
ofst[ 88]:err_code:0xa0022110, clock:0xffffffff
ofst[ 92]:err_code:0xa0022110, clock:0xffffffff
ofst[ 96]:err_code:0xa0022110, clock:0xffffffff
ofst[100]:err_code:0xa0022110, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$

becount
Bringup : 1420 times
Shutdown: 852 times
Power-on: 129day 15hour 23min 12sec
[mullion]$
Press Ctrl+C to exit
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
Press Ctrl+C to exit
>$ shutdown
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0022110
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$ 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.
Press Ctrl+C to exit
>$

[/CODE]

 

[pstreecco]

One user reported a failed capacitor was causing the short, but other than that I'm afraid you'll have to figure out yourself what's broken.
Luckily you can find service manuals for CECHC consoles, so after confirming the short you can use that to check what's connected to the line and do a visual inspection. If that yields nothing you could try voltage injection to find the components that heat up (might require a thermal camera).
Since the rail normally runs at 5V it should be safe to inject a couple volts capped at low current with a bench power supply, but. I'm no technician so don't just take my word for it.

 

[TwitTheNit]

Sorry, was going to update this but never got around to it. - I did end up fixing the issue, removed two capacitors on the 5v line (C6019 and C6020) and when testing with a multimeter their capacitance was fluctuating a lot. (Anywhere from 0 to 60uf when they are supposed to be 22uf). I replaced them with capacitors from a K-Model motherboard and replaced the fuse with a fuse from a 2000A (This is because I already used a fuse off the K model, but it blew again.) It now boots but overheats after about 15-25 seconds - So i have ordered a delid tool, I will follow up with whether this works or not when I delid.

Delided it - Replaced thermal paste. It still overheats, though i can not tell if it is a bad thermal monitor or if it is actually overheating. As when left alone for a while it will continue to stay on for ~20-30 seconds, but turning it on immediately after it turns itself off makes it overheat instantly.