PS3 CECHC PS3 Triple Beeps as soon as power is connected

[axolotso]

Hey everyone

I've been given a CECHC Fat PS3 to look at with some strange issues

I'm not too sure of it's full history, the warranty sticker was in tact so that gives me hope but it could've been tinkered with before I got my hands on it

I've been able to get connected to the SYSCON to try and figure out why it beeps as soon as the power cable is plugged in, I did do the eepcsum check, although it's not in the logs I got out, it's not showing the "sum" line anymore.

I've swapped with a power supply from a CECHA console that did try to turn on but unfortunately died to BGA failure but I'm sure the PSU is at least fine enough to try turn on unlike what this PS3 wants to do

Possibly a bit of info from the SYSCON can help?

>$ AUTH

Auth successful

Press Ctrl+C to exit

>$ errlog

errlog

ofst[116]:err_code:0xffffffff, clock:0x16b8618a  2012/01/29 19:59:06

ofst[120]:err_code:0xa0801001, clock:0x1708c6ff  2012/03/30 19:33:19

ofst[124]:err_code:0xa0801001, clock:0x17234c6d  2012/04/19 22:21:33

ofst[  0]:err_code:0xa0801001, clock:0x1738f855  2012/05/06 08:52:37

ofst[  4]:err_code:0xa0801001, clock:0x173dacf2  2012/05/09 22:32:18

ofst[  8]:err_code:0xa0801001, clock:0x174d86ab  2012/05/21 23:05:15

ofst[ 12]:err_code:0xa0801001, clock:0x17e273df  2012/09/11 22:12:47

ofst[ 16]:err_code:0xa0801004, clock:0x17ecff5a  2012/09/19 22:10:34

ofst[ 20]:err_code:0xa0801001, clock:0x17f323d9  2012/09/24 13:59:53

ofst[ 24]:err_code:0xa0801004, clock:0x17fe14b2  2012/10/02 21:10:10

ofst[ 28]:err_code:0xa0801001, clock:0x18c25273  2013/02/28 17:37:55

ofst[ 32]:err_code:0xa0801001, clock:0x191ecd68  2013/05/09 21:11:04

ofst[ 36]:err_code:0xa0801001, clock:0x19337f35  2013/05/25 13:55:01

ofst[ 40]:err_code:0xa0801001, clock:0x1937c6ce  2013/05/28 19:49:34

ofst[ 44]:err_code:0xa0801001, c

Press Ctrl+C to exit

>$ errlog

lock:0x1939268d  2013/05/29 20:50:21

ofst[ 48]:err_code:0xa0801004, clock:0x1948f335  2013/06/10 20:27:33

ofst[ 52]:err_code:0xa0801004, clock:0x19ae1e08  2013/08/26 14:09:12

ofst[ 56]:err_code:0xa0801001, clock:0x19d3147f  2013/09/23 15:02:23

ofst[ 60]:err_code:0xa0801004, clock:0x19d32467  2013/09/23 16:10:15

ofst[ 64]:err_code:0xa0801001, clock:0x19f6ed42  2013/10/20 19:36:34

ofst[ 68]:err_code:0xa0902120, clock:0x19f6ed42  2013/10/20 19:36:34

ofst[ 72]:err_code:0xa0802022, clock:0x19f6f1e5  2013/10/20 19:56:21

ofst[ 76]:err_code:0xa0802022, clock:0x19f6f274  2013/10/20 19:58:44

ofst[ 80]:err_code:0xa0801001, clock:0x1ae4174c  2014/04/18 17:03:08

ofst[ 84]:err_code:0xa0801001, clock:0x1b28c0ff  2014/06/09 19:01:19

ofst[ 88]:err_code:0xa0801001, clock:0x1b4dc1d0  2014/07/07 20:38:40

ofst[ 92]:err_code:0xa0801004, clock:0x1b4dc29c  2014/07/07 20:42:04

ofst[ 96]:err_code:0xa0801001, clock:0x1b4de93b  2014/07/07 23:26:51

ofst[100]:err_code:0xa0801001, clock:0x1b56922f  2014/07/14 13:05:51

of

Press Ctrl+C to exit

>$ errlog

st[104]:err_code:0xa0801001, clock:0x1b5985f5  2014/07/16 18:50:29

ofst[108]:err_code:0xa0801004, clock:0x240c1406  2019/03/01 16:02:14

ofst[112]:err_code:0xa0801001, clock:0x24155e5f  2019/03/08 17:09:51

[mullion]$ errlog

ofst[116]:err_code:0xffffffff, clock:0x16b8618a  2012/01/29 19:59:06

ofst[120]:err_code:0xa0801001, clock:0x1708c6ff  2012/03/30 19:33:19

ofst[124]:err_code:0xa0801001, clock:0x17234c6d  2012/04/19 22:21:33

ofst[  0]:err_code:0xa0801001, clock:0x1738f855  2012/05/06 08:52:37

ofst[  4]:err_code:0xa0801001, clock:0x173dacf2  2012/05/09 22:32:18

ofst[  8]:err_code:0xa0801001, clock:0x174d86ab  2012/05/21 23:05:15

ofst[ 12]:err_code:0xa0801001, clock:0x17e273df  2012/09/11 22:12:47

ofst[ 16]:err_code:0xa0801004, clock:0x17ecff5a  2012/09/19 22:10:34

ofst[ 20]:err_code:0xa0801001, clock:0x17f323d9  2012/09/24 13:59:53

ofst[ 24]:err_code:0xa0801004, clock:0x17fe14b2  2012/10/02 21:10:10

ofst[ 28]:err_code:0xa0801001, clock:0x18c25273  2013/02/28 17:37:55

ofst[ 32]:err_code:0xa0

Press Ctrl+C to exit



>$ becount

becount

Bringup : 1501 times

Shutdown: 938 times

Power-on: 68day 19hour 53min 51sec

[mullion]$

Press Ctrl+C to exit

>$ bringup

bringup

Do nothing. (FatalOff State)

Press Ctrl+C to exit

>$ powerstate

powerstate

ATA Power          : OFF

PCI Power          : OFF

RSX Power          : OFF

XDR Power          : OFF

Eurus Power        : OFF

SB Power           : OFF

RSX Thermal Sensor : UNAVAILABLE

BE Thermal Sensor  : UNAVAILABLE

[mullion]$

Press Ctrl+C to exit

>$ tmp 0

tmp 0

*** Inaccurate Temperature:0.00(0x0000) ***

[mullion]$

Press Ctrl+C to exit

>$ tmp 1

tmp 1

*** Inaccurate Temperature:0.00(0x0000) ***

[mullion]$

Press Ctrl+C to exit

>$ shutdown

shutdown

[SSM] cannot clear fatal error state because of unrecoverable error.

I'm a bit at a loss of what to do now so really any help is appreciated!!! Thanks!

 

[sagemono]

Try "w 3292 FF"

This disables the checksum validation on boot.

 

[axolotso]

Try "w 3292 FF"

This disables the checksum validation on boot.

That did it! Thanks so much!

Got it up and running enough to blow up F6001, C6019 and C6020 and start throwing 0xa0022110 codes, gotta love these CECHCs

After replacing those from a donor board it's back up and running again, everything else seems fine. Out of curiosity what could've possibly caused checksum validation problems so severe it couldn't even try to power up, as it booted up fine to XMB after disabling validation? I updated after to be sure but it seemed to be fine

 

[sagemono]

> Out of curiosity what could've possibly caused checksum validation problems so severe it couldn't even try to power up, as it booted up fine to XMB after disabling validation?

I'm not sure, I haven't seen this at all on an untampered system. It happens if you update a value in EEPROM without running eepcsum and writing the corrected value. Maybe pulling the plug during the exact time frame a write occurred before the checksum was updated did it?