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

[aldostools]

WARNING TO ALL: Please do not post links to external sites selling goods or services. Please read forum rules:
https://www.psx-place.com/threads/site-forum-rules-guidelines.79/

6.) No Selling / Trading allowed in forums.

• Listings of items for sale or trade is not permitted, there are many avenues that can be used for such transactions, PSX-Place forums is NOT the place for such transactions. This is to protect user's and the website from any potential fraud, If you are seeking something, you are welcome to post about it in the forums to seek help or advice. Then it can be taken privately at your own risk, if there are any potential transaction's taking place.

 

[RIP-Felix]

WARNING TO ALL: Please do not post links to external sites selling goods or services. Please read forum rules:
https://www.psx-place.com/threads/site-forum-rules-guidelines.79/

6.) No Selling / Trading allowed in forums.

• Listings of items for sale or trade is not permitted, there are many avenues that can be used for such transactions, PSX-Place forums is NOT the place for such transactions. This is to protect user's and the website from any potential fraud, If you are seeking something, you are welcome to post about it in the forums to seek help or advice. Then it can be taken privately at your own risk, if there are any potential transaction's taking place.

Serious question, for clearification. This isn't a retort. Does this mean we shouldn't post links to other products on ebay?

I thought the rule was intended to prevent direct sales through psx place, where people don't have buyer protections. I didn't think it applied to linking products and services outside the PSX place. What I'm wondering is how posting a link to a member's ebay frankie service is different than posting a link to thermal paste, or an IC, or professional rework company, mod, a resistor, or my tantalizers, or a dev's donation page? I see that so often I didnt think posting a link to an ebay service wasnt allowed. I'm trying to understand the distinction now, or have we been breaking the rules the whole time?

Sorry if this seems like talking back. I'm just confused.

 

[Oxihixo]

EDIT: I was just looking back over my spreadsheet and found one console that had 3010 after RSX_FBVDDQ was short. Could you check if your's is? Referr to the motherboard Ohms test location in the picture a few posts back.

I just checked RSX_FBVDDQ. It is shorted. Does this mean it's a lost cause and perhaps better suited as a donor? Thank you for your previous replies. I wish I had the electronics knowledge that some of you possess.

 

[RIP-Felix]

No, that's actually good news. It means the effed up RSX reflow could be all that's wrong, besides the tokins.

 

[Polynian]

I had to jog my memory. Looked back over some notes and alot of people are having 3032 errors from bad delids or eraser mods gone wrong. Cracked CPU die and etc. You should inspect the area around the CPU carefully for any SMDs that are out of place and the die itself for any hairline cracks. You could try a pressure test to see if it's just a CPU BGA as well. You could also check that +1.5V_YC_RC_VDDA is present and making it into the CPU. If so it shouldn't be the lack of VDDA causing it.

Thank you so much for your replys i will test it with pressure, but about controlling the rail of +1.5V_YC_RC_VDDA i dont know where its placed or how it looks The motherboard is Sem-001 Cechg04 i searched for it on internet like 5 hours but i cannot found anything except one schematic and that shows its under the cell but i cant find the starting point.

 

[TurboYoda]

Can anyone help me find out the FBVDDQ on my slim CECH 3008B. Board layout is different from this.
RSX - https://imgur.com/a/AFNJLpK

 

[aldostools]

Serious question, for clearification. This isn't a retort. Does this mean we shouldn't post links to other products on ebay?

I thought the rule was intended to prevent direct sales through psx place, where people don't have buyer protections. I didn't think it applied to linking products and services outside the PSX place. What I'm wondering is how posting a link to a member's ebay frankie service is different than posting a link to thermal paste, or an IC, or professional rework company, mod, a resistor, or my tantalizers, or a dev's donation page? I see that so often I didnt think posting a link to an ebay service wasnt allowed. I'm trying to understand the distinction now, or have we been breaking the rules the whole time?

Sorry if this seems like talking back. I'm just confused.

Dear @RIP-Felix
That rule #6 was added recently. Apparently it was initially there, but apparently it was removed (mistakenly??).

As the description in the rule says, the reason of this prohibition is to protect the PSX-PLACE users from external offers that cannot be controlled. The rule can be subjective since it cannot cover all possible cases in a short paragraph. So the decision about external links is at moderator discretion and according to rule #3 the staff has the last word.

If someone need a service or parts can start a private conversation.

@STLcardsWS can provide further information about this subject or correct me if I'm wrong.

Lmao! Well if i cannot advertise my TantalACEr's then why should you be allowed to advertise your Tantaizers lol. All sorts of shenanigans going on atm lol

I'd like to remember you this rule:

8.) No childish behavior (Don't be an annoyance or child-like)

• Post will be removed and/or your posting abilities will be revoked.

 

[RIP-Felix]

Ok, so like github pages, products like resistors and other misellaneous things that are mainstream products is probably fine. But sounds like self promotion of products for sale is probably crossing the line. Well, IG I was linking to someone else's service, not self promoting, but since they're not a mainstream product (like a thermal pad or resistor pack with 100k sales and positive review) it's sketchier.

IG I won't worry about it and just post what I think is fine and let the mods use their discretion. I assume as long as I'm not being a dick about it I don't need to understand the minutia or let fear of posting links prevent me from trying to help. Yawl can sort it out if I accidentlly overstep a rule.

Thanks for the clerification.

 

[Coro]

github pages, products like resistors and other misellaneous things that are mainstream products is probably fine. But sounds like self promotion of products for sale is probably crossing the line.

recommending a mainstream product is okay. i would recommend just saying a brand name and letting them find it is better (so you are not pointing to a specific seller--PM if they need more help). github (or other) hosted gerber files or 3d printing files (or somilar) is probably fine in most cases. the concern is mostly about self-promotion, but not entirely.

 

[Coro]

github pages, products like resistors and other misellaneous things that are mainstream products is probably fine. But sounds like self promotion of products for sale is probably crossing the line.

recommending a mainstream product is okay. i would recommend just saying a brand name and letting them find it is better (so you are not pointing to a specific seller--PM if they need more help). github (or other) hosted gerber files or 3d printing files (or somilar) is probably fine in most cases. the concern is mostly about self-promotion, but not entirely.

 

[JelkoBG]

I can't auth in the syscon in both external and internal mode. I tried soldering the wires and the method without soldering . I tried using only 5v from the psu without plugging the 12v. I checked the 3 diodes under the tx pad and they are good. Any idea what try next?

 

[John_Claymore]

Hello All, Working on a Fat CECH 40GB. Syscon reports a single fault: A0203010 (Cell Thermal Sensor). Anyone had any luck with a repair action for this one?

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

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

becount
Bringup : 2285 times
Shutdown: 2264 times
Power-on: 231day 00hour 17min 45sec
[mullion]$

 

[Oxihixo]

Simple question. On the Sherwood syscon systems, the command "becount" doesn't work. Is there another command that can be used? Help didn't seem to bring up anything useful. Or maybe I'm the one that needs help. Lol.

 

[RIP-Felix]

Inspect the CPU for cracks or trace damage. Has it been delided? Check the area around the CPU for any damaged or missing SMDs.

Check for the presence of voltages.

 

[RIP-Felix]

Simple question. On the Sherwood syscon systems, the command "becount" doesn't work. Is there another command that can be used? Help didn't seem to bring up anything useful. Or maybe I'm the one that needs help. Lol.

For example: If it returns...

0B720A5D00C9B580
0B72 | 0A5D | 00C9B580
Bringups | Shutdowns | Uptime (in seconds)
​

Copy the groups into a hex to decimal converter.

0B72 = 2930 Bringups
0A5D = 2653 Shutdowns
00C9B580 = 13219200 seconds = 153 days of uptime​

 

[sfe4]

please help

i have a CECHA01 have yold wen i heat it up for 5 min and let it cool will work for a week i did that 3 times

Statistics: Boot Count 3125 - Shutdown Count 1223 - Runtime 79d 17h 17mn 4s

Errors (32)

Error 0: 0xA0403034 Time: Mon, 10 Jul 2006 12:38:27 GMT

Error 1: 0xA0404412 Time: Mon, 10 Jul 2006 12:38:27 GMT

Error 2: 0xA0403034 Time: Mon, 10 Jul 2006 11:55:39 GMT

Error 3: 0xA0404412 Time: Mon, 10 Jul 2006 11:55:39 GMT

Error 4: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 5: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 6: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 7: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 8: 0xA0801802 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 9: 0xA0802022 Time: Thu, 29 Jun 2006 22:16:31 GMT

Error 10: 0xA0802022 Time: Thu, 29 Jun 2006 22:15:47 GMT

Error 11: 0xA0403034 Time: Tue, 27 Jun 2006 23:51:29 GMT

Error 12: 0xA0404412 Time: Tue, 27 Jun 2006 23:51:29 GMT

Error 13: 0xA0403034 Time: Tue, 27 Jun 2006 23:46:56 GMT

Error 14: 0xA0404412 Time: Tue, 27 Jun 2006 23:46:56 GMT

Error 15: 0xA0403034 Time: Tue, 27 Jun 2006 23:44:23 GMT

Error 16: 0xA0404412 Time: Tue, 27 Jun 2006 23:44:23 GMT

Error 17: 0xA0403034 Time: Tue, 27 Jun 2006 23:43:51 GMT

Error 18: 0xA0404412 Time: Tue, 27 Jun 2006 23:43:51 GMT

Error 19: 0xA0801601 Time: Tue, 27 Jun 2006 23:41:26 GMT

Error 20: 0xA0801701 Time: Tue, 27 Jun 2006 23:41:26 GMT

Error 21: 0xA0403034 Time: Sun, 25 Jun 2006 17:27:19 GMT

Error 22: 0xA0404412 Time: Sun, 25 Jun 2006 17:27:19 GMT

Error 23: 0xA0403034 Time: Sun, 25 Jun 2006 17:27:15 GMT

Error 24: OxA0404412 Time: Sun, 25 Jun 2006 17:27:15 GMT

Error 25: OxA0403034 Time: Sun, 25 Jun 2006 17:27:10 GMT

Error 26: OxA0404412 Time: Sun, 25 Jun 2006 17:27:10 GMT

Error 27: 0xA0401001 Time: Sun, 25 Jun 2006 17:27:06 GMT

Error 28: 0xA0403034 Time: Sun, 25 Jun 2006 17:27:01 GMT

Error 29: OxA0404412 Time: Sun, 25 Jun 2006 17:27:01 GMT

Error 30: 0xA0403034 Time: Sat, 24 Jun 2006 19:34:58 GMT

Error 31: 0xFFFFFFFF Time: Thu, 01 Jan 1970 00:00:00 GMT

any help would be apreciated

 

[John_Claymore]

Yes, the unit was de-lidded. I checked the CELL die and surrond area. I could spot 2 possible damages:

1) Lower right corner in between the middle of where the 4 traces join, there seems to be a small patch of exposed copper. Inder the magnifying glass it looks to me like no trace is damaged, just the conformal coating stripped away. Easy to test with a drop of coating added.

2) This is what worries me the most: The upper left corner of the die look has a chip, with a hairline crack extending from that location to about 2/3 of the die length. I am not sure if in this flip chip design this is a conductive metal plate or the chip itself. It might be the root cause.

All other SMDs look good.

Is it gone for good or somehow recoverable?

 

[RIP-Felix]

Hello All, Working on a Fat CECH 40GB. Syscon reports a single fault: A0203010 (Cell Thermal Sensor). Anyone had any luck with a repair action for this one?

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

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

becount
Bringup : 2285 times
Shutdown: 2264 times
Power-on: 231day 00hour 17min 45sec
[mullion]$

Step #20 = Initialize CPU/RSX Cores and Adjust VRM to VID. It's part of the AV Backend and occurs before BE on. RSX FBVDDQ shorts, BE thermal/PLL VDDA open line, PWM signal disruption to CPU Buck Converters at startup have all been known to cause A0203010 errors. There is not enough information to make a conclusion. But if there's no physical damage to the CPU or BGA, I suspect an SMD in the CPU VRM.

 

[RIP-Felix]

please help

i have a CECHA01 have yold wen i heat it up for 5 min and let it cool will work for a week i did that 3 times

Statistics: Boot Count 3125 - Shutdown Count 1223 - Runtime 79d 17h 17mn 4s

Errors (32)

Error 0: 0xA0403034 Time: Mon, 10 Jul 2006 12:38:27 GMT

Error 1: 0xA0404412 Time: Mon, 10 Jul 2006 12:38:27 GMT

Error 2: 0xA0403034 Time: Mon, 10 Jul 2006 11:55:39 GMT

Error 3: 0xA0404412 Time: Mon, 10 Jul 2006 11:55:39 GMT

Error 4: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 5: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 6: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 7: 0xA0902203 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 8: 0xA0801802 Time: Mon, 10 Jul 2006 11:54:38 GMT

Error 9: 0xA0802022 Time: Thu, 29 Jun 2006 22:16:31 GMT

Error 10: 0xA0802022 Time: Thu, 29 Jun 2006 22:15:47 GMT

Error 11: 0xA0403034 Time: Tue, 27 Jun 2006 23:51:29 GMT

Error 12: 0xA0404412 Time: Tue, 27 Jun 2006 23:51:29 GMT

Error 13: 0xA0403034 Time: Tue, 27 Jun 2006 23:46:56 GMT

Error 14: 0xA0404412 Time: Tue, 27 Jun 2006 23:46:56 GMT

Error 15: 0xA0403034 Time: Tue, 27 Jun 2006 23:44:23 GMT

Error 16: 0xA0404412 Time: Tue, 27 Jun 2006 23:44:23 GMT

Error 17: 0xA0403034 Time: Tue, 27 Jun 2006 23:43:51 GMT

Error 18: 0xA0404412 Time: Tue, 27 Jun 2006 23:43:51 GMT

Error 19: 0xA0801601 Time: Tue, 27 Jun 2006 23:41:26 GMT

Error 20: 0xA0801701 Time: Tue, 27 Jun 2006 23:41:26 GMT

Error 21: 0xA0403034 Time: Sun, 25 Jun 2006 17:27:19 GMT

Error 22: 0xA0404412 Time: Sun, 25 Jun 2006 17:27:19 GMT

Error 23: 0xA0403034 Time: Sun, 25 Jun 2006 17:27:15 GMT

Error 24: OxA0404412 Time: Sun, 25 Jun 2006 17:27:15 GMT

Error 25: OxA0403034 Time: Sun, 25 Jun 2006 17:27:10 GMT

Error 26: OxA0404412 Time: Sun, 25 Jun 2006 17:27:10 GMT

Error 27: 0xA0401001 Time: Sun, 25 Jun 2006 17:27:06 GMT

Error 28: 0xA0403034 Time: Sun, 25 Jun 2006 17:27:01 GMT

Error 29: OxA0404412 Time: Sun, 25 Jun 2006 17:27:01 GMT

Error 30: 0xA0403034 Time: Sat, 24 Jun 2006 19:34:58 GMT

Error 31: 0xFFFFFFFF Time: Thu, 01 Jan 1970 00:00:00 GMT

any help would be apreciated

GPU needs replaced.

 

[RIP-Felix]

Yes, the unit was de-lidded. I checked the CELL die and surrond area. I could spot 2 possible damages:

1) Lower right corner in between the middle of where the 4 traces join, there seems to be a small patch of exposed copper. Inder the magnifying glass it looks to me like no trace is damaged, just the conformal coating stripped away. Easy to test with a drop of coating added.

2) This is what worries me the most: The upper left corner of the die look has a chip, with a hairline crack extending from that location to about 2/3 of the die length. I am not sure if in this flip chip design this is a conductive metal plate or the chip itself. It might be the root cause.

All other SMDs look good.

Is it gone for good or somehow recoverable?

The nick is near the XDR memory traces and wouldnt cause that error IMO. The Die being cracked is more likely the cause. It's been reported from cracked dies before.

If that's the cause (probably) it's done. You can't replace the CPU without also replacing the Flash and SYSCON as well (they're married). You can replace them, but need a donor set from a board that isn't more easily fixable itself, which is rare.

 

[Oxihixo]

View attachment 41766

For example: If it returns...

0B720A5D00C9B580
0B72 | 0A5D | 00C9B580
Bringups | Shutdowns | Uptime (in seconds)
​

Copy the groups into a hex to decimal converter.

0B72 = 2930 Bringups
0A5D = 2653 Shutdowns
00C9B580 = 13219200 seconds = 153 days of uptime​

@RIP-Felix
Thank you for providing the community with this information and sharing your wisdom.
I ran the provided command and got a return of: 01 1C 00 DC 00 0E C3 B1.
Wow! Only 11.19 days of ON time.