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

[Intruder_911]

Hey all! i havent posted to this site in quite awhile, recently picked up a B01 with GLOD/Artifact. got a 40nm RSX off aliexpress preballed, gonna try and swap the RSX with my home methods, i do not own a reballing machine or anything fancy, but i will be getting a board preheat device, and use a heatgun for the procedure, obviously not professional but i want to see what i can do with what i have, and if it works awesome! if not then it was worth the experience, i have been out of the scene for awhile and its absolutely amazing what everyone has been able to find in the last year and a half! cheers everyone! ill report my results once i get everything

You'll just burn RAMs on that RSX by that way.

 

[RIP-Felix]

Hey all! i havent posted to this site in quite awhile, recently picked up a B01 with GLOD/Artifact. got a 40nm RSX off aliexpress preballed, gonna try and swap the RSX with my home methods, i do not own a reballing machine or anything fancy, but i will be getting a board preheat device, and use a heatgun for the procedure, obviously not professional but i want to see what i can do with what i have, and if it works awesome! if not then it was worth the experience, i have been out of the scene for awhile and its absolutely amazing what everyone has been able to find in the last year and a half! cheers everyone! ill report my results once i get everything

Famous last words...

1. Heat gun
2. Ali express RSX

My advice would be to practice lifting, reballing, and reflowing a dead scrap board. Repeating at least 4-6 times to gain proficciency first, before making an attempt on a board that can be saved.

Impatience WILL KILL!

 

[Revak3115]

Famous last words...

1. Heat gun
2. Ali express RSX

My advice would be to practice lifting, reballing, and reflowing a dead scrap board. Repeating at least 4-6 times to gain proficciency first, before making an attempt on a board that can be saved.

Impatience WILL KILL!

i have had experiences before doing this, obviously never actually reballed before but i will be testing on scrap systems! i have enough confidence so i feel like as long as i go slow and be gentle everything should be alright tbh, if i fail then i fail i bought this system with the gamble in mind.

on another note i just did NECTOKINs on a A01 (tired doing syscon over the PC but i somehow ripped the pads) so i decided to risk again and used a heatgun and removed the NECs and replaced them with tantalums, for all 4 underside Tokins, BGToolset reads 3034, wonder how long this system will last now since that reads as BGA issue. but i just gave this system liquid metal and runs like a dream right now, hopefully i can get some use out of it before it dies, or maybe it wont idk

anyways rambles over, cheers!

 

[RIP-Felix]

...i have enough confidence so i feel like as long as i go slow and be gentle everything should be alright tbh...

Over confidence. They only times this has worked for me was when I was sure it wouldn't. Each time I think I have everything figured out and controled for, something new murders the attempt.

Saturday I killed a NOS 40nm because all previous experiances taught me the NOS was ready to go. I didn't have issues with VRAM popcorning due to moisture before. So I didn't think I needed to bake the NOS before the reflow. And this was the result...

That's the VRAM bumps squirting out of the underfill! BGA is fine, everything else was perfect. The VRAM was short!

Uanticipated curveballs at every attempt. My advice is to bake everything. Wrap in foil to prevent drafting and large temp difference between top/bottom sides. There's a ton of other little things.

Tiny cap in the corners to act as spaces. Yes or no?

Cover hole in CPU or not?

IPA to clean the BGA after wick. Warm or cooled?

If you have no idea what I'm talking about, then UR not ready.

 

[squeept]

So I didn't think I needed to bake the NOS before the reflow.

As always, I expect NOS in these instances is harvested and repackaged, but I digress.

If a BGA package (or any moisture sensitive component) is not packaged in sealed mylar with a dessicant and a HIC (humidity indicator card), it requires baking.

Relevant IPC document is J-STD-033B
https://www.digikey.com/en/pdf/s/scs/scs-jedec-jstd033b-standards

In practice, I do overnight bakes (probably averages around the 20 hour mark all said and done) at 100C because I have a standalone drying oven that I trust not to burn my house down. I would not go to sleep if you are using a preheater or anything else not specifically designed to be left on for extended periods for your bake.

edit: Also, anecdotally, from what I remember of the BGAmods forum and everyone trying to put together stats to figure out how to prevent "RAM bleed" like in Felix's picture, hot air top heat was less likely to cause it, especially when skipping the bake. But it happens sometimes no matter what, so don't worry about the occasional pop.

If RAM bleed is happening frequently, try keeping the top heater a little farther away. And check top and bottom heaters for hot spots. Bottom heat will require FLIR or one of those kitchen laser IR thermometers. Top heat you can check with a "paper test" which is pretty much what you'd guess from the name. Slap a bit of plain white paper under the heater, crank it to high heaven, and watch the burn marks form. The results should be pretty obvious if there are problems.

 

[Revak3115]

Over confidence. They only times this has worked for me was when I was sure it wouldn't. Each time I think I have everything figured out and controled for, something new murders the attempt.

Saturday I killed a NOS 40nm because all previous experiances taught me the NOS was ready to go. I didn't have issues with VRAM popcorning due to moisture before. So I didn't think I needed to bake the NOS before the reflow. And this was the result...
View attachment 38184

That's the VRAM bumps squirting out of the underfill! BGA is fine, everything else was perfect. The VRAM was short!

Uanticipated curveballs at every attempt. My advice is to bake everything. Wrap in foil to prevent drafting and large temp difference between top/bottom sides. There's a ton of other little things.

Tiny cap in the corners to act as spaces. Yes or no?

Cover hole in CPU or not?

IPA to clean the BGA after wick. Warm or cooled?

If you have no idea what I'm talking about, then UR not ready.

i can say i know 99% of what you said here, i have messed with a COK board before so i am used to what it does under heat, ill be wrapping around the RSX with kapton tape (and under the CELL so the components dont fall) and foil everywhere else. i didnt know about this NOS issue though so thank you for that, i know a good amount of reballing i just never fully gave a try because i dont own the proper tools for such a job, this is more an experiment for me tbh.

 

[Dariush Aghaee]

Hi every body
I managed to get a BC PS3 CECHA12 in working state that factory seal is not broken. the first thing I did to this device was a syscon errlog dump (just a bunch of 801001) so I upload the code here to see what your opinion is and any suggestions

Firmware Version: 4.88 (build 50731)
Platform ID: Cok14
Product Code: 00 8E
Product Sub Code: 00 01
Hardware Config: 00000000FFFFFFFF
Syscon Fimware Version: 0B8E.0001000000000006 (EEPROM: 0001000000000006)
Bringup Count: 1242, Shutdown Count: 1118
Runtime: 81 Days, 13 Hours, 44 Minutes, 15 Seconds
Error Log
01: A0801001 Mon Mar 23 14:05:01 2020
02: A0801001 Mon Mar 23 14:02:10 2020
03: A0801001 Mon Mar 23 13:57:47 2020
04: A0801001 Thu Apr 18 17:48:02 2019
05: A0801001 Sun Apr 2 02:06:49 2017
06: A0801001 Thu Oct 6 13:41:34 2016
07: A0801001 Thu Sep 8 16:19:50 2016
08: A0801001 Wed Jul 27 23:16:29 2016
09: A0801001 Sun Feb 28 23:33:06 2016
10: A0801001 Sun Feb 28 23:23:32 2016
11: A0801001 Wed Feb 24 15:42:44 2016
12: A0801001 Wed Feb 24 15:17:12 2016
13: A0801001 Mon Feb 1 22:19:52 2016
14: A0801001 Wed Nov 11 17:54:54 2015
15: A0801001 Tue Dec 2 10:41:37 2014
16: A0801001 Tue Jul 22 17:07:42 2014
17: A0801001 Sun Jun 8 10:34:01 2014
18: A0801001 Thu Nov 28 19:06:56 2013
19: A0801004 Wed Oct 23 17:21:13 2013
20: A0801001 Sat Mar 2 16:41:30 2013
21: A0801001 Thu Nov 3 15:06:42 2011
22: A0801001 Wed Aug 10 15:32:34 2011
23: A0801001 Tue Aug 9 12:28:53 2011
24: A0801001 Thu Jul 28 21:24:31 2011
25: A0801001 Sun Jul 10 17:18:35 2011
26: A0801001 Sun Jul 10 10:31:36 2011
27: A0801001 Wed Feb 16 20:00:45 2011
28: A0801001 Wed Feb 16 15:21:38 2011
29: A0801001 Sun Feb 13 14:13:09 2011
30: A0801001 Sun Feb 13 14:10:27 2011
31: A0801001 Sun Feb 13 13:56:25 2011
32: FFFFFFFF Tue Feb 8 19:33:39 2011

thank you.

yesterday I opened it and delided both cell and rsx. then I applied new regular thermal paste an close it to test and see if anything went wrong with the delid but the device booted fine. after that I opened it again to apply LM under IHSs. I did it and ... GLOD!!! I AM THE MOST BAD LUCK GUY EVER! or the most idiot maybe. here is some details about the disaster I made.

The LM I have used is this one. bought from third party store and I highly doubt that it is not FAKE.

every time I enter the verification code that came whit it on TG site it just says the product is official but it doesn't say how many times this code has been entered. I mean every fake producers can pick up a code like this one in my photos and print it on their cards! maybe they fill it with mercury!!

I cleaned the LM and saw that this sh!t made some bad footprints on silicon like smook.

and even on nikle plated IHSs. is this normal? or is it prof that this LM is fake?

I hooked up syscon wires and this is the codes I get

>$ errlog
errlog
ofst[112]:err_code:0xffffffff, clock:0x14eee96d 2011/02/16 20:00:45
ofst[116]:err_code:0xa0801001, clock:0x15ac3c08 2011/07/10 10:31:36
ofst[120]:err_code:0xa0801001, clock:0x15ac9b6b 2011/07/10 17:18:35
ofst[124]:err_code:0xa0801001, clock:0x15c4900f 2011/07/28 21:24:31
ofst[ 0]:err_code:0xa0801001, clock:0x15d3e485 2011/08/09 12:28:53
ofst[ 4]:err_code:0xa0801001, clock:0x15d56112 2011/08/10 15:32:34
ofst[ 8]:err_code:0xa0801001, clock:0x16456a82 2011/11/03 15:06:42
ofst[ 12]:err_code:0xa0801001, clock:0x18c4e83a 2013/03/02 16:41:30
ofst[ 16]:err_code:0xa0801004, clock:0x19fac209 2013/10/23 17:21:13
ofst[ 20]:err_code:0xa0801001, clock:0x1a2a50d0 2013/11/28 19:06:56
ofst[ 24]:err_code:0xa0801001, clock:0x1b26f899 2014/06/08 10:34:01
ofst[ 28]:err_code:0xa0801001, clock:0x1b6156de 2014/07/22 17:07:42
ofst[ 32]:err_code:0xa0801001, clock:0x1c1053e1 2014/12/02 10:41:37
ofst[ 36]:err_code:0xa0801001, clock:0x1dd63d6e 2015/11/11 17:54:54
ofst[ 40]:err_code:0xa0801001, clock:0x1e429688 2016/02/01 22:19:52
ofst[ 44]:err_code:0xa0801001, clock:0x1e6085f8 2016/02/24 15:17:12
ofst[ 48]:err_code:0xa0801001, clock:0x1e608bf4 2016/02/24 15:42:44
ofst[ 52]:err_code:0xa0801001, clock:0x1e663df4 2016/02/28 23:23:32
ofst[ 56]:err_code:0xa0801001, clock:0x1e664032 2016/02/28 23:33:06
ofst[ 60]:err_code:0xa0801001, clock:0x1f2bfd4d 2016/07/27 23:16:29
ofst[ 64]:err_code:0xa0801001, clock:0x1f644c26 2016/09/08 16:19:50
ofst[ 68]:err_code:0xa0801001, clock:0x1f89110e 2016/10/06 13:41:34
ofst[ 72]:err_code:0xa0801001, clock:0x20731939 2017/04/02 02:06:49
ofst[ 76]:err_code:0xa0801001, clock:0x244b74d2 2019/04/18 17:48:02
ofst[ 80]:err_code:0xa0801001, clock:0x260b7cdb 2020/03/23 13:57:47
ofst[ 84]:err_code:0xa0801001, clock:0x260b7de2 2020/03/23 14:02:10
ofst[ 88]:err_code:0xa0801001, clock:0x260b7e8d 2020/03/23 14:05:01
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0902203, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902203, clock:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ 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]$
>$ lasterrlog
lasterrlog
Last Error Code:0xa0902203, Time:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ 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 -> 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
>$ lasterrlog
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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_DUMP0000000000000000000000000a6f0ade000000000a850aea000000000a760ae20000000009e30a450000000009ed0a510000000009e60a4b000000000a790ae20000000000000000000000000a5c0ac7000000000a550ac00000000009ac0a10000000000a520abd0000000009b70a230000000009ae0a100000000009b60a17000000000a610ac800000000000000000000000009b30a140000000009950a00000000000a160a8500000000098a09f400000000098109eb00000000098f09f10000000009b20a12000000000a0a0a730000000000000000000000000a0b0a73000000000a150a7e0000000009c20a27000000000a320a990000000009b20a15000000000a310a9b000000000a2d0a91000000000a390a9f00000000000000000000000009ad0a0a000000000a3d0aa9000000000a100a7c00000000098409e7000000000a2b0a8f000000000a2a0a8f0000000009a20a04000000000a330a9d0000000000000000000000000a1c0a83000000000a0f0a770000000009aa0a12000000000a270a8d00000000099209f90000000009a70a0800000000098709ea00000000097709e200000000000000000000000009e20a450000000009b70a1a000000000a500ab7000000000a4c0ab20000000009a90a070000000009ab0a080000000009af0a11000000000a510ab40000000000000000000000000a670acc000000000a400aa40000000009df0a38000000000a6b0acf0000000009ed0a4f0000000009e50a3b000000000a530abd000000000a6f0acf0000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP0001000200090000020b00000363000000000016000000000000020c000710e109410000000f000f00200000a08000080001e10f000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443
>$ lasterrlog
lasterrlog
Last Error Code:0xa0902203, Time:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ powerstate
powerstate
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
[mullion]$
>$ powerstate
powerstate
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
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

does over tightening the hit sync clamps makes problems? is there any way to find out what's going on with this device? any other clues that can find from syscon?

 

[Revak3115]

yesterday I opened it and delided both cell and rsx. then I applied new regular thermal paste an close it to test and see if anything went wrong with the delid but the device booted fine. after that I opened it again to apply LM under IHSs. I did it and ... GLOD!!! I AM THE MOST BAD LUCK GUY EVER! or the most idiot maybe. here is some details about the disaster I made.

The LM I have used is this one. bought from third party store and I highly doubt that it is not FAKE.
View attachment 38191 View attachment 38192 View attachment 38193 View attachment 38194

every time I enter the verification code that came whit it on TG site it just says the product is official but it doesn't say how many times this code has been entered. I mean every fake producers can pick up a code like this one in my photos and print it on their cards! maybe they fill it with mercury!!

I cleaned the LM and saw that this sh!t made some bad footprints on silicon like smook.
View attachment 38196 View attachment 38197 View attachment 38198


and even on nikle plated IHSs. is this normal? or is it prof that this LM is fake?


View attachment 38199


I hooked up syscon wires and this is the codes I get

>$ errlog
errlog
ofst[112]:err_code:0xffffffff, clock:0x14eee96d 2011/02/16 20:00:45
ofst[116]:err_code:0xa0801001, clock:0x15ac3c08 2011/07/10 10:31:36
ofst[120]:err_code:0xa0801001, clock:0x15ac9b6b 2011/07/10 17:18:35
ofst[124]:err_code:0xa0801001, clock:0x15c4900f 2011/07/28 21:24:31
ofst[ 0]:err_code:0xa0801001, clock:0x15d3e485 2011/08/09 12:28:53
ofst[ 4]:err_code:0xa0801001, clock:0x15d56112 2011/08/10 15:32:34
ofst[ 8]:err_code:0xa0801001, clock:0x16456a82 2011/11/03 15:06:42
ofst[ 12]:err_code:0xa0801001, clock:0x18c4e83a 2013/03/02 16:41:30
ofst[ 16]:err_code:0xa0801004, clock:0x19fac209 2013/10/23 17:21:13
ofst[ 20]:err_code:0xa0801001, clock:0x1a2a50d0 2013/11/28 19:06:56
ofst[ 24]:err_code:0xa0801001, clock:0x1b26f899 2014/06/08 10:34:01
ofst[ 28]:err_code:0xa0801001, clock:0x1b6156de 2014/07/22 17:07:42
ofst[ 32]:err_code:0xa0801001, clock:0x1c1053e1 2014/12/02 10:41:37
ofst[ 36]:err_code:0xa0801001, clock:0x1dd63d6e 2015/11/11 17:54:54
ofst[ 40]:err_code:0xa0801001, clock:0x1e429688 2016/02/01 22:19:52
ofst[ 44]:err_code:0xa0801001, clock:0x1e6085f8 2016/02/24 15:17:12
ofst[ 48]:err_code:0xa0801001, clock:0x1e608bf4 2016/02/24 15:42:44
ofst[ 52]:err_code:0xa0801001, clock:0x1e663df4 2016/02/28 23:23:32
ofst[ 56]:err_code:0xa0801001, clock:0x1e664032 2016/02/28 23:33:06
ofst[ 60]:err_code:0xa0801001, clock:0x1f2bfd4d 2016/07/27 23:16:29
ofst[ 64]:err_code:0xa0801001, clock:0x1f644c26 2016/09/08 16:19:50
ofst[ 68]:err_code:0xa0801001, clock:0x1f89110e 2016/10/06 13:41:34
ofst[ 72]:err_code:0xa0801001, clock:0x20731939 2017/04/02 02:06:49
ofst[ 76]:err_code:0xa0801001, clock:0x244b74d2 2019/04/18 17:48:02
ofst[ 80]:err_code:0xa0801001, clock:0x260b7cdb 2020/03/23 13:57:47
ofst[ 84]:err_code:0xa0801001, clock:0x260b7de2 2020/03/23 14:02:10
ofst[ 88]:err_code:0xa0801001, clock:0x260b7e8d 2020/03/23 14:05:01
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0902203, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902203, clock:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ 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]$
>$ lasterrlog
lasterrlog
Last Error Code:0xa0902203, Time:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ 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 -> 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
>$ lasterrlog
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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_DUMP0000000000000000000000000a6f0ade000000000a850aea000000000a760ae20000000009e30a450000000009ed0a510000000009e60a4b000000000a790ae20000000000000000000000000a5c0ac7000000000a550ac00000000009ac0a10000000000a520abd0000000009b70a230000000009ae0a100000000009b60a17000000000a610ac800000000000000000000000009b30a140000000009950a00000000000a160a8500000000098a09f400000000098109eb00000000098f09f10000000009b20a12000000000a0a0a730000000000000000000000000a0b0a73000000000a150a7e0000000009c20a27000000000a320a990000000009b20a15000000000a310a9b000000000a2d0a91000000000a390a9f00000000000000000000000009ad0a0a000000000a3d0aa9000000000a100a7c00000000098409e7000000000a2b0a8f000000000a2a0a8f0000000009a20a04000000000a330a9d0000000000000000000000000a1c0a83000000000a0f0a770000000009aa0a12000000000a270a8d00000000099209f90000000009a70a0800000000098709ea00000000097709e200000000000000000000000009e20a450000000009b70a1a000000000a500ab7000000000a4c0ab20000000009a90a070000000009ab0a080000000009af0a11000000000a510ab40000000000000000000000000a670acc000000000a400aa40000000009df0a38000000000a6b0acf0000000009ed0a4f0000000009e50a3b000000000a530abd000000000a6f0acf0000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP0001000200090000020b00000363000000000016000000000000020c000710e109410000000f000f00200000a08000080001e10f000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443
>$ lasterrlog
lasterrlog
Last Error Code:0xa0902203, Time:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ powerstate
powerstate
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
[mullion]$
>$ powerstate
powerstate
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
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

does over tightening the hit sync clamps makes problems? is there any way to find out what's going on with this device? any other clues that can find from syscon?

have you FULLY inspected that LM didnt get under the kapton tape on the RSX? i been using LM on PS3 and use clear nail polish and ia have had no issues, closely inspect the RSX for LM runoff and also the gold contact points on the CELL and RSX should be covered aswell, any runoff on the points will for sure fry it

 

[Dariush Aghaee]

have you FULLY inspected that LM didnt get under the kapton tape on the RSX? i been using LM on PS3 and use clear nail polish and ia have had no issues, closely inspect the RSX for LM runoff and also the gold contact points on the CELL and RSX should be covered aswell, any runoff on the points will for sure fry it

I'm pretty sure that no LM were dropped or ran off. I removed the tapes and took another picture.

Have checked under magnifier.

Is it regular to the silicons getting smokey like this?
Or IHSs get black dirt after cleaning LM?
If RSX dies should make YLOD not GLOD right?

 

[sandungas]

Hello, got a bit of an odd error I've not seen before. This is from a PS3 slim CECH-2003, the error code it keeps spitting out in the syscon is A0092114.

I have attached the bringup output and the error log. Any help would be appreciated!

I hope this answer is not too late, the other day i did read your post and boosted my interest but i was not able to write a short and straightforward answer, but you are right, that error code doesnt appears in the list neither in wiki, and never was reported before
Is a bit tricky to explain, but we can deduce partially what it means, this explanation is directly related with a theory i was discussing with @RIP-Felix and @M4j0r some months ago, as far i remember we never had a proof to know if this theory is right or wrong, and i dont remember if they agrees with what im going to explain, anyway...

The error codes are composed by 8 digits, the first 4 are special, and the last 4 are the real error code.... so let me simplify your error code A0092114 ---to---> xxxx2114
The number 2 is the identifyer for the category = FATAL ERROR https://www.psdevwiki.com/ps3/Syscon_Error_Codes#Fatal_Errors
Ok, now it comes the interesting detail... scroll to most top of the wiki page and take some time to see how are organized the error code names under the "fatal" category in the page index
I added names to that index to help focus our attention to this detail, is like a sequence, we never made a list of it to have a better overview, but the other day when i did read your post i made this table, at bottom of the talk page, are just notes, but eventually if this theory is confirmed we can regorganize the front page following this concept... it would be an improvement in the page because it would make the list of error coes shorter
https://www.psdevwiki.com/ps3/Talk:Syscon_Error_Codes#Fatal_error_codes_relationship

This is a bit conceptual, but when they was devolping this they considered the values given to the error codes was like "slots" where eventually they could assign the reserved slots to new new error codes provided by the newer versions of the syscon firmwares
The point is... the error codes "xxxx20xx" "xxxx21xx" "xxxx22xx" "xxxx23xx" are related with each others... seems to be the same stuff under different conditions

To be more explicit... your error code xxxx2114 is really a xxxx2x14 (2=fatal, 14=error) that happened under condition xxxx2114 (2=fatal, 1=condition, 14=error)

So... lets forget about that "condition" by now because we dont really know what is it and keep attention to the description and how are grouped the error codes for xxxx2x10 xxxx2x11 xxxx2x12 xxxx2x13... ALL THEM ARE CLOCKS... so you your error code xxxx2x14 should be also a clock (but we dont have any proof, is just a theory by now)

Actually... note how they organized the error codes in the "slots" starting with xxxx2x0x (seems to be general, and they reserved a few slots in that group), then the clocks at xxxx2x1x (again some reserved), next is the group of xxxx2x2x (seems to be for video), and finally xxxx2x3x (for thermal), are 4 groups

 

[RIP-Felix]

yesterday I opened it and delided both cell and rsx. then I applied new regular thermal paste an close it to test and see if anything went wrong with the delid but the device booted fine. after that I opened it again to apply LM under IHSs. I did it and ... GLOD!!! I AM THE MOST BAD LUCK GUY EVER! or the most idiot maybe. here is some details about the disaster I made.

The LM I have used is this one. bought from third party store and I highly doubt that it is not FAKE.
View attachment 38191 View attachment 38192 View attachment 38193 View attachment 38194

every time I enter the verification code that came whit it on TG site it just says the product is official but it doesn't say how many times this code has been entered. I mean every fake producers can pick up a code like this one in my photos and print it on their cards! maybe they fill it with mercury!!

I cleaned the LM and saw that this sh!t made some bad footprints on silicon like smook.
View attachment 38196 View attachment 38197 View attachment 38198


and even on nikle plated IHSs. is this normal? or is it prof that this LM is fake?


View attachment 38199


I hooked up syscon wires and this is the codes I get

>$ errlog
errlog
ofst[112]:err_code:0xffffffff, clock:0x14eee96d 2011/02/16 20:00:45
ofst[116]:err_code:0xa0801001, clock:0x15ac3c08 2011/07/10 10:31:36
ofst[120]:err_code:0xa0801001, clock:0x15ac9b6b 2011/07/10 17:18:35
ofst[124]:err_code:0xa0801001, clock:0x15c4900f 2011/07/28 21:24:31
ofst[ 0]:err_code:0xa0801001, clock:0x15d3e485 2011/08/09 12:28:53
ofst[ 4]:err_code:0xa0801001, clock:0x15d56112 2011/08/10 15:32:34
ofst[ 8]:err_code:0xa0801001, clock:0x16456a82 2011/11/03 15:06:42
ofst[ 12]:err_code:0xa0801001, clock:0x18c4e83a 2013/03/02 16:41:30
ofst[ 16]:err_code:0xa0801004, clock:0x19fac209 2013/10/23 17:21:13
ofst[ 20]:err_code:0xa0801001, clock:0x1a2a50d0 2013/11/28 19:06:56
ofst[ 24]:err_code:0xa0801001, clock:0x1b26f899 2014/06/08 10:34:01
ofst[ 28]:err_code:0xa0801001, clock:0x1b6156de 2014/07/22 17:07:42
ofst[ 32]:err_code:0xa0801001, clock:0x1c1053e1 2014/12/02 10:41:37
ofst[ 36]:err_code:0xa0801001, clock:0x1dd63d6e 2015/11/11 17:54:54
ofst[ 40]:err_code:0xa0801001, clock:0x1e429688 2016/02/01 22:19:52
ofst[ 44]:err_code:0xa0801001, clock:0x1e6085f8 2016/02/24 15:17:12
ofst[ 48]:err_code:0xa0801001, clock:0x1e608bf4 2016/02/24 15:42:44
ofst[ 52]:err_code:0xa0801001, clock:0x1e663df4 2016/02/28 23:23:32
ofst[ 56]:err_code:0xa0801001, clock:0x1e664032 2016/02/28 23:33:06
ofst[ 60]:err_code:0xa0801001, clock:0x1f2bfd4d 2016/07/27 23:16:29
ofst[ 64]:err_code:0xa0801001, clock:0x1f644c26 2016/09/08 16:19:50
ofst[ 68]:err_code:0xa0801001, clock:0x1f89110e 2016/10/06 13:41:34
ofst[ 72]:err_code:0xa0801001, clock:0x20731939 2017/04/02 02:06:49
ofst[ 76]:err_code:0xa0801001, clock:0x244b74d2 2019/04/18 17:48:02
ofst[ 80]:err_code:0xa0801001, clock:0x260b7cdb 2020/03/23 13:57:47
ofst[ 84]:err_code:0xa0801001, clock:0x260b7de2 2020/03/23 14:02:10
ofst[ 88]:err_code:0xa0801001, clock:0x260b7e8d 2020/03/23 14:05:01
ofst[ 92]:err_code:0xa0902203, clock:0xffffffff
ofst[ 96]:err_code:0xa0902203, clock:0xffffffff
ofst[100]:err_code:0xa0902203, clock:0xffffffff
ofst[104]:err_code:0xa0902203, clock:0xffffffff
ofst[108]:err_code:0xa0902203, clock:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ 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]$
>$ lasterrlog
lasterrlog
Last Error Code:0xa0902203, Time:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ 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 -> 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
>$ lasterrlog
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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_DUMP0000000000000000000000000a6f0ade000000000a850aea000000000a760ae20000000009e30a450000000009ed0a510000000009e60a4b000000000a790ae20000000000000000000000000a5c0ac7000000000a550ac00000000009ac0a10000000000a520abd0000000009b70a230000000009ae0a100000000009b60a17000000000a610ac800000000000000000000000009b30a140000000009950a00000000000a160a8500000000098a09f400000000098109eb00000000098f09f10000000009b20a12000000000a0a0a730000000000000000000000000a0b0a73000000000a150a7e0000000009c20a27000000000a320a990000000009b20a15000000000a310a9b000000000a2d0a91000000000a390a9f00000000000000000000000009ad0a0a000000000a3d0aa9000000000a100a7c00000000098409e7000000000a2b0a8f000000000a2a0a8f0000000009a20a04000000000a330a9d0000000000000000000000000a1c0a83000000000a0f0a770000000009aa0a12000000000a270a8d00000000099209f90000000009a70a0800000000098709ea00000000097709e200000000000000000000000009e20a450000000009b70a1a000000000a500ab7000000000a4c0ab20000000009a90a070000000009ab0a080000000009af0a11000000000a510ab40000000000000000000000000a670acc000000000a400aa40000000009df0a38000000000a6b0acf0000000009ed0a4f0000000009e50a3b000000000a530abd000000000a6f0acf0000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP0001000200090000020b00000363000000000016000000000000020c000710e109410000000f000f00200000a08000080001e10f000008540c540000000000010bad000000000000000000000000000c000c000c000c00580058005800580000000000000000007f007f007f007f4438443
>$ lasterrlog
lasterrlog
Last Error Code:0xa0902203, Time:0x0b48885a 2005/12/31 00:07:54
[mullion]$
>$ powerstate
powerstate
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
[mullion]$
>$ powerstate
powerstate
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
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

does over tightening the hit sync clamps makes problems? is there any way to find out what's going on with this device? any other clues that can find from syscon?

That's normal with LM. The gallium stains both silicon and the Nickel plated copper IHS. The gallium is what penetrates the surfaces oxides and boundary molecules. It promotes good wetting.

 

[Dariush Aghaee]

That's normal with LM. The gallium stains both silicon and the Nickel plated copper IHS. The gallium is what penetrates the surfaces oxides and boundary molecules. It promotes good wetting.

So the LM (whatever is) didn't influx inside the silicon die and I have over tightened hit sync and a bga under cell is gone? Is there any way to test this?
Does a reflow on cell help?

 

[RIP-Felix]

0xb0002001 (FATAL) XDR Link not initilized.

I'm getting the same error on a console at the moment. I shelved it until a thermal camera arrives, because I'm operating under the assumption that an XDR memory module has failed. When booting it should be the only one that doesn't heat up. I'll first try replacing that, but if that doesn't work it could be the CPU's BGA pads from the XDR.

ACE Console repairs had this happen to him recently. In his case it looked like drop damage, because the CPU pads were completly torn.

 

[Dariush Aghaee]

0xb0002001 (FATAL) XDR Link not initilized.

I'm getting the same error on a console at the moment. I shelved it until a thermal camera arrives, because I'm operating under the assumption that an XDR memory module has failed. When booting it should be the only one that doesn't heat up. I'll first try replacing that, but if that doesn't work it could be the CPU's BGA pads from the XDR.

ACE Console repairs had this happen to him recently. In his case it looked like drop damage, because the CPU pads were completly torn.

Well I'm sure I'm not going to buy a thermal camera because it's really too expensive so I have to assume that my console got a BGA problem under CELL. I have the instruments to do a reflow but I don't know how to do it perfectly with minimum damages to the motherboard. Is there any good instructions?
Your guidance is truly appreciated.

 

[squeept]

#9

Spoiler

 

[Error_404]

Can anyone point me in the right direction to replace the fuse/cap combo for a 2120/3031 error combo in powerstep 20/21?

 

[feng_ye]

Hello, got a bit of an odd error I've not seen before. This is from a PS3 slim CECH-2003, the error code it keeps spitting out in the syscon is A0092114.

I have attached the bringup output and the error log. Any help would be appreciated!

I got nearly the same A0092114 in one of my recent CECHL. I thought was a thermal IC error before: https://www.psx-place.com/threads/problems-with-hdmi-display.29590/#post-343009

Before getting YLOD, it has the weird color segment issue described by the OP of the above link. AV cable seems fine. I got the YLOD after pressure test it on AV cable.

 

[feng_ye]

I got nearly the same A0092114 in one of my recent CECHL. I thought was a thermal IC error before: https://www.psx-place.com/threads/problems-with-hdmi-display.29590/#post-343009

Before getting YLOD, it has the weird color segment issue described by the OP of the above link. AV cable seems fine. I got the YLOD after pressure test it on AV cable.

I got some progress, or made it worse.

So I believe error A009 2114 is indeed clock generator IC or related circuit error since 2110-2113 all points to those clock generator ICs. I took a comparison between VER-001(this board in question) and SEM-001, turns out that VER-001 only has two ICs related to clock generator while SEM-001 has 4(that's why the error code is from 2110-2113). Testing for short shows that XCG_I2C_SDA and XCG_I2C_SCL are shorted on IC5005 and IC5002. According to SEM-001 service manual, there seems no other components connect in between those two ICs along these two lines, i.e. they're directly connected.

Since IC5005 is much smaller, I tried to desolder it first. However the pin with XCG_I2C_SDA and XCG_I2C_SCL are still shorted. Testing the decodered IC5005, which is a bus switching cmos IC, the two lines are not shorted. Then I moved onto IC5002, which is much larger, and desoldered it. As expected, the short is gone after removing IC5002. Testing desoldered IC5002 on the two pins in question, however, doesn't show any shorts. So maybe it's a soldering issue after all?

Nevertheless, I decided not to use the IC5002 on VER-001(Manufacturer is Texas Instruments). Instead I took the equivalent IC5002 on a donor DIA-002(Manufacturer is ICS) desolder it and resolder onto the VER-001. And solder the old IC5005 back into place.

When it comes to testing, to my disappointment, the first time I bringup I still getting 2114 error. However, several subsequent boots are much longer, then YLOD again. Showing A080 1301 error(BE PLL Unlick?? Funny word, or it's a translation error like should be PLL Unlock? Donno)

>$ br
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

>$
F0000003
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.6.0
#!(Build ID: 3440,37120,
#!Build Date: 2008-12-26_15:20:27)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# [UCMD] Unknown command.

>$
00000000
# [UCMD] Unknown command.
NG F0000003
# [SSM] Cond/Fatal received, msg=24AF.
# [SSM] Fataldown Start.

>$
F0000003
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [UCMD] Unknown command.

However, after a few trying, the YLOD seems getting much shorter, almost instance YLOD. Now I'm having 3010, 3012, 3020 errors, all at a bit of different stages.

>$ errlog
00000000
# CODE     CLOCK
# A0233020 FFFFFFFF
# A0801301 FFFFFFFF
# A0801301 FFFFFFFF
# A0801301 FFFFFFFF
# A0092114 FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

So what I've learnt so far is, it seems error 2114 are indeed clock generator related issue. The problem I've seen so far, might be:
1. The "equivalent" IC5002 on DIA-002 is not entirely hardware compatible, or maybe should be replaced with IC5001 too
2. Or the soldering I did for IC5002 and IC5005 has some problems maybe poor contacts or even shorts.
3. Or I did fixed the 2114 error by replacing IC(stage number goes from A009 to A023, the best is A080), but when removing the heatsink or doing soldering work, the CPU BGA problem appeared
4. Something else

 

[feng_ye]

I got some progress, or made it worse.

So I believe error A009 2114 is indeed clock generator IC or related circuit error since 2110-2113 all points to those clock generator ICs. I took a comparison between VER-001(this board in question) and SEM-001, turns out that VER-001 only has two ICs related to clock generator while SEM-001 has 4(that's why the error code is from 2110-2113). Testing for short shows that XCG_I2C_SDA and XCG_I2C_SCL are shorted on IC5005 and IC5002. According to SEM-001 service manual, there seems no other components connect in between those two ICs along these two lines, i.e. they're directly connected.

Since IC5005 is much smaller, I tried to desolder it first. However the pin with XCG_I2C_SDA and XCG_I2C_SCL are still shorted. Testing the decodered IC5005, which is a bus switching cmos IC, the two lines are not shorted. Then I moved onto IC5002, which is much larger, and desoldered it. As expected, the short is gone after removing IC5002. Testing desoldered IC5002 on the two pins in question, however, doesn't show any shorts. So maybe it's a soldering issue after all?

Nevertheless, I decided not to use the IC5002 on VER-001(Manufacturer is Texas Instruments). Instead I took the equivalent IC5002 on a donor DIA-002(Manufacturer is ICS) desolder it and resolder onto the VER-001. And solder the old IC5005 back into place.

When it comes to testing, to my disappointment, the first time I bringup I still getting 2114 error. However, several subsequent boots are much longer, then YLOD again. Showing A080 1301 error(BE PLL Unlick?? Funny word, or it's a translation error like should be PLL Unlock? Donno)

>$ br
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

>$
F0000003
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.6.0
#!(Build ID: 3440,37120,
#!Build Date: 2008-12-26_15:20:27)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# [UCMD] Unknown command.

>$
00000000
# [UCMD] Unknown command.
NG F0000003
# [SSM] Cond/Fatal received, msg=24AF.
# [SSM] Fataldown Start.

>$
F0000003
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [UCMD] Unknown command.

However, after a few trying, the YLOD seems getting much shorter, almost instance YLOD. Now I'm having 3010, 3012, 3020 errors, all at a bit of different stages.

>$ errlog
00000000
# CODE     CLOCK
# A0233020 FFFFFFFF
# A0801301 FFFFFFFF
# A0801301 FFFFFFFF
# A0801301 FFFFFFFF
# A0092114 FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

So what I've learnt so far is, it seems error 2114 are indeed clock generator related issue. The problem I've seen so far, might be:
1. The "equivalent" IC5002 on DIA-002 is not entirely hardware compatible, or maybe should be replaced with IC5001 too
2. Or the soldering I did for IC5002 and IC5005 has some problems maybe poor contacts or even shorts.
3. Or I did fixed the 2114 error by replacing IC(stage number goes from A009 to A023, the best is A080), but when removing the heatsink or doing soldering work, the CPU BGA problem appeared
4. Something else

Update on my own fixing of 2114 + 3020 error on a VER-001 which initially only has HDMI display color segmentation issue.

According to my yesterday's conclusion, I decided to retouch the two ICs I soldered, since I found one pin on the bigger IC5002(marking shows SCEI (TI logo) 88J9LKK C5714 G4) is not touching the PCB. First time using iron with preheated workstation, failed and back to error 2114 at an early boot stage A009. Second time using hotair gun with preheated, successfully boot into OS. No more 2114, no more 1301, 3010, 3012 or 3020. However, the initial HDMI color segmentation issue still remains. Found more fault like Ethernet, Wifi and Bluetooth not working.

But the take way of this fix is, 2114, like 2110-2113 erros, all link to clock generator circuits. So @Rozus you might want to check those IC and test for shorts. IC5005 is also worth checking. @sandungas @RIP-Felix you might be also interested in the finding.

Spoiler: ICs Involved

The Texas Instruments clock generator IC which has XCG_I2C_SDA and XCG_I2C_SCL line shorted:

Replaced with ICS 9249AGLF from a DIA-002 donor board. This picture was taken with the bottom left pin still has soldering issue. It was later fixed.

 

[squeept]

Just killed a 40nm RSX on a SUR-001 that I was hoping to transplant, was impossible to delid - last time I used this much force I actually popped the top off of one of the RAM chips. Worked normally before delid, now 7 second RLOD.

Not sure if this information is helpful due to the cause of failure, but here's the console, and the old, irrelevant parts of the error log removed for easy viewing.

>$ errlog
00000000
# CODE  CLOCK
# A0403034 FFFFFFFF
# A0404411 FFFFFFFF
# A0403034 FFFFFFFF
# A0404411 FFFFFFFF
# A0403034 FFFFFFFF
# A0404411 FFFFFFFF
# A0403034 FFFFFFFF
# A0404411 FFFFFFFF

>$ bringup
00000000
# [SSM] Bringup Start.

>$ bringup
FFFFA605
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9003
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0