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

#10

IMG_1033.JPG
 
squeept said:
I don't actually keep one for myself, so am I excluded?!?
Click to expand...
No, you're not excluded. But you can only answer once. So choose the answer that best fits your "average reball."

I would apreciate you commenting with and esitimate of how many people use your warranty repair. And how many of those were related to the RSX again. That could be useful. As well as the relative number of times a reball doesn't fix the GPU issue (excluding GLOD, which can be VRAM and isn't bump related).

But you've only been keeping the data sheets for a little while and they would be most useful for getting good numbers, especially for tracking the same console if/when it comes back in for repair. So time will tell, hopefully.
 
I had my first win using the syscon on a SEM-001 board with a YLOD. The error code I was getting was a 801002, so I changed out the RSX NEC TOKINS with some 470uF caps and it has brought it back to life.

I have de-lided the RSX is it worth doing the CELL or not, what are your guys thoughts.
 
This super slim powers off with no beep just in a second after bringup command. its power switch is missing so I don't know the led colors.
syscon errlogs:
>$ bringup
00000000
# [SSM] Bringup Start.
>$
F0000003
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9203
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [UCMD] Unknown command.
>$ ERRLOG
00000000
# CODE CLOCK
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF
# A0404003 FFFFFFFF
# A0403034 FFFFFFFF

Is this a rsx failure? the mobo rev is ppx-001. so rsx is 28nm.

And I have another problem with beccunt command. does not work on this device and another slim I had tried befor.
>$ becount
F0000003
# [UCMD] Unknown command.
thank you.

Edit: a history of device from its owner (can't confirm he is not lying): It was working with a cobra ODE until they decided to remove the cobra board. After removing it they didn't have success with hen installation. Does cobra ode board installation/removal have any relation to those syscon errors?
 
Last edited:
That's an interesting one. Never seen 3034 on a SS. Not gonna say it's impossible tho.

IDK about the Cobra ODE. I've never looked into it or how it works. I do know that 4034 can result from other causes than the BGA or Bumps, like the FlexIO voltage reference, but that's rare too. That it coincided with the ODE removal, that is sus. Perhaps the maker of the ODE would know?
 
What about the following a0404003? Dev wiki says it's south bridge witch is more related to the cobra because as far as I know the cobra board connects to blue ray drive sata port. I have removed a cobra ode from a slim PS3 before. When I removed it the console powered on but the bd didn't work. Then I realized that 4 sata signal bypass caps should be reinstalled to make the bd work again. I added caps and it bd started to work.
Any way, how can I find and test that FlexIO reference thing on this motherboard?

Edit: I have checked the bypass capacitors and they have installed them but another thing I have noticed is that there is some dirt and footprints of heat and flux on SB. RSX is clean so I think those two errors are separated maybe two separated problems on this motherboard. Any way this one is a double headache not worth it to repair.
 
Last edited:
Was Computer Booter one of very first unit with 3003 when one mosfet had short from 12v line to vddc on cell? Surprised to see that cell did work again.
 
vyktormvmpay25 said:
Was Computer Booter one of very first unit with 3003 when one mosfet had short from 12v line to vddc on cell? Surprised to see that cell did work again.
Click to expand...

Hey Vyktor, i'm sorry i'm interrupting this thread but i dont have enough Karma to PM you. Would you be willing to fix a BC COK-001 PS3 for me? I replaced some NEC Tokins but it did nothing and i also accidentally knocked some small capacitors off. How much would it cost me for you to replace the RSX and Frankenstein me a working one + replacing some tiny capacitors?
 
HI, new to this syscon testing, but have a lots of PS3 boards home that I would like to bring back to life ...

The first test was on SEM-001 (first soldered the diag,and didn't get nothing) ...

So after removing DIAG pin got this result :

===================================
ERR 00: 00000000 A0022110 23815B98
ERR 01: 00000000 A0022110 23815B8F
ERR 02: 00000000 A0022110 217DE5EF
ERR 03: 00000000 A0022110 217DE5E7
ERR 04: 00000000 A0022110 213C0D11
ERR 05: 00000000 A0022110 213C0D08
ERR 06: 00000000 A0022110 213C0D01
ERR 07: 00000000 A0022110 20F72F67
ERR 08: 00000000 A0022110 20F72F64
ERR 09: 00000000 A0022110 20F72F26
ERR 10: 00000000 A0022110 20F0FA0A
ERR 11: 00000000 A0022110 20F0FA06
ERR 12: 00000000 A0022110 20F0F9FE
ERR 13: 00000000 A0022110 20F0F9F6
ERR 14: 00000000 A0022110 20F0E80C
ERR 15: 00000000 A0022110 20F0E7E6
ERR 16: 00000000 A0022110 20F0E7A8
ERR 17: 00000000 A0022110 20F0E790
ERR 18: 00000000 A0022110 20F0E77E
ERR 19: 00000000 A0801001 15713A43
===================================

As I read this is somthing with clock failture ... As a solve read here on pages to chech F6001, which is ok with multimeter ...

Can someone point me further wheare to check ...

THX
 
You must log in or register to reply here.

Similar threads

Back
Top