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

I will suggest removing completely nec capacitors, on both sides. As per example I've attached few photos. I have worked on this board just to test only error I get is 1001.
Reball both solved 3034 4402 and 1002.
Board is water damage to syscon side and few more parts corrosion , soldering so I get glod with only 1001 but didn't look very close to bootloaders on SB debugging. Got more into ps4 those days.
Now think in January when I get more time to duplicate syscon and reuse from another motherboard. Syscon out of board mullion model can be reused as nands/nor ic. Erase and write for your needs.
Now I still don't want to lose time because of liquid damage on most important parts.
I have seen that board is glod may give it a chance later with time.
Now you may need one ps3 slim models 2500/3000 and harvest tantal caps, is faster than buy new caps, ps3 have best caps then newer ones on market.
I'm afraid your rsx is too low resistance, may be affected by those caps, you may need at least 10 if you swap entire side of rsx, same with cpu(see photos).
Now I have 3.2 ohms cpu, 2.7 on rsx.
197b9e3e7ad206abe9f8efc2e3ba9351.jpg
ebbd9caf2010c97260ef8f3e7d573d48.jpg
b82f3aef214365aa3da4f92fdf92f061.jpg
 
Last edited:
Will definitely try replacing all Tokins one by one once replacement caps arrive. It might take a while, though, but definitely will be faster than sourcing junk slim at my place as those are far more reliable.

As for liquid damage/corrosion, on my photos from the previous post you can see that my board also has some. It even had blue oxides on metal shields, but all that corrosion has only touched the outer edge of the board and I haven't found any traces of corrosion on the board itself. It seems to me as if this PS3 was used in a humid environment before I bought it.

BTW, do you have any suggestions on measurements points and values?
 
Pavel said:
I don't have any other board to compare measurements to and I haven't found any supplier to order a replacement chip from, so I guess, I'll have to look for an inexpensive PS3 in working condition as a source of reliable measurements and will keep researching this board in the meanwhile.
Click to expand...
I have a few old boards laying around (COX-001 & COX-002). So I can check some resistances. But I'm not going to have much free time until december. If you post your resistor, cap, or IC resistances, then maybe someone on the forum will check to see if their board is in the same ballpark.

Of course, it's faster if you have an identical board for comparison and donor boards for parts. It's not entirely necessary the comparison board is working as long as you know what's wrong. If it needs reballed, then perhaps the tokin resistances are affected, a few VDDIO lines could be broken, but for the most part everything should be fine. The chances of having the same fault, resulting in the same resistance, is unlikly. So you can use the resistance comparison to identify differences that can help you hone in on potential shorts. It's a long process, doing it that way tho.

Alternatively, you can inject power and see what gets hot. It's quick and dirty, but works.
 
Before replacing tokins, try replacing IC2408. I strongly suspect that converter.

Vout being short to ground may be internal. Once you work it off the board the short should be gone. If so, replace it. If not, keep removing resistors and caps down stream.
 
Hello everyone, I'd like to get some insight on a problem I've been having with my PS3 back compatible.
So I recently just reflowed the CELL and RSX because I was having some problems (no boot, boot and then crash with graphical glitches etc...) after doing so, the PS3 started giving me consistent errors, now when I turn it on, I get nothing on the screen, and it doesn't turn off unless I hold the power button, and when it turns off, it beeps 3 times signifying that it has error'd during shutdown, the syscon returns this error A0901001 . Of course I can't access the recovery menu or anything, it's all just a black screen both on HDMI and SCART. now it's worth mentioning that after the console warms up a bit, it doesn't beep anymore during shutdown, but that's about all that changes, still get nothing, with or without an HDD or other components...
I tried soldering some tantalum caps on the NEC tokins (piggyback style) but it doesn't seem like it has changed anything, it's also worth noting that when the shutdown error goes away, the syscon doesn't return any errors, so that's all I can go from.
Any ideas on what may be causing the problem? I'm more keen on knowing what the issue is at the very least, because it's really bugging my noggin.
 
Code said:
Hello everyone, I'd like to get some insight on a problem I've been having with my PS3 back compatible.
So I recently just reflowed the CELL and RSX because I was having some problems (no boot, boot and then crash with graphical glitches etc...) after doing so, the PS3 started giving me consistent errors, now when I turn it on, I get nothing on the screen, and it doesn't turn off unless I hold the power button, and when it turns off, it beeps 3 times signifying that it has error'd during shutdown, the syscon returns this error A0901001 . Of course I can't access the recovery menu or anything, it's all just a black screen both on HDMI and SCART. now it's worth mentioning that after the console warms up a bit, it doesn't beep anymore during shutdown, but that's about all that changes, still get nothing, with or without an HDD or other components...
I tried soldering some tantalum caps on the NEC tokins (piggyback style) but it doesn't seem like it has changed anything, it's also worth noting that when the shutdown error goes away, the syscon doesn't return any errors, so that's all I can go from.
Any ideas on what may be causing the problem? I'm more keen on knowing what the issue is at the very least, because it's really bugging my noggin.
Click to expand...
I'm in same way after reball both, caps exchange but thought my board is water damaged somehow on syscon area (apart from many parts I've resoldered)
I may not have time with this, we should certainly check some voltages around cpu VDDC line, don't think rsx have any problems, mine is for sure fine, same value before and after reball.
 
vyktormvmpay25 said:
I'm in same way after reball both, caps exchange but thought my board is water damaged somehow on syscon area (apart from many parts I've resoldered)
I may not have time with this, we should certainly check some voltages around cpu VDDC line, don't think rsx have any problems, mine is for sure fine, same value before and after reball.
Click to expand...

I should be able to check said voltages tomorrow, but since I'm somewhat of a rookie to this, do you mind pointing me to the right spot to check? That'd be sweet, in the meantime, I'll also do my homework on this
 
vyktormvmpay25 said:
http://s.go.ro/ax49drsu
Just following schematic on cell power supply conversion from 12v to 1,0v
Click to expand...

Alright I just did the measurements and I even doubted my own capabilities, but basically I got 1.22V on the CELL, and 1.20 on the RSX, and judging from what you said and from what the schematics says, the CELL should be 1.0V

20211119_121446.jpg

That's where I probed
20211119_122909.jpg

The CELL (ignore the minus I just switched my probes)

20211119_122951.jpg

RSX seems to be in order.

Im pretty sure I did my measurements right, Also keep in mind that I still have 6 caps installed on the other side of the board... What do you think?
 
Hello all; I hope for your support with my DIA-002 board:
Code: 
>$ 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 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
I'm not posting errlog, as it is absolutely full of 2102 errors, but I once got a 1002 code. The console started showing this error after I put a 1mm thermopad on RSX instead of bending the clamp, as after delidding temps were higher than before. So far I can see no missing caps/resistors, main RSX voltage at NECs seems fine. From looking at DECR syscon bringup power states it fails right after state number 30, so it doesn't have enough power to keep going or these are varius voltage checks?
 
Code said:
Alright I just did the measurements and I even doubted my own capabilities, but basically I got 1.22V on the CELL, and 1.20 on the RSX, and judging from what you said and from what the schematics says, the CELL should be 1.0V

20211119_121446.jpg

That's where I probed
20211119_122909.jpg

The CELL (ignore the minus I just switched my probes)

20211119_122951.jpg
RSX seems to be in order.

Im pretty sure I did my measurements right, Also keep in mind that I still have 6 caps installed on the other side of the board... What do you think?
Click to expand...
http://s.go.ro/554yi0et
http://s.go.ro/1hjwkibl
While assembly as test mode test more voltages, also try soldering those resistances better. Also what resistance do you see on cell vddc side? Nearly 2 ohms or over 3 ohms?
adcffc0822542853aff03817446d1a57.jpg

I didn't came until now at this tipe of error, also we may have to see an error log or internal " bringup " command and we should understand from there if all PSU are OK, they will come as PS0/1/2/3/4.
 
Last edited:
N3Star said:
Hello all; I hope for your support with my DIA-002 board:
Code: 
>$ 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 -> 0303
[SSM] PowSeq Fail : Detected !
[SSM] state: 0303 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0232102
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
I'm not posting errlog, as it is absolutely full of 2102 errors, but I once got a 1002 code. The console started showing this error after I put a 1mm thermopad on RSX instead of bending the clamp, as after delidding temps were higher than before. So far I can see no missing caps/resistors, main RSX voltage at NECs seems fine. From looking at DECR syscon bringup power states it fails right after state number 30, so it doesn't have enough power to keep going or these are varius voltage checks?
Click to expand...
Again is something strange if low resistance on vddc cpu side more to be cpu fried under 2.5 ohms, still not sure, may other users to confirm. Those 2101/2102 are clock generator and I'm waiting botakompong to explain problems that is causing those, even 1001 it is not often seen so I'm still searching. It may take me time and need good overall boards, not touched to understand what could causing errors.
 
vyktormvmpay25 said:
Again is something strange if low resistance on vddc cpu side more to be cpu fried under 2.5 ohms, still not sure, may other users to confirm. Those 2101/2102 are clock generator and I'm waiting botakompong to explain problems that is causing those, even 1001 it is not often seen so I'm still searching. It may take me time and need good overall boards, not touched to understand what could causing errors.
Click to expand...

I've found a picture of this board with resistances (only on the back side) and they all seem perfect. I wonder if it is a problem with mounting pressure; I've only tried this trick with CECHG consoles, but comparing clamp screws from CECHC, CECHG, CECHK seem to be slightly different in thread length.
 
vyktormvmpay25 said:
http://s.go.ro/554yi0et
http://s.go.ro/1hjwkibl
While assembly as test mode test more voltages, also try soldering those resistances better. Also what resistance do you see on cell vddc side? Nearly 2 ohms or over 3 ohms?
adcffc0822542853aff03817446d1a57.jpg

I didn't came until now at this tipe of error, also we may have to see an error log or internal " bringup " command and we should understand from there if all PSU are OK, they will come as PS0/1/2/3/4.
Click to expand...

For some reason I can't post anymore... The website thinks I'm spamming or something.

Anyway here's the results of my testing, the rest was also tested with the same results pretty much: https://prnt.sc/202te67 (yes I can't posts pictures either)

And the log (I also linked the file cause the website is acting kinda wacky for some reason)

Code: 
> 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.
WmDiscOpr_ChuckOffEvent
[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
>
[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
[mullion]$ [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
WmDiscOpr_ChuckOnEvent
WmDiscOpr_ChuckOffEvent
WmDiscOpr_ChuckOnEvent
[SERV NVS] READ CMD
[mullion]$
> shutdown
[SERV THERM] Thermal Error Detected!
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801200
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SERV NVS] *** sending error ***
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>
 

Attachments

Last edited:
Code said:
For some reason I can't post anymore... The website thinks I'm spamming or something.

Anyway here's the results of my testing, the rest was also tested with the same results pretty much: https://prnt.sc/202te67 (yes I can't posts pictures either)

And the log (I also linked the file cause the website is acting kinda wacky for some reason)

Code: 
> 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.
WmDiscOpr_ChuckOffEvent
[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
>
[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
[mullion]$ [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
WmDiscOpr_ChuckOnEvent
WmDiscOpr_ChuckOffEvent
WmDiscOpr_ChuckOnEvent
[SERV NVS] READ CMD
[mullion]$
> shutdown
[SERV THERM] Thermal Error Detected!
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[WMZONE] *** Thermal Shutdown (1st BE Primary ) ***
[SSM] *** Thermal Alert (ZONE) ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801200
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
[SERV NVS] *** sending error ***
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>
Click to expand...
Everything was fine before your CPU overheated and the console went into thermal shutdown (1200).
 
Code said:
Yeah that's what I thought, the boot sequence doesn't fail in any way as far as I could tell
Click to expand...
About spamming wornings should dissappear after 10 posts.
So this 1001 is coming from thermal heat? Delid both and add new thermal paste on and test again.
I've referred this points In pictures to be resolder as 1001 is kind of loss power but can not understand glod situation.
Still cannot believe is only that.
91a896f1f84bc79b9ba682594a9414b4.jpg
 
Last edited:
vyktormvmpay25 said:
About spamming wornings should dissappear after 10 posts.
So this 1001 is coming from thermal heat? Delid both and add new thermal paste on and test again.
I've referred this points In pictures to be resolder as 1001 is kind of loss power but can not understand glod situation.
Still cannot believe is only that.
91a896f1f84bc79b9ba682594a9414b4.jpg
Click to expand...

Oh no no the problem isn't the overheating part, excuse me for not mentioning it at first, I forgot to add that I didn't have the heatsink on, so the error is natural, I typed this the first time I was trying to post, until the site gave me a hard time doing so and I missed the detail.
 
Ok no problem but those units need first thing to be done is delid both, ppl must understand that all ps3 where we can must delid both, start from 2100 to 3000 are a pain. On 3000 only I can delid out of board rsx with shaving blade old type. Is a pain to delid rsx starting from 2100. Cell can be delid easy with grey silicone around. White silicone cells are bounded so tight and most often those will die first if people don't maintain units on right time every 2 years.
White silicone is not for delid models.
 
You must log in or register to reply here.

Similar threads

Back
Top