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

[marciolsf]

Ok, so I've done and measured the resistance points on my board, finally. Other than the RSX ones, they're all within tolerances. The RSX points are a little further away until you get to VDDR, which is +80ohms above the values. Probably not by coincidence, this is also where BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS maps to. Taking a very close look with my phone's camera (not shown here, this image is Felix's original), that corner looks pretty grimy with flux residue... some of it might've been from my own work at replacing the caps. I'm going to try and clean that up and see if that improves the resistance, mostly out of science and because @RIP-Felix noticed that when working on his own boards

 

[Workz_777]

ok, so I hooked up my cecha01 again. I was having issues at first because I forgot I left it with internal mode enabled, so I was using the incorrect python parameters...

Then next I had to go lookup the commands, and wow, it's been a long time since I've last looked them up. The wiki has changed a lot! There's a ton of new info, that's awesome.

Anyway, here's some of my stats. I was surprised at my becount! I wonder how much of that was me just testing it over and over again over the last 2 years since it died

>$ becount
becount
Bringup : 5644 times
Shutdown: 5604 times
Power-on: 351day 23hour 13min 15sec

And sure enough, my errlog is filled with these guys (don't mind the clock, the battery is unplugged)

Spoiler: error codes

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

While poking around and getting refamiliarized, I ran eepcsum, and was surprised at the errors I got

>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff

I had to run the initial patch to enable internal mode, that's nothing new, but then we do fix it afterwards... I don't remember seeing these errors in the past. Is this to be expected? (and fixing them would then disable internal mode?). Bring up does work as expected

Spoiler: bringup log

>$ bringup
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
>$
[mullion]$ [POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034

Wow...
Bringup : 5644 times
Shutdown: 5604 times
Power-on: 351day 23hour 13min 15sec

RIP-Felix had one that was like 12,000+ hours (gold medal)

Yours here is like:- ~ 8447 hours (silver medal)

That's a very loved PS3 right there!

 

[RIP-Felix]

PS3 Sabotage
(Selectively disabling the SYSCON power control line to see what Error it produces)​

Part 1:

Thanks to @Computer Booter for conducting these tests. He has a better setup than I do, and more skill with an iron.

Timestamps for the bringup & errorlog of each change:

• 21:34 = Lifted STBY2 Pin 10 (IC6301) = error: 0xb0000004 lv0 not found. No SYSCON errorlog generated.
  
• 33:46 = Lifted CONT Pin 5 (IC6020) = A0022110
• 42:30 = Lifted CONT Pin 5 (IC6013) = A0092113
• 51:33 = Lifted IN_PSV Pin 1 (IC6302) = No Error generated.
  
• 1:09:09 = L6305 removed = 10x A0202120 & 1x A0213013
• 1:24:30 = Lifted Enable Pin 3 (IC3501) = No error. SB Paripheral (perhaps SB UART would reveal something
• 1:33:48 = Lifted EN Pin 3 (IC6305) = A0302203 & A0403034 (SB:RRAC:BX0:BX:FLEXIO_ID)
• 1:45:13 = Lifted Gate Pin 5 (Q6006) = No error.
• 1:50:25 = Lifted CONT Pin 5 (IC6014) = No error.
• 1:57:30 = Lifted EN Pin 3 (IC6011) = 4x A0802203

Part 2:

Timestamps for the bringup & errorlog of each change:

• 23:42 = Lifted CE Pin 3 (IC6012) = No error
  
• 32:08 = Lifted EN Pin 3 (IC6303) = A0213013
• 37:36 = Lifted EN Pin 3 (IC6007) = No error
• 44:00 = Lifted EN Pin 3 (IC6304) = A0313032
  • IC6304 is a BD3504 N-Ch MOSFET driver that we can use to perform the VDDR Voltage Mod (+1.2v --> +0.95V) on a Frankenstein Phat PS3 using a 40nm RSX.
    
    Spoiler: Testing a hypothesis

    We used this result to test a hypothesis. @David Rainer replaced IC6304 on a console exhibiting a A0402101, A0403032, & A0403034. It resolved the 3032 and 2101 errors, initially. Now he did use hot air, which might have flexed the board. BGA false positives are always possible when doing this. Keep that in mind. Then he put the OG back on and it went away also. That made me start thinking BGA. But then started coming back. So then he put the good one back on and we started getting the 2101 again. So the result was inconclusive. What we didn't try, and should have, is replacing the MOSFET (Q6308) this Driver controls! So @David Rainer you should give that a try. There are also a number of discrete SMD's that filter/condition power from that MOSFET so it's suitable to enter the CELL, RSX, and SB. Each have their own filter, where the power branches off. See page 6/45 (CELL), 10/45 (RSX), and 14/45 (SB) on the COK-001 service manual to find the filter caps. You should look for a short in these. BTW: This also means that a BGA defect on RSX, CELL, and/or SB can cause this error! Would have to reflow all three to rule it out. And SB is usually forgotten in this equation. People just assume a dead CPU after a reflow/reball of RSX and CPU doesn't work.
• 50:25 = Lifted EN Pin 3 (IC6019) = No Error
• 58:24 = Lifted EN Pin 3 (IC6017) = 10x A0202120 & 1x A0403034
• 1:05:00 = Lifted EN Pin 3 (IC6008) = A0801701

Here are the above results in context of the SYSCON switch power control Line...

Spoiler: SYSCON Switches (Enable & Control)

SW_0

--> CTL1 Pin 9 (IC6003) --> +5V_MISC

--> If lifted = A0022110​

--> CTL2 Pin 10 (IC6003) --> +3.3V_MISC

--> If lifted = A0093003​

--> STBY2 Pin 10 (IC6301) --> +1.7V_MISC

--> If lifted = Fatal Error Requested by OS. "error: 0xb0000004 lv0 not found" No SYSCON errorlog generated.​

SW_1_A --> CONT Pin 5 (IC6020) --> +3.3V_MK_VDD (IC5001)

--> If lifted = A0022110​

• For Clock Synthesizer

SW_1_B --> CONT Pin 5 (IC6013) --> +2.5V_LREG_XCG_500_MEM

--> If lifted = A0092113​

• Analog Voltage for the core PLL of IC5004, which is an ICS9214 Clock Generator used to support the Rambus XDR memory subsystem and Redwood logic interface.

SW_2

--> IN_PSV Pin 1 (IC6302) --> +1.8V_VDD_MEM (JL9647)

--> If lifted = No error. Console Overheated from no IHS.​

--> BASE for Q6311 --> Gate of Q6312

--> INV1 Pin 1 (IC6301)
--> FB1 Pin 2 (IC6301)

--> +1.8V_RSX_FBVDDQ

--> If L6305 removed = 10x A0202120 & 1x A0213013​

SW_3

--> EN Pin 3 (IC6305)

--> +1.2V_SB_VDDC (JL9648)
--> +1.2V_SB_VDDR (JL9648)

--> If lifted = A0302203 & A0403034 (SB:RRAC:BX0:BX:FLEXIO_ID)​

SW_4_A

--> Base Q3501

--> Enable Pin 3 (IC3501) --> +1.2V_ESW

--> If lifted = No error. SB Paripheral (perhaps SB UART would reveal something)​

--> CONT Pin 5 (IC3502) --> +1.9V_ESW

--> If lifted = ?​

--> Base (Q3502) --> Base (Q3503) --> +3.3V_ESW

--> If lifted = ?​

--> P3_ENABLE PD Pin 93 (IC3503) --> Ethernet Controller

--> If lifted = ?​

SW_4_B

--> Enables Gate Pin 5 (Q6006) --> Enables Gate (Q6008) --> +5V_USB

--> If lifted = No error.​

--> CONT Pin 5 (IC6014) --> +1.8V_SB_PERI

--> If lifted = No error.​

--> EN Pin 3 (IC6011) --> +2.5V_SB_PLL_VDDC

--> If lifted = 4x A0802203​

SW_5_A

--> Enable Pin 29 (IC6201)

--> PWM Pin 3 (IC6202) --> +1.2V_RSX_VDDC (JL6205/6)
--> PWM Pin 3 (IC6203) --> +1.2V_RSX_VDDC (JL6207/8)​

SW_5_B

--> Enable Pin 3 (IC6200)

--> Gate Pin 4 (Q6200) --> +1.2V_RSX_VDDR (JL9651)

--> If lifted = A0403034 (BitTraining RSX:RRAC:BX0:BX:FlexIO_ID)​

SW_6

--> CE Pin 3 (IC6012) --> +1.2V_MC2_VDDIO

--> If lifted = No error​

--> EN Pin 3 (IC6303) --> +1.2V_YC_RC_VDDIO (JL9652)

--> If lifted = A0213013​

SW_7_A

--> Enable Pin 29 (IC6103)

--> PWM Pin 3 (IC6004) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6005) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6006) --> +1.0V_BE_VDDC​

SW_8_A

--> EN Pin 3 (IC6007) --> +1.6V_BE_VDDA (JL9654)

--> If lifted = No error​

--> EN Pin 3 (IC6304) --> +1.5V_YC_RC_VDDA (JL9655)

--> If lifted = A0313032​

SW_8_B

-->EN Pin 3 (IC6019) --> +1.5V_AVCG_VDDIO (IC2102)

--> If lifted = No error​

--> EN Pin 3 (IC6017) --> +1.5V_RSX_VDDIO

--> If lifted = 10x A0202120 & 1x A0403034
​

SW_8_C

--> EN Pin 3 (IC6008) --> +1.8V_RSX_PLL_VDD

--> If lifted = A0801701​

--> STBY1 Pin 9 (IC6301) --> +1.8V_RSX_FBVDDQ

--> If lifted = ? (A0232102 suspected. Needs verified)​

I'll edit this later with results and comments as we continue with the tests. I'll also include the YT videos as we do them. It's a nice way to record how the console behaves with each error! I will update this post as I get time to analyze the results and come up with theories.

I suggest using the above in conjunction with Power Control Topology Part 2 and the COK-001 Service Manual to understand what we're doing.

 

[marciolsf]

PS3 Sabotage
(Selectively disabling the SYSCON power control line to see what Error it produces)​

Part 1:

Thanks to @David Rainer (AKA, Computer Booter on YT) for conducting these tests. He has a better setup than I do, and more skill with an iron.

Timestamps for the bringup & errorlog of each change:

• 21:34 = Lifted STBY2 Pin 10 (IC6301) = error: 0xb0000004 lv0 not found. No SYSCON errorlog generated.
  
• 33:46 = Lifted CONT Pin 5 (IC6020) = A0022110
• 42:30 = Lifted CONT Pin 5 (IC6013) = A0092113
• 51:33 = Lifted IN_PSV Pin 1 (IC6302) = No Error generated.
  
• 1:09:09 = L6305 removed = 10x A0202120 & 1x A0213013
• 1:24:30 = Lifted Enable Pin 3 (IC3501) = No error. SB Paripheral (perhaps SB UART would reveal something
• 1:33:48 = Lifted EN Pin 3 (IC6305) = A0302203 & A0403034 (SB:RRAC:BX0:BX:FLEXIO_ID)
• 1:45:13 = Lifted Gate Pin 5 (Q6006) = No error.
• 1:50:25 = Lifted CONT Pin 5 (IC6014) = No error.
• 1:57:30 = Lifted EN Pin 3 (IC6011) = 4x A0802203

After that we moved on to his Frankenstein Phat, which is having HDMI issues. Didn't figure it out.

Here are the above results in context of the SYSCON switch power control Line...

Spoiler: SYSCON Switches (Enable & Control)

SW_0

--> CTL1 Pin 9 (IC6003) --> +5V_MISC

--> If lifted = A0022110​

--> CTL2 Pin 10 (IC6003) --> +3.3V_MISC

--> If lifted = A0093003​

--> STBY2 Pin 10 (IC6301) --> +1.7V_MISC

--> If lifted = Fatal Error Requested by OS. "error: 0xb0000004 lv0 not found" No SYSCON errorlog generated.​

SW_1_A --> CONT Pin 5 (IC6020) --> +3.3V_MK_VDD (IC5001)

--> If lifted = A0022110​

• For Clock Synthesizer

SW_1_B --> CONT Pin 5 (IC6013) --> +2.5V_LREG_XCG_500_MEM

--> If lifted = A0092113​

• Analog Voltage for the core PLL of IC5004, which is an ICS9214 Clock Generator used to support the Rambus XDR memory subsystem and Redwood logic interface.

SW_2

--> IN_PSV Pin 1 (IC6302) --> +1.8V_VDD_MEM (JL9647)

--> If lifted = No error. Console Overheated from no IHS.​

--> BASE for Q6311 --> Gate of Q6312

--> INV1 Pin 1 (IC6301)
--> FB1 Pin 2 (IC6301)

--> +1.8V_RSX_FBVDDQ

--> If L6305 removed = 10x A0202120 & 1x A0213013​

SW_3

--> EN Pin 3 (IC6305)

--> +1.2V_SB_VDDC (JL9648)
--> +1.2V_SB_VDDR (JL9648)

--> If lifted = A0302203 & A0403034 (SB:RRAC:BX0:BX:FLEXIO_ID)​

SW_4_A

--> Base Q3501

--> Enable Pin 3 (IC3501) --> +1.2V_ESW

--> If lifted = No error. SB Paripheral (perhaps SB UART would reveal something)​

--> CONT Pin 5 (IC3502) --> +1.9V_ESW

--> If lifted = ?​

--> Base (Q3502) --> Base (Q3503) --> +3.3V_ESW

--> If lifted = ?​

--> P3_ENABLE PD Pin 93 (IC3503) --> Ethernet Controller

--> If lifted = ?​

SW_4_B

--> Enables Gate Pin 5 (Q6006) --> Enables Gate (Q6008) --> +5V_USB

--> If lifted = No error.​

--> CONT Pin 5 (IC6014) --> +1.8V_SB_PERI

--> If lifted = No error.​

--> EN Pin 3 (IC6011) --> +2.5V_SB_PLL_VDDC

--> If lifted = 4x A0802203​

SW_5_A

--> Enable Pin 29 (IC6201)

--> PWM Pin 3 (IC6202) --> +1.2V_RSX_VDDC (JL6205/6)
--> PWM Pin 3 (IC6203) --> +1.2V_RSX_VDDC (JL6207/8)​

SW_6

--> CE Pin 3 (IC6012) --> +1.2V_MC2_VDDIO

--> If lifted = ?​

--> EN Pin 3 (IC6303) --> +1.2V_YC_RC_VDDIO (JL9652)

--> If lifted = ?​

SW_7_A

--> Enable Pin 29 (IC6103)

--> PWM Pin 3 (IC6004) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6005) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6006) --> +1.0V_BE_VDDC​

SW_8_A

--> EN Pin 3 (IC6007) --> +1.6V_BE_VDDA (JL9654)

--> If lifted = ?​

--> EN Pin 3 (IC6304) --> +1.5V_YC_RC_VDDA (JL9655)

--> If lifted = ?​

SW_8_B

-->EN Pin 3 (IC6019) --> +1.5V_AVCG_VDDIO (IC2102)

--> If lifted = ?​

--> EN Pin 3 (IC6017) --> +1.5V_RSX_VDDIO

--> If lifted = ?​

SW_8_C

--> EN Pin 3 (IC6008) --> +1.8V_RSX_PLL_VDD

--> If lifted = ?​

--> STBY1 Pin 9 (IC6301)​

I'll edit this later with results and comments as we continue with the tests. I'll also include the YT videos as we do them. It's a nice way to record how the console behaves with each error! I will update this post as I get time to analyze the results and come up with theories.

I suggest using the above in conjunction with Power Control Topology Part 2 and the COK-001 Service Manual to understand what we're doing.

I was confused as to why lifting pin 3 on IC6305 caused a flexio_id error, since that's controlling southbridge voltages, but then i went back and reread the error

SB:RRAC:BX0:BX:FLEXIO_ID

I didn't realize before, but it makes sense that the southbridge is also connected through flexio. It's also interesting that it can't find an id, similar I guess to the errors you were getting with the rsx.

 

[Computer Booter]

PS3 Sabotage
(Selectively disabling the SYSCON power control line to see what Error it produces)​

Part 1:

Thanks to @David Rainer (AKA, Computer Booter on YT) for conducting these tests. He has a better setup than I do, and more skill with an iron.

Timestamps for the bringup & errorlog of each change:

• 21:34 = Lifted STBY2 Pin 10 (IC6301) = error: 0xb0000004 lv0 not found. No SYSCON errorlog generated.
  
• 33:46 = Lifted CONT Pin 5 (IC6020) = A0022110
• 42:30 = Lifted CONT Pin 5 (IC6013) = A0092113
• 51:33 = Lifted IN_PSV Pin 1 (IC6302) = No Error generated.
  
• 1:09:09 = L6305 removed = 10x A0202120 & 1x A0213013
• 1:24:30 = Lifted Enable Pin 3 (IC3501) = No error. SB Paripheral (perhaps SB UART would reveal something
• 1:33:48 = Lifted EN Pin 3 (IC6305) = A0302203 & A0403034 (SB:RRAC:BX0:BX:FLEXIO_ID)
• 1:45:13 = Lifted Gate Pin 5 (Q6006) = No error.
• 1:50:25 = Lifted CONT Pin 5 (IC6014) = No error.
• 1:57:30 = Lifted EN Pin 3 (IC6011) = 4x A0802203

After that we moved on to his Frankenstein Phat, which is having HDMI issues. Didn't figure it out.

Here are the above results in context of the SYSCON switch power control Line...

Spoiler: SYSCON Switches (Enable & Control)

SW_0

--> CTL1 Pin 9 (IC6003) --> +5V_MISC

--> If lifted = A0022110​

--> CTL2 Pin 10 (IC6003) --> +3.3V_MISC

--> If lifted = A0093003​

--> STBY2 Pin 10 (IC6301) --> +1.7V_MISC

--> If lifted = Fatal Error Requested by OS. "error: 0xb0000004 lv0 not found" No SYSCON errorlog generated.​

SW_1_A --> CONT Pin 5 (IC6020) --> +3.3V_MK_VDD (IC5001)

--> If lifted = A0022110​

• For Clock Synthesizer

SW_1_B --> CONT Pin 5 (IC6013) --> +2.5V_LREG_XCG_500_MEM

--> If lifted = A0092113​

• Analog Voltage for the core PLL of IC5004, which is an ICS9214 Clock Generator used to support the Rambus XDR memory subsystem and Redwood logic interface.

SW_2

--> IN_PSV Pin 1 (IC6302) --> +1.8V_VDD_MEM (JL9647)

--> If lifted = No error. Console Overheated from no IHS.​

--> BASE for Q6311 --> Gate of Q6312

--> INV1 Pin 1 (IC6301)
--> FB1 Pin 2 (IC6301)

--> +1.8V_RSX_FBVDDQ

--> If L6305 removed = 10x A0202120 & 1x A0213013​

SW_3

--> EN Pin 3 (IC6305)

--> +1.2V_SB_VDDC (JL9648)
--> +1.2V_SB_VDDR (JL9648)

--> If lifted = A0302203 & A0403034 (SB:RRAC:BX0:BX:FLEXIO_ID)​

SW_4_A

--> Base Q3501

--> Enable Pin 3 (IC3501) --> +1.2V_ESW

--> If lifted = No error. SB Paripheral (perhaps SB UART would reveal something)​

--> CONT Pin 5 (IC3502) --> +1.9V_ESW

--> If lifted = ?​

--> Base (Q3502) --> Base (Q3503) --> +3.3V_ESW

--> If lifted = ?​

--> P3_ENABLE PD Pin 93 (IC3503) --> Ethernet Controller

--> If lifted = ?​

SW_4_B

--> Enables Gate Pin 5 (Q6006) --> Enables Gate (Q6008) --> +5V_USB

--> If lifted = No error.​

--> CONT Pin 5 (IC6014) --> +1.8V_SB_PERI

--> If lifted = No error.​

--> EN Pin 3 (IC6011) --> +2.5V_SB_PLL_VDDC

--> If lifted = 4x A0802203​

SW_5_A

--> Enable Pin 29 (IC6201)

--> PWM Pin 3 (IC6202) --> +1.2V_RSX_VDDC (JL6205/6)
--> PWM Pin 3 (IC6203) --> +1.2V_RSX_VDDC (JL6207/8)​

SW_6

--> CE Pin 3 (IC6012) --> +1.2V_MC2_VDDIO

--> If lifted = ?​

--> EN Pin 3 (IC6303) --> +1.2V_YC_RC_VDDIO (JL9652)

--> If lifted = ?​

SW_7_A

--> Enable Pin 29 (IC6103)

--> PWM Pin 3 (IC6004) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6005) --> +1.0V_BE_VDDC
--> PWM Pin 3 (IC6006) --> +1.0V_BE_VDDC​

SW_8_A

--> EN Pin 3 (IC6007) --> +1.6V_BE_VDDA (JL9654)

--> If lifted = ?​

--> EN Pin 3 (IC6304) --> +1.5V_YC_RC_VDDA (JL9655)

--> If lifted = ?​

SW_8_B

-->EN Pin 3 (IC6019) --> +1.5V_AVCG_VDDIO (IC2102)

--> If lifted = ?​

--> EN Pin 3 (IC6017) --> +1.5V_RSX_VDDIO

--> If lifted = ?​

SW_8_C

--> EN Pin 3 (IC6008) --> +1.8V_RSX_PLL_VDD

--> If lifted = ?​

--> STBY1 Pin 9 (IC6301)​

I'll edit this later with results and comments as we continue with the tests. I'll also include the YT videos as we do them. It's a nice way to record how the console behaves with each error! I will update this post as I get time to analyze the results and come up with theories.

I suggest using the above in conjunction with Power Control Topology Part 2 and the COK-001 Service Manual to understand what we're doing.

Very nice, rewatched the video of the Frankie and it was working with HDD and HDMI prior to ultrasonic and scrub so I'm betting I damaged or knocked something off. Will be going live soon might take another look

Great work on those errors I can't wait for more


Sent from my iPhone using Tapatalk

 

[Dynamik1]

Good Day to you all. I am new to this forum, however i have been reading posts from this forum for many months.

First of all a big many thanks for the OP and @RIP-Felix for his awesome guide logging into the SISCON running the internal commands, and it all worked first time.

Right so basically i have about 6 x BC consoles all YLOD, the majority of them have the RSX error code so they have been placed in a pile to fix later.

I am currently working on another with board COK-002, 2 sec YLOD the original error log is as follows.

C:\Users\dynam\Desktop\ps3syscon-master\ps3syscon-master>python ps3_syscon_uart_script.py COM6 CXR
>$ AUTH
Auth successful
>$ ERRLOG
F0000006
>$ ERRLOG GET 00
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 1B
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 1C
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 1D
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 1E
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
>$

Error codes show A0093003 - POWER FAIL, A0071004 - AC/DC POWER FAIL, A0081001 - BE VRAM POWER FAIL

I then proceeded to run command bringup, and it worked but i was suprised to see the consoled stayed on for at least 10 seconds before beeping and showing YLOD. BTW no BD on SD card reader or bluetooth card installed at time of test.

This is the bringup log and powerstate whilst it was on:

>$ 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
>$ 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
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
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]$
>$ errlog
[SSM] RSX Interrupt : Detected !
RSX SY_IES register (0x0008) = 0x4000
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SSM] *** NON-FATAL EVENT received while fataldown/fataloff, ignored. ***
[SSM] *** NON-FATAL EVENT received while fataldown/fataloff, ignored. ***
[ERROR]: 0xa0801802
[ERROR]: 0xa08014ff
[ERROR]: 0xa0801701
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
errlog
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xa0093003, clock:0xffffffff
ofst[ 80]:err_code:0xa0071004, clock:0xffffffff
ofst[ 84]:err_code:0xa0081001, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0071004, clock:0xffffffff
ofst[ 96]:err_code:0xa0081001, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0071004, clock:0xffffffff
ofst[108]:err_code:0xa0081001, clock:0xffffffff
ofst[112]:err_code:0xa0093003, clock:0xffffffff
ofst[116]:err_code:0xa0071004, clock:0xffffffff
ofst[120]:err_code:0xa0081001, clock:0xffffffff
ofst[124]:err_code:0xa0093003, clock:0xffffffff
ofst[ 0]:err_code:0xa0071004, clock:0xffffffff
ofst[ 4]:err_code:0xa0081001, clock:0xffffffff
ofst[ 8]:err_code:0xa0093003, clock:0xffffffff
ofst[ 12]:err_code:0xa0071004, clock:0xffffffff
ofst[ 16]:err_code:0xa0081001, clock:0xffffffff
ofst[ 20]:err_code:0xa0093003, clock:0xffffffff
ofst[ 24]:err_code:0xa0071004, clock:0xffffffff
ofst[ 28]:err_code:0xa0081001, clock:0xffffffff
ofst[ 32]:err_code:0xa0093003, clock:0xffffffff
ofst[ 36]:err_code:0xa0071004, clock:0xffffffff
ofst[ 40]:err_code:0xa0081001, clock:0xffffffff
ofst[ 44]:err_code:0xa0093003, clock:0xffffffff
ofst[ 48]:err_code:0xa0071004, clock:0xffffffff
ofst[ 52]:err_code:0xa0081001, clock:0xffffffff
ofst[ 56]:err_code:0xa0093003, clock:0xffffffff
ofst[ 60]:err_code:0xa0801802, clock:0x0b488694 2005/12/31 00:00:20
ofst[ 64]:err_code:0xa08014ff, clock:0x0b488694 2005/12/31 00:00:20
ofst[ 68]:err_code:0xa0801701, clock:0x0b488694 2005/12/31 00:00:20
[mullion]$
>$ becount
becount
Bringup : 1662 times
Shutdown: 1575 times
Power-on: 102day 18hour 50min 31sec
[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:0x21e2
>$

So as power looked like it was getting to both the CELL & BE but shut off after 10 seconds i proceeded to replace the TOKINS with tantalum as my assumption was the TOKINS were unable to keep the power flowing to the requested lines. The resistance on all four CELL TOKINS were between 6 - 7 ohms and the RX was 3 - 5 ohms. This was the only thing i could think of at the time.

I replaced the two next to the CELL BE on the bottom side and one on the top side and retried the poweron cammand and now get the following bringup log:

C:\Users\dynam\Desktop\ps3syscon-master\ps3syscon-master>ps3_syscon_uart_script.py COM6 CXRF
>$ AUTH
Auth successful
>$ 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
>$ powerstate
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404432
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
powerstate
ATA Power : OFF
PCI Power : OFF
(PowerOff State) (Fatal)
RSX Power : OFF
XDR Power : OFF
Eurus Power : OFF
SB Power : OFF
RSX Thermal Sensor : UNAVAILABLE
BE Thermal Sensor : UNAVAILABLE
[mullion]$
>

So now i am getting errors on the RSX that were not there previously. Is this due to the fact i did not remove all 4 TOKINS on the CELL side so the RSX is unable to communicate with the CELL competely.

I would appreciate any help and advice you an provide. i am trying to repair this for my daughter so she can have her very on first PS3 - obviously in my mind the BC are the best even though they are beasts.

BTW how do you clear the error log so it just brings up the new ones?

 

[ElGris]

@M4j0r @sandungas @RIP-Felix @ElGris @Pacorretaco @DeadEnd @David Rainer
I want some opinions after you guys watch those videos and explain what is wrong inside rsx , I know is faulty unstable one but how is that possible by hardware adding that.
So it was in the begin 5,4 ohms on vddc onboard ,pulled out of board rsx got 5,2 ohms ,after reball left 2 days, got 8 ohms no boot ,added that 2,2 ohms resistor and work!
http://s.go.ro/rxixxzkw
Also 4,4 ohms will drop to 2,7 ohms around .Still boot.Ill just desolder and left in cold enviroment like 20 another day to see if resistance is increased and work back without any parallel resistor.

Are you normally used to do this kind of checks and "fixes" Victor?

Delid and see if everything is normal. I can't help in the electronic side, and @RIP-Felix already left his comments

Bonus:

 

[vyktormvmpay25]

I wanted to show more to people that even slims can die unexpected, just for people interested to fix BC ps3 with 40nm we better pick good working slims before desolder and port it on BC model. Also to many reballs one rsx can make his internal thermal config high instead low. Just anyone can tell his opinion

 

[RIP-Felix]

Good Day to you all. I am new to this forum, however i have been reading posts from this forum for many months.

First of all a big many thanks for the OP and @RIP-Felix for his awesome guide logging into the SISCON running the internal commands, and it all worked first time.

Right so basically i have about 6 x BC consoles all YLOD, the majority of them have the RSX error code so they have been placed in a pile to fix later.

I am currently working on another with board COK-002, 2 sec YLOD the original error log is as follows.

C:\Users\dynam\Desktop\ps3syscon-master\ps3syscon-master>python ps3_syscon_uart_script.py COM6 CXR
>$ AUTH
Auth successful
>$ ERRLOG
F0000006
>$ ERRLOG GET 00
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 01
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 02
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 03
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 04
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 05
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 06
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 07
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 08
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 09
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 0A
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 0B
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 0C
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 0D
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 0E
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 0F
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 10
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 11
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 12
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 13
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 14
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 15
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 16
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 17
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 18
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 19
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 1A
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 1B
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 1C
00000000 A0081001 FFFFFFFF
>$ ERRLOG GET 1D
00000000 A0071004 FFFFFFFF
>$ ERRLOG GET 1E
00000000 A0093003 FFFFFFFF
>$ ERRLOG GET 1F
00000000 FFFFFFFF FFFFFFFF
>$

Error codes show A0093003 - POWER FAIL, A0071004 - AC/DC POWER FAIL, A0081001 - BE VRAM POWER FAIL

I then proceeded to run command bringup, and it worked but i was suprised to see the consoled stayed on for at least 10 seconds before beeping and showing YLOD. BTW no BD on SD card reader or bluetooth card installed at time of test.

This is the bringup log and powerstate whilst it was on:

>$ 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
>$ 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
[INFO]: Connecting to Debug Device (SB UART)
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
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]$
>$ errlog
[SSM] RSX Interrupt : Detected !
RSX SY_IES register (0x0008) = 0x4000
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SSM] *** NON-FATAL EVENT received while fataldown/fataloff, ignored. ***
[SSM] *** NON-FATAL EVENT received while fataldown/fataloff, ignored. ***
[ERROR]: 0xa0801802
[ERROR]: 0xa08014ff
[ERROR]: 0xa0801701
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
errlog
ofst[ 72]:err_code:0xffffffff, clock:0xffffffff
ofst[ 76]:err_code:0xa0093003, clock:0xffffffff
ofst[ 80]:err_code:0xa0071004, clock:0xffffffff
ofst[ 84]:err_code:0xa0081001, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0071004, clock:0xffffffff
ofst[ 96]:err_code:0xa0081001, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0071004, clock:0xffffffff
ofst[108]:err_code:0xa0081001, clock:0xffffffff
ofst[112]:err_code:0xa0093003, clock:0xffffffff
ofst[116]:err_code:0xa0071004, clock:0xffffffff
ofst[120]:err_code:0xa0081001, clock:0xffffffff
ofst[124]:err_code:0xa0093003, clock:0xffffffff
ofst[ 0]:err_code:0xa0071004, clock:0xffffffff
ofst[ 4]:err_code:0xa0081001, clock:0xffffffff
ofst[ 8]:err_code:0xa0093003, clock:0xffffffff
ofst[ 12]:err_code:0xa0071004, clock:0xffffffff
ofst[ 16]:err_code:0xa0081001, clock:0xffffffff
ofst[ 20]:err_code:0xa0093003, clock:0xffffffff
ofst[ 24]:err_code:0xa0071004, clock:0xffffffff
ofst[ 28]:err_code:0xa0081001, clock:0xffffffff
ofst[ 32]:err_code:0xa0093003, clock:0xffffffff
ofst[ 36]:err_code:0xa0071004, clock:0xffffffff
ofst[ 40]:err_code:0xa0081001, clock:0xffffffff
ofst[ 44]:err_code:0xa0093003, clock:0xffffffff
ofst[ 48]:err_code:0xa0071004, clock:0xffffffff
ofst[ 52]:err_code:0xa0081001, clock:0xffffffff
ofst[ 56]:err_code:0xa0093003, clock:0xffffffff
ofst[ 60]:err_code:0xa0801802, clock:0x0b488694 2005/12/31 00:00:20
ofst[ 64]:err_code:0xa08014ff, clock:0x0b488694 2005/12/31 00:00:20
ofst[ 68]:err_code:0xa0801701, clock:0x0b488694 2005/12/31 00:00:20
[mullion]$
>$ becount
becount
Bringup : 1662 times
Shutdown: 1575 times
Power-on: 102day 18hour 50min 31sec
[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:0x21e2
>$

So as power looked like it was getting to both the CELL & BE but shut off after 10 seconds i proceeded to replace the TOKINS with tantalum as my assumption was the TOKINS were unable to keep the power flowing to the requested lines. The resistance on all four CELL TOKINS were between 6 - 7 ohms and the RX was 3 - 5 ohms. This was the only thing i could think of at the time.

I replaced the two next to the CELL BE on the bottom side and one on the top side and retried the poweron cammand and now get the following bringup log:

C:\Users\dynam\Desktop\ps3syscon-master\ps3syscon-master>ps3_syscon_uart_script.py COM6 CXRF
>$ AUTH
Auth successful
>$ 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
>$ powerstate
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404432
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
powerstate
ATA Power : OFF
PCI Power : OFF
(PowerOff State) (Fatal)
RSX Power : OFF
XDR Power : OFF
Eurus Power : OFF
SB Power : OFF
RSX Thermal Sensor : UNAVAILABLE
BE Thermal Sensor : UNAVAILABLE
[mullion]$
>

So now i am getting errors on the RSX that were not there previously. Is this due to the fact i did not remove all 4 TOKINS on the CELL side so the RSX is unable to communicate with the CELL competely.

I would appreciate any help and advice you an provide. i am trying to repair this for my daughter so she can have her very on first PS3 - obviously in my mind the BC are the best even though they are beasts.

BTW how do you clear the error log so it just brings up the new ones?

The 80 1802 is an RSX initialization error (1802) occuring during the power on state (step# 80). I wrote some about it here. Your log called it, "RSX Interrupt : Detected!"It even provides details, "RSX SY_IES register (0x0008) = 0x4000." @M4j0r @sandungas are the programming gurus, I'm not sure about memory addresses and such. So manybe they can provide more insight about what it's complaining about there.

When 1802s occur at step# 20, I associate them with a dead RSX. That's because step# 20 is when the RSX is first initialized. If it doesn't initialize then, it's dead. However, your 1802 is only occuring after the console has booted (step# 80) and is associated with the BE Attention (1701) alarm raised when a Checkstop error (14FF) occured. That makes sense because the CPU couldn't continue with it's process when the RSX interrupt occured.

A checkstop occurs when - usually a processor but sometimes a cache, memory, or I/O bus controller - determines that something is in an "impossible" state. An error occurs that cannot be isolated to a particular bus transfer in progress, or a processor detects no progress being made...Checkstops are inherently hardware phenomena. They do not necessarily indicate a solid failure of a component, so diagnostics will rarely determine that a problem exists.

We've seen this error a lot. The common story between them was the console was on at the time the YLOD occurred. All subsequent attempt to start the console resulted in a GLOD with subsequent 1601/1701 errors, or a YLOD within 2 seconds. SYSCON errors usually show one A0801601/A0801701 occurring at the same timestamp, followed thereafter by 3034/4xxx errors for all subsequent attempts to PWR it on. Or it'll GLOD and throw more 1701/1601's or 14FF's. I think this means there is a precarious BGA defect teetering on the edge of breaking and it'll soon switch back to 3034/4xxx like the others. But that's a guess.

Since your 3034/4432 errors appeared just as predicted, I would suspect the RSX has either bad BGA/bumps or died. We can test that theory by ohm testing the following voltage lines and seeing if they all check out...

These were taken from a board that's currently working, althought not thoroughly tested.

If any of those read close to a short, then you'll need to remove and replace the RSX. If they all test fine, you may be able to fix it with a reball. Just ohm test the RSX off the board to be sure it hasn't died before balling it. But if you have to remove the RSX anyway, you may as well just replace the 90nm RSX with a more reliable 65nm or 40nm (now that we know how to do it).

 

[Cypha]

Got some error codes from 2 ps3 bc 4usb boards are cok-002 the one with 3034 and 4401 consistent what would you say is a fix for this reball or a rsx replacement etc as this one has been untouched just pulled the warranty sticker of and soldered for syscon readings, and as for the other one with multiple error codes i have a feeling its a dead cell brought it without warranty sticker and has been delidded (not by me) with the cell having a tiny graze but doesnt look like it's damaged anything as isnt a deep scratch as is near to no traces, let me know what your thoughts are on these and if youve have same error log and the repair that you carried out for it to work thinking of reballing but will wait patiently for your opinions

 

[alty75]

So a bootOS issue was my first thought, but I wanted to make sure it wasnt something easier first.

So yeah, this looks like a FW corruption. This kind of error doesnt generate a syscon error and the reason you only get FFFFFFFF in the log is because your console has never had any errors.

Afraid you'll have to try a hardware flasher to reinstall the OS FW.

Edit: can you post the csum results. csum checks the FW checksum. It mat return a mismatch if Im correct that the FW is corrupt.

I have a SEM-001 I have attempted a Frankenstein on with a 65nm RSX. Just as an experiment.
I removed and swapped out the same resisitors and adjusted the syscon to suit.
bringup produces a ylod after the reset beep with the "[SSM] *** FATAL ERROR requested by OS *** " error but does not throwe an error into the "errlog".
I changed the syscon back to make it think it had a 90nm RSX onboard and it threw an error to the errlog( 3034/4002) which was to be expected.
Change the syscon back to tell it it has a 65nm RSX and it keeps yellow lighting with no error log with the [SSM] *** FATAL ERROR requested by OS ***
It has me intrigued as to wether the SEM-001 board cannot handle the franky mod,I would expect it to be able to if done correctly.
Anyway I am going to put a 90nm back on it tomorrow and readjust everything else and see if it boots as standard.

 

[alty75]

You could try to switch the firmware bank via the syscon eeprom flag to see if it'll at least boot the other firmware bank.

Can you show me the post where I can try this please

 

[alty75]

Got some error codes from 2 ps3 bc 4usb boards are cok-002 the one with 3034 and 4401 consistent what would you say is a fix for this reball or a rsx replacement etc as this one has been untouched just pulled the warranty sticker of and soldered for syscon readings, and as for the other one with multiple error codes i have a feeling its a dead cell brought it without warranty sticker and has been delidded (not by me) with the cell having a tiny graze but doesnt look like it's damaged anything as isnt a deep scratch as is near to no traces, let me know what your thoughts are on these and if youve have same error log and the repair that you carried out for it to work thinking of reballing but will wait patiently for your opinions

lift it and test the ohm circuit,if it tests good,reball and reattach
low ohm then repplace it

 

[M4j0r]

I have a SEM-001 I have attempted a Frankenstein on with a 65nm RSX. Just as an experiment.
I removed and swapped out the same resisitors and adjusrted the syscon to suit.
bringup produces a ylod after the reste beep wit the "[SSM] *** FATAL ERROR requested by OS *** " error but does not throwe an error into the "errlog".
I changed the syscon back to make it think it had a 90nm RSX onboard and it threw an error to the errlog( 3034/4002) which was to be expected.
Change the syscon back to tellit it has a 65nm RSX and it keeps yelloe lighting with no error log with the [SSM] *** FATAL ERROR requested by OS ***
It has me intrigued as to wether the SEM-001 board cannot handle the franky mod,I would expect it to be able to if done correctly.
Anyway I am going to put a 90nm back on it tomorrow and readjust everything else and see if it boots as standard.

That error is not related to the RSX, the 203GB syscon supports this mod - the error has to be somewhere else.

Can you show me the post where I can try this please

Boot banks only work on NOR consoles (https://www.psdevwiki.com/ps3/SC_EEPROM 0x48C42+).

 

[RIP-Felix]

I have a SEM-001 I have attempted a Frankenstein on with a 65nm RSX. Just as an experiment.
I removed and swapped out the same resisitors and adjusrted the syscon to suit.
bringup produces a ylod after the reste beep wit the "[SSM] *** FATAL ERROR requested by OS *** " error but does not throwe an error into the "errlog".
I changed the syscon back to make it think it had a 90nm RSX onboard and it threw an error to the errlog( 3034/4002) which was to be expected.
Change the syscon back to tellit it has a 65nm RSX and it keeps yelloe lighting with no error log with the [SSM] *** FATAL ERROR requested by OS ***
It has me intrigued as to wether the SEM-001 board cannot handle the franky mod,I would expect it to be able to if done correctly.
Anyway I am going to put a 90nm back on it tomorrow and readjust everything else and see if it boots as standard.

You could try adding a 47k resistor to R2002. @botakompong said that sometimes it was needed to fix a GLOD situation. He didn't go into much detail.

 

[Workz_777]

You could try adding a 47k resistor to R2002. @botakompong said that sometimes it was needed to fix a GLOD situation. He didn't go into much detail.

Felix, R2002 is already a 47k resistor, so do you mean add a 47k resistor to r2001 (currently not used), or add another 47k resistor in series to r2002 on the other side? Sorry, i'm asking because i too have a couple SEM-001 and have ordered both 40nm and 65nm RSX for them, so was wondering just in case i have same symptoms.

 

[marciolsf]

After cleaning my board with a few cycles of electronic cleaner and 91% IPA, my VDDR resistance went up from 380 to 450... lol!

@RIP-Felix what exactly is that point measuring?

 

[RIP-Felix]

Felix, R2002 is already a 47k resistor, so do you mean add a 47k resistor to r2001 (currently not used), or add another 47k resistor in series to r2002 on the other side? Sorry, i'm asking because i too have a couple SEM-001 and have ordered both 40nm and 65nm RSX for them, so was wondering just in case i have same symptoms.

View attachment 36459

Huh, well I'm not as familiar with the SEM-001 as I am with the COK-00X. COK-002 doesn't have either populated, COK-001 has both. So I was assuming SEM were like the COK-002.

Anyway, it was a longshot. I didn't really think that was it, but thought I'd mention it just in case.

 

[ElGris]

First time posting logs over here, finally!! lol

Well, I mentioned somewhere that I had a couple of mobos having GLOD issues, those that @RIP-Felix and @vyktormvmpay25 call "special GLOD". I didn't find anything wierd (until now) on these mobos, it wasn't the Panasonic HDMI this time provoking this GLOD, and I have to mention, these two act different.
A doubt that I have is if powerstate only shows you the stages that the CELL turned on, or if it's really trying to show you everything that should be running without issue, because I get WLAN: ON even when the console is turned off, and both are missing the wifi module. If this is a false positive, it really sucks. Because I don't know if both SB are dead, or if some of the ram modules are, this due the string I get on becount "![ERROR]: 0xb000200d (FATAL) XDR Link not initilized."

Well, to summary this: MSX/GLOD/turns off at 45 seconds without red light after boot.

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

Spoiler: MSX

>$ ERRLOG
00000000
# CODE CLOCK
# A0801005 FFFFFFFF No energy abruptly
# A0801004 FFFFFFFF Power AC/DC 1004
# A0805FFF FFFFFFFF Turns off by itself 5FFF
# A0003001 FFFFFFFF 12v Power Failure 3001
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 264717AE
# A0805FFF 26471768
# A0805FFF 26431EDA
# A0805FFF 26431EA3
# A0805FFF 261783C8
# A0805FFF 26177860
# A0805FFF 261777DA
# A0805FFF 2617775A
# A0805FFF 2477716B
# A0805FFF 2477711F



>$ ERRLOG
00000000
# CODE CLOCK
# A0801200 FFFFFFFF
# A0801005 FFFFFFFF
# A0801004 FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 264717AE
# A0805FFF 26471768
# A0805FFF 26431EDA
# A0805FFF 26431EA3
# A0805FFF 261783C8
# A0805FFF 26177860
# A0805FFF 261777DA
# A0805FFF 2617775A
# A0805FFF 2477716B

>$ becount
F0000003
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [UCMD] Unknown command.

>$ bringup
00000000
# [SSM] Bringup Start.

>$
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.2.0
#!(Build ID: 4809,49233,
#!Build Date: 2012-06-12_21:19:37)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!

>$ powerstate
FFFFFFFF Answer length
>$ powerstate
00000000
#!0000
#!0000
#!
#!PTC_DUMP
#!0000
#!0000
#!0000
#!0000
#!0000
# ATA :ON
# PCI :OFF
# PCIex:OFF
# RSX :ON
# GDDR :ON
# XDR :ON
# EURUS:ON
# SB :ON
# LAN :ON
# WLAN :ON
OK 00000000
#!0000
#!0000
#!0a0c
#!0a70
#!0000
#!0000
#!09c3
#!0a2e
#!0000
#!0000
#!09d0
#!0a31
#!0000
#!0000
#!09c5
#!0a31
#!0000
#!0000
#!09cd
#!0a34
#!0000
#!0000
#!0a0f
#!0a73
#!0000
#!0000
#!09f5
#!0a5a
#!0000
#!0000
#!09f2
#!0a54
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!09eb
#!0a52
#!0000
#!0000
#!09f5

>$
00000000
#!0a5c
#!0000
#!0000
#!09bd
#!0a24
#!0000
#!0000
#!09ca
#!0a31
#!0000
#!0000
#!09c7
#!0a31
#!0000
#!0000
#!09e1
#!0a42
#!0000
#!0000
#!09d4
#!0a38
#!0000
#!0000
#!09eb
#!0a4c
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0a0a
#!0a74
#!0000
#!0000
#!09e5
#!0a4d
#!0000
#!0000
#!09e4
#!0a4f
#!0000
#!0000
#!09e1
#!0a50
#!0000
#!0000
#!09eb
#!0a54
#!0000
#!0000
#!0a12
#!0a78
#!0000
#!0000
#!09d9
#!0a39
#!0000
#!0000
#!0a0b
#!0a72
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0a19
#!0a80
#!0000
#!0000
#!0a16
#!0a7d
#!0000
#!0000
#!09da
#!0a43
#!0000
#!0000
#!09e6
#!0a52
#!0000
#!0000
#!09e0
#!0a3e
#!0000
#!0000
#!0a23
#!0a93
#!0000
#!0000
#!0a12
#!0a78
#!0000
#!0000
#!0a25
#!0a92
#!0000
#!0000
#!0000
#!0000
#!
#!MIC_DUMP
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!3200000000000000
#!0000000000000000
#!0000000000000000
#!0000000fffffff80
#!0000000000012000
#!0000000000100000
#!8000000000000000
#!0000000000000000
#!0800000000000000
#!0800000000000000
#!0000000000000000
#!0000000000000000
#!ffc0000000000000
#!6040000000000000
#!00e0000000000000
#!6284055ad6b00000
#!5d70000000000000
#!7180021000000000
#!0a963d6000000000
#!edd61229594ba6b4
#!0000000000000000
#!1b87000000000000
#!0481000000000000
#!0100000000000000
#!c800000000000000
#!0000000000000000
#!0000100000000000
#!0000000000000000
#!1b87000000000000
#!0481000000000000
#!0100000000000000
#!c800000000000000
#!0000000000000000
#!0000100000000000
#!0000000000000000
#!6040000000000000
#!00e0000000000000
#!6284055ad6b00000
#!5d70000000000000
#!7180021000000000
#!0a963d6000000000
#!edd61229594ba6b4
#!0000000000000000
#!8000000000000000
#!0000000000000000
#!0800000000000000
#!0800000000000000
#!0000000000000000
#!0000000000000000
#!ffc0000000000000
#!0611017000000000
#!4000000000000000
#!7cfe000000000000
#!e1c0000000000000
#!0000000000000000
#!0000000000000000
#!0000fd4000000000
#!0000028000000000
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!0000000000000000
#!0000000000000013
#!0000000000000000
#!
#!XIO_DUMP
#!0001
>$ errlog
00000000

# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0801200 FFFFFFFF
# A0801200 FFFFFFFF
# A0801005 FFFFFFFF
# A0801004 FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 264717AE
# A0805FFF 26471768
# A0805FFF 26431EDA

>$
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.2.0
#!(Build ID: 4809,49233,
#!Build Date: 2012-06-12_21:19:37)
#!
#!Copyright(C) 2012 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![ERROR]: 0xb0002001 (FATAL) XDR Link not initilized.
#!ITC_DUMP
#!0000

PQX/GLOD/Infinite green light until turn off.

becount: #![ERROR]: 0xb000200d (FATAL) XDR Link not initilized.

Spoiler: PQX

Auth successful
>$ errlog
00000000
# CODE CLOCK
# A0801200 FFFFFFFF 1200 (Thermal CELL)
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF Turns off by itself 5FFF
# A0801005 FFFFFFFF
# A0801002 FFFFFFFF 1002 (Power RSX)
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF 12v Power Failure 3001
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 0F5BBB47
# A0805FFF 0F5BBA7F
# A0805FFF 0E8F81EB
# A0805FFF 0E8F745A
# A0805FFF 0DCF1FEF
# A0805FFF 0DCF1F2E
# A0805FFF 0DCF1A78
# A0805FFF 0DCED6E3
# A0805FFF 0DCED5C3
# A0805FFF 0DCED53C
# A0805FFF 0DCED4B2
# A0805FFF 0DCED415
# A0805FFF 0DCDF454
# A0805FFF 0DCDF3BB
# A0805FFF 0DCDF26E
# A0801601 0DC82D03 BE Livelock Detection 1601
# A0801701 0DC82D02 BE Livelock Detection 1701
# A0802031 0CFBCE91 2031 (Thermal Sensor, RSX)
# A0402131 0CF51B37 2131 (Thermal Sensor, RSX)
# A0402130 0CF51B37 2130 (Thermal Sensor, CELL)
# A0402131 0CF51B34

>$ powerstate
00000000
# ATA :OFF
# PCI :OFF
# PCIex:OFF
# RSX :OFF
# GDDR :OFF
# XDR :OFF
# EURUS:OFF
# SB :OFF
# LAN :OFF
# WLAN :ON

>$ bringup
00000000
# [SSM] Bringup Start.

>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# [UCMD] Unknown command.

>$ powerstate
00000000
# ATA :ON
# PCI :OFF
# PCIex:OFF
# RSX :ON
# GDDR :ON
# XDR :ON
# EURUS:ON
# SB :ON
# LAN :ON
# WLAN :ON

>$ becount
F0000003
# [UCMD] Unknown command.

>$ shutdown
00000000
# [SSM] Shutdown Start.
# [SSM] Shutdown ok.
# (PowerOff State)

>$ becount
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![ERROR]: 0xb000200d (FATAL) XDR Link not initilized.
#!ITC_DUMP
#!0000
#!0000
#!0000
# [UCMD] Unknown command.
NG F0000003
#!0000
#!0000
--------------------------------------------
>$ errlog
00000000
# CODE CLOCK
# A0805FFF FFFFFFFF
# A0801200 FFFFFFFF
# A0801200 FFFFFFFF
# A0805FFF FFFFFFFF
# A0801005 FFFFFFFF
# A0801002 FFFFFFFF
# A0805FFF FFFFFFFF
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF FFFFFFFF
# A0805FFF 0F5BBB47
# A0805FFF 0F5BBA7F
# A0805FFF 0E8F81EB
# A0805FFF 0E8F745A
# A0805FFF 0DCF1FEF
# A0805FFF 0DCF1F2E
# A0805FFF 0DCF1A78
# A0805FFF 0DCED6E3
# A0805FFF 0DCED5C3
# A0805FFF 0DCED53C
# A0805FFF 0DCED4B2
# A0805FFF 0DCED415
# A0805FFF 0DCDF454
# A0805FFF 0DCDF3BB
# A0805FFF 0DCDF26E
# A0801601 0DC82D03
# A0801701 0DC82D02
# A0802031 0CFBCE91
# A0402131 0CF51B37
# A0402130 0CF51B37

>$ bringup
00000000
# [SSM] Bringup Start.

>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 4.5.5
#!(Build ID: 5149,50179,
#!Build Date: 2014-01-28_18:27:23)
#!
#!Copyright(C) 2014 Sony Computer Entertainment Inc.All Rights Reserved.
#!
# [UCMD] Unknown command.

Something to notice, both have almost the same errors on that XDR stage, but they act different. I wanted to change those SBs but it seems rams could be the issue mainly (which they're northbdrige in this case), so what do you thing people?

BTW, both RSX/CELL on both mobos warm like normal. When I had a GLOD due that HDMI chip being damaged, I had no boot on CELL, and question would be, why this fault blocked the CELL?

 

[RIP-Felix]

After cleaning my board with a few cycles of electronic cleaner and 91% IPA, my VDDR resistance went up from 380 to 450... lol!

@RIP-Felix what exactly is that point measuring?

I wish I knew exactly what it is. I do know is that it's the FlexIO refremce voltage for the RSX's digital core logic. What I don't whow is why it needs VDDR, since YC_RC_VDDIO is the same thing, but powering CELL/SB/RSX FlexIO simultaneously.

I suspect it has to do with an ADC internal to the RSX, but we dont have any datasheets or hardware installation guides available for the RSX. It's a black box. It makes sense however, because the RSX needs and ADC for the analog HDMI/DVE and audio signals to be interprited and sent back over the FlexIO to the Cell and SB. Perhaps YC_RC_VDDIO is for CELL/SB --> RSX traffic and VDDR is RSX --> CELL/SB traffic.

I speculate it's so the RSX can be initialized at separate step in power on sequencing. I am still testing this hypothesis. Currently I am using a O-scope to see exactly when each Voltage starts. I will present the timeline along with an interpritation of the SYSCON switches (power control line), and corresponding step# of the errors produced, when @David Rainer and I are finished collecting our Sabotage tests.

I will update that post with more as I get the time to collect data and interprit it. Many moving cogs in that gear.