NightLess
Member
Hello, it's the PS3 slim of JSD-001, and you are absolutely right, there is a capacitor on the cell that is short-circuited, I removed it and the console is completely revived! Thank you for your help!
PS3 SYSCON Tutorial (Windows)
- Thread starter RIP-Felix
- Start date
RIP-Felix
Senior Member
Which capacitor was it? For the record. Can you post a picture?
NightLess
Member
It is a small yellow capacitor. This is my fault. I scratched this capacitor when I delid cell,But the fault diagnosis you gave is accurate, thank you again!!
RIP-Felix，帖子：386009，会员：69150 said:
Last edited by a moderator:
NightLess
Member
Hello Felix, I'm here again, I recently got a CECHA00 COK-001 (its case was battered by logistics) and I found that it comes with GLOD, but occasionally can also enter XMB, since I don't have a display device with AV interface The AV interface output cannot be tested. The following is the code I read using SYSCON,1001 and 1004 seem to be errors caused by my forced shutdown. Is there any error about no display output in the code? Thanks!
Code:
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
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:0x20e2
Press Ctrl+C to exit
>$ becount
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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 THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
becount
Bringup : 327 times
Shutdown: 196 times
Power-on: 10day 07hour 30min 15sec
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 12]:err_code:0xffffffff, clock:0x12f59241 2010/01/29 12:34:09
ofst[ 16]:err_code:0xa0801004, clock:0x12f5949a 2010/01/29 12:44:10
ofst[ 20]:err_code:0xa0801001, clock:0x12f5c04f 2010/01/29 15:50:39
ofst[ 24]:err_code:0xa0801001, clock:0x12f715f4 2010/01/30 16:08:20
ofst[ 28]:err_code:0xa0801001, clock:0x12f81fc8 2010/01/31 11:02:32
ofst[ 32]:err_code:0xa0801004, clock:0x12f82324 2010/01/31 11:16:52
ofst[ 36]:err_code:0xa0801004, clock:0x12f83001 2010/01/31 12:11:45
ofst[ 40]:err_code:0xa0801004, clock:0x12f8303c 2010/01/31 12:12:44
ofst[ 44]:err_code:0xa0801001, clock:0x12f850e3 2010/01/31 14:32:03
ofst[ 48]:err_code:0xa0801004, clock:0x12f851d9 2010/01/31 14:36:09
ofst[ 52]:err_code:0xa0801004, clock:0x12f852c9 2010/01/31 14:40:09
ofst[ 56]:err_code:0xa0801001, clock:0x12f85f92 2010/01/31 15:34:42
ofst[ 60]:err_code:0xa0801001, clock:0x12fa674e 2010/02/02 04:32:14
ofst[ 64]:err_code:0xa0801004, clock:0x12faaba3 2010/02/02 09:23:47
ofst[ 68]:err_code:0xa0801001, clock:0x12fc47b8 2010/02/03 14:42:00
ofst[ 72]:err_code:0xa0801001, clock:0x12fefdce 2010/02/05 16:03:26
ofst[ 76]:err_code:0xa0801001, clock:0x1307fff0 2010/02/12 12:02:56
ofst[ 80]:err_code:0xa0801001, clock:0x1314ad97 2010/02/22 02:51:03
ofst[ 84]:err_code:0xa0801001, clock:0x1314afb2 2010/02/22 03:00:02
ofst[ 88]:err_code:0xa0801001, clock:0x135b3777 2010/04/16 14:57:59
ofst[ 92]:err_code:0xa0801001, clock:0x136142e1 2010/04/21 05:00:17
ofst[ 96]:err_code:0xa0801001, clock:0x13a260c3 2010/06/09 14:25:07
ofst[100]:err_code:0xa0801001, clock:0x13a26142 2010/06/09 14:27:14
ofst[104]:err_code:0xa0801004, clock:0x13a2ca75 2010/06/09 21:56:05
ofst[108]:err_code:0xa0801001, clock:0x13a3c2e9 2010/06/10 15:36:09
ofst[112]:err_code:0xa0801004, clock:0x15556fa0 2011/05/05 14:24:32
ofst[116]:err_code:0xa0801004, clock:0x19bac7bf 2013/09/05 04:40:31
ofst[120]:err_code:0xa0801004, clock:0x19bac8bb 2013/09/05 04:44:43
ofst[124]:err_code:0xa0801001, clock:0x0b49d8b2 2006/01/01 00:02:58
ofst[ 0]:err_code:0xa0801001, clock:0x0b49d8b9 2006/01/01 00:03:05
ofst[ 4]:err_code:0xa0801001, clock:0x0b49d87a 2006/01/01 00:02:02
ofst[ 8]:err_code:0xa0801004, clock:0x0b49d952 2006/01/01 00:05:38
[mullion]$
Press Ctrl+C to exitRIP-Felix
Senior Member
Yeah, so this is a tokin trap log. When you used the command "bringup" to start the console it will automatically perform a video reset, which sends an image to both HDMI and AV ports. So whichever one you're using, you'll see a screen that say's something like "an hdmi cable was detected, would you like to switch to HDMI output?" In your case you arent seeing anything. There are no POST errors. The console doesnt shutdown, it's just stuck with a Green light and no video. That's a Green Light of Death (GLOD).
The trap is that the only way to shut the console off is by holding the power button (which doesnt always work) or flipping it off at the rocker on the back...which causes 1001 and 1004 codes. If you've done this enough, the errorlog will be full of them and if there were any errors from before the GLOD started they'll have been erased.
People will see 1001 codes and think CPU tokins, when in this case it's very likely the GLOD responsable for the codes. You should be certain the console does not display and that safe mode options don't change the situation. If not, GLOD is usually a bad RSX.
NightLess
Member
When I use the bringup command or press the power switch, my TV will prompt the HDMI device input, but there is no picture display. I even saw a distorted screen once. As you can see, this machine has not been used for a long time. I feel that it should not be Tokin's problem? Of course, this is just speculation. I bought a video decoding IC to try to replace it, and I also bought a 40nm RSX CXD5300A1GB, which does not look like a refurbished one, but the resistance measurement is different from your measurement. What do you think about this?
RSX CXD5300A1GB
+1.2v_RSX_VDDC 2.9
+1.8v_RSX_FBVDDQ 457
+1.2v_RSX_VDDR 0.73k
+1.2_YC_RC_VDDIO 6k
+1.5v_RSX_VDDIO 1.7k
+1.5v_RSX_RC_VDDA 7.1k
+1.8v_RSX_PLL_VDD 65.5k
Multimeter Auto-ranging
Thanks Felix!
Hi good Day.
I'm new here and hopefully in the right thread. I bought a backwards compatible PS3 that was broken. YLOD. Since I didn't see these working, my first intention was to open them and see what the Syscon outputs. It's the 'COK-001' motherboard model and I can apparently only use external mode because 'SC_Diag' doesn't want to work. In any case, this is what I got, without the commands:
There seems to be some problem with HDMI According to PsDevWiki, but I don't understand. How could I solve it? Would replacing the NEC/Tokin help in any way or would nothing change?
I'm new here and hopefully in the right thread. I bought a backwards compatible PS3 that was broken. YLOD. Since I didn't see these working, my first intention was to open them and see what the Syscon outputs. It's the 'COK-001' motherboard model and I can apparently only use external mode because 'SC_Diag' doesn't want to work. In any case, this is what I got, without the commands:
Code:
00000000 A0A02031 FFFFFFFF
00000000 A0213013 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0A02031 FFFFFFFF
00000000 A0A02031 FFFFFFFF
00000000 A0A02031 FFFFFFFF
00000000 A0213013 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0A02031 FFFFFFFF
00000000 A0213013 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 A0202120 FFFFFFFF
00000000 FFFFFFFF FFFFFFFFThere seems to be some problem with HDMI According to PsDevWiki, but I don't understand. How could I solve it? Would replacing the NEC/Tokin help in any way or would nothing change?
RIP-Felix
Senior Member
You reminded me that I've been meaning to edit that code on the wiki. here's the pending changes once moderation approves it. This should give you a better idea what your codes mean and hopefully avoid this sort of confusion in the future.
No.
Check to see if F6302 is blown. If so, find the short that caused it to blow. Fix it and replace the fuse with a slow blow.
Last edited:
RIP-Felix
Senior Member
RSX readings seem fine.
Be sure it's not your AV setup.
- Hook up the PS3 directly to the TV via HDMI, no HDMI switches, splitters, or anything else that could get in the way.
- Be sure your TV isn't stuck in some kind of weird no signal state. My LG OLED will do that for no reason sometimes and I have to change inputs then go back.
- Inspect the HDMI port for damage or corrosion. Cleaning it with IPA and insert the HDMI cable several times.
- Try a different HDMI cable.
- Perform a manual video reset and/or see if you can enter safe mode. Are you able to see the screen that says an HDMI cable has been detected? Or the safe mode options?
- Try AV cables. Do you get an image from Analog AV?
If you get Analog AV, but not HDMI, it could be the HDMI transmitter or SMDs between it and the RSX (like chokes or resistors). In a GLOD, you won't get either Analog AV or HDMI. That's probably a bad RSX. So you need to figure out if this is a GLOD before trying to replace the HDMI transmitter.
Thanks for the quick reply.
Quick correction: I have the 'COK-002' motherboard.
I wanted to ask, where I can find this F6302 or whether there is a picture somewhere where it can be "easily" viewed. And if because the mobo was wrong, can another error or part be responsible and what would that be?
And you said that I should swap the fuse for a "slow blow". Is there anything I need to pay attention to? I have little to no knowledge of surface mount parts and how they are marked. I have soldering experience and some technical know-how. But I don't do that kind of specific stuff very often.
NightLess
Member
When I tried to connect the TV with an AV cable, I got no picture. The HDMI cable was definitely working on another PS3. There was also no picture in safe mode. This was probably a bad RSX.
Some of the resistance values of my 40nm RSX are very low (such as PLL, VDDA, +1.5v_RSX_VDDIO). Others look good, but I am a little worried about whether it can work? I can't make BGA myself. If this RSX doesn't work, I will Don't want to put the motherboard through multiple reflows. Thank you Felix!
RIP-Felix
Senior Member
All I'm looking for with PLL is that it's not open or short.
VDDC, anything 2 or above is fine (when at room temp. Will read lower or short when hot).
The rest of them I'm looking for anything that's not low or open. Like anything in the kilohms is normal. VDDR and FBVDDQ may read as low as 300 and be fine. But I dont like VDDR being lower.
An RSX can read fine and still be bad. I just installed a 40nm with ok readings both before and after the frankie. It's artifacting and on it's way out, but not completely dead yet. Only way to know was to install it.
VDDC, anything 2 or above is fine (when at room temp. Will read lower or short when hot).
The rest of them I'm looking for anything that's not low or open. Like anything in the kilohms is normal. VDDR and FBVDDQ may read as low as 300 and be fine. But I dont like VDDR being lower.
An RSX can read fine and still be bad. I just installed a 40nm with ok readings both before and after the frankie. It's artifacting and on it's way out, but not completely dead yet. Only way to know was to install it.
NightLess
Member
I still don't have much confidence in it, I ordered another one and I will take the reading of the other one, I don't know if the chip is brand new, it looks like it is brand new, all I can do is test the resistance. Thanks Felix.
MOD Edit: Next time, provide an English translation please.
Last edited by a moderator:
I'll report back because unfortunately I haven't been able to make much progress. I tried to find a short, but I'm not sure if I could find one. As for the coils, I don't even know if I can find anything without replacing the fuse so I can see the behavior when turned on. Unfortunately I don't own an oscilloscope. But I have now created a list of SMCs and would like to make sure whether they are correct or which ones might otherwise fit. I also have to make sure that these can be delivered to Germany because I live here.
I hope that the "Mouser Nr." are enough.
- Mouser-Nr.:
673-P1170.142NLT - Mouser-Nr.:
652-SRN8040HA-1R0M - Mouser-Nr.:
581-TCJB226M016R070E - Mouser-Nr.:
581-0603YC104K4T4A
Antony López
Forum Noob
HELP MEE PLEASEE!!!
i know is reballing
:c i want to repared my ps3
i know is reballing
:c i want to repared my ps3
Code:
PS3 SLIM CECH-25001A
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE CLOCK
# A0403034 2DDF0B2C
# A0404402 2DDF0B2B
# A0403034 2DD15DF2
# A0404402 2DD15DF2
# A0403034 2DD15DEB
# A0404402 2DD15DEB
# A0403034 2DCC0C54
# A0404402 2DCC0C54
# A0403034 2DCC0C1D
# A0404402 2DCC0C1C
# A0403034 2DCC0C11
# A0404402 2DCC0C11
# A0403034 23FF1E0F
# A0404402 23FF1E0F
# A0403034 23FF1DC9
# A0404402 23FF1DC8
# A0403034 23FF1DB7
# A0404402 23FF1DB6
# A0403034 23FF0B9A
# A0404402 23FF0B9A
# A0403034 23FF0B3E
# A0404402 23FF0B3D
# A0403034 23FF0B04
# A0404402 23FF0B04
# A0403034 23FF09EA
# A0404402 23FF09E9
# A0403034 23FF09E4
# A0404402 23FF09E3
# A0403034 23FF09DD
# A0404402 23FF09DD
# A0403034 23FF09BA
Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9103
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9103
# [SSM] PS3 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)RIP-Felix
Senior Member
Can you run command "r 800 8"? It's the uptime, I'm curious how old it was. Also what were the circumstances around the error? Was the console in good condition, stored properly, kept clean. Was it sealed? Or has it been opened and cleaned, delided, paste replaced...the work history. Any drop damage? Drop kicked by an angry brother?
Context may help use explain how this happened.
As for getting it fixed. That's on you. You'll have to find a reputible reballer. Just understand it's going to cost like $300, which isn't worth it for a 25xx model. You're better off buying another, working slim.
Antony López
Forum Noob
Code:
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ errlog
00000000
# CODE CLOCK
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 FFFFFFFF
# A0404402 FFFFFFFF
# A0403034 2DDF0B2C
# A0404402 2DDF0B2B
# A0403034 2DD15DF2
# A0404402 2DD15DF2
# A0403034 2DD15DEB
# A0404402 2DD15DEB
# A0403034 2DCC0C54
# A0404402 2DCC0C54
# A0403034 2DCC0C1D
# A0404402 2DCC0C1C
# A0403034 2DCC0C11
Press Ctrl+C to exit
>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 0F 64 0E DA 01 D5 6C 40
Bringups = 3940
Shutdowns = 3802
30764096 = 356 days
Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$ shutdown
00000000
# [PowSeq] Error:8403
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)
Press Ctrl+C to exit
>$ power sw
F0000003
# [UCMD] Unknown command.
Press Ctrl+C to exit
>$ powersw
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$ shutdown
00000000
# [PowSeq] Error:8403
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)i have this problem,yesterday ps03 is bad, to now is ps0
the playstation is stored in my room and i wanned play wiht my friends, after has this problem
this isn´t clean, i have all tools to repared.
diagnostic is pass. but it has the problem, i wiil try to reflow cpu/gpu or what most recomendly ??
sorry my english is not perfet, but i try to explain with you
Similar threads
-
-
PS3 (SOLVED) Trying to use the CP2102 adapter for SYSCON. Stuck at Internal Mullion (Scoped error).
- Started by RbrdM
- Replies: 0
-
PS3 SYSCON 2024 & 2124 need help diagnosing my PS3 phat
- Started by Krayek
- Replies: 3
-
PS3 A0801002 after 4 nec/tokin replacement (maybe Felix or anyone help me)
- Started by Swhalegod
- Replies: 3