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

Ganjo · Jul 2, 2024

XCieroX said:
Hey,

I'm new to the forum but I have a CECHA01 that I recently acquired. The system powers on with red and green lights for maybe 2 or seconds before powering off and blinking red. The systems was filthy with brown fuzz that indicates overheat potential. No signs of drop damage and tamper seal was intact. Below is the error codes I was able to pull up from following RIP Felix's video.

RSX needs rework or replacement

Ganjo · Jul 2, 2024

Hunter926 said:
Hi guys, I have a CECHA01 model that started giving me a GLOD. It will turn on and run, but no image and no power to the USB ports at all.
It will go into safe mode (or sound like it), but still no video or USB power.
I should note that I had another GLOD console, that would supply power to the USB ports and that turned out to be a bad HDD.
This is not the same.
I've read the syscon logs and included them below.
Additionally, due to the syscon logs showing lots of 1001 errors, i've replaced 1 of the Cell's Tokin's with RIP Felix's Tantalizer. There was no change in behavior afterwards.
I'm unsure of the ps3 boot process, and as such, am not sure if the USB ports receiving no power is normal or not for GLOD. Could there be a bad component in charge of supplying power to the usb ports/hdmi out? or is it likely the cell/caps?

Just looking for a little guidance as i'm not sure if i should continue replacing Tokins for the cell, or look for something else.

As a side question, is there any need to swap the syscon back to External mode after repairing? Or will it function normally in Internal mode?
Thanks.

Error Log (Oldest to Newest)

Its likely all the 1001 errors are from shutting it off because of the GLOD issue. Since you have no controller sync its likely a bad RSX. Did you try regular AV connection? Could have more than one issue but its almost always the RSX. I wouldnt bother replacing anymore TOKINs at this time.

Raidmax · Jul 3, 2024

[deleted, don't do the same stupidity i did]

DeadEnd · Jul 6, 2024

XCieroX said:

Hey,

I'm new to the forum but I have a CECHA01 that I recently acquired. The system powers on with red and green lights for maybe 2 or seconds before powering off and blinking red. The systems was filthy with brown fuzz that indicates overheat potential. No signs of drop damage and tamper seal was intact. Below is the error codes I was able to pull up from following RIP Felix's video.

Code:

>$ errlog
errlog
ofst[ 84]:err_code:0xffffffff, clock:0x1be1a0f7  2014/10/28 00:33:59
ofst[ 88]:err_code:0xa0403034, clock:0x1be1a331  2014/10/28 00:43:29
ofst[ 92]:err_code:0xa0403034, clock:0x1be1a346  2014/10/28 00:43:50
ofst[ 96]:err_code:0xa0403034, clock:0x1be1a352  2014/10/28 00:44:02
ofst[100]:err_code:0xa0403034, clock:0x1be1a35b  2014/10/28 00:44:11
ofst[104]:err_code:0xa0801001, clock:0x1be1a388  2014/10/28 00:44:56
ofst[108]:err_code:0xa0403034, clock:0x1be1a3ae  2014/10/28 00:45:34
ofst[112]:err_code:0xa0403034, clock:0x1be1a743  2014/10/28 01:00:51
ofst[116]:err_code:0xa0403034, clock:0x1be1a763  2014/10/28 01:01:23
ofst[120]:err_code:0xa0403034, clock:0x1be1a76d  2014/10/28 01:01:33
ofst[124]:err_code:0xa0403034, clock:0x1be1a786  2014/10/28 01:01:58
ofst[  0]:err_code:0xa0403034, clock:0x1be1a78c  2014/10/28 01:02:04
ofst[  4]:err_code:0xa0403034, clock:0x1be1a833  2014/10/28 01:04:51
ofst[  8]:err_code:0xa0801001, clock:0x1be1c695  2014/10/28 03:14:29
ofst[ 12]:err_code:0xa0403034, clock:0x1be1c698  2014/10/28 03:14:32
ofst[ 16]:err_code:0xa0403034, clock:0x1be1c69d  2014/10/28 03:14:37
ofst[ 20]:err_code:0xa0403034, clock:0x1be1c6a5  2014/10/28 03:14:45
ofst[ 24]:err_code:0xa0403034, clock:0x1e5e826c  2016/02/23 02:37:32
ofst[ 28]:err_code:0xa0403034, clock:0x1e5e8272  2016/02/23 02:37:38
ofst[ 32]:err_code:0xa0403034, clock:0x1e5e827f  2016/02/23 02:37:51
ofst[ 36]:err_code:0xa0403034, clock:0x1e5e8292  2016/02/23 02:38:10
ofst[ 40]:err_code:0xa0403034, clock:0x1e5e82a2  2016/02/23 02:38:26
ofst[ 44]:err_code:0xa0403034, clock:0x1e5e82d8  2016/02/23 02:39:20
ofst[ 48]:err_code:0xa0403034, clock:0x1e5e82e0  2016/02/23 02:39:28
ofst[ 52]:err_code:0xa0403034, clock:0x1e5e82e6  2016/02/23 02:39:34
ofst[ 56]:err_code:0xa0403034, clock:0x2c1e3072  2023/06/15 20:26:26
ofst[ 60]:err_code:0xa0403034, clock:0x2c1e30a1  2023/06/15 20:27:13
ofst[ 64]:err_code:0xa0902120, clock:0x2c1e30a1  2023/06/15 20:27:13
ofst[ 68]:err_code:0xa0403034, clock:0x2c1e30b5  2023/06/15 20:27:33
ofst[ 72]:err_code:0xa0902120, clock:0x2c1e30b5  2023/06/15 20:27:33
ofst[ 76]:err_code:0xa0403034, clock:0x2e08bebc  2024/06/21 22:44:12
ofst[ 80]:err_code:0xa0403034, clock:0x2e08bed5  2024/06/21 22:44:37
[mullion]$

Code:

>$ becount
becount
Bringup : 1566 times
Shutdown: 1228 times
Power-on: 159day 09hour 33min 18sec
[mullion]$

Code:

>$ 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:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[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
bringup
Do nothing. (FatalDown State)
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ shutdown
shutdown
Do nothing. (PowerOff State)
Press Ctrl+C to exit
>$ shutdown
[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.
shutdown
Do nothing. (UpBusy State)
[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
[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
Press Ctrl+C to exit
>$ bringup
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
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
Press Ctrl+C to exit
>$ bringup
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[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)
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
bringup
Do nothing. (UpBusy State)
[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
[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

I'm looking to see what the consensus is on what the fix would be.

Thank you!

Does this have 90nm in there? It looks like rsx cannot be ID'd. Typical behavior when bittraining is messed when swapping with 40nm or if VDDR is bad. Not so typical for 90 chips however. Unless badly damaged? Also check that checksum is ok.

90s usually fail at a different rambus register step. FlexIO ID is the very first step in the sequence, so usually there's a serious reason why it cannot initialise. But I suppose anything is possible...

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

Josh Star · Jul 6, 2024

Code:

errlog
ofst[ 72]:err_code:0xffffffff, clock:0x0b545bf8  2006/01/08 23:25:44
ofst[ 76]:err_code:0xa0902031, clock:0x0b545bf8  2006/01/08 23:25:44
ofst[ 80]:err_code:0xa0082031, clock:0x0b545bfe  2006/01/08 23:25:50
ofst[ 84]:err_code:0xa0902031, clock:0x0b545bfe  2006/01/08 23:25:50
ofst[ 88]:err_code:0xa0082031, clock:0x0b545c09  2006/01/08 23:26:01
ofst[ 92]:err_code:0xa0902031, clock:0x0b545c09  2006/01/08 23:26:01
ofst[ 96]:err_code:0xa0a02030, clock:0x0b5462bf  2006/01/08 23:54:39
ofst[100]:err_code:0xa0a02030, clock:0x0b54706f  2006/01/09 00:53:03
ofst[104]:err_code:0xa0a02030, clock:0x0b54706f  2006/01/09 00:53:03
ofst[108]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[112]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[116]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[120]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[124]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[  0]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[  4]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[  8]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[ 12]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[ 16]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[ 20]:err_code:0xa0a02031, clock:0x0b547070  2006/01/09 00:53:04
ofst[ 24]:err_code:0xa0902031, clock:0x0b547070  2006/01/09 00:53:04
ofst[ 28]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 32]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 36]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 40]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 44]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 48]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 52]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 56]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 60]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 64]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
ofst[ 68]:err_code:0xa0a02031, clock:0x0b547133  2006/01/09 00:56:19
[mullion]$
Press Ctrl+C to exit
>$

Press Ctrl+C to exit
>$ becount
becount
Bringup : 1667 times
Shutdown: 1241 times
Power-on: 27day 04hour 13min 41sec
[mullion]$
Press Ctrl+C to exit
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0082131
Press Ctrl+C to exit
>$

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.
[SSM] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0082031
[ERROR]: 0xa0902031
Press
>$ shutdown
[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
>$

This is a CECHKO3 DIA-002 board, I got it from scrap, first it was showing YLOD, I have replaced the NEC TOKINS at the beginning and the console was fine, I played about 7 to 8 hours continuously, then kept untouched for 1 week, and when I turned it back on yesterday, it shows YLOD, the duration of the green light staying solid is different in every startup, sometimes 1 second, sometimes 3, sometimes it stays green for 7 to 10 seconds, so I thought it would output something to TV, so I connected the console to TV, but nothing happened, but I noticed that, after connecting it to the TV, the YLOD duration reduced to 1 to 2 seconds and never went beyond 2 seconds. then I hooked up SYSCON and I only got 2030 and 2031 error codes, it has only 27 days of power on state. The 2030 and 2031 errors are CELL and RSX thermal related issues. the thermal pastes are new, still has 2030 and 2031 errors, 2031 is shown more compared to 2030, I did a bit of research and found it may be because of the dead diodes in RSX (not sure). I wonder why the dates shows 2006 while this model was released in 2008. if possible someone please explain the errors and the possible fix for this error, also what's the use of this 'bringup' and 'shutdown' commands.

Is the issue related with the temperature sensor circuit ? That T1B and T1L named IC near RSX and CELL which has a triangle logo in it ? if anyone know the values of the resistors in that circuit please give a clue, also is there any way to get the datasheet for those IC's ?

Also, there is one error ( 'A0082031' ) with step number '08', in the wiki, I only saw the step numbers like, A0,80,90. what could be that error ?

Josh Star · Jul 6, 2024

Den4515 said:
I solve A0A02031 error by soldering transistor 2N3906 to T1L chip (see datasheet to ADT7461A there displayed about the way to make external 'thermal' transistor) It will help, if the problem only in dead RSX thermal diod. But as usual the problem is bigger than that

will this fix the errors like:
A0902031, A0802031, A0082031 and A0A02030 I'm having the DIA-002 board
only need to add a transistor ? nothing else to do ? just make the transistor hang their ?
is this a fixing method or bypassing the sensor ?

DeadEnd · Jul 6, 2024

Josh Star said:
Code:

errlog ofst[ 72]:err_code:0xffffffff, clock:0x0b545bf8 2006/01/08 23:25:44 ofst[ 76]:err_code:0xa0902031, clock:0x0b545bf8 2006/01/08 23:25:44 ofst[ 80]:err_code:0xa0082031, clock:0x0b545bfe 2006/01/08 23:25:50 ofst[ 84]:err_code:0xa0902031, clock:0x0b545bfe 2006/01/08 23:25:50 ofst[ 88]:err_code:0xa0082031, clock:0x0b545c09 2006/01/08 23:26:01 ofst[ 92]:err_code:0xa0902031, clock:0x0b545c09 2006/01/08 23:26:01 ofst[ 96]:err_code:0xa0a02030, clock:0x0b5462bf 2006/01/08 23:54:39 ofst[100]:err_code:0xa0a02030, clock:0x0b54706f 2006/01/09 00:53:03 ofst[104]:err_code:0xa0a02030, clock:0x0b54706f 2006/01/09 00:53:03 ofst[108]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[112]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[116]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[120]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[124]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 0]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 4]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 8]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 12]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 16]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 20]:err_code:0xa0a02031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 24]:err_code:0xa0902031, clock:0x0b547070 2006/01/09 00:53:04 ofst[ 28]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 32]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 36]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 40]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 44]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 48]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 52]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 56]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 60]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 64]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 ofst[ 68]:err_code:0xa0a02031, clock:0x0b547133 2006/01/09 00:56:19 [mullion]$ Press Ctrl+C to exit >$ Press Ctrl+C to exit >$ becount becount Bringup : 1667 times Shutdown: 1241 times Power-on: 27day 04hour 13min 41sec [mullion]$ Press Ctrl+C to exit >$ bringup bringup [SSM] state: 0000 -> 0101 Bringup Mode #0 (0xFF) [SSM] ssmCb_OnStartingBePowOn() called. [SSM] First Boot. [SSM] Bringup mode : syspm_stat=00000000/00000000 [POWSEQ] PowerSeq_Setup called. [SSM] state: 0101 -> 0301 [SSM] PowSeq Fail : Detected ! [SSM] state: 0301 -> 0700 [POWSEQ] AV Backend Letup [SSM] Shutdown mode : syspm_stat=00000000/00000000 [ERROR]: 0xa0082131 Press Ctrl+C to exit >$ 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. [SSM] state: 0101 -> 0301 [SSM] PowSeq Fail : Detected ! [SSM] state: 0301 -> 0700 [POWSEQ] AV Backend Letup [SSM] Shutdown mode : syspm_stat=00000000/00000000 [ERROR]: 0xa0082031 [ERROR]: 0xa0902031 Press >$ shutdown [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 >$

This is a CECHKO3 DIA-002 board, I got it from scrap, first it was showing YLOD, I have replaced the NEC TOKINS at the beginning and the console was fine, I played about 7 to 8 hours continuously, then kept untouched for 1 week, and when I turned it back on yesterday, it shows YLOD, the duration of the green light staying solid is different in every startup, sometimes 1 second, sometimes 3, sometimes it stays green for 7 to 10 seconds, so I thought it would output something to TV, so I connected the console to TV, but nothing happened, but I noticed that, after connecting it to the TV, the YLOD duration reduced to 1 to 2 seconds and never went beyond 2 seconds. then I hooked up SYSCON and I only got 2030 and 2031 error codes, it has only 27 days of power on state. The 2030 and 2031 errors are CELL and RSX thermal related issues. the thermal pastes are new, still has 2030 and 2031 errors, 2031 is shown more compared to 2030, I did a bit of research and found it may be because of the dead diodes in RSX (not sure). I wonder why the dates shows 2006 while this model was released in 2008. if possible someone please explain the errors and the possible fix for this error, also what's the use of this 'bringup' and 'shutdown' commands.

Is the issue related with the temperature sensor circuit ? That T1B and T1L named IC near RSX and CELL which has a triangle logo in it ? if anyone know the values of the resistors in that circuit please give a clue, also is there any way to get the datasheet for those IC's ?

Also, there is one error ( 'A0082031' ) with step number '08', in the wiki, I only saw the step numbers like, A0,80,90. what could be that error ?

Syscon dates are often inaccurate. Not sure if it's related to the battery somehow. Most likely Rsx TC monitor fault. Might as well replace the one on Cell too. I wouldn't get too hung up on steps, the fault can get registered at different steps if the sensor fails at a slightly different stage. Easiest is to get them from a spare board and see if it fixes it. At least cok boards use OnSemi ADT7461A. Not sure if they stayed the same on DIAs. They could have. Here is some info https://www.psdevwiki.com/ps3/Thermal#RSX_(RSX_Primary)

Josh Star · Jul 6, 2024

DeadEnd said:
Syscon dates are often inaccurate. Not sure if it's related to the battery somehow. Most likely Rsx TC monitor fault. Might as well replace the one on Cell too. I wouldn't get too hung up on steps, the fault can get registered at different steps if the sensor fails at a slightly different stage. Easiest is to get them from a spare board and see if it fixes it. At least cok boards use OnSemi ADT7461A. Not sure if they stayed the same on DIAs.

is it possible to fix this error by soldering a 2N3906 transistor to the 'D+' and 'D-' of ADT7461A

Josh Star · Jul 6, 2024

Den4515 said:
I solve A0A02031 error by soldering transistor 2N3906 to T1L chip (see datasheet to ADT7461A there displayed about the way to make external 'thermal' transistor) It will help, if the problem only in dead RSX thermal diod. But as usual the problem is bigger than that

but isn't there a 100ohm resistor and 0.001μF 50V from 'D+' and 'D-'pin of the temp monitor to the temperature diodes ?
so, when adding 2N3906 transistor, isn't that resistor and capacitor necessary ?

Josh Star · Jul 7, 2024

Replacement of Temperature sensors in RSX and CELL:

I have a CECHKO3 DIA-002 board, the SYSCON gives me 2031 and 2030 errors(2031 is shown more). In GITHUB repo of SYSCON, it says 2031 error is because of dead diodes(actually thermal sensors) in RSX (not sure).

In PSX-PLACE, I found that we can actually use an external temp sensor by soldering a 2N3906 transistor to the D+ and D- of the temp monitor which is located near RSX and CELL (ADT7461). Connect the emitter to D+ and collector-base junction to D-. I don't know how will this setup measure the temp of RSX and CELL as the sensor is external.

In the datasheet of 'ADT7461' it says we can use 2N3906 transistor.

Also, is it necessary to use 2N3906 itself ? actually we can use an equivalent transistor like BC557(widely available). I've seen this BC557 in computer UPS for measuring the switching MOSFET temp.

Also, How can I confirm that the error is with the temperature sensor or the temperature monitor IC (ADT7461) ?

I found this image in PSX-PLACE https://ibb.co/rttKC5S

RIP-Felix · Jul 7, 2024

sin89rus said:
any way to fix checksum on SW syscon?

Address 7FE on Sherwood. It doesn't have more than one address it could be, but rather one address for the entire thing. So run eepcsum then `w 7fe` and the value it returns (byte swapped OFC).

RIP-Felix · Jul 7, 2024

Raidmax said:
I am also going with @Ganjo 's diagnostic here. I have a slim 2503A that used to do this as well. (which is surprising, for a CXD5300CGB 40nm RSX - you'd think the newer RSXs were somewhat safe from GLODs...right?)

Since mine was a junk find console, I just stuck a 5 eurocent penny between the RSX IHS and the heatsink it's supposed to come in contact with, applied a bit of MX6 paste, and called it a day - given how horribly nasty the slim I have was inside, I'd care less if it dies - at least it'll be a good donor for another 2503 that is missing its HDMI port.

Please...just no.

It's not even a good idea to mention doing that, because it can be taken the wrong way. Perpetuating this HORRIBLE idea. It doesn't matter that it was garbage. Someone is going to read that and thing "it might help" and be so desperate they'll think "I have nothing to lose." Then the die cracks and the console is FUBAR.

Raidmax · Jul 7, 2024

At this point it's a bit too late, the board is already gone. And the one it was supposed to give its HDMI port to as well (though not for the same reasons)

Raidmax · Jul 8, 2024

Dumped the syscon off my latest 2504 I had just refurbed.
I used the dump function from the CFW tools, since bgtoolset is down at this moment on the PS3 browser end, and I'll have to wait quite some time until I can get a FTDI.

Firmware Version: 4.91 (build 50754)
Platform ID: CokJ20
Product Code: 00 85
Product Sub Code: 00 0B
Hardware Config: 000000000A03BC3C
Syscon Firmware Version: 08C2.0000000000000000 (EEPROM: 0000000000000000)

Bringup Count: 2774, Shutdown Count: 2743
Runtime: 259 Days, 5 Hours, 12 Minutes, 24 Seconds

Error Log
01: A0802130 Tue Jan 27 16:57:53 2015
02: A0802031 Tue Jan 27 16:57:49 2015
03: A0802131 Sun May 18 12:02:28 2014
04: A0802130 Mon Dec 2 16:55:02 2013
05: A0802030 Mon Dec 2 16:55:01 2013
06: A0802131 Mon Dec 2 16:54:58 2013
07: A0802130 Mon Dec 2 16:54:54 2013
08: A0802131 Mon Dec 2 16:54:52 2013
09: A0802130 Mon Dec 2 16:54:49 2013
10: A0802130 Mon Dec 2 16:54:44 2013
11: A0802131 Mon Dec 2 16:54:41 2013
12: A0802030 Mon Dec 2 16:54:38 2013
13: A0802131 Mon Dec 2 16:54:32 2013
14: A0802130 Mon Dec 2 16:54:29 2013
15: A0802031 Mon Dec 2 16:54:26 2013
16: A0802130 Mon Dec 2 16:54:24 2013
17: A0802131 Mon Dec 2 16:54:22 2013
18: A0802030 Sun Dec 1 22:26:33 2013
19: A0802030 Sun Dec 1 22:26:31 2013
20: A0802031 Sun Dec 1 22:26:28 2013
21: A0802131 Sun Dec 1 22:26:26 2013
22: A0802131 Sun Dec 1 22:26:24 2013
23: A0802130 Sun Dec 1 22:26:22 2013
24: A0802131 Sun Dec 1 22:26:19 2013
25: A0802031 Sun Dec 1 22:26:16 2013
26: A0802131 Sun Dec 1 22:26:14 2013
27: A0802131 Sun Dec 1 22:26:09 2013
28: A0802130 Sun Dec 1 22:26:06 2013
29: A0802130 Sun Dec 1 22:26:03 2013
30: A0802130 Sun Dec 1 22:26:00 2013
31: A0802031 Sun Dec 1 22:25:57 2013
32: FFFFFFFF Sat Jan 1 01:59:59 2000

Josh Star · Jul 9, 2024

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]: 0xa0082031
[ERROR]: 0xa0902031

what's step number 08 ?

Josh Star · Jul 9, 2024

Raidmax said:
Dumped the syscon off my latest 2504 I had just refurbed.
I used the dump function from the CFW tools, since bgtoolset is down at this moment on the PS3 browser end, and I'll have to wait quite some time until I can get a FTDI.

Firmware Version: 4.91 (build 50754)
Platform ID: CokJ20
Product Code: 00 85
Product Sub Code: 00 0B
Hardware Config: 000000000A03BC3C
Syscon Firmware Version: 08C2.0000000000000000 (EEPROM: 0000000000000000)

Bringup Count: 2774, Shutdown Count: 2743
Runtime: 259 Days, 5 Hours, 12 Minutes, 24 Seconds

Error Log
01: A0802130 Tue Jan 27 16:57:53 2015
02: A0802031 Tue Jan 27 16:57:49 2015
03: A0802131 Sun May 18 12:02:28 2014
04: A0802130 Mon Dec 2 16:55:02 2013
05: A0802030 Mon Dec 2 16:55:01 2013
06: A0802131 Mon Dec 2 16:54:58 2013
07: A0802130 Mon Dec 2 16:54:54 2013
08: A0802131 Mon Dec 2 16:54:52 2013
09: A0802130 Mon Dec 2 16:54:49 2013
10: A0802130 Mon Dec 2 16:54:44 2013
11: A0802131 Mon Dec 2 16:54:41 2013
12: A0802030 Mon Dec 2 16:54:38 2013
13: A0802131 Mon Dec 2 16:54:32 2013
14: A0802130 Mon Dec 2 16:54:29 2013
15: A0802031 Mon Dec 2 16:54:26 2013
16: A0802130 Mon Dec 2 16:54:24 2013
17: A0802131 Mon Dec 2 16:54:22 2013
18: A0802030 Sun Dec 1 22:26:33 2013
19: A0802030 Sun Dec 1 22:26:31 2013
20: A0802031 Sun Dec 1 22:26:28 2013
21: A0802131 Sun Dec 1 22:26:26 2013
22: A0802131 Sun Dec 1 22:26:24 2013
23: A0802130 Sun Dec 1 22:26:22 2013
24: A0802131 Sun Dec 1 22:26:19 2013
25: A0802031 Sun Dec 1 22:26:16 2013
26: A0802131 Sun Dec 1 22:26:14 2013
27: A0802131 Sun Dec 1 22:26:09 2013
28: A0802130 Sun Dec 1 22:26:06 2013
29: A0802130 Sun Dec 1 22:26:03 2013
30: A0802130 Sun Dec 1 22:26:00 2013
31: A0802031 Sun Dec 1 22:25:57 2013
32: FFFFFFFF Sat Jan 1 01:59:59 2000

whats the difference between 2031 and 2131, they both are rsx thermal monitor issues right ?

Raidmax · Jul 9, 2024

No idea as to why 2031 and 2131 show up there - the fan seems to work normally, webMAN even controls it without issue using my own thermal settings of 70*C max and 31% minimum fan speed, something that stuck with me ever since I've bought my CECHB00 (which ended up being expensive as all hell, despite not being a Frankie lol)

Josh Star · Jul 9, 2024

Raidmax said:
No idea as to why 2031 and 2131 show up there - the fan seems to work normally, webMAN even controls it without issue using my own thermal settings of 70*C max and 31% minimum fan speed, something that stuck with me ever since I've bought my CECHB00 (which ended up being expensive as all hell, despite not being a Frankie lol)

Wait what, console boots up with 2031 error?
Currently I'm having the same errors,(only 2031) but it just shows ylod and turns off.

Raidmax · Jul 9, 2024

Josh Star said:
Wait what, console boots up with 2031 error?
Currently I'm having the same errors,(only 2031) but it just shows ylod and turns off.

Yes, so far I have not noticed anything out of the ordinary about it. Even the SYSCON log was dumped through the CFW menus, seeing that bgtoolset doesn't work at the moment. I'm hoping to get a FTDI adapter soon, but until then, if a console powers up and can stay long enough to either get CFW'd or to run bgtoolset (hopefully whenever it'll come back up), I prefer to dump the SYSCON log through the CFW tools or photograph it from bgtoolset (as I used to do until recently).

NE5TA · Jul 9, 2024

Hi Guys, New to the scene. I've got a CECHA12 which I did a SYSCON on with the following log:
ofst[ 4]:err_code:0xffffffff, clock:0x17105ce5 2012/04/05 13:38:45
ofst[ 8]:err_code:0xa0802022, clock:0x17105ce5 2012/04/05 13:38:45
ofst[ 12]:err_code:0xa0802022, clock:0x17105ce5 2012/04/05 13:38:45
ofst[ 16]:err_code:0xa0802022, clock:0x17105ce5 2012/04/05 13:38:45
ofst[ 20]:err_code:0xa0802022, clock:0x17105d13 2012/04/05 13:39:31
ofst[ 24]:err_code:0xa0802022, clock:0x17105d13 2012/04/05 13:39:31
ofst[ 28]:err_code:0xa0802022, clock:0x17105d13 2012/04/05 13:39:31
ofst[ 32]:err_code:0xa0802022, clock:0x17105d13 2012/04/05 13:39:31
ofst[ 36]:err_code:0xa0801701, clock:0x1711b5b8 2012/04/06 14:10:00
ofst[ 40]:err_code:0xa0801601, clock:0x1711b5b8 2012/04/06 14:10:00
ofst[ 44]:err_code:0xa0403034, clock:0x1711b5d0 2012/04/06 14:10:24
ofst[ 48]:err_code:0xa0403034, clock:0x1711b62c 2012/04/06 14:11:56
ofst[ 52]:err_code:0xa0403034, clock:0x1711b715 2012/04/06 14:15:49
ofst[ 56]:err_code:0xa0403034, clock:0x1711b72c 2012/04/06 14:16:12
ofst[ 60]:err_code:0xa0403034, clock:0x1711b734 2012/04/06 14:16:20
ofst[ 64]:err_code:0xa0403034, clock:0x1711b7ee 2012/04/06 14:19:26
ofst[ 68]:err_code:0xa0403034, clock:0x174bf19b 2012/05/20 18:16:59
ofst[ 72]:err_code:0xa0403034, clock:0x17a01977 2012/07/23 14:17:27
ofst[ 76]:err_code:0xa0403034, clock:0x2dc8a28b 2024/05/04 07:38:51
ofst[ 80]:err_code:0xa0403034, clock:0x2dec4e6a 2024/05/31 09:01:30
ofst[ 84]:err_code:0xa0403034, clock:0x2dec4e7d 2024/05/31 09:01:49
ofst[ 88]:err_code:0xa0403034, clock:0x2dec51a4 2024/05/31 09:15:16
ofst[ 92]:err_code:0xa0403034, clock:0x2dec51ab 2024/05/31 09:15:23
ofst[ 96]:err_code:0xa0403034, clock:0x2df080ee 2024/06/03 13:26:06
ofst[100]:err_code:0xa0403034, clock:0x2df08107 2024/06/03 13:26:31
ofst[104]:err_code:0xa0403034, clock:0x2df08117 2024/06/03 13:26:47
ofst[108]:err_code:0xa0403034, clock:0x2df08138 2024/06/03 13:27:20
ofst[112]:err_code:0xa0403034, clock:0x2df34da9 2024/06/05 16:24:09
ofst[116]:err_code:0xa0403034, clock:0x2df34db6 2024/06/05 16:24:22
ofst[120]:err_code:0xa0403034, clock:0x2df34ea5 2024/06/05 16:28:21
ofst[124]:err_code:0xa0403034, clock:0x2df34eef 2024/06/05 16:29:35
ofst[ 0]:err_code:0xa0403034, clock:0x2df3517b 2024/06/05 16:40:27

becount
Bringup : 1761 times
Shutdown: 1575 times
Power-on: 100day 19hour 59min 24sec

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

Going off PSdevwiki: "A0403034 was seen PHAT consoles (VER-001) with a bad south bridge or cold joint underneath it."
Or is it most likely a faulty RSX?

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

Member

Member

Member

Senior Member

Member

Member

Senior Member

Member

Member

Member

Senior Member

Senior Member

Member

Member

Member

Member

Member

Member

Member

Forum Noob

Similar threads