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

Heyo, me again.

Got a CECHK with GLOD, been searching around for a long time before coming back here (I won't bother you guys!) but I can't found any UART guide to check the boot sequence can someone link me the guide? :(

Typical GLOD : 1 sec power HDD
Only charging controller

Important fact : console was sealed so no one messed around her, no trace of humidity aswell.
 
Last edited:
Stryder said:
Heyo, me again.

Got a CECHK with GLOD, been searching around for a long time before coming back here (I won't bother!) but I can't found any UART guide to check the boot sequence can someone link me the guide? :(

Typical GLOD : 1 sec power HDD
Only charging controller

Important fact : console was sealed so no one messed around her, no trace of humidity aswell.
Click to expand...

Here's my SYSCON guide.
 
So i've got my reader and i've learned the process of pulling these codes and learning their meaning. It was actually much easier than I anticipated once I sat down and got going with it. I'm diagnosing a Ylod CECHE model i just picked up. I'm getting the following codes (these are the main ones that keep repeating throughout the 20 I pulled):
> ERRLOG GET 00
00000000 A0003001 FFFFFFFF
> ERRLOG GET 01
00000000 A0003001 FFFFFFFF
> ERRLOG GET 02
00000000 A0403034 28CEAFC9
> ERRLOG GET 03
00000000 A0404412 28CEAFC9

The github guide is stating this for the main code that keeps popping up
A0403034, A0404402,A0404411 = Poor BGA solder connections for RSX ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )... wasn't able to find a correlation for the
A0003001 code.

Since it's talking of BGA solder connections, i'm assuming my best attempt to fix this would be to go for a reflow and see if I have any luck. Any thoughts?
 
M4j0r said:
@joesaiditstrue

You can find a precompiled version (debug pkg) with the "Get Syscon Info" support here: https://workupload.com/file/yExhQFXdsFy .
Click to expand...
Enormously helpful pkg. Now people can get useful diagnostic info without even opening the case, not to mention soldering! Thank you so much. I noticed the release build on the github page https://github.com/bucanero/psl1ghtv2_ports is only up till the commits on Jun 1st and doesn't contains the get syscon info program though.
 
Checkity_CheckYoSelf said:
So i've got my reader and i've learned the process of pulling these codes and learning their meaning. It was actually much easier than I anticipated once I sat down and got going with it. I'm diagnosing a Ylod CECHE model i just picked up. I'm getting the following codes (these are the main ones that keep repeating throughout the 20 I pulled):
> ERRLOG GET 00
00000000 A0003001 FFFFFFFF
> ERRLOG GET 01
00000000 A0003001 FFFFFFFF
> ERRLOG GET 02
00000000 A0403034 28CEAFC9
> ERRLOG GET 03
00000000 A0404412 28CEAFC9

The github guide is stating this for the main code that keeps popping up
A0403034, A0404402,A0404411 = Poor BGA solder connections for RSX ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )... wasn't able to find a correlation for the
A0003001 code.

Since it's talking of BGA solder connections, i'm assuming my best attempt to fix this would be to go for a reflow and see if I have any luck. Any thoughts?
Click to expand...

Careful! The first 2 errors are the newest and there's no telling how old the 3034/4xxx eerors are! They could have been repaired already and still in the log. 3001 is a 12v power failure, usually because the PSU isn't plugged in or it's dying. Did you try to PWR the console on without those two 12v prongs pluged in? If so that's what those errors are. Otherwise check the fuses and PSU *BEFORE REFLOWING*.

About the reflow. Be sure to THOROUGHLY clean the MB first with 99% IPA first! Toothbrush + Paper towel to soak up the diluted flux/dirt/dust/grime. Repeat at least 3 times! Then use electronics contact cleaner. Hold the board on an angle and allow it to run underneath the BGA. Use a paper towel to soak up the liquid as it runs out, so it doesn't run all over the board and under other components. Turn 90-deg and repeat. Repeat with 99% IPA, doing the same procedures. Spray, turn,...spray, turn...spray, turn...etc. Dry thoroughly before continuing on to the reflow. Be sure to use compressed air to blow out the liquid hiding underneathe the chips. I can look dry when it isn't, so be sure (don't use heat to speed the process). Just sit in front of a fan for 2 hours or so (if your house is very dusty, maybe place a paper towel over the back side of the fan to filter the air first).

Then use AMTECH flux for the reflow. Heat it to 150C and hold it there for 3-5minutes before increasing to reflow temps. That activates the flux (undoes oxidation). That's the best you can hope for with a reflow, but it's not going to last as long a reball, if it works at all. Only reballing can getrid of stubbarnly oxidized pads. But this cleaning/flux process gives you the best chance.
 
Last edited:
feng_ye said:
Enormously helpful pkg. Now people can get useful diagnostic info without even opening the case, not to mention soldering! Thank you so much. I noticed the release build on the github page https://github.com/bucanero/psl1ghtv2_ports is only up till the commits on Jun 1st and doesn't contains the get syscon info program though.
Click to expand...
Yeah, the UART process is for people who can't turn their console on. Obviously, PS3 Advance Tools can't be used if you can't turn the console on. I added the link to my SYSCON tutorial though.
 
RIP-Felix said:
Careful! The first 2 errors are the newest and there's no telling how old the 3034/4xxx eerors are! They could have been repaired already and still in the log. 3001 is a 12v power failure, usually because the PSU isn't plugged in or it's dying. Did you try to PWR the console on without those two 12v prongs pluged in? If so that's what those errors are. Otherwise check the fuses and PSU *BEFORE REFLOWING*.

About the reflow. Be sure to THOROUGHLY clean the MB first with 99% IPA first! Toothbrush + Paper towel to soak up the diluted flux/dirt/dust/grime. Repeat at least 3 times! Then use electronics contact cleaner. Hold the board on an angle and allow it to run underneath the BGA. Use a paper towel to soak up the liquid as it runs out, so it doesn't run all over the board and under other components. Turn 90-deg and repeat. Repeat with 99% IPA, doing the same procedures. Spray, turn,...spray, turn...spray, turn...etc. Dry thoroughly before continuing on to the reflow. Be sure to use compressed air to blow out the liquid hiding underneathe the chips. I can look dry when it isn't, so be sure (don't use heat to speed the process). Just sit in front of a fan for 2 hours or so (if your house is very dusty, maybe place a paper towel over the back side of the fan to filter the air first).

Then use AMTECH flux for the reflow. Heat it to 150C and hold it there for 3-5minutes before increasing to reflow temps. That activates the flux (undoes oxidation). That's the best you can hope for with a reflow, but it's not going to last as long a reball, if it works at all. Only reballing can getrid of stubbarnly oxidized pads. But this cleaning/flux process gives you the best chance.
Click to expand...
Ended up getting it fixed with a reflow. Definitely cleaned off well before attempting. I like that you suggested using amtech flux as this is the method I use for reflows. Things working like a charm now...

I'm working on an A model now with what seems to be A0213013 as the main error. I've removed C4001, having a hard time getting a reading on it though and also don't see it listed in the schematic as to what it is supposed to be reading, although i'm no expert at reading these. I'm not sure my multimeter is good enough to read this particular cap. Any experience by chance chasing down this error code?

A0213013 = BE_SPI DI/DO ERROR - CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead?
 
Last edited:
Checkity_CheckYoSelf said:
...I'm working on an A model now with what seems to be A0213013 as the main error. I've removed C4001, having a hard time getting a reading on it though and also don't see it listed in the schematic as to what it is supposed to be reading, although i'm no expert at reading these. I'm not sure my multimeter is good enough to read this particular cap. Any experience by chance chasing down this error code?

A0213013 = BE_SPI DI/DO ERROR - CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead?
Click to expand...

C4001 on an A model is 1uF 10V.

3013 isn't a listed error in the SYSCON PDF. It skips from 3012 to 3020. However we have seen error 3013 before in a SEM-001, so there are errors that are not on the PDF...
Kleon1876 said:
So here is an update.

I have a SEM-001 which had GLOD. I have removed RSX bottom 2 tokins, havent replaced them with tantlums yet. I dumped the error codes originally and i got the following.

===================================
ERR 00: 00000000 A0213013 FFFFFFFF
ERR 01: 00000000 A0213013 FFFFFFFF
ERR 02: 00000000 A0213013 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0213013 FFFFFFFF
ERR 11: 00000000 A0213013 FFFFFFFF
ERR 12: 00000000 A0213013 FFFFFFFF
ERR 13: 00000000 A0213013 FFFFFFFF
ERR 14: 00000000 A0213013 FFFFFFFF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
BE_SPI DI/DO ERROR - CELL not communicating to syscon via
SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible
shorts on the line, check C4001 and trailing caps. Possible CELL dead?
ERR 17: 00000000 A0403034 FFFFFFFF
Poor BGA solder connections for RSX
( you will see errors like - [POWERSEQ] Error :
BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
ERR 18: 00000000 A0404411 FFFFFFFF
Poor BGA solder connections for RSX
( you will see errors like - [POWERSEQ] Error :
BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )
ERR 19: 00000000 A0402101 FFFFFFFF
???????????????????
===================================

after this, I decided to remove the RSX to reball.
I dumped the error codes without the rsx on and still missing the two necs on the bottom of the pcb. Got the following error codes.
===================================
ERR 00: 00000000 A0093003 FFFFFFFF
ERR 01: 00000000 A0A02031 FFFFFFFF
ERR 02: 00000000 A0A02030 FFFFFFFF
ERR 03: 00000000 A0213013 FFFFFFFF
ERR 04: 00000000 A0213013 FFFFFFFF
ERR 05: 00000000 A0213013 FFFFFFFF
ERR 06: 00000000 A0213013 FFFFFFFF
ERR 07: 00000000 A0213013 FFFFFFFF
ERR 08: 00000000 A0213013 FFFFFFFF
ERR 09: 00000000 A0213013 FFFFFFFF
ERR 10: 00000000 A0213013 FFFFFFFF
ERR 11: 00000000 A0213013 FFFFFFFF
ERR 12: 00000000 A0213013 FFFFFFFF
ERR 13: 00000000 A0213013 FFFFFFFF
ERR 14: 00000000 A0213013 FFFFFFFF
ERR 15: 00000000 A0213013 FFFFFFFF
ERR 16: 00000000 A0213013 FFFFFFFF
ERR 17: 00000000 A0213013 FFFFFFFF
ERR 18: 00000000 A0213013 FFFFFFFF
ERR 19: 00000000 A0213013 FFFFFFFF
===================================

As you can see 3013 persisted even tho no RSX. My theory is its either RSX related, or has nothing to do with RSX (maybe because necs are missing). New errors popped up tho 3003, 2031 and 2030. since I removed the RSX. My guess 3003, 2031, 2030 are RSX related error. I also screwed up some tiny capacitors that came off near the RSX. I'll post a picture of the PCB next. What are your thoughts to help narrow down these errors to a specific part?

Also, where did my original errors go when I hadn't removed the RSX including 4411, 3035 and 2101. All i did was remove the RSX...and some tiny components next to the rsx.

and I think I killed the cpu when I was deliding it up scratching it.
Click to expand...
@Kleon1876 were those 3013 error before or after you delided the CPU? @Checkity_CheckYoSelf, did you delid the CPU? Maybe you should Ceckity_CheckYoCPU for damage. It's also possible it's the BGA.

You didn't type that in backwards did you? Do you mean 3031? If so, no I don't have it listed in my PDF (in which I've been making notes). User @Bbowes9 recently had a 3031 here. It's still unresolved AFAIK. I suspect it's another potential thing that BGA defects can affect, but IDK don't know.

@Kleon1876 @squeept what were the errors after squeept fixed your damaged CPU traces? Did the 3013 disappear?
 
Last edited:
RIP-Felix said:
C4001 on an A model is 1uF 10V.

3013 isn't a listed error in the SYSCON PDF. It skips from 3012 to 3020. However we have seen error 3013 before in a SEM-001, so there are errors that are not on the PDF...

@Kleon1876 were those 3013 error before or after you delided the CPU? @Checkity_CheckYoSelf, did you delid the CPU? Maybe you should Ceckity_CheckYoCPU for damage. It's also possible it's the BGA.

You didn't type that in backwards did you? Do you mean 3031? If so, no I don't have it listed in my PDF (in which I've been making notes). User @Bbowes9 recently had a 3031 here. It's still unresolved AFAIK. I suspect it's another potential thing that BGA defects can affect, but IDK don't know.
Click to expand...
Yea it's defintitely A0213013 is the error i'm getting. I unfortunately did attempt a reflow of the cpu and gpu initially when I got this as I was being impatient waiting for my cousin to get me some of those connector wires to use my syscon. I should of honestly waited, instead I started throwing darts at the wall. I swapped out my two NEC caps with 8 tantalum 470's. Did a nice clean job on that. I hope I didn't fry the CPU though with jumping first at doing a reflow before testing with the syscon. If I did I did, and that's my bad for being impatient. Now that I know how easy it is to use the syscon, this will always be my first start before jumping into attempting random fixes. I have not attempted a de-lid on this as of yet but i'm certainly capable of it if there's a chance it'll help. I have done several now so i'm definitely comfortable with it now.

Still gonna try a few more things. I'm still kind of wet behind the ears with tracing power faults on a mobo, but I have a decent multimeter and i'm still gonna see if I can get this CECHA model back up and going.

This is my full error log I had pulled the other night, if this helps any... I'll keep you posted on the CECHE model, but so far she's running real good now after the reflow and now that it's on CFW. I gave it a nice full reflow with good amtech flux so hopefully she'll stay up and going for me for a while. I may end up selling this one though, as I already am hoarding too many consoles. Lol

> ERRLOG GET 00
00000000 A0003001 FFFFFFFF
> ERRLOG GET 01
00000000 A0003001 FFFFFFFF
> ERRLOG GET 02
00000000 A0003001 FFFFFFFF
> ERRLOG GET 03
00000000 A0003001 FFFFFFFF
> ERRLOG GET 04
00000000 A0003001 FFFFFFFF
> ERRLOG GET 05
00000000 A0003001 FFFFFFFF
> ERRLOG GET 06
00000000 A0213013 FFFFFFFF
> ERRLOG GET 07
00000000 A0202120 FFFFFFFF
> ERRLOG GET 08
00000000 A0202120 FFFFFFFF
> ERRLOG GET 09
00000000 A0202120 FFFFFFFF
> ERRLOG GET 10
00000000 A0202120 FFFFFFFF
> ERRLOG GET 11
00000000 A0213013 FFFFFFFF
> ERRLOG GET 12
00000000 A0202120 FFFFFFFF
> ERRLOG GET 13
00000000 A0202120 FFFFFFFF
> ERRLOG GET 14
00000000 A0202120 FFFFFFFF
> ERRLOG GET 15
00000000 A0202120 FFFFFFFF
> ERRLOG GET 16
00000000 A0202120 FFFFFFFF
> ERRLOG GET 17
00000000 A0202120 FFFFFFFF
> ERRLOG GET 18
00000000 A0202120 FFFFFFFF
> ERRLOG GET 19
00000000 A0202120 FFFFFFFF
 
Last edited:
Hello guys,

today I got another VER-001 in my hands:


It starts up, goes through all three stages and then shuts down after 15-20seconds.
No output on screen.

Now, during these 15 seconds, i see:
> powerstate
00000000
# ATA :ON
# PCI :OFF
# PCIex:OFF
# RSX :ON
# GDDR :ON
# XDR :ON
# EURUS:ON
# SB :ON
Click to expand...

And then three beeps...

> auth
Auth1 response invalid
> auth
Auth successful

> revision
00000000
# Revision = 1629(065D)

> version
00000000
# Sherwood Version = 0.17.0

> eepcsum
00000000
# csum = 0xE083

> patchinfo
00000000
#
# MAJOR :0000
# MINOR :0000
# REV :0000
# SYS_REV :0000
# TABLE :00FFFFFF
# DATSIZ :FFFF
# DATSUM :FFFF
# SUM :FFFF
# not applyed


> bestat
00000000
# (PowerOff State)
# State = 00

> bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.5.0
#!(Build ID: 3318,35708,
#!Build Date: 2008-10-11_00:31:58)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [UCMD] Invalid Argument.


> errlog
00000000
# CODE CLOCK
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# A0802124 0C5BC655
# A0801002 0C5BC655
# A0802124 0C5BBD41
# A0801002 0C5BBD41
# A0802124 0C5BBD15
# A0802124 0C5BBD14
# A0801002 0C5BBD14
# A0802124 0C5BBAE4
# A0802124 0C5BBAE4
# A0801002 0C5BBAE3
# A0802124 0C5BBA94
# A0802124 0C5BBA94
# A0801002 0C5BBA93
# A0802124 0C5BBA30
# A0802124 0C5BBA30
# A0801002 0C5BBA2F
# A0802124 0C5BB9F9
# A0801002 0C5BB9F9
# A0802124 0C5BB9CD
# A0801002 0C5BB9CD
# A0802124 0C5BB9B1
# A0802124 0C5BB9B0
Click to expand...


A0801002 = RSX Power on VRAM failure
A0802124 = ????

Similar error:
A0802120 = HDMI Power on failure (IC2502) - Sil9132CBU chip failure or related power line failure - check diodes,fuses and regulator IC2501

So perhaps this case would indicate that NEC/Tokin must be replaced for RSX?
Or... can someone confirm whether A0802124 would also be related to HDMI?

Maybe I'd do the CPU/RSX delid first.
Replace the TC under ihs.
Then test...

If not working, then replace two RSX tokins for tantalum ones.

After that, I assume the A0801002 error should be gone, right?
So.. if there still won't be any output on the screen, but the console won't be turning off... I'd go for the HDMI part, right?
 
RIP-Felix said:
I just confirmed with a stock COK-002 that has never been opened before...
Code: 
>$ EEP GET 3901 01
00000000 BF

So yeah, execute EEP SET 3901 01 BF, log back into internal access mode to fix the checksum, and see if that was the problem.
Click to expand...
First I would like to thank everyone here for their help, reading this forum I learned a lot about the PS3!


@RIP-Felix, I fixed the checksum!
Now the HD light blinks once and I have syscon errors again. Errors 1701 and 3034, GLOD on start. I'm thinking about reflowing the RSX and CPU. I even bought a small hot air station for this.


I bought a CECHA never opened, very new. with ylod when starting.
Error 1002 in syscon.
I added 3 tantalus capacitors on rsx and it worked perfectly.
I didn't perform nectokin removal. so I have a question, leaving the nectokin or having an excess of capacitors can damage the rsx and cpu?
 
Last edited:
SkaziChris said:
Hello guys,

today I got another VER-001 in my hands:


It starts up, goes through all three stages and then shuts down after 15-20seconds.
No output on screen.

Now, during these 15 seconds, i see:


And then three beeps...




A0801002 = RSX Power on VRAM failure
A0802124 = ????

Similar error:
A0802120 = HDMI Power on failure (IC2502) - Sil9132CBU chip failure or related power line failure - check diodes,fuses and regulator IC2501

So perhaps this case would indicate that NEC/Tokin must be replaced for RSX?
Or... can someone confirm whether A0802124 would also be related to HDMI?

Maybe I'd do the CPU/RSX delid first.
Replace the TC under ihs.
Then test...

If not working, then replace two RSX tokins for tantalum ones.

After that, I assume the A0801002 error should be gone, right?
So.. if there still won't be any output on the screen, but the console won't be turning off... I'd go for the HDMI part, right?
Click to expand...
Yes, if that 1002 is persistent or being generated at every YLOD, it has to do with the Filter (which includes more than just the Tokins). However, yes, you have the right type of error and YLOD behavior to suggest the tokins need replaced. Changing the TIC at this point won't do anything. However, if you make a mistake and scratch the CPU then it's better to destroy the console before doing a bunch of work first. So yeah, delid now. Just be careful so that you don't make replacing the tokins pointless.

2024 is undocumented. @vyktormvmpay25 if you have seen this error before, how did you resolve it? I'll add a note to my PDF.

EDIT:
Nevermind, I read that link you posted. Here's the note I added to my PDF.
@victormvmpay25 had 2124 and 2024 errors in a super slim that he fixed by replacing both the AV and HDMI encoders. He didn't check which cause the error, just replaced them both. Other users have reported 2024/2124 errors too. Another user resolved it by replacing the HDMI encoder. They tend to cause a delayed YLOD (10s-1min). Sometimes described as a GLOD. One user had them associated with a 1002.
Click to expand...

@SkaziChris you may also have to replace the HDMI encoder. It's a BGA package, so I hope you have the skills to do it. IDK if the replacments you can buy come preballed, but it so it should be doable if you have a hot air station and AMTECH flux. If you can pull off the tokin fix, then the HDMI encoder is not too hard (just different).
 
Last edited:
RIP-Felix said:
Yes, if that 1002 is persistent or being generated at every YLOD, it has to do with the Filter (which includes more than just the Tokins). However, yes, you have the right type of error and YLOD behavior to suggest the tokins need replaced. Changing the TIC at this point won't do anything. However, if you make a mistake and scratch the CPU then it's better to destroy the console before doing a bunch of work first. So yeah, delid now. Just be careful so that you don't make replacing the tokins pointless.

2024 is undocumented. @vyktormvmpay25 if you have seen this error before, how did you resolve it? I'll add a note to my PDF.

EDIT:
Nevermind, I read that link you posted. Here's the note I added to my PDF.


@SkaziChris you may also have to replace the HDMI encoder. It's a BGA package, so I hope you have the skills to do it. IDK if the replacments you can buy come preballed, but it so it should be doable if you have a hot air station and AMTECH flux. If you can pull off the tokin fix, then the HDMI encoder is not too hard (just different).
Click to expand...


Many thanks for your reply.

RSX delid is done.

CPU delid is done.

SYSCON retest after both delids and new TC applied.

Long story short.
After clearing the error log, and reissuing bootup sequence, I still see following errors:
> errlog
00000000
# CODE CLOCK
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
Click to expand...

Next... I will go on and replace the HDMI IC...
 
Last edited:
HDMI IC removal:


SYSCON retest with HDMI IC removed from the board.

> auth
Auth successful
> ERRLOG CLEAR
FFFFFFFF Answer length
>
F0000003
OK 00000000

> errlog
00000000
# CODE CLOCK
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

> bringup
00000000
# [SSM] Bringup Start.

> powerstate
FFFFFFFF Answer length
> powerstate
FFFFFFFF Answer length
> powerstate
FFFFFFFF Answer length
> powerstate
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.5.0
#!(Build ID: 3318,35708,
#!Build Date: 2008-10-11_00:31:58)
#!
#!Copyright(C) 2008 Sony Computer Entertainment Inc.All Rights Reserved.
#!

>
F0000002
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] csumerr.

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

> errlog
00000000
# CODE CLOCK
# A0802024 FFFFFFFF
# A0802024 FFFFFFFF
# A0802124 FFFFFFFF
# A0802024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF

> shutdown
00000000
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

>
Click to expand...
 
So I started working on another CECHE board (COK-002) I had hanging out in the stash last night. Was able to clear my first run of codes using some hot air and flux. Cleared those codes successfully, but apparently knocked off a resistor in the process that got lost. Looking at the schematic it appears to be R1165 located just to the right of IC1101. The code that led me to this was A0A02030. I'm looking at the schematic to try to determine what resistor value I should be using as a replacement, and it states XX on the schematic. I dont' see it listed in the parts list section of the schematic. Does anyone by chance know what value of resistor I should be replacing this with?

upload_2021-9-14_8-30-27.png
 
Checkity_CheckYoSelf said:
So I started working on another CECHE board (COK-002) I had hanging out in the stash last night. Was able to clear my first run of codes using some hot air and flux. Cleared those codes successfully, but apparently knocked off a resistor in the process that got lost. Looking at the schematic it appears to be R1165 located just to the right of IC1101. The code that led me to this was A0A02030. I'm looking at the schematic to try to determine what resistor value I should be using as a replacement, and it states XX on the schematic. I dont' see it listed in the parts list section of the schematic. Does anyone by chance know what value of resistor I should be replacing this with?

View attachment 34887
Click to expand...
XX means wasn't there. Something wrong with cpu.Add photo so we can compare it.
 
Last edited:
SkaziChris said:
Many thanks for your reply.

RSX delid is done.

CPU delid is done.

SYSCON retest after both delids and new TC applied.

Long story short.
After clearing the error log, and reissuing bootup sequence, I still see following errors:


Next... I will go on and replace the HDMI IC...
Click to expand...

Well, the videos were helpful. I can see you have good equipment. Question: Do you have an Oscilloscope? If so, you can probe VDDC and measure the noise to confirm bad tokins. Set scope to 50mV/div and 1uS, trigger at 1v. Noise should be under 50mVpp.

I would start with the troubleshooting the VDDC filter on both the CPU and RSX. First compare the resistance and ESR of the first stage RC filter. It amplifies the attenuation of the second stage (tokins). So if the first stage is bad, the whole filter will be detuned. and cause the 1002 error. It's easier to replace a couple of SMD's. Compare the values to the other 3-4 in the filter. Here's what I mean...
1st stage filter.jpg

...The resistanc and ESR of those SMD's should match (within reason). If not replace and retest, before removing the tokins.

Stuff you get to skip thanks to the SYSCON UART Diagnosis (Imagine how much time that would have wasted):
  • ESR/resistance of the larger MLCC's next to the IOR VRM and the electrolytic caps. I'm sure they're fine or you'd get 1004 error and the RSX wouldn't start.
  • Compare the SMD components next to the Inductors to a known good board (to the left of the inductors in the pic above. May be different on a VER-001 IDK). There are more on the back side.
  • Check for voltage @ a few MOSFET in that section. The console wouldn't be booting this long or report a RSX OK PowerState if there were an issue here.
If the 1st stage filter is fine, then replace each tokin with 3x470uF Low ESR TaPol caps. I recommend Panasonic 2R5TPF470M6L or you can harvest them from dead motherboards. AlPol caps will work too, but they're theoretically not as good. You also need to bridge the + rails with at least 16AWG.
 
Checkity_CheckYoSelf said:
So I started working on another CECHE board (COK-002) I had hanging out in the stash last night. Was able to clear my first run of codes using some hot air and flux. Cleared those codes successfully, but apparently knocked off a resistor in the process that got lost. Looking at the schematic it appears to be R1165 located just to the right of IC1101. The code that led me to this was A0A02030. I'm looking at the schematic to try to determine what resistor value I should be using as a replacement, and it states XX on the schematic. I dont' see it listed in the parts list section of the schematic. Does anyone by chance know what value of resistor I should be replacing this with?

View attachment 34887
Click to expand...
Pro Tip: Press CTRL+F to search the PDF. Then write in the part (eg, R2001). It'll take you to everywhere in the schematic it's found. I wish it worked for Text too. It would be nice to be able to search for signal names and voltages, but you can't.

A0 2031 & 09 3003 were seen in a CPU with bump failures on the die due to heat damage (delamination). looked like a heat gun special. Anyway it can act like thermal error in RSX or CELL. Saw something similar with @botakompong when he had 2131 and changed the CPU set to fix it. We're still unsure if 2031 and 2131 are related, but they may be. 2030 is the same error, but for the CPU. You'll probably have to reball if the reflow didn't work. You did cover the hole in the PCB under the CPU with aluminum tape, right? Otherwise you probably didn't actually reflow the CPU. Just an FYI.
 
You must log in or register to reply here.

Similar threads

Back
Top