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

[Timbo9876]

Good luck with the de-lidding [emoji3]

Sent from my SM-G988B using Tapatalk

 

[Tony359]

aha yes. But again, this is much more fun than just de-lid and fix the PS3!
Also, I have an engineer mind, I like to learn new things.

I took a look at that lid the other day: the sealant is not soft at all! I was hoping in a silicone-style compound but no. It'll take some time with floss line I guess.

 

[RCWD21]

"M7" stands for 7mOhms ESR.

Those are the best caps IMO and should be perfectly adequate, if they're installed correctly. Are you sure that they are?


Let me see if I understand you.

1. You flip the power rocker. Standby LED goes solid red witohut beeps.
   • Means standby circuit is fine and there are no checksum issues.
2. You press the PWR touchpad and the console boots.
   • Means the power on sequencing completed sucessfully. No shorts, blown fuses, or serious HW failures.
3. XMB loads.
   • Means the bootloader finished sucessfully. No NAND corruption. No GLOD because of it.
4. You can see and hear the menu? Can navigate around?
   • Means the controller paired, HDMI/AV are working, no slowdown, artifacting, or freezing to indicate a BGA/Bump defect.
5. And then for no reason whatsoever it immediately shuts off, witout any warning. And the standby LED is still solid red.
   • Means the PSU didn't die or the LED wouldn't be illuminated.
     
   • Means there was no YLOD or SYSCON error or the LED would be flashing.
   • Acts like the SYSCON was issued a shutdown comand, immediately shutting down (not gracefully), except it wasn't. At least not by you, not intentionally.

Did I get all that right?

Regardless, it would be helpful to see the bringup command. I would especially like to see what it records while the shutdown occurs. So hookup the UART, HDMI, a controller, and auth into internal mode. Use the bringup command to start the console. Then switch to HDMI. Navigate around XMB until it shuts off. Then hit enter on the UART to see the string of events that took place. The bootloader and shutdown sequence should be recorded. Post that entire log here.

I can plug the console in and it will sit on the red standby light once i flip the rocker switch all day long no issues. Once I ether issue the bringup command via syscon or touch the power button the console beeps and the light turns green and you can hear the fan start spinning like it should and after about 40 to 50 seconds the console just goes back to a solid red standby light. If its hooked up to a TV I never get any signal, just a black screen.

And yes I'm 100% sure I installed the tantalums correctly, I double checked everything before even reassembling everything to test.

Here are some commands from just now though:

Spoiler: Bringup

>$ auth
Auth successful
>$ bringup
[SERV THERM] NOTIFY_MODE CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV DEVPM] CONTROL_PCI_BUS_POWER_STATE CMD
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000274, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
>$

Spoiler: Errlog

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

Spoiler: Disp_Err

>$ disp_err
[SERV THERM] NOTIFY_MODE CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV DEVPM] CONTROL_PCI_BUS_POWER_STATE CMD
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000274, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
disp_err
CheckStop: None
PLLUnlock: 0
RSX Int: None
PowerSeq: ff
[mullion]$
>$

Spoiler: Powerstate

>$ powerstate
[SERV NVS] READ CMD
Boot Loader SE Version 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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 THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
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]$
>$

Also the only HDMI command this console will recognize is "bstatus"

Spoiler: HDMI

>$ bstatus
bstatus
OK
>$

If you need any other logs just let me know

 

[RIP-Felix]

Please do this exactly.

bringup

wait until console shuts down

press enter on keyboard to make the rest of the log appear!!! (after you perform a bringup command the log will stop at the end of the power on sequence. But there is more information about the bootloader and shutdown state. It will all display, when you press enter.)

copy the entire string. From the moment you press enter on the bringup command, to after pressing enter again after the console shuts down.

I want to see the full powerup and shutdown log, start to finish. All in one string.

 

[RCWD21]

Please do this exactly.

bringup

wait until console shuts down

press enter on keyboard to make the rest of the log appear!!! (after you perform a bringup command the log will stop at the end of the power on sequence. But there is more information about the bootloader and shutdown state. It will all display, when you press enter.)

copy the entire string. From the moment you press enter on the bringup command, to after pressing enter again after the console shuts down.

I want to see the full powerup and shutdown log, start to finish. All in one string.

I didn't know you could do that, thanks! Here's the full string.

Spoiler: Bringup + Enter

>$ 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:0x20e2
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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 THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV THERM] NOTIFY_MODE CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV DEVPM] CONTROL_PCI_BUS_POWER_STATE CMD
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000274, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
[mullion]$

 

[Tony359]

Don't say anything, Felix. But I can here confirm that floss line is NOT the safest method to de-lid. I repeat: IT'S NOT.

 

[Timbo9876]

Sorry to hear that, when I tried it I knew it wasn't for me.

Sent from my SM-G988B using Tapatalk

 

[Tony359]

as usual it's a matter of experience. If I had to do another one, I would be 70% successful. The third one probably 90 and so on.

I'll show you what happened but towards the end (my hands were almost bleeding because of the floss line!) I grabbed a razor blade - the super flexible ones - and with one of those I cut through the glue in seconds with no damage.

I thought the floss line method was slow but safe.

Again, next time it will go better. Unfortunately there has to be a first time for everything.

Upside: the repair video is now finished!

 

[vyktormvmpay25]

Felix isn't that rsx for RCWD21? died in middle of update heat . If it is corrupt nand during update, remember it happened few times before with David Frankies live, those units were faulty on rsx and got nand corruption same time . Lucky syscon know to recover from those types of corruption if we shut down during updates.
I'll call it special glod.
Well wasn't same case exactly but they show nand corruption after we changed rsx and they closed themselves and only recovery was working, after updates from there were fine.

 

[yanvbraz]

So I grabbed a PS3 with YLOD for really cheap at a local store, then I did the Syscon diagnosis and got the following error codes:

===================================
ERR 00: 00000000 A0203010 FFFFFFFF
ERR 01: 00000000 A0203010 FFFFFFFF
ERR 02: 00000000 A0203010 FFFFFFFF
ERR 03: 00000000 A0203010 FFFFFFFF
ERR 04: 00000000 A0203010 FFFFFFFF
ERR 05: 00000000 A0203010 FFFFFFFF
ERR 06: 00000000 A0203010 FFFFFFFF
ERR 07: 00000000 A0203010 FFFFFFFF
ERR 08: 00000000 A0203010 FFFFFFFF
ERR 09: 00000000 A0203010 FFFFFFFF
ERR 10: 00000000 A0203010 FFFFFFFF
ERR 11: 00000000 A0203010 FFFFFFFF
ERR 12: 00000000 A0203010 FFFFFFFF
ERR 13: 00000000 A0203010 FFFFFFFF
ERR 14: 00000000 A0203010 FFFFFFFF
ERR 15: 00000000 A0203010 FFFFFFFF
ERR 16: 00000000 A0203010 FFFFFFFF
ERR 17: 00000000 A0203010 FFFFFFFF
ERR 18: 00000000 A0901001 25E4161F
ERR 19: 00000000 A0802022 25E41430
===================================

So I'm not exactly sure what is the meaning behind that:
A0203010 = BE_INIT OR BE_POWGOOD OR CLOCK ERRORS

The error before that (1001) indicates it was a shutdown (A090) error related with insufficient Filtering on CPU's core voltage (perhaps bad NEC Tokins?)
And then 2022 = DVE Error (IC2406, CXM4024R MultiAV controller for analog out) - Not sure what is the meaning behind that either...

With this sample of errors, would it be reasonable to think that perhaps replacing NEC Tokins on this board would fix this issue?
Could it be PSU fault?

I wish I didn't try to boot it up so many times so I would get more error codes...

 

[RIP-Felix]

So I grabbed a PS3 with YLOD for really cheap at a local store, then I did the Syscon diagnosis and got the following error codes:

===================================
ERR 00: 00000000 A0203010 FFFFFFFF
ERR 01: 00000000 A0203010 FFFFFFFF
ERR 02: 00000000 A0203010 FFFFFFFF
ERR 03: 00000000 A0203010 FFFFFFFF
ERR 04: 00000000 A0203010 FFFFFFFF
ERR 05: 00000000 A0203010 FFFFFFFF
ERR 06: 00000000 A0203010 FFFFFFFF
ERR 07: 00000000 A0203010 FFFFFFFF
ERR 08: 00000000 A0203010 FFFFFFFF
ERR 09: 00000000 A0203010 FFFFFFFF
ERR 10: 00000000 A0203010 FFFFFFFF
ERR 11: 00000000 A0203010 FFFFFFFF
ERR 12: 00000000 A0203010 FFFFFFFF
ERR 13: 00000000 A0203010 FFFFFFFF
ERR 14: 00000000 A0203010 FFFFFFFF
ERR 15: 00000000 A0203010 FFFFFFFF
ERR 16: 00000000 A0203010 FFFFFFFF
ERR 17: 00000000 A0203010 FFFFFFFF
ERR 18: 00000000 A0901001 25E4161F
ERR 19: 00000000 A0802022 25E41430
===================================

So I'm not exactly sure what is the meaning behind that:
A0203010 = BE_INIT OR BE_POWGOOD OR CLOCK ERRORS

The error before that (1001) indicates it was a shutdown (A090) error related with insufficient Filtering on CPU's core voltage (perhaps bad NEC Tokins?)
And then 2022 = DVE Error (IC2406, CXM4024R MultiAV controller for analog out) - Not sure what is the meaning behind that either...

With this sample of errors, would it be reasonable to think that perhaps replacing NEC Tokins on this board would fix this issue?
Could it be PSU fault?

I wish I didn't try to boot it up so many times so I would get more error codes...

3010 is bad news. It's still mysterious. It hasn't appeared in any of me and booter's sabotage tests. From anecdotal reports, it's usually related to the CPU. It makes me suspect CPU BGA, but other things have caused it. Like I said, a mystery.

You could try replacing a CPU tokin to see if that has any effect. But if it does, you should expect a false positive. Do not get too excited. It may not last.

 

[Tony359]

I've made a video on my PS3 repair attempt. My channel is a hobby, I do not make money out of it. And please remember I am not a PS3 expert - I am always learning! Tips and comments are always welcome! And sorry for the catching thumbnail! But the PS3 was indeed drilled at some point LOL!

(Spoiler alert, I've got another PS3 to fix... )

 

[RIP-Felix]

I've made a video on my PS3 repair attempt. My channel is a hobby, I do not make money out of it. And please remember I am not a PS3 expert - I am always learning! Tips and comments are always welcome! And sorry for the catching thumbnail! But the PS3 was indeed drilled at some point LOL!

(Spoiler alert, I've got another PS3 to fix... )

Well, I offer you my condolences. I'm just sorry I couldn't convince you to make a proper tool to delid it. 1 hour with a Dremel and you'd have a tool that can delid the IHS safely. You went to much more trouble making the jig to hold the MB and researching the error.

I know you wanted to forge the information for yourself, for the sake of the video and personal growth. But sometimes we can learn from the mistakes others before us have made. Perhaps your video will do a better job of convincing the next person to learn from your mistake than I did in convincing you. Many others before you on this forum have made the same error. And I'm sure you will not be the last.

I'd like to say the outcome was surprising, but I knew what what was coming. I apologize if this sounds like I'm pouring salt on an open wound. There's no need, I think the loss doing a better job of sinking that lesson in. You made it clear you were intent on that fate. So I got out of the way and let you.

I felt the growing pains you are talking about and appreciate your candor in posting an unflattering video. I understood each and every one of your erroneous rationalizations implicitly, as only someone who has experienced the same journey can. The video has serious cringe factor for me because it's too real...raw...infuriating. That the first "fixes" people come across on the internet are the ones most likely to kill an otherwise repairable console.

It's just how search engines and AI algorithms work. The most popular search results are answers people are looking for. And they want the easy way out. So of course the most popular solutions are going to be tokins, hairdriers, heat guns. Not SYSCON diagnostics, reballing, and Delidding tools. Truth be damned! Wishful thinking rules the web!

 

[Tony359]

Felix

your comment is much appreciated and I've always valued your input - I just made the wrong decisions and also my implementation was not great.

I can very much imagine from an expert point of view my video must feel frustrating! And yes, I hope my video will be useful for others to decide what to do and what NOT to do

in the end I had fun - despite the final outcome - and this community has been great for info and help!

again, I've got another PS3 coming - I felt sorry for this one so I feel I 'have' to fix one now - so do expect me coming back here!

 

[RIP-Felix]

again, I've got another PS3 coming - I felt sorry for this one so I feel I 'have' to fix one now - so do expect me coming back here!

Well, I guess the first one is a good candidate to teach you microsoldering. I've got one too. It's extreemly small. That's currently the limit of my ability. But always room to learn.

 

[yanvbraz]

3010 is bad news. It's still mysterious. It hasn't appeared in any of me and booter's sabotage tests. From anecdotal reports, it's usually related to the CPU. It makes me suspect CPU BGA, but other things have caused it. Like I said, a mystery.

You could try replacing a CPU tokin to see if that has any effect. But if it does, you should expect a false positive. Do not get too excited. It may not last.

Aww that sucks, well at least this unit served to restore another unit that had a faulty BD drive and missing components. About replacing Tokins, I might give it a try later since looks like I don't anything to lose now xD

 

[sandungas]

I been doing a table in wiki with the pinout of the CXM4024R (Digital Video Encoder) of the fat PS3 models. You know.. the responsible to output the video signal to the MultiAV connector. There was people reporting problems related with this IC, maybe this helps troubleshooting it
https://www.psdevwiki.com/ps3/CXM4024R

Im advising about it because i need confirmation of a few pins, if some of you have one of this PS3 fat motherboards without the RSX (removed to touch his pads with a multimeter) please check them and report back (or edit wiki to update the info about them):

DVE pin 31 <-----> RSX pad AK38
DVE pin 32 <-----> RSX pad AA37
DVE pin 34 <-----> RSX pad AM40
DVE pin 80 <-----> RSX pad AJ36
DVE pin 83 <-----> RSX pad AK36
DVE pin 84 <-----> RSX pad AK40
DVE pin 85 <-----> RSX pad AL40
DVE pin 93 <-----> RSX pad AE36

To identify the RSX pad names use this image https://www.psdevwiki.com/ps3/File:RSX_SKEMA.jpg


-------
Btw, the descriptions about the DVE pins in wiki are the most shorter posible because my main goal was to find the connections with syscon. There are some pins that are connected to multiple components but i just mentioned the easyest
Lets say... if the pin have 5 traces connected to different places and one of them is simnply a "0.1uf capacitor to GND", then thats what i mentioned... all that descriptions are open for improvements, but by now is enought for me... in other words, im done with it

All i can tell is the power lines of this IC are very tricky in the PS3 fat models (later sony simplifyed it), because the DVE is sharing power lines and power components with RSX and HDMI
Actually... the RSX have tenths of "duplicated" connections with HDMI and DVE chips, and are sharing the same official signal names, as you can see by comparing the list above with the pinout of the wiki page im asking about some lines using the suffix "1"
As example... the RSX pad named RSX_CLKOUT1 have the suffix "1" (because is connected to the DVE chip)... and RSX_CLKOUT0 have the suffix "0" (because is connected to the HDMI chip)

In some way it looks like the DVE and HDMI chips are like siamese brothers, lets say... the connections in between RSX and them is pretty much the same... just duplicated 2 times and using around 50 lines for each

 

[vyktormvmpay25]

@sandungas more specific phat model?

 

[sandungas]

@sandungas more specific phat model?

Any, in wiki is mentioned the CXM4024R is used in all this PS3 models/motherboards:

Seen on all the PS3 FAT, CECHAxx/COK-00x up to including CECHQxx/VER-00x

In other words... all the PS3 fats uses the CXM4024R (digital video encoder)

Spoiler

It was updated in slims and superslims to CXM4027R with a different pinout

And the RSX 41x41 pad layout is shared by all the PS3 models (except the latest 28nm RSX)

So is mostly a matter of identifying the unknown 8 pins i mentioned from the CXM4024R (specific for fats) <---to---> RSX

 

[vyktormvmpay25]

Ok I'll do it, first I've cleared one slim dyn001 for syscon missing pins. I'll complete rest of your request after.

DVE pin 31 <--22 ohms resistance---> RSX pad AK38
DVE pin 32 <-----> RSX pad AA37 straight
DVE pin 34 <-----> RSX pad AM40 straight
DVE pin 80 <--22 ohms resistance---> RSX pad AJ36
DVE pin 83 <--22 ohms resistance---> RSX pad AK36
DVE pin 84 <--22 ohms resistance---> RSX pad AK40
DVE pin 85 <--0 ohms resistance---> RSX pad AL40
DVE pin 93 <-----> RSX pad AE36 straight