marciolsf
Member
thanks for confirming that.
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
vyktormvmpay25
Senior Member
I did SB uart test for Cok002 board but I assume they have same pinout for PCI port . They are not tested yet. We didn't need it so much, usually we figure from syscon UART port issues.
https://s.go.ro/fxwgtlvl
https://s.go.ro/4t2k3p0v
Last edited:
RIP-FELIX, I have rechecked RSX_PLL and it is showing 5.66 K Ohms, and MC2_VDDIO is 38.2 K Ohms, so I'm guessing this is a good sign. Would it still be a reball on the RSX or could it be something else and not the RSX at all?. I am hoping your going to say the latter.
I don't mind changing parts as I do have a doner board but unsure of the condition of the parts on that board as that had a YLOD issue.
Also I have checked continuity of all capacitors and parts (by placing probes on either side of each part) in the location of MC2_VDDIO and VDDA on both sides and a do get continuity as if there is a short but unable to locate what is causing it. Is this right, or is this normal?. if I place on probe on leg 5 of Q6308 and tap all the of the legs individually my multi meter beeps same as Q6309, C1101, C1105 and all the other little capacitors in that location. I noticed this after test continuity from MC2_VDDIO to opposite side of C6068 on the top side of the board.
On a separate note, I have purchased another CECHC03 PS3 (pictures on Ebay showed it working and description of BR needing remarry as black screen when a Bluray disc or PS3 game inserted- which I love fixing), I got it on the cheap and it starts OK but after a few minutes goes Artifacting, At first i thought it was a failing RSX but after a few seconds of doing this the HDMI signal cuts out then back on then after 30 seconds the system completely freezes on the XMB and the screen goes fully pixelated showing blue and red colours.
If i were to leave it another minute you can hear the fan slightly kick in but its not loud at all. It does not turn itself off and responds on the power button. I turn it off just to make sure it doesn't cause further damage.
I have done a Syscon error log and there is nothing coinciding to the problem, which is weird. I tried hooking up my banana plugs and crocodile clips to motherboard instead of placing PSU straight on motherboard. Weirdly enough when i hook the PSU with banana plugs I get YLOD even though I have hooked it up correctly but if i put PSU on the motherboard no YLOD,. Very strange indeed. Theses are the only error codes I'm getting relating to power due to the YLOD.
I have heard this could be a CPU issue and not the RSX. So i decided to put a penny washer under the CPU bracket and it does it again, tried with the RSX, and same situation. it even does this in safe mode.
This only happens once the PS3 is getting warm and not straight away when its cold or been left for a while to cool down. I have replaced the paste with MX4 before I had noticed this or even hooked it up to a TV, As I turned it on when I got it just to make sure I didn't buy a falsely advertised YLOD one.
Last edited by a moderator:
RIP-Felix
Senior Member
VDDA is normally 4 ohms. A multimeter in continuity mode will buzz on low impeedance ines like this and the tokins. That's normal. To find a short in lo impeedance lines you need to look at the resistance value and compare it to GND. Usually anything, under 0.5 ohms is a short.
I am sorry if I got your hopes up. This was onlay ever going to end badly for you. That 3034 is the nail in your PS3's coffin. It definately needs a reball.
The point of the ohm tests was to see if the console is likely to be revived with a reball. If any of those voltages were reading bad, then a reball would be unscuessful because the RSX is dead. It would need to be replaced...which I would do anyway if I were you, since it's not that much more work to add a 65nm or 40nm. And it would be best to put the MB through fewer reflow cycles anyway.
vyktormvmpay25
Senior Member
Just one board Ive quick fixed ever!
Dia001 error 2110-Clock Generator Error was F6001 faulty.All errors were 2110.
Dia001 error 2110-Clock Generator Error was F6001 faulty.All errors were 2110.
Workz_777
Senior Member
Exactly the same on my DIA-001 too, all errors = 2110, and indeed the F6001 fuse had a hole on the top / blown.
Hello.
Here is my problem. Board DIA-001. Instant YLOD. Replaced all the NECs as recommended, bridged tantalum's positive ends, everything as it should be. Got 3 Ohms on the RSX line and 4.2 Ohms on the CELL one. Tested. It worked for about 8 seconds and YLODed - as I supposed due to overheating. After the test I've assembled everything and have got the insatant YLOD as in the beginning. I thought it might be the overheathig issue, delidded both CELL and RSX, changed all the paste - still instant YLOD. Delidding went just fine - not my first attempt and on the working state consoles everything always was OK. Please give me some advice what should I try and check next before trying a reflow.
Here is my problem. Board DIA-001. Instant YLOD. Replaced all the NECs as recommended, bridged tantalum's positive ends, everything as it should be. Got 3 Ohms on the RSX line and 4.2 Ohms on the CELL one. Tested. It worked for about 8 seconds and YLODed - as I supposed due to overheating. After the test I've assembled everything and have got the insatant YLOD as in the beginning. I thought it might be the overheathig issue, delidded both CELL and RSX, changed all the paste - still instant YLOD. Delidding went just fine - not my first attempt and on the working state consoles everything always was OK. Please give me some advice what should I try and check next before trying a reflow.
===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404422 FFFFFFFF
ERR 02: 00000000 A0403034 FFFFFFFF
ERR 03: 00000000 A0404422 FFFFFFFF
ERR 04: 00000000 A0403034 FFFFFFFF
ERR 05: 00000000 A0404422 FFFFFFFF
ERR 06: 00000000 A0403034 FFFFFFFF
ERR 07: 00000000 A0404422 FFFFFFFF
ERR 08: 00000000 A0403034 FFFFFFFF
ERR 09: 00000000 A0404422 FFFFFFFF
ERR 10: 00000000 A0403034 FFFFFFFF
ERR 11: 00000000 A0404422 FFFFFFFF
ERR 12: 00000000 A0403034 FFFFFFFF
ERR 13: 00000000 A0404422 FFFFFFFF
ERR 14: 00000000 A0403034 FFFFFFFF
ERR 15: 00000000 A0404422 FFFFFFFF
ERR 16: 00000000 A0403034 FFFFFFFF
ERR 17: 00000000 A0404422 FFFFFFFF
ERR 18: 00000000 A0403034 FFFFFFFF
ERR 19: 00000000 A0404422 FFFFFFFF
===================================
ERR 00: 00000000 A0403034 FFFFFFFF
ERR 01: 00000000 A0404422 FFFFFFFF
ERR 02: 00000000 A0403034 FFFFFFFF
ERR 03: 00000000 A0404422 FFFFFFFF
ERR 04: 00000000 A0403034 FFFFFFFF
ERR 05: 00000000 A0404422 FFFFFFFF
ERR 06: 00000000 A0403034 FFFFFFFF
ERR 07: 00000000 A0404422 FFFFFFFF
ERR 08: 00000000 A0403034 FFFFFFFF
ERR 09: 00000000 A0404422 FFFFFFFF
ERR 10: 00000000 A0403034 FFFFFFFF
ERR 11: 00000000 A0404422 FFFFFFFF
ERR 12: 00000000 A0403034 FFFFFFFF
ERR 13: 00000000 A0404422 FFFFFFFF
ERR 14: 00000000 A0403034 FFFFFFFF
ERR 15: 00000000 A0404422 FFFFFFFF
ERR 16: 00000000 A0403034 FFFFFFFF
ERR 17: 00000000 A0404422 FFFFFFFF
ERR 18: 00000000 A0403034 FFFFFFFF
ERR 19: 00000000 A0404422 FFFFFFFF
===================================
Workz_777
Senior Member
Hi, here is the link to the PSDevWiki for Syscon error codes definitions, (for error 3034):
https://www.psdevwiki.com/ps3/Syscon_Error_Codes#3034
Thanks for the reply. I've seen that list but I've thought whether there has been something else to take into consideration before trying to reflow the RSX.
RIP-Felix
Senior Member
I have a new one, at least to me.
I went to do some testing on PS3#12 (CECH-E01 with a 40nm RSX). The moment I flipped the rocker to PWR up the standby circuit it started the console automatically. Then it held the PWR button down until the console forced a shutdown (error A0901001).
So I decided to try another PWR/EJT daughter board and it resolved the issue. I just thought it was an interesting tidbit I should record here in case anyone else has this issue. Here's the log...
I checked back in my notes and the initial errorlog, which I always do first thing upon receiving a console (to preserve the error history), also contained a 90 1001. So this problem was there all along. I think. I'm not sure why it went away when I was testing earlier and just now came back. Perhaps I swapped the PWR/EJT board's around in testing. I have a few of them. I hope there's nothing about the console that's causing this, but I guess I'll find out with use.
I went to do some testing on PS3#12 (CECH-E01 with a 40nm RSX). The moment I flipped the rocker to PWR up the standby circuit it started the console automatically. Then it held the PWR button down until the console forced a shutdown (error A0901001).
So I decided to try another PWR/EJT daughter board and it resolved the issue. I just thought it was an interesting tidbit I should record here in case anyone else has this issue. Here's the log...
Code:
Microsoft Windows [Version 10.0.19044.1526]
(c) Microsoft Corporation. All rights reserved.
C:\Users\HTPC\Desktop\PS3\SYSCON>python ps3_syscon_uart_script.py COM5 CXRF
>$ AUTH
Auth successful
>$
[mullion]$
>$ errlog
errlog
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:0xa0801200, clock:0x0b488687 2005/12/31 00:00:07
ofst[ 4]:err_code:0xa0801004, clock:0x0b488a0b 2005/12/31 00:15:07
ofst[ 8]:err_code:0xa0801200, clock:0x0b488f02 2005/12/31 00:36:18
ofst[ 12]:err_code:0xa0901001, clock:0x0b488692 2005/12/31 00:00:18
ofst[ 16]:err_code:0xa0901001, clock:0x0b488800 2005/12/31 00:06:24
ofst[ 20]:err_code:0xa0101001, clock:0x0b4888ba 2005/12/31 00:09:30
ofst[ 24]:err_code:0xa0404002, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404002, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0801200, clock:0xffffffff
ofst[ 44]:err_code:0xa0901001, clock:0x0b488682 2005/12/31 00:00:02
ofst[ 48]:err_code:0xa0801001, clock:0xffffffff
ofst[ 52]:err_code:0xa0901001, clock:0xffffffff
ofst[ 56]:err_code:0xa0901001, clock:0x0b488682 2005/12/31 00:00:02
[mullion]$
>$ clear errlog
clear errlog
*** Unknown Command ***
[mullion]$
>$
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
[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: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
[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
[mullion]$ [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
[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
Power Button Long Long Pressed..
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SSM] fatalreq delayed.
[ERROR]: 0xa0901001
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
[SSM] *** Power Fail BE ***
[SSM] state: 0000 -> 0800
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0800 -> 0600
(PowerOff State) (Fatal)
>$ AUTH
Auth successful
>$ errlog
errlog
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:0xa0801200, clock:0x0b488687 2005/12/31 00:00:07
ofst[ 4]:err_code:0xa0801004, clock:0x0b488a0b 2005/12/31 00:15:07
ofst[ 8]:err_code:0xa0801200, clock:0x0b488f02 2005/12/31 00:36:18
ofst[ 12]:err_code:0xa0901001, clock:0x0b488692 2005/12/31 00:00:18
ofst[ 16]:err_code:0xa0901001, clock:0x0b488800 2005/12/31 00:06:24
ofst[ 20]:err_code:0xa0101001, clock:0x0b4888ba 2005/12/31 00:09:30
ofst[ 24]:err_code:0xa0404002, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0404002, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0801200, clock:0xffffffff
ofst[ 44]:err_code:0xa0901001, clock:0x0b488682 2005/12/31 00:00:02
ofst[ 48]:err_code:0xa0801001, clock:0xffffffff
ofst[ 52]:err_code:0xa0901001, clock:0xffffffff
ofst[ 56]:err_code:0xa0901001, clock:0x0b488682 2005/12/31 00:00:02
ofst[ 60]:err_code:0xa0901001, clock:0x0b4886e3 2005/12/31 00:01:39
ofst[ 64]:err_code:0xa0901001, clock:0x0b488682 2005/12/31 00:00:02
[mullion]$
>$I checked back in my notes and the initial errorlog, which I always do first thing upon receiving a console (to preserve the error history), also contained a 90 1001. So this problem was there all along. I think. I'm not sure why it went away when I was testing earlier and just now came back. Perhaps I swapped the PWR/EJT board's around in testing. I have a few of them. I hope there's nothing about the console that's causing this, but I guess I'll find out with use.
Oh, you see - I had an instant YLOD and the info that the two most common problems could be the NECs and the solder balls. Hadn't got the TTL device. Taking into account the lack of proper equipment to perform a reball anyway I started with the easiest. After replacing the NECs the console worked for solid 8 seconds and YLODed but not instantly. I considered it to be overheating, assembled it and got an instant YLOD again. Got the UART and now it is what it is. So I'll try a reflow.
I saw a video on youtube - a guy started to apply heat at 150C gradually increasing up to 300C for 10 minutes in total. Is this the correct way of doing this?
vyktormvmpay25
Senior Member
Felix is this still working with nec caps or tantals?
RIP-Felix
Senior Member
Tokins are fine. I didn't need to replace them. Even though this console has 512 days of use on it (12,288 hours)! Which BTW was the most use I had ever seen until @David Rainer's A01 which has 800+ (16,000 hours)! And his tokins are fine too!
For reference the tokens are rated at 2000 hours at 105C. But the estimated lifespan increases quickly if the operating temperature of the tokins is lowered. In my tests on a well ventalated case the tokins are somewhere between 65 and 85 C. So the math works out like this...
If they get to 85C...
Llytic = F x 2^[(T0-Tamb)/10] = 362038.672 x 2^[(20°C -85°C)/10] = 4000 hrs
LPoly = F x 10^[(T0-Tamb)/20] = 17782794.1 x 10^[(20°C -85°C)/20] = 10,000 hrs
If they get to 65C...
Llytic = F x 2^[(T0-Tamb)/10] = 362038.672 x 2^[(20°C - 65°C)/10] = 16,000 hrs
LPoly = F x 10^[(T0-Tamb)/20] = 17782794.1 x 10^[(20°C - 65°C)/20] = 100,000 hrs
Now the tokins are a hybrid of electrolytic and polymer caps. So they will fall somewhere in between the 2 chemistry types.
IMO, he reason those toshiba laptops had bad tokins was because they put them directly underneath the CPU (the hottest possible place). SONY put them right next to them, but used thermal VIAs to provide separation between the GPU/CPU and the tokins. That was a smart design choice!
A potential mod to cool the tokins would be to use thermal pads to contact the RF shield and use it as a passive heatsink for the tokins. Cooling them further would extend their operating lifespan. And of course keeping the console free from dust, using more agressive fan curves, standing the console vertical, replacing TIM every 5-7 years, etc. will too.
Last edited:
sandungas
Developer
Btw, the other day i was learning/documenting in wiki how works the timestamps (used in the error log, and also in the runtime counters) and i used your PS3#12 for the example because i realized it contained 3 different timestamp "sytles".. also i realized you was doing something a bit special, lol, is just a curiosity but is interesting because it seems some syscon models does it in a diffrent way
https://www.psdevwiki.com/ps3/Talk:Syscon_Error_Codes
https://www.psdevwiki.com/ps3/Syscon_Error_Codes#Error_log_format
As far i understand... in the errorcodes where appears a timestamp close to 2005/12/31 00:00:00 is because you was inserting the battery cell... and inmedialy after you was "flipping the power rocker", right ?
You are breaking all world records in this last errorlogs, only took you 2 seconds
RIP-Felix
Senior Member
No.
But a DIA-001 isn't exactly desirable to own or worth much. So I guess you don't have much to loose by trying (if you already have the materials and skill). IDK what your skill/equipment situation is like, but judging by your desire to perform a reflow I assume you are a beginner (reflows suck. If they work, they won't for long).
If that's the case, What you want to do is buy another console and cut your losses.
If that's not the case there are things you can do to improve your chances of achieving a "better" reflow. But they all involve buying materials that'll cost more than this console is worth.
What you should not do, and I hope you're not the evil person I'm about to describe, is reflow it and sell it as working to an unsuspecting dupe on e-bay! That's a bait and switch tactic that preys on innocence and sours the joy gaming is supposed provide. We have enough badness in the world already. If you want to sell the console, be up front about it's condition and sell it in a reparable (not working) state for what it's worth.
RIP-Felix
Senior Member
Yes I cheated to get that world record though. The power/eject board was rigged to turn the console on as soon as the rocker was flipped! So 2s is theoretical max. #AccidentalWorldRecordBtw, the other day i was learning/documenting in wiki how works the timestamps (used in the error log, and also in the runtime counters) and i used your PS3#12 for the example because i realized it contained 3 different timestamp "sytles".. also i realized you was doing something a bit special, lol, is just a curiosity but is interesting because it seems some syscon models does it in a diffrent way
https://www.psdevwiki.com/ps3/Talk:Syscon_Error_Codes
https://www.psdevwiki.com/ps3/Syscon_Error_Codes#Error_log_format
As far i understand... in the errorcodes where appears a timestamp close to 2005/12/31 00:00:00 is because you was inserting the battery cell... and inmedialy after you was "flipping the power rocker", right ?
You are breaking all world records in this last errorlogs, only took you 2 seconds
That's not a title I'm happy to hold. It means this power board is faulty.
Hey everyone, I'm trying to get the ERRLOG data out of a PS3, but it doesn't seem to be working for some reason... This is a VER-001, with a SW-301 SYSCON. I have it all connected, and auth/AUTH works just fine. I can use the commands bringup and shutdown, but becount doesn't seem to be recognized, and after using bestat, I get this:
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!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.
#!
#![ERROR]: 0xb0000004 lv0 authentication fail
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# (Error State) (Fatal)
# State = 07
Not sure if this is normal, but more importantly, my errlog/ERRLOG commands return nothing but FFFFFFFF. Is it blank? I'm not entirely sure where to go from here... I was trying to read the SYSCON logs before replacing the caps, because it seems like my problem is something else... Any help would be appreciated!
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
#!
#!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.
#!
#![ERROR]: 0xb0000004 lv0 authentication fail
# [SSM] Cond/Fatal received, msg=2649.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# (Error State) (Fatal)
# State = 07
Not sure if this is normal, but more importantly, my errlog/ERRLOG commands return nothing but FFFFFFFF. Is it blank? I'm not entirely sure where to go from here... I was trying to read the SYSCON logs before replacing the caps, because it seems like my problem is something else... Any help would be appreciated!
If to speak about buying things to improve the chances of achieving a better reflow that cost more than this console is - it is buying a BGA soldering station to perform a true reball)
Reflow worked btw and everything i needed were good old Quick 857D, some flux, foil, kapton tape and isopropyl alcohol. Nothing bought for this specific reason. Now I have a PS3 at my workplace and no need to bring there the one from home. Quite a good outcome taking into consideration this PS3 was bought in a non-working state exactly for such experiments.
Thanks for helping me to take correct decisions.
sandungas
Developer
But how you was doing the sequence exactly ?, i thought you was doing this:
1) insert battery
2) flip da powah rockr (im liking this sentence, you use it a lot, lol)
3) press ON button in the front panel
With the rigged front panel you bypassed step 3, but you had to do 1) and 2) anyway, and just took you 2 seconds... is a bit in the limits. Is because you had one hand with the battery, and the other hand in the power rocker ?
I mean... is needed to remove the battery before step 1) because the time starts counting inmediatly after you insert the battery, right ?
---------
Btw, not sure if you already did, but consider the ribbon cable of the front panel board as a different component, sometimes one or more of the copper lines breaks in the ribbon cable, internally and cant be seen because is covered with plastic... so check with a different ribbon cable, maybe is the cale what is wrong, and the circuit board is fine
I use to check that ribbon cables by placing them on a flat surface with the copper to top direction, and holding them in his position at the center by pressure (just placing some weight at the center, usually a book if the cable is long)... this allows to use a multimeter to check the copper lines one by one by touching them at the extremes
Last edited:
Similar threads
-
-
PS3 CECHA00 with several SYSCON errors (3004, 1001,1002, 2120,3011)
- Started by LSL
- Replies: 7
-
PS3 Interesting PS3 Errors (1802, 1701, 1601) and Capacitor Replacement- Started by Cheshire UK
- Replies: 2
-