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

TimeWalker75a said:
Hiya,

A long-time lurker, finally a poster.

I have in me hands a CECHC03 that appears to have had the RSX reballed at one point (judging by the pool of flux on the board and an off-brand security label on the torx screw plug), then worked for some time as a BD player (came with a kiddy disk inside), got a YLOD and someone didn't feel like fixing it again and passed it on... Now, it had arrived here in this YLOD state, but I didn't know much about diagnostics via syscon, so went with the NEC/Token waft.

I had recapped this COK-002 on the side of the board without chips and the system came to life, silently glowing with a green light. Surprised, I had connected the HDMI lead and gotten to a point of seeing the XMB, twice, but both times the PS3 was shutting down due to the overheating. Fine, time to de-lid and re-paste everything, so I did .. and upon assembling everything back it had a YLOD again, a very quick one (0.5 sec) at that. So out went the NEC/Tokens on the chip side and replaced with TaPol counterparts. Now, the system boots into a GLOD (everything bar the SD board is connected), recovery doesn't work and I need to hold the power down for 10 sec to shut it off .. What's peculiar, is in the UART readouts I get from the syscon .. there's nothing, yet the system is dead.

Initial state of things after recapping, which lead to it booting into a GLOD:
Code: 
>$ becount
becount
Bringup : 2466 times
Shutdown: 2342 times
Power-on: 107day 03hour 32min 44sec

>$ lasterrlog
lasterrlog
Last Error Code:0xa0801001, Time:0xffffffff
[mullion]$

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

Cleared the log and rebooted - no errors, yet the glaring GLOD is there. Would it not report at least some problem that prevents the darn thing from starting?

Code: 
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$

>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2

>$ errlog
errlog
ofst[  0]:err_code:0xffffffff, clock:0xffffffff
ofst[  4]:err_code:0xffffffff, clock:0xffffffff
ofst[  8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
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

>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000002F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

If I request powerstate before shutdown, it comes back with the following:
Code: 
>$ powerstate
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.
ITC_DUMP000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PTC_DUMP0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009e90a45000000000a5d0ac3000000000a330a930000000009bb0a21000000000a4b0aa9000000000a4a0aa80000000009db0a31000000000a550ab50000000000000000000000000a330a91000000000a2b0a8a0000000009e60a3d000000000a460aa50000000009c80a1a0000000009da0a3a0000000009c60a240000000009ad0a0c0000000000000000000000000a0a0a640000000009e70a3c000000000a850ae2000000000a760ad40000000009cc0a270000000009cf0a2b0000000009d40a2e000000000a830add0000000000000000000000000a8e0aea000000000a6d0ac9000000000a070a59000000000a8e0ae6000000000a170a710000000009fb0a60000000000a860ae6000000000aa50af70000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP0001000a00090000020c00000373000000000018000000000000020c000710e109410000000f000f00200000a08000080001e10f000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443844384438931593159319931300ff00ff00ff00ff000000000000000000000bad00000bad00220bad00220bad00000000000000000bad3f000bad3f39000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE

Anyone have any clue as to how to peek and poke the thing in such a state? Cheers
Click to expand...


Very odd... i don't remember seeing an error log looking like that, but maybe @RIP-Felix has.

As far as peek/poke, i don't think that's enabled at all on retail syscons.
 
TimeWalker75a said:
Hiya,

A long-time lurker, finally a poster.

I have in me hands a CECHC03 that appears to have had the RSX reballed at one point (judging by the pool of flux on the board and an off-brand security label on the torx screw plug), then worked for some time as a BD player (came with a kiddy disk inside), got a YLOD and someone didn't feel like fixing it again and passed it on... Now, it had arrived here in this YLOD state, but I didn't know much about diagnostics via syscon, so went with the NEC/Token waft.

I had recapped this COK-002 on the side of the board without chips and the system came to life, silently glowing with a green light. Surprised, I had connected the HDMI lead and gotten to a point of seeing the XMB, twice, but both times the PS3 was shutting down due to the overheating. Fine, time to de-lid and re-paste everything, so I did .. and upon assembling everything back it had a YLOD again, a very quick one (0.5 sec) at that. So out went the NEC/Tokens on the chip side and replaced with TaPol counterparts. Now, the system boots into a GLOD (everything bar the SD board is connected), recovery doesn't work and I need to hold the power down for 10 sec to shut it off .. What's peculiar, is in the UART readouts I get from the syscon .. there's nothing, yet the system is dead.

Initial state of things after recapping, which lead to it booting into a GLOD:
Code: 
>$ becount
becount
Bringup : 2466 times
Shutdown: 2342 times
Power-on: 107day 03hour 32min 44sec

>$ lasterrlog
lasterrlog
Last Error Code:0xa0801001, Time:0xffffffff
[mullion]$

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

Cleared the log and rebooted - no errors, yet the glaring GLOD is there. Would it not report at least some problem that prevents the darn thing from starting?

Code: 
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$

>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] First Boot.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2

>$ errlog
errlog
ofst[  0]:err_code:0xffffffff, clock:0xffffffff
ofst[  4]:err_code:0xffffffff, clock:0xffffffff
ofst[  8]:err_code:0xffffffff, clock:0xffffffff
ofst[ 12]:err_code:0xffffffff, clock:0xffffffff
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xffffffff, clock:0xffffffff
ofst[ 28]:err_code:0xffffffff, clock:0xffffffff
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
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

>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000002F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

If I request powerstate before shutdown, it comes back with the following:
Code: 
>$ powerstate
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.
ITC_DUMP000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PTC_DUMP0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009e90a45000000000a5d0ac3000000000a330a930000000009bb0a21000000000a4b0aa9000000000a4a0aa80000000009db0a31000000000a550ab50000000000000000000000000a330a91000000000a2b0a8a0000000009e60a3d000000000a460aa50000000009c80a1a0000000009da0a3a0000000009c60a240000000009ad0a0c0000000000000000000000000a0a0a640000000009e70a3c000000000a850ae2000000000a760ad40000000009cc0a270000000009cf0a2b0000000009d40a2e000000000a830add0000000000000000000000000a8e0aea000000000a6d0ac9000000000a070a59000000000a8e0ae6000000000a170a710000000009fb0a60000000000a860ae6000000000aa50af70000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP0001000a00090000020c00000373000000000018000000000000020c000710e109410000000f000f00200000a08000080001e10f000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443844384438931593159319931300ff00ff00ff00ff000000000000000000000bad00000bad00220bad00220bad00000000000000000bad3f000bad3f39000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000powerstate
ATA Power          : ON
PCI Power          : OFF
RSX Power          : ON
XDR Power          : ON
Eurus Power        : ON
SB Power           : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor  : AVAILABLE

Anyone have any clue as to how to peek and poke the thing in such a state? Cheers
Click to expand...
marciolsf said:
Very odd... i don't remember seeing an error log looking like that, but maybe @RIP-Felix has.

As far as peek/poke, i don't think that's enabled at all on retail syscons.
Click to expand...
Well, unfortunately it doesn't sound so strange to me...

Your machine was having RSX related YLOD (3034)
Then you went ahead with the tokin magic and zing za da bim, the thing responded as it tends to do. But assuming the capacitor job went well, the underlying problem is still there (RSX) and now it's manifesting itself as a GLOD instead of the 3034 YLOD. (Of course this is just my educated guess)
The GLOD unfortunately is not an error that gets detected and logged by the syscon.
As for current "error" 1001... Not sure how far you've gone into reading this thread but I say it's a non-error. (Actually your case represents a sad experiment that Felix wanted to see)

This is what makes everything so tricky. Rsx problems are very fiddly. They are known to respond to even slight temperature changes and pressure. Which can make it easy to arrive at wrong conclusions.

Remember the legendary hairdryer trick and similar quack youtube videos from the old times?
Well they exist because they actually worked. And this is more or less what you collaterally did when doing the tokin thing, or even delidding.

(Or perhaps even the repair guy who "reballed" it)

Cheers
 
Pacorretaco said:
The GLOD unfortunately is not an error that gets detected and logged by the syscon.
As for current "error" 1001... Not sure how far you've gone into reading this thread but I say it's a non-error. (Actually your case represents a sad experiment that Felix wanted to see)
Click to expand...

Yeah, I figured the 1001's are just from flipping the power switch a bunch of times to get the system to turn off. What bugs me is that the YLOD codes (the initial lovely bunch of 3034 and 4411) are followed by a0902203, which the OP seems to denote as SB GLOD (fitting), implying the firmware hashes are corrupt? I mean, I can see that RSX BGA issues would be the prime candidate considering the course of events, but would that render any communication with the SB dead too, i.e. no HDD activity, no USB power? As that's what it sits with here.

Also, calling it reballed would be a stretch .. I'm sure it was "reflown" at best as I'd found solid flux under the RSX IHS, which would imply it had never melted, so the temps never made it even past flux boiling point, ah well.
 
TimeWalker75a said:
Yeah, I figured the 1001's are just from flipping the power switch a bunch of times to get the system to turn off. What bugs me is that the YLOD codes (the initial lovely bunch of 3034 and 4411) are followed by a0902203, which the OP seems to denote as SB GLOD (fitting), implying the firmware hashes are corrupt? I mean, I can see that RSX BGA issues would be the prime candidate considering the course of events, but would that render any communication with the SB dead too, i.e. no HDD activity, no USB power? As that's what it sits with here.

Also, calling it reballed would be a stretch .. I'm sure it was "reflown" at best as I'd found solid flux under the RSX IHS, which would imply it had never melted, so the temps never made it even past flux boiling point, ah well.
Click to expand...
Hmm, I admit I don't know much about that error, but the prefix (09) indicates it was triggered on the OFF state. Which is interesting. Also it no longer appears? Maybe you can somehow trigger it again? But I'm guessing you already powered off and on multiple times and the error is not being reproduced.

Your bugging is well founded but,
If we now assume it's indeed a southbridge problem, that would mean we are having multiple different problems at the same time? Always hard to believe... and it's not like the 3034 ever went away. If this were the case, it would probably mean that this SB problem is actually on top of the old problem.
Also now that you mention... I don't think "no power from USB" is normal either. Not even the first two yellow HDD blinks?
And can you hear the HDD spinning at all?

I have no clue... Maybe somebody has more knowledge of this.
Or diagnosing the GLOD in general. I saw mentions of connecting to the southbridge UART. But I personally have no clue and would like to know too.
 
Well there are no timestamps, so the battery was removed. Someone opened it and "did something" requiring them to unplug the CMOS battery. Whatever they did didn't work, since they had 10x YLOD with 3034 and 4411. These are consistent with an RSX issue usually requiring areball to fix. That means that the 10x YLODs recorded in the errorlog were form subsequent testing after work was done on the console. I'm guessing this was you @TimeWalker75a?

I generally suggest the first thing anyone do is get the errorlog off the console before they start filling it with new errors, which overwrite the error history of the console. You might erase important errors that tell the console's story.

Spilled milk. Moving on...It looks like there are a string of 80 1001's that singal a GLOD to me. @squeept had a console he reballed that exhibited the same behavior. Namely, GLOD & SYSCON full of 80 1001's. He replaced the tokins and it had no effect. He concluded it was a dead RSX due to bump failure, but I still wonder if it might mean the CPU needs a reball. I would expect to see an unhealthy resistance on the RSX (less than 1 Ohm) if it were dead. @TimeWalker75a could you measure the resistance of the tokins on the CPU/RSX +/GND? If the RSX is less than 1 ohm it could mean it's dead or you screwed up the tantalum mod. I just released the Tantalizer beta, so you could go that route now, if you want. It makes it easy.

Your latest error related to the SB is concerning. So is the behavior. Sounds like a blown fuse that's taken out that circuit. You need to pull out a multimeter and go to town! Find the blow fuse, shorting cap, resistor, or lightning struck IC. The bigger question is what happened to cause that since the GLOD??? Did you test a good PSU? Is it possable the old one was bad, and that all that flipping the PWR switch caused a surge that blew a fuse on the motherboard? Almost sound like you left something in there and it shorted out and blew a fuse. Liquid damage maybe? A stray piece of wire? IDK, you'll have to troubleshoot your MB to figure out the source of that.

Edit:
Lastly, the bootloader failing to initialize is interesting. Have you tried rebuilding the database in the recovery menu? I wonder if a corrupt DB was causing your GLOD.
 
Last edited:
Pacorretaco said:
Also now that you mention... I don't think "no power from USB" is normal either. Not even the first two yellow HDD blinks?
And can you hear the HDD spinning at all?
Click to expand...
I can hear the HDD spin up and shut off (with an audible click on head return, the same way it would when you cut laptop power), but alas the HDD activity light stays dead the entire time. As for the USB power, I stuck a USB A/V meter in one of the slots to see if it would light up upon but, but it doesn't, no matter the USB slot I use.

RIP-Felix said:
I would expect to see an unhealthy resistance on the RSX (less than 1 Ohm) if it were dead. @TimeWalker75a could you measure the resistance of the tokins on the CPU/RSX +/GND? If the RSX is less than 1 ohm it could mean it's dead or you screwed up the tantalum mod. I just released the Tantalizer beta, so you could go that route now, if you want. It makes it easy.
Click to expand...
Will measure the resistance alright. I had actually made my own variant of the Soulkilla's interface boards, so the recap is not an absolute botch job, but something done rather neatly, no wires or pools of solder involved, etc.

RIP-Felix said:
You need to pull out a multimeter and go to town! Find the blow fuse, shorting cap, resistor, or lightning struck IC. The bigger question is what happened to cause that since the GLOD??? Did you test a good PSU? Is it possable the old one was bad, and that all that flipping the PWR switch caused a surge that blew a fuse on the motherboard? Almost sound like you left something in there and it shorted out and blew a fuse. Liquid damage maybe? A stray piece of wire? IDK, you'll have to troubleshoot your MB to figure out the source of that.
Click to expand...
I mean, the board was basically flooded with flux from the RSX "repair" to a point it got everywhere, I've no idea whether it's a no-clean flux or something cheap and nasty, but boy it still sticks after cleaning the entire board with IPA and horse hair brushes you normally use for applying barge cement. Whilst cleaning, I had found a single resistor that was hanging by a hair, fortunately the pads were still there, so I just stuck it back on.

Will have to snoop around with a multimeter to see if something (token aside) is obviously shorting, altough I'd expect for PowerOn signal to be null and void if something was, but as powerstate from syscon is reporting everything having power, I'm somewhat dubious.

RIP-Felix said:
Edit:
Lastly, the bootloader failing to initialize is interesting. Have you tried rebuilding the database in the recovery menu? I wonder if a corrupt DB was causing your GLOD.
Click to expand...
As mentioned, it doesn't get into recovery, so that option is out the window. Holding down the power button at any time just shuts the console off, regardless which power cycle it is, never seems to beep twice.
 
TimeWalker75a said:
Will measure the resistance alright.
Click to expand...
RSX measures 1.1 Ohm, CELL measures 1.3 Ohm
TimeWalker75a said:
Will have to snoop around with a multimeter to see if something (token aside) is obviously shorting
Click to expand...
All the fuses (both marked on silk as F and the ones denoted as 0 Ohm SMD resistors) I could find read as open. So far, the only thing that may possibly induce a short is a package marked as 649 561J above the Marvell chip, for which lugs 2,3,4 all short to ground, causing adjacent SMD caps both next to it and underneath the board to also read as SC. No idea what this component is though nor does google.
5TzFrcp.png

Realized why there are no timestamps anywhere in syscon readouts ( the battery still reads 3.2V) - someone ripped the whole 2032 battery connector out from the board at some point. The metal U prongs were barely soldered on and were rocking back and forth barely making any contact with the board.

P.S. tried to unplug the PSU from the board slightly and got an immediate YLOD signifying CELL power issues (rightfully so). So at least the board reacts to tampering. Reseating the PSU properly just brought me back to the brain-dead GLOD again.
Code: 
[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]: 0xa0093003
 
TimeWalker75a said:
Will measure the resistance alright. I had actually made my own variant of the Soulkilla's interface boards...
Click to expand...
Oh, A fellow maker? Show and tell, I want to see...let me see!

Well it's not diagnostic, but If the RSX or CPU is dying, the resistance of the filter circuit ican be thought of like a health meter. 3-4 ohms is good, 2-3 ohms is okay, 1-2 ohms is on it's last leg, and less than one is basically dead. So if you are sure the tantalum mod is soldered correctly, then the resistance you are seeing is not a good sign. However, it might make sense given the flux on the board. Sounds like someone went postal with a heat gun. Either they murdered the chips, or you just need to reball again. I've seen those resistances improve quite a bit after a reball/reflow, so old solder balls and oxidized pads can cause that. Maybe crap flux, IDK what they used. I've seen the resistance increase just from cleaning off the flux!

Only when you have the CPU/RSX off you can physically measure them directly, which is more diagnostic of a good/bad chip.
 
TimeWalker75a said:
RSX measures 1.1 Ohm, CELL measures 1.3 Ohm

All the fuses (both marked on silk as F and the ones denoted as 0 Ohm SMD resistors) I could find read as open. So far, the only thing that may possibly induce a short is a package marked as 649 561J above the Marvell chip, for which lugs 2,3,4 all short to ground, causing adjacent SMD caps both next to it and underneath the board to also read as SC. No idea what this component is though nor does google.
5TzFrcp.png
Click to expand...

It occurs to me that you don't have the schematic. @vyktormvmpay25 posted a link to them here. Anyways that is IC2408, a DC-DC converter that converts 3.3v_MISC (Vin pin7) to 1.8v_ANA (Vout pin1). I'm guessing "ANA" stands for analog, but I'm not sure. Pin 2 is NC and Pin 3 is GND. It's not good to leave NC's floating, so it was probably tied to GND. C2460 connects pin 4 (CN) to GND, so it may have low resistance and trip your continuity buzzer, but it should read a resistance value greater than a short. So double check that it is actually shorting before you replace.
 
COK-001 last 20 errors all:

00000000 A0022110 FFFFFFFF

Fixable or doorstop?

UPDATE: looks like it is related to IC5001.
 
Last edited:
finalman said:
COK-001 last 20 errors all:

00000000 A0022110 FFFFFFFF

Fixable or doorstop?

UPDATE: looks like it is related to IC5001.
Click to expand...
Could you check resistance of cpu power line? 2 ohms excluded multimeter variations.?
Should be nearly 3 ohms, if 2 means dead/defective ic.
Not sure but done some practice with cok002 board with same error as your. Exchanged all 4 isl ic near sata port. Reballed cpu even seen 2 ohms before and after reball on board same.
That board had liquid spillage on side of sata.
Now can be that isl clock frequency on your case. Ic5001 on schematics. You may simply check for shorts and cpu power line resistance will tell exactly.
 
vyktormvmpay25 said:
Could you check resistance of cpu power line? 2 ohms excluded multimeter variations.?
Should be nearly 3 ohms, if 2 means dead/defective ic.
Click to expand...

Sorry I'm new to this syscon error finding. I just did my first one yesterday. I'm off looking for this info now but just encase I can't find it could you just add a quick note or picture on where to probe with the multi-meter to get that info.

UPDATE: So if I test between GND and the CPU side of the tokin I get about 4 Ohms.
 
Last edited:
This is my water damaged board. For me is a lost cause under 2 ohms. Probably your have different problem or one of those ic referred by syscon errors pdf. Now compared with another board should have nearly 3 ohms on that points.
77c5766016060ea8ec8fac6b60d93b76.jpg


I have worked on a different project all day, now I have left to cure the silicone over cpu.
Can check more of my work and compared measurements. Not sure if rsx will have same values because mine is from a slim now but think should be quite same for untouched boards.
https://www.psx-place.com/threads/reball-ps3-cell-rsx.32376/page-2#post-290603
Took out and replaced all those ic's near sata port, didn't got any further, still same error, I am sure îs a dead cpu, it gets worn but nothing more.
Is just flux between legs of ic , checked all under microscope by the time when exchanged.
bfab10fa96516d58a8d5310d36ed1476.jpg
4ac39d25c75c2b652e206851ba508fc4.jpg
 
Last edited:

Thanks to @NSC-Modz and @Pacorretaco for making this. Looking forward to the tutorial and upcoming videos. I think it's cool how the word is getting out about the SYSCON UART script and what a critical step it is in diagnosing problems with the PS3. Maybe as it gets more attention someone will write a more comprehensive GUI that automates the process better. I would like one that enabels internal access mode and allows easy changes to fan tables. It's not so easy for non-coders as it is now.

Hopefully people don't get the idea that we have all the error codes figured out. Often they are cryptic, misleading, or can be associated with multiple problems. Most of the time it doesn't give you a clear "replace the PSU" or "change the tokins." You still have to troubleshoot the motherboard with a multimeter and schematics systematically to narrow down potential solutions. But, it can point you in the right direction and keep you from fixing what ain't broke. So that's the real benefit.
 
TimeWalker75a said:
Hiya,

>$ powerstate
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
Copyright(C) 2006 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.
ITC_DUMP000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PTC_DUMP0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000009e90a45000000000a5d0ac3000000000a330a930000000009bb0a21000000000a4b0aa9000000000a4a0aa80000000009db0a31000000000a550ab50000000000000000000000000a330a91000000000a2b0a8a0000000009e60a3d000000000a460aa50000000009c80a1a0000000009da0a3a0000000009c60a240000000009ad0a0c0000000000000000000000000a0a0a640000000009e70a3c000000000a850ae2000000000a760ad40000000009cc0a270000000009cf0a2b0000000009d40a2e000000000a830add0000000000000000000000000a8e0aea000000000a6d0ac9000000000a070a59000000000a8e0ae6000000000a170a710000000009fb0a60000000000a860ae6000000000aa50af70000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP0001000a00090000020c00000373000000000018000000000000020c000710e109410000000f000f00200000a08000080001e10f000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443844384438931593159319931300ff00ff00ff00ff000000000000000000000bad00000bad00220bad00220bad00000000000000000bad3f000bad3f39000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000060806080608060806080608060806080608000200020002000200020002000200020002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000powerstate
ATA Power : ON
PCI Power : OFF
RSX Power : ON
XDR Power : ON
Eurus Power : ON
SB Power : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor : AVAILABLE
[/code]

Anyone have any clue as to how to peek and poke the thing in such a state? Cheers
Click to expand...

Judging from

[ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.

Error message, possible faulty RAM near the cell chip.
 
Pacorretaco said:
Contradictions aside, all I'm saying (for now) is that I would like to be convinced better that error 1001 indicates nec tokin problems. Have you found this to be the case really?

Remember we are "fault finding" after all yeah?
Click to expand...

If you are seeing them alot in the errlog, it gives an indication of failed or failing nec tokins.

Lets just say, 90% of the time I was right, 1001 and 1002 are VRAM power fails, which is associated to power issues near the CELL or RSX = NEC tokins or power ICs.
 
RIP-Felix said:

Thanks to @NSC-Modz and @Pacorretaco for making this. Looking forward to the tutorial and upcoming videos. I think it's cool how the word is getting out about the SYSCON UART script and what a critical step it is in diagnosing problems with the PS3. Maybe as it gets more attention someone will write a more comprehensive GUI that automates the process better. I would like one that enabels internal access mode and allows easy changes to fan tables. It's not so easy for non-coders as it is now.

Hopefully people don't get the idea that we have all the error codes figured out. Often they are cryptic, misleading, or can be associated with multiple problems. Most of the time it doesn't give you a clear "replace the PSU" or "change the tokins." You still have to troubleshoot the motherboard with a multimeter and schematics systematically to narrow down potential solutions. But, it can point you in the right direction and keep you from fixing what ain't broke. So that's the real benefit.
Click to expand...

Like the video.

Yes, it should said that not all error codes are known, and this sony error code list was made in 2007, so probably recently, sony engineers have a more up to date record of the later models.

Let the knowledge expand.....
 
Pacorretaco said:
Contradictions aside, all I'm saying (for now) is that I would like to be convinced better that error 1001 indicates nec tokin problems. Have you found this to be the case really?

Remember we are "fault finding" after all yeah?
Click to expand...

I don't have to convince you of anything, Im just sharing what I know and what fixes these issues.

So, as you claim to know everything, I will leave it to your capable hands...
 
RIP-Felix said:
Only when you have the CPU/RSX off you can physically measure them directly, which is more diagnostic of a good/bad chip.
Click to expand...

Yes, the resistance is the core readings of the CELL or RSX.

Even with my IR heater and a profile heating, trying to put back CELL or RSX that are reading 1.2ohms or less is pointless, the sum of resistance is also the RAM chips on top of the RSX, they usually fail first.

I've only found one good seller on aliexpress that has good RSX chips, the reset just keep sending dead RSX's.
 
You must log in or register to reply here.

Similar threads

Back
Top