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

I cant edit my other post, sorry for the doublepost.

I checked the syscon error codes again and there is nothing new.
I've updated the ps3 firmware to the latest version and everything looks fine over AV, still got a black screen when connected to HDMI though.
 
Chmielu77 said:
Hello, im working on a COK-002 motherboard. Im getting 3010 error on startup. It happend after CELL and RSX delid.
Somebody already replaced NEC TOKIN capacitors with tantalums. CELL has been delided, I checked under the microscope and it looks ok, has some scratches on the interposer, but there are no traces in the area. I made resistance mesurments around CELL and RSX and everything looks ok, but i have only 83 ohms on FBVDDQ. Console has previously 3034 error if this matters. Board doesn't have any sign of BGA rework.​
Here is bringup log:
Code: 
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
[POWERSEQ] Error : wait attention timeout.(SEQ1)
[SSM] state: 0102 -> 0302
[SSM] PowSeq Fail : Detected !
[SSM] state: 0302 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0203010
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

Can somebody give me hint what to check next? Any help will be appreciated.
Click to expand...

A little update about that console. Recently i upgraded my microscope, and decided to took the board under new microscope, and looks like I missed that during CELL delid I managed to damage two tiny SMD components near CELL. After replacing them and RSX with 40 nm one, console is working again! Another frankie is alive! :P

@DeadEnd Again thank you for the advices, apparently issue was very simple and I'm blind idiot :D​
 
Hello. I have a ps3 with ylod. I tried a flow chips but i didn't get result. I want order FT232RL and diagnose syscon. What FT232RL better? With type-c or mini-usb
 
Hello knowledgable and helpful fellow PS3 enthusiasts.

So my PS3 PHAT died while i was on holiday abroad and it was in an empty house not being used.
Got home, pressed on and I get the green light, flash yellow, 3 beeps and flashing red.

Here is my errlog from syscon.

Would anyone be able to give some pointers? I have looked up the individual error codes but i was hoping someone with more knowledge than me might identify this particular combination and have a hunch what may be the cause.

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

Thanks in advance.

AcidReach
 
Hello everyone,

I have CECHL that seems to have faulty tokins, but there's some weird symptoms that makes me doubt.
  1. It starts up for really briefly short after warming from several bringup. By that I mean, system will keep running, but as soon as it displays the safe mode message, it YLODs.
  2. Sometimes the LED just... blinks and beeps at the same time. Usually 5-10 seconds before the YLOD. Not consistent, but it tends to go away once console starts warming up.
syscon logs says otherwise though. Is this non-tokin fail somewhere in power block?
EDIT : I have used another PSU from other CECHL I have. did not change the results.
Code: 
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

F0000003
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.4.5
#!(Build ID: 3163,33519,
#!Build Data: 2008-07-14_20:31:16)
#!
#!Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [UCMD] Unknown command.

00000000
# [UCMD] Unknown command.
NG F0000003
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.

F0000003
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [UCMD] Unknown command.

Code: 
# CODE     CLOCK
# A0802124 FFFFFFFF
# A0802124 FFFFFFFF
# A0801002 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
errlog was filled with two 2124, and one 1002

there were no becount on my syscon, so I used "r 800 8".
Code: 
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 0A 45 0A 24 00 BF DC 94
-> 2629 bringups
-> 2596 shutdowns
-> 12573844 seconds
-> 145 days, 12 hours and 44 minutes
 
Hey guys,
I got my hands on a Ps3 CECHCxx at a reasonable price. This one had GLOD so I thought it would be perfect as practice for a Frankenstein mod. I read the syscon and surprisingly only got 1001 and 1002 errors. The console was unopened and I was the first to take it apart. So I removed the NEC tokens on the RSX side and replaced them with a RIP Felix board that I had fitted with capacitors. Now I only get 3004 errors. I have checked all my soldering again, no broken solder connections and no shorts. What could be the reason? Should I remove the small board again, clean it and solder it again?
 
nothanks said:
alright got the new chip in and all the signals are showing good. havent gotten the hdmi to work yet but now i can get into recovery. no im getting stopped trying to reinstall the firmware. its asking for firmware 4.25 or newer, i throw 4.25 on the flashdrive (tried multiple). its set mbr/fat32, active. file is at PS3>UPDATE>PS3UPDAT.PUP. tried setting the allocation to16kb, default, and 4092. still get stuck with checking please wait until it says it cant find the file. tried a new hdd fresh out of the box too. tried the unplug the controller thing as well. im currently running through cex, dex, and ofw just because i have no way of telling whats on the thing. anyone have anything for my new issue? the old hdd let me rebuild the database but after or on normal boot it still only black screens. no new errors have been recorded either. they still all have the same 2024/2124 listed but thats probably from before.

updated: 11-30-2024
welp reflowed the rsx and got hdmi back. ran cex 4.25 and get error 8002f313.
Click to expand...

How did you go in the end?
Update on my error (A0A02124, A0A02024) device, I replaced the HDMI port in addition to the HDMI encoder and I got an image over HDMI briefly. I had to set it to the lowest resolution and enable one by one and I was able to work it up to 1080i (1080p gave no image).

I turned it off after getting the 1080i HDMI signal and then it gave no image again on subsequent boot.

Now it only works on the Av multi out port again.
I'm thinking that it might just be an RSX issue but I don't have the right tools to reflow that, only a cheap hot air station.
 
first time doing anything like this and would like help on what issues these codes require for a remedy. i came across this ps3 cecha001 while recycling at my local recycle center. I asked an attendant if I could have it and he aloowed me to take it. it looked fine on the outside, besides having the top cover off with the DVD drive, PSU, and Memory card visible, no HDD. So bought it home popped in a fat32 formatted 60GB hdd, setup a fat32 formated usb w/ root of PS3>UPDATE>PS3UPDAT.PUP (v3.50 OFW) because I am still unsure of what version is on it currently. nonetheless, I safe mode booted and chose option 6 in recovery menu; it instructed to plug in controller, hold select>start for 5 seconds, then started formatting/updateing/installing. a few minutes in, the screen just froze (with what looked like sporadic green vertical Matrix lines (it wasn't as far as I know, but it resembled them). and it wasn't full screen, just small around bottom, top and left and right. So, i came across RIP Felix fantastic video tutorial on ttl / uart to gain access to internal commands (first CXR and then CXRF) which are listed below. i included what I was allowed to generate -- becount and internal errlog. a lot of other commands available, i.e. serial number, board number and a few others produced an *unknown* reply. not sure what's going on. any help or suggestions or whatever would be cool. I appreciate in advance all replies.



Code: 
>$ becount
becount
Bringup : 3943 times
Shutdown: 3877 times
Power-on: 257day 08hour 14min 29sec
[mullion]$
Code: 
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0404411, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0404411, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0404411, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0404411, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0404411, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404411, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404411, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0404411, clock:0xffffffff
ofst[  8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0801004, clock:0x0b49dbb6  2006/01/01 00:15:50
ofst[ 16]:err_code:0xa0801004, clock:0x0b49dc71  2006/01/01 00:18:57
ofst[ 20]:err_code:0xa0801004, clock:0x0b49dcd5  2006/01/01 00:20:37
ofst[ 24]:err_code:0xa0801004, clock:0x0b49ddb9  2006/01/01 00:24:25
ofst[ 28]:err_code:0xa0801004, clock:0x0b49dfb4  2006/01/01 00:32:52
ofst[ 32]:err_code:0xa0801004, clock:0x0b49e7f4  2006/01/01 01:08:04
ofst[ 36]:err_code:0xa0801004, clock:0x0b49e838  2006/01/01 01:09:12
ofst[ 40]:err_code:0xa0801004, clock:0x0b49e850  2006/01/01 01:09:36
ofst[ 44]:err_code:0xa0801004, clock:0x0b4adab5  2006/01/01 18:23:49
ofst[ 48]:err_code:0xa0801004, clock:0xffffffff
ofst[ 52]:err_code:0xa0801001, clock:0xffffffff
ofst[ 56]:err_code:0xa0801001, clock:0xffffffff
ofst[ 60]:err_code:0xa0801001, clock:0xffffffff
ofst[ 64]:err_code:0xa0801001, clock:0xffffffff
[mullion]$
 
james1962.k said:
first time doing anything like this and would like help on what issues these codes require for a remedy. i came across this ps3 cecha001 while recycling at my local recycle center. I asked an attendant if I could have it and he aloowed me to take it. it looked fine on the outside, besides having the top cover off with the DVD drive, PSU, and Memory card visible, no HDD. So bought it home popped in a fat32 formatted 60GB hdd, setup a fat32 formated usb w/ root of PS3>UPDATE>PS3UPDAT.PUP (v3.50 OFW) because I am still unsure of what version is on it currently. nonetheless, I safe mode booted and chose option 6 in recovery menu; it instructed to plug in controller, hold select>start for 5 seconds, then started formatting/updateing/installing. a few minutes in, the screen just froze (with what looked like sporadic green vertical Matrix lines (it wasn't as far as I know, but it resembled them). and it wasn't full screen, just small around bottom, top and left and right. So, i came across RIP Felix fantastic video tutorial on ttl / uart to gain access to internal commands (first CXR and then CXRF) which are listed below. i included what I was allowed to generate -- becount and internal errlog. a lot of other commands available, i.e. serial number, board number and a few others produced an *unknown* reply. not sure what's going on. any help or suggestions or whatever would be cool. I appreciate in advance all replies.
*****UPDATE***** I also wanted to mention that "psxpro" and someones initials/signature is written on the MB. i thought that may be helpful. the 3v battery was depleted as well and I replaced that, too ... as well as I reapplied thermal paste after the TTL endeavor. and after a little more research while waiting for a reply here, I seen that the RSX may need reballed. and an additional question would be can this MB be "baked" in the oven to attempt a hail-mary reball/reflow/re-solder connection?



Code: 
>$ becount
becount
Bringup : 3943 times
Shutdown: 3877 times
Power-on: 257day 08hour 14min 29sec
[mullion]$
Code: 
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0404411, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0404411, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0404411, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0404411, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0404411, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404411, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404411, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0404411, clock:0xffffffff
ofst[  8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0801004, clock:0x0b49dbb6  2006/01/01 00:15:50
ofst[ 16]:err_code:0xa0801004, clock:0x0b49dc71  2006/01/01 00:18:57
ofst[ 20]:err_code:0xa0801004, clock:0x0b49dcd5  2006/01/01 00:20:37
ofst[ 24]:err_code:0xa0801004, clock:0x0b49ddb9  2006/01/01 00:24:25
ofst[ 28]:err_code:0xa0801004, clock:0x0b49dfb4  2006/01/01 00:32:52
ofst[ 32]:err_code:0xa0801004, clock:0x0b49e7f4  2006/01/01 01:08:04
ofst[ 36]:err_code:0xa0801004, clock:0x0b49e838  2006/01/01 01:09:12
ofst[ 40]:err_code:0xa0801004, clock:0x0b49e850  2006/01/01 01:09:36
ofst[ 44]:err_code:0xa0801004, clock:0x0b4adab5  2006/01/01 18:23:49
ofst[ 48]:err_code:0xa0801004, clock:0xffffffff
ofst[ 52]:err_code:0xa0801001, clock:0xffffffff
ofst[ 56]:err_code:0xa0801001, clock:0xffffffff
ofst[ 60]:err_code:0xa0801001, clock:0xffffffff
ofst[ 64]:err_code:0xa0801001, clock:0xffffffff
[mullion]$
Click to expand...
 
UPDATE RE: My posts #4430 & #4431. I believe I have successfully fixed/repaired my PS3 CECHA001 by de-lidding the RSX and cleaning the almost non-existent thermal paste. I then applied new thermal paste and re-assembled everything and let it sit for a few hours while we cooked and enjoyed Christmas dinner. belly full, hooked it up and installed a new 500gb fat32 formatted HDD and reformatted a 8gb usb drive fat32 as well and D/L an OFW v4.80 and safe booted and nervously plugged in controller to far-right usb port, and chose to format and install and after the step of holding both SELECT and START to proceed, I started feeling nervous...and it go to 30% and I flt hope because by now, in the past, it would have frozen, but it kept trucking and finally completed. restarted, accepted T&C's, ajusted correct date and time ,etc. and now I am able to use normally w/o issues. I realize I may have posted to the wrong forum section, because I dont believe it was a YLOD due to the fact that I was able to get SOME operation. after viewing RIP Felix's vid tutorial on obtaining error codes via serial conn., I was able to see an overheat issue. and took my chance with RSX due to screen freezing. I did go to ps3toolset again by watching RIP Felix vid and I took pics of the results. Perhaps the mods or experts can compare them w/ the logs from my original post. Replies and/or questions welcomed. Thx again.
BM83TZC

https://imgur.com/a/BM83TZC Forum newbie so unsure how to insert or attach my pictures so I uploaded them to my imgur acct.




Code: 
>$ becount
becount
Bringup : 3943 times
Shutdown: 3877 times
Power-on: 257day 08hour 14min 29sec
[mullion]$
Code: 
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 68]:err_code:0xffffffff, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0404411, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0404411, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0404411, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0404411, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0404411, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404411, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404411, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0404411, clock:0xffffffff
ofst[  8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0801004, clock:0x0b49dbb6  2006/01/01 00:15:50
ofst[ 16]:err_code:0xa0801004, clock:0x0b49dc71  2006/01/01 00:18:57
ofst[ 20]:err_code:0xa0801004, clock:0x0b49dcd5  2006/01/01 00:20:37
ofst[ 24]:err_code:0xa0801004, clock:0x0b49ddb9  2006/01/01 00:24:25
ofst[ 28]:err_code:0xa0801004, clock:0x0b49dfb4  2006/01/01 00:32:52
ofst[ 32]:err_code:0xa0801004, clock:0x0b49e7f4  2006/01/01 01:08:04
ofst[ 36]:err_code:0xa0801004, clock:0x0b49e838  2006/01/01 01:09:12
ofst[ 40]:err_code:0xa0801004, clock:0x0b49e850  2006/01/01 01:09:36
ofst[ 44]:err_code:0xa0801004, clock:0x0b4adab5  2006/01/01 18:23:49
ofst[ 48]:err_code:0xa0801004, clock:0xffffffff
ofst[ 52]:err_code:0xa0801001, clock:0xffffffff
ofst[ 56]:err_code:0xa0801001, clock:0xffffffff
ofst[ 60]:err_code:0xa0801001, clock:0xffffffff
ofst[ 64]:err_code:0xa0801001, clock:0xffffffff
[mullion]$
[/QUOTE]
 
Hey yall, Im trying to fix a ylod cecha01, cok 001. Was given it by a friend, me and him ovened it in an attempt to fix ylod like 7 years ago. Same symptoms as before it was ovened, no board damage from being ovened that i can see. read syscon codes and they all said A0231002. Spent a few hours researching and decided to do capictor replacement. Felix tantelizors looked a little past my soldering ability so i decided it would be best to just solder standard ebay 470uf 6vs. I replaced all nec tokins on the bottom of the board with 4x tantulums each, and only replaced the nec tokins on the top of the board by the rsx with 6x tantulums, as the internet seems to tell me that 14 tantulums should be more than enough. While soldering the tantulums on i got several different errors , including A0101002,s AO091002s, a single A0063004, and maybe one other . After cleaning up my tantulum job and redoing a part that i thought might have shorted I now only get A0231002 as it was when i started before the tantulum replacement. Any ideas where to look on the board with step number 23, its about a 2 secon ylod, never seen the console boot. My only thoughts are that im misunderstanding my tantulum installation heavilly, or the board was cooked by the oven and something earlier in the power pipeline is wrong. I have tried 3 different power supplies from known consoles and same issue. Any ideas?
 
kianiscoooooool said:
Hey yall, Im trying to fix a ylod cecha01, cok 001. Was given it by a friend, me and him ovened it in an attempt to fix ylod like 7 years ago. Same symptoms as before it was ovened, no board damage from being ovened that i can see. read syscon codes and they all said A0231002. Spent a few hours researching and decided to do capictor replacement. Felix tantelizors looked a little past my soldering ability so i decided it would be best to just solder standard ebay 470uf 6vs. I replaced all nec tokins on the bottom of the board with 4x tantulums each, and only replaced the nec tokins on the top of the board by the rsx with 6x tantulums, as the internet seems to tell me that 14 tantulums should be more than enough. While soldering the tantulums on i got several different errors , including A0101002,s AO091002s, a single A0063004, and maybe one other . After cleaning up my tantulum job and redoing a part that i thought might have shorted I now only get A0231002 as it was when i started before the tantulum replacement. Any ideas where to look on the board with step number 23, its about a 2 secon ylod, never seen the console boot. My only thoughts are that im misunderstanding my tantulum installation heavilly, or the board was cooked by the oven and something earlier in the power pipeline is wrong. I have tried 3 different power supplies from known consoles and same issue. Any ideas?
Click to expand...

Did you remember to bridge the two positive contacts on the RSX side, if you didn't you'd have errors similar to this since the RSX wouldn't see RSX_VDDC.

Tantalizers are generally better than cheap ebay caps, actually, anything is, you should order parts from reputable sites like mouser or digikey so you know what you're actually getting. Tantalizers are a bit easier to solder imo as long as your iron is able to handle the PS3 ground plane.
 
RGBeter said:
Did you remember to bridge the two positive contacts on the RSX side, if you didn't you'd have errors similar to this since the RSX wouldn't see RSX_VDDC.

Tantalizers are generally better than cheap ebay caps, actually, anything is, you should order parts from reputable sites like mouser or digikey so you know what you're actually getting. Tantalizers are a bit easier to solder imo as long as your iron is able to handle the PS3 ground plane.
Click to expand...

Hey, ill try bridging them more today as i see that in videos where people do this with tantulums on their own they bridge them with several wires and i even see that in rip felixs video his bridge wire lights on fire from having too much current going through one wire. I have already bridged the topside once and the bottom side once though. I was hoping to see the console turn on before i did a cleaner job. While im doing that, do you think i need to replace the nec tokins on the topside next to the cpu, ive never gotten a cpu error
 
kianiscoooooool said:
Hey, ill try bridging them more today as i see that in videos where people do this with tantulums on their own they bridge them with several wires and i even see that in rip felixs video his bridge wire lights on fire from having too much current going through one wire. I have already bridged the topside once and the bottom side once though. I was hoping to see the console turn on before i did a cleaner job. While im doing that, do you think i need to replace the nec tokins on the topside next to the cpu, ive never gotten a cpu error
Click to expand...


Hmm, so all your codes are related to RSX_VDDC, with the system partially assembled, can you probe it with a multimeter? (RSX side of the caps) You should see it reach 1.2 volts for a time. Also, any photos of the installation would help significantly. If the caps aren't correct you'll end up with 1002 anyway, since they'd be unable to filter the voltage properly due to their high ESR.
 
Hi everyone, I am new and seeking help. I have a PS3 fat model CECHL04 with motherboard version 001, and I am encountering syscon errors. The error is 1701, with no other errors. All I know is that the previous owner had jailbroken the PS3. The symptom I observe is that every 4-5 seconds, the PS3 turns off immediately, and the light goes from green to yellow and pulsating red indefinitely until I press the power button to get a steady red light. No matter what, I cannot enter safe mode (by pressing and holding the power button for 5- seconds). Today, I noticed that after trying to turn it on 20-25 times, the fan sped up loudly during the last 5 attempts. I checked the cell temperature using command tmp 00, and it was 80 degrees Celsius. Does this indicate a direct error with the CPU, or is it normal for it to get that hot since the PS3 was turning on and off immediately, and the fan did not have a chance to cool it down? The RSX temperature was staying at just 30-35 degrees Celsius. I also saw a video on YouTube where a guy with the same board measured some SMD chips, and I had exactly the same ohms as his, but I could not check the NEC/Tokin or other components because I do not have an oscilloscope or whatever that item is called. I am not sure. Please, any suggestions on what the issue could be? Any advice?

# CODE CLOCK
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801200 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
# A0801701 FFFFFFFF
#!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=24AE.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
 
I need help guys so what can i do with this ps3 its a CECHH06 Fat and everything about it looks clean so any help would be appreciated thanks guys
Heres what i retrieved :

Code: 
>$ errlog
errlog
ofst[108]:err_code:0xffffffff, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
ofst[116]:err_code:0xa0404402, clock:0xffffffff
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0404402, clock:0xffffffff
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0404402, clock:0xffffffff
ofst[  8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0404402, clock:0xffffffff
ofst[ 16]:err_code:0xa0403034, clock:0xffffffff
ofst[ 20]:err_code:0xa0404402, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0404402, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0404401, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0404401, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0404401, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0404401, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0404401, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0404401, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0404401, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0404401, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0404401, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$ becount
becount
Bringup : 2426 times
Shutdown: 2171 times
Power-on: 127day 01hour 20min 25sec
[mullion]$
Press Ctrl+C to exit
>$ 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:0x20e7
Press Ctrl+C to exit
>$ shutdown
[POWERSEQ] Error : BitTraining BE:RRAC:RX0:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0404401
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
 
Hello fellas, i'm having 3003 syscon error with COK-002 mobo, tried swapping single CELL nec/tokin for 4 470uf 2.5v tantalum caps, didn't work, then i checked IC6201, pin 7 gives me 60mv instead of 3.3v, and pin 22 gives me 2.5-5v instead of 12. Tried replacing IC6201, took it from dead mobo, but voltages were fine there, after installing it onto first mobo - voltages remained the same.
What else should i check? I have no idea anymore, unfortunately :(

Also i checked the fuses, they are fine
 
Nvm, just figured out i was checking RSX power block.....
Anyway, i checked the CELL IC6301 and..... got alm the same result, 50-60mv 7 pin and 2.5-3.5v 22 pin. Also swapped IC6301 between mobos, on the donor board it was showing 2.5-3v on pin 7 and 11.8v on 22 pin.
Pls help guys, i feel like this PS3 can be saved, but my skill is just not enough here
In case any further measurements required, i only have multimeter, no oscilloscope.

Also, when i first got the errorlog, oldest errors were mostly 2120, a little bit of 1001 and just one 3013, now it only shows 3003 every time
I it's power issue somewhere on the board, but i just can't figure out where exactly
 
Last edited by a moderator:
dumbass370 said:
Hello fellas, i'm having 3003 syscon error with COK-002 mobo, tried swapping single CELL nec/tokin for 4 470uf 2.5v tantalum caps, didn't work, then i checked IC6201, pin 7 gives me 60mv instead of 3.3v, and pin 22 gives me 2.5-5v instead of 12. Tried replacing IC6201, took it from dead mobo, but voltages were fine there, after installing it onto first mobo - voltages remained the same.
What else should i check? I have no idea anymore, unfortunately :(

Also i checked the fuses, they are fine
Click to expand...
My tip is to analyze the 12v line or check the fuse on the line.
My CECHA00 has an error 3004, pin 22 has 12v, but pin 7 has 0v. Pins 5 and 11 have 900mv.
 
You must log in or register to reply here.

Similar threads

Back
Top