NeonBlack
Forum Noob
Fixed swapping the faulty RSX with a 40 NM one, changing also the Tokins.
PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting
Oliwasprawiedliwa
Forum Noob
Hi, need some help. I'm completly new here and english is not my first language, so sorry for mistakes. Got ps3 super slim Cech4004c and decided to play around with syscon. The console is turning on for few seconds, fan is spinning and then it turns off no standby light. Got this errors and was wondering what to look for and what to do with them. I'm not experienced so I'm doing it just for fun. Best regards
Code:
> ERRLOG GET 00
00000000 A0403034 FFFFFFFF
> ERRLOG GET 01
00000000 A0404401 FFFFFFFF
> ERRLOG GET 02
00000000 A0403034 FFFFFFFF
> ERRLOG GET 03
00000000 A0404401 FFFFFFFF
> ERRLOG GET 04
00000000 A0403034 FFFFFFFF
> ERRLOG GET 05
00000000 A0404402 FFFFFFFF
> ERRLOG GET 06
00000000 A0403034 FFFFFFFF
> ERRLOG GET 07
00000000 A0404401 FFFFFFFF
> ERRLOG GET 08
00000000 A0403034 FFFFFFFF
> ERRLOG GET 09
00000000 A0404402 FFFFFFFF
> ERRLOG GET 0A
00000000 A0403034 FFFFFFFF
> ERRLOG GET 0B
00000000 A0404401 FFFFFFFF
> ERRLOG GET 0C
00000000 A0403034 FFFFFFFF
> ERRLOG GET 0D
00000000 A0404401 FFFFFFFF
> ERRLOG GET 0E
00000000 A0403034 FFFFFFFF
> ERRLOG GET 0F
00000000 A0404401 FFFFFFFF
> ERRLOG GET 10
00000000 A0403034 FFFFFFFF
> ERRLOG GET 11
00000000 A0404401 FFFFFFFF
> ERRLOG GET 12
00000000 A0403034 FFFFFFFF
> ERRLOG GET 13
00000000 A0404401 FFFFFFFF
> ERRLOG GET 14
00000000 A0403034 FFFFFFFF
> ERRLOG GET 15
00000000 A0404401 FFFFFFFF
> ERRLOG GET 16
00000000 A0403034 FFFFFFFF
> ERRLOG GET 17
00000000 A0404401 FFFFFFFF
> ERRLOG GET 18
00000000 A0403034 FFFFFFFF
> ERRLOG GET 19
00000000 A0404401 FFFFFFFF
> ERRLOG GET 1A
00000000 A0403034 FFFFFFFF
> ERRLOG GET 1B
00000000 A0404401 FFFFFFFF
> ERRLOG GET 1C
00000000 A0403034 FFFFFFFF
> ERRLOG GET 1D
00000000 A0404401 FFFFFFFF
> ERRLOG GET 1E
00000000 A0403034 FFFFFFFF
> ERRLOG GET 1F
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.
# [PowSeq] Error:9003
# [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)
tomiosk
Forum Noob
Hello! I have been trying to fix a CECHK (dia-002) ps3 with YLOD/GLOD. When I got the console i noticed the board was full of flux near the RSX, CELL and some other components (probably repair service tried to do a reball to fix the YLOD but failed to). The 1002 errors may be due to the tokins but the other error A0002120 doesn't seem to be that common. Fuses seem to be ok, C2570 and C2558 are not shorted, TH2501 measured 1.5ohm.
The A0901002 errors were caused when running 'shutdown' during GLOD (no video, tried AV and HDMI, started with 'bringup') and the A0801002 + A0002120 combination shows up when the console shows the YLOD (not instant, about 2s-3s) after starting with power button. The 2120 error shows up without HDMI cable plugged in and the syscon hdmi commands work when cable is plugged in (hdmi redid & hdmi chstat work as expected).
Should I replace the tokins? Any help would be appreciated!
The A0901002 errors were caused when running 'shutdown' during GLOD (no video, tried AV and HDMI, started with 'bringup') and the A0801002 + A0002120 combination shows up when the console shows the YLOD (not instant, about 2s-3s) after starting with power button. The 2120 error shows up without HDMI cable plugged in and the syscon hdmi commands work when cable is plugged in (hdmi redid & hdmi chstat work as expected).
Should I replace the tokins? Any help would be appreciated!
Code:
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e7
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.3.5 (Build ID: 3034,32025, Build Data: 2008-05-12_15:29:27)
Press Ctrl+C to exit
>$
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[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
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[mullion]$
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[SSM] fatalreq delayed.
[ERROR]: 0xa0901002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
[SSM] *** Power Fail RS ***
[SSM] state: 0000 -> 0800
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
Press Ctrl+C to exit
>$ shutdown
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0800 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xffffffff, clock:0xffffffff
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xffffffff, clock:0xffffffff
ofst[ 52]:err_code:0xffffffff, clock:0xffffffff
ofst[ 56]:err_code:0xffffffff, clock:0xffffffff
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:0xa0901002, clock:0x0b4886d3 2005/12/31 00:01:23
ofst[ 4]:err_code:0xa0801002, clock:0x0b4888e0 2005/12/31 00:10:08
ofst[ 8]:err_code:0xa0002120, clock:0x0b4888e1 2005/12/31 00:10:09
ofst[ 12]:err_code:0xa0801002, clock:0x0b488c8b 2005/12/31 00:25:47
ofst[ 16]:err_code:0xa0002120, clock:0x0b488c8b 2005/12/31 00:25:47
ofst[ 20]:err_code:0xa0801002, clock:0x0b488dde 2005/12/31 00:31:26
ofst[ 24]:err_code:0xa0002120, clock:0x0b488ddf 2005/12/31 00:31:27
ofst[ 28]:err_code:0xa0901002, clock:0x0b488e31 2005/12/31 00:32:49
ofst[ 32]:err_code:0xa0901002, clock:0x0b488e45 2005/12/31 00:33:09
[mullion]$
Press Ctrl+C to exit
>$
Starship2
Member
For me this looks like a dying chip. 3034 is a Bit Training error that most likely indicates a Problem with BGA except of fat models where this error also occurs when Tokins are faulty. But in your case we can cross that out due to superslims dont have tokins anymore. Next clue are those 4002/4001 errors which are just known as data errors. At that point its pretty clear that your chip is dead or BGA failed. Seems like you have either to reball your chip or replace it. We cant clearly say if its cell or rsx related, even if 3034 is declared as a rsx problem. In some cases a bad Cell or bad Cell Data lines triggered 3034 errors because of missing bits letting syscon think its an RSX Issue. Maybe @RIP-Felix can confirm.
Starship2
Member
Look for shorts near C6320, its pretty common that a short somewhere in this area causes Fuse 6302 to blow.
2120 can be caused by many things, but i would start with that cap and fuse because it would be the most obvious. if they are fine its getting way more complex. i dont wanna say that it is not possible to be triggered by faulty tokins, but i guess its not. That error can also be triggered by missing VDDIO voltage and that can be, who would have guessed it, a bad BGA or faulty GPU (or excessive heat from a reflow attempt..) Check F6302, if its fine you got a bigger, expensive problem i guess.
Last edited:
Hello! I am having a slim ps3 2004B 250gb and encounter a red light (not yellow in between) with 3 beeps later on, when i booted up it works normally,I even jailbroke it. But in gaming in times it turns off and does the beep thing with the red light. I replaced the thermal paste also and monitored the temps which are normal. I installed ps3 tools and got the output error file of syscon. If you can help me with my next step,i will appreciated it. Thank!
Firmware Version: 4.88 (build 50731)
Bringup Count: 6618, Shutdown Count: 6577
Runtime: 414 Days, 11 Hours, 11 Minutes, 56 Seconds
Error Log
01: A0801002 Sat Jan 20 19:31:09 2007
02: A0801002 Fri Jan 19 05:00:32 2007
03: A0801002 Fri Jan 19 03:30:05 2007
04: A0802130 Thu Jan 18 18:15:58 2007
05: A0802030 Thu Jan 18 18:15:57 2007
06: A0801002 Thu Jan 18 05:34:47 2007
07: A0801002 Thu Jan 18 04:25:46 2007
08: A0801002 Mon Jan 15 01:08:20 2007
09: A0801002 Mon Jan 15 00:49:52 2007
10: A0801002 Mon Jan 15 00:49:06 2007
11: A0801002 Sun Jan 1 02:55:13 2006
12: A0801002 Sun Jan 1 01:45:04 2006
13: A0801002 Sun Jan 1 01:14:09 2006
14: A0801002 Sun Jan 1 00:59:08 2006
15: A0801002 Sat Oct 2 19:14:12 2021
16: A0801002 Sat Oct 2 19:10:56 2021
17: A0801002 Wed Sep 29 22:40:59 2021
18: A0801002 Tue Sep 28 17:54:38 2021
19: A0801002 Tue Sep 28 17:34:38 2021
20: A0801002 Wed Jan 6 03:49:54 2021
21: A0801002 Wed Jan 6 02:59:03 2021
22: A0801002 Wed Jan 6 01:43:07 2021
23: A0801002 Wed Jan 6 01:30:16 2021
24: A0801002 Thu Dec 24 01:31:38 2020
25: A08014FF Thu Dec 24 01:31:38 2020
26: A0801002 Mon Nov 2 21:09:18 2020
27: A0802130 Thu Jul 9 16:17:35 2020
28: A0802030 Thu Jul 9 16:17:32 2020
29: A0802130 Thu Jul 9 16:17:27 2020
30: A0802030 Thu Jul 9 16:17:25 2020
31: A0802130 Thu Jul 9 16:17:22 2020
32: FFFFFFFF Fri Dec 31 23:59:59 1999
Firmware Version: 4.88 (build 50731)
Bringup Count: 6618, Shutdown Count: 6577
Runtime: 414 Days, 11 Hours, 11 Minutes, 56 Seconds
Error Log
01: A0801002 Sat Jan 20 19:31:09 2007
02: A0801002 Fri Jan 19 05:00:32 2007
03: A0801002 Fri Jan 19 03:30:05 2007
04: A0802130 Thu Jan 18 18:15:58 2007
05: A0802030 Thu Jan 18 18:15:57 2007
06: A0801002 Thu Jan 18 05:34:47 2007
07: A0801002 Thu Jan 18 04:25:46 2007
08: A0801002 Mon Jan 15 01:08:20 2007
09: A0801002 Mon Jan 15 00:49:52 2007
10: A0801002 Mon Jan 15 00:49:06 2007
11: A0801002 Sun Jan 1 02:55:13 2006
12: A0801002 Sun Jan 1 01:45:04 2006
13: A0801002 Sun Jan 1 01:14:09 2006
14: A0801002 Sun Jan 1 00:59:08 2006
15: A0801002 Sat Oct 2 19:14:12 2021
16: A0801002 Sat Oct 2 19:10:56 2021
17: A0801002 Wed Sep 29 22:40:59 2021
18: A0801002 Tue Sep 28 17:54:38 2021
19: A0801002 Tue Sep 28 17:34:38 2021
20: A0801002 Wed Jan 6 03:49:54 2021
21: A0801002 Wed Jan 6 02:59:03 2021
22: A0801002 Wed Jan 6 01:43:07 2021
23: A0801002 Wed Jan 6 01:30:16 2021
24: A0801002 Thu Dec 24 01:31:38 2020
25: A08014FF Thu Dec 24 01:31:38 2020
26: A0801002 Mon Nov 2 21:09:18 2020
27: A0802130 Thu Jul 9 16:17:35 2020
28: A0802030 Thu Jul 9 16:17:32 2020
29: A0802130 Thu Jul 9 16:17:27 2020
30: A0802030 Thu Jul 9 16:17:25 2020
31: A0802130 Thu Jul 9 16:17:22 2020
32: FFFFFFFF Fri Dec 31 23:59:59 1999
Starship2
Member
Doesnt look too good. You should check the VRM Environment first, maybe youre lucky and its just a problem with your power delivery. Check the converters near the chips and also check the Tokins from RSX. Dynamo 001 Mainboards still have Tokins at GPU. Since you have a thermal alert it is possible that tokins have been harmed by that excessive heat. heat from the chips does dissipate extremely to those tokins and can wear them down quickly. i would consider this worth a measurement. If that doesnt help the probability is high that your BGA/GPU has an issue. Thats the result of too much thermal stress as it was too late for changing the thermal paste...
Lkylon
Forum Noob
So I got error message 0xa0092113 now.
Is this a fan error?
This is my bring up:
[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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0092113
My error log is as follows:
errlog
ofst[ 92]:err_code:0xffffffff, clock:0x0b488bb4 2005/12/31 00:22:12
ofst[ 96]:err_code:0xa0902020, clock:0x0b488bb4 2005/12/31 00:22:12
ofst[100]:err_code:0xa0404421, clock:0x0b488bc2 2005/12/31 00:22:26
ofst[104]:err_code:0xa0403034, clock:0x0b488bc2 2005/12/31 00:22:26
ofst[108]:err_code:0xa0902120, clock:0x0b488bc2 2005/12/31 00:22:26
ofst[112]:err_code:0xa0404421, clock:0x0b488bf2 2005/12/31 00:23:14
ofst[116]:err_code:0xa0403034, clock:0x0b488bf2 2005/12/31 00:23:14
ofst[120]:err_code:0xa0404421, clock:0x0b488c0a 2005/12/31 00:23:38
ofst[124]:err_code:0xa0403034, clock:0x0b488c0a 2005/12/31 00:23:38
ofst[ 0]:err_code:0xa0902020, clock:0x0b488c0a 2005/12/31 00:23:38
ofst[ 4]:err_code:0xa0404421, clock:0x0b488eb5 2005/12/31 00:35:01
ofst[ 8]:err_code:0xa0403034, clock:0x0b488eb5 2005/12/31 00:35:01
ofst[ 12]:err_code:0xa0404421, clock:0x0b488ebf 2005/12/31 00:35:11
ofst[ 16]:err_code:0xa0403034, clock:0x0b488ebf 2005/12/31 00:35:11
ofst[ 20]:err_code:0xa0404421, clock:0x0b488ec9 2005/12/31 00:35:21
ofst[ 24]:err_code:0xa0403034, clock:0x0b488ec9 2005/12/31 00:35:21
ofst[ 28]:err_code:0xa0902120, clock:0x0b488ec9 2005/12/31 00:35:21
ofst[ 32]:err_code:0xa0404421, clock:0x0b48a93a 2005/12/31 02:28:10
ofst[ 36]:err_code:0xa0403034, clock:0x0b48a93a 2005/12/31 02:28:10
ofst[ 40]:err_code:0xa0902120, clock:0x0b48a93a 2005/12/31 02:28:10
ofst[ 44]:err_code:0xa0404421, clock:0x0b48a945 2005/12/31 02:28:21
ofst[ 48]:err_code:0xa0403034, clock:0x0b48a945 2005/12/31 02:28:21
ofst[ 52]:err_code:0xa0404421, clock:0x0eeccfba 2007/12/08 03:44:58
ofst[ 56]:err_code:0xa0403034, clock:0x0eeccfba 2007/12/08 03:44:58
ofst[ 60]:err_code:0xa0404421, clock:0x0eecd05c 2007/12/08 03:47:40
ofst[ 64]:err_code:0xa0403034, clock:0x0eecd05c 2007/12/08 03:47:40
ofst[ 68]:err_code:0xa0404421, clock:0x0eecd0b0 2007/12/08 03:49:04
ofst[ 72]:err_code:0xa0403034, clock:0x0eecd0b0 2007/12/08 03:49:04
ofst[ 76]:err_code:0xa0404421, clock:0x11a22466 2009/05/17 01:27:02
ofst[ 80]:err_code:0xa0403034, clock:0x11a22466 2009/05/17 01:27:02
ofst[ 84]:err_code:0xa0404421, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Bringup : 1624 times
Shutdown: 1282 times
Power-on: 154day 08hour 04min 48sec
Any suggestions?
Is this a fan error?
This is my bring up:
[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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0092113
My error log is as follows:
errlog
ofst[ 92]:err_code:0xffffffff, clock:0x0b488bb4 2005/12/31 00:22:12
ofst[ 96]:err_code:0xa0902020, clock:0x0b488bb4 2005/12/31 00:22:12
ofst[100]:err_code:0xa0404421, clock:0x0b488bc2 2005/12/31 00:22:26
ofst[104]:err_code:0xa0403034, clock:0x0b488bc2 2005/12/31 00:22:26
ofst[108]:err_code:0xa0902120, clock:0x0b488bc2 2005/12/31 00:22:26
ofst[112]:err_code:0xa0404421, clock:0x0b488bf2 2005/12/31 00:23:14
ofst[116]:err_code:0xa0403034, clock:0x0b488bf2 2005/12/31 00:23:14
ofst[120]:err_code:0xa0404421, clock:0x0b488c0a 2005/12/31 00:23:38
ofst[124]:err_code:0xa0403034, clock:0x0b488c0a 2005/12/31 00:23:38
ofst[ 0]:err_code:0xa0902020, clock:0x0b488c0a 2005/12/31 00:23:38
ofst[ 4]:err_code:0xa0404421, clock:0x0b488eb5 2005/12/31 00:35:01
ofst[ 8]:err_code:0xa0403034, clock:0x0b488eb5 2005/12/31 00:35:01
ofst[ 12]:err_code:0xa0404421, clock:0x0b488ebf 2005/12/31 00:35:11
ofst[ 16]:err_code:0xa0403034, clock:0x0b488ebf 2005/12/31 00:35:11
ofst[ 20]:err_code:0xa0404421, clock:0x0b488ec9 2005/12/31 00:35:21
ofst[ 24]:err_code:0xa0403034, clock:0x0b488ec9 2005/12/31 00:35:21
ofst[ 28]:err_code:0xa0902120, clock:0x0b488ec9 2005/12/31 00:35:21
ofst[ 32]:err_code:0xa0404421, clock:0x0b48a93a 2005/12/31 02:28:10
ofst[ 36]:err_code:0xa0403034, clock:0x0b48a93a 2005/12/31 02:28:10
ofst[ 40]:err_code:0xa0902120, clock:0x0b48a93a 2005/12/31 02:28:10
ofst[ 44]:err_code:0xa0404421, clock:0x0b48a945 2005/12/31 02:28:21
ofst[ 48]:err_code:0xa0403034, clock:0x0b48a945 2005/12/31 02:28:21
ofst[ 52]:err_code:0xa0404421, clock:0x0eeccfba 2007/12/08 03:44:58
ofst[ 56]:err_code:0xa0403034, clock:0x0eeccfba 2007/12/08 03:44:58
ofst[ 60]:err_code:0xa0404421, clock:0x0eecd05c 2007/12/08 03:47:40
ofst[ 64]:err_code:0xa0403034, clock:0x0eecd05c 2007/12/08 03:47:40
ofst[ 68]:err_code:0xa0404421, clock:0x0eecd0b0 2007/12/08 03:49:04
ofst[ 72]:err_code:0xa0403034, clock:0x0eecd0b0 2007/12/08 03:49:04
ofst[ 76]:err_code:0xa0404421, clock:0x11a22466 2009/05/17 01:27:02
ofst[ 80]:err_code:0xa0403034, clock:0x11a22466 2009/05/17 01:27:02
ofst[ 84]:err_code:0xa0404421, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Bringup : 1624 times
Shutdown: 1282 times
Power-on: 154day 08hour 04min 48sec
Any suggestions?
NextJack0325
Member
Ps3 DIA-002 -xxxx1165607
Amotherboard GLOD 3 seconds shut down Is it possible to lose 12V voltage How to detect the short circuit of the main voltage of 12V
Amotherboard GLOD 3 seconds shut down Is it possible to lose 12V voltage How to detect the short circuit of the main voltage of 12V
Code:
C:\Users\Administrator>C:\Users\Administrator\Desktop\ps3syscon-master\Linux\ps3
_syscon_uart_script.py COM5 CXRF
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ becount
becount
Bringup : 778 times
Shutdown: 610 times
Power-on: 51day 09hour 01min 16sec
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 64]:err_code:0xffffffff, clock:0xffffffff
ofst[ 68]:err_code:0xa0313032, clock:0xffffffff
ofst[ 72]:err_code:0xa0313032, clock:0xffffffff
ofst[ 76]:err_code:0xa0313032, clock:0xffffffff
ofst[ 80]:err_code:0xa0313032, clock:0xffffffff
ofst[ 84]:err_code:0xa0313032, clock:0xffffffff
ofst[ 88]:err_code:0xa0313032, clock:0xffffffff
ofst[ 92]:err_code:0xa0313032, clock:0xffffffff
ofst[ 96]:err_code:0xa0313032, clock:0xffffffff
ofst[100]:err_code:0xa0313032, clock:0xffffffff
ofst[104]:err_code:0xa0313032, clock:0xffffffff
ofst[108]:err_code:0xa0313032, clock:0xffffffff
ofst[112]:err_code:0xa0313032, clock:0xffffffff
ofst[116]:err_code:0xa0313032, clock:0xffffffff
ofst[120]:err_code:0xa0313032, clock:0xffffffff
ofst[124]:err_code:0xa0313032, clock:0xffffffff
ofst[ 0]:err_code:0xa0313032, clock:0xffffffff
ofst[ 4]:err_code:0xa0313032, clock:0xffffffff
ofst[ 8]:err_code:0xa0313032, clock:0xffffffff
ofst[ 12]:err_code:0xa0313032, clock:0xffffffff
ofst[ 16]:err_code:0xa0313032, clock:0xffffffff
ofst[ 20]:err_code:0xa0313032, clock:0xffffffff
ofst[ 24]:err_code:0xa0303030, clock:0xffffffff
ofst[ 28]:err_code:0xa0313032, clock:0xffffffff
ofst[ 32]:err_code:0xa0313032, clock:0xffffffff
ofst[ 36]:err_code:0xa0313032, clock:0xffffffff
ofst[ 40]:err_code:0xa0313032, clock:0xffffffff
ofst[ 44]:err_code:0xa0313032, clock:0xffffffff
ofst[ 48]:err_code:0xa0313032, clock:0xffffffff
ofst[ 52]:err_code:0xa0313032, clock:0xffffffff
ofst[ 56]:err_code:0xa0313031, clock:0xffffffff
ofst[ 60]:err_code:0xa0313031, clock:0xffffffff
[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
[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]: 0xa0313031
Press Ctrl+C to exit
Last edited:
LittleGish
Forum Noob
Hello everyone
Trying to fix ps3 CechG08 Sem-001
Came into my hands without Tokins
The error code at that time was 3004
After replacing with tantalum capacitors (2R5TPE470M7) I get error 3032
Previously there were no errors like 3034 and 4412 in the logs, so I think that rsx is alive
Having found the circuit diagram for the board, I looked at all the elements along the +1.2V_YC_RC_VDDIO and +1.5V_YC_RC_VDDA lines and they were all intact
If you try to turn it on, there is no voltage on the elements
The Cell was most likely reballed
Now I'm at a dead end and don't know what else to check
Please help
Syscon logs
Trying to fix ps3 CechG08 Sem-001
Came into my hands without Tokins
The error code at that time was 3004
After replacing with tantalum capacitors (2R5TPE470M7) I get error 3032
Previously there were no errors like 3034 and 4412 in the logs, so I think that rsx is alive
Having found the circuit diagram for the board, I looked at all the elements along the +1.2V_YC_RC_VDDIO and +1.5V_YC_RC_VDDA lines and they were all intact
If you try to turn it on, there is no voltage on the elements
The Cell was most likely reballed
Now I'm at a dead end and don't know what else to check
Please help
Syscon logs
Code:
Press Ctrl+C to exit
>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 88]:err_code:0xffffffff, clock:0xffffffff
ofst[ 92]:err_code:0xa0093004, clock:0xffffffff
ofst[ 96]:err_code:0xa0093004, clock:0xffffffff
ofst[100]:err_code:0xa0093004, clock:0xffffffff
ofst[104]:err_code:0xa0093004, clock:0xffffffff
ofst[108]:err_code:0xa0093004, clock:0xffffffff
ofst[112]:err_code:0xa0093004, clock:0xffffffff
ofst[116]:err_code:0xa0093004, clock:0xffffffff
ofst[120]:err_code:0xa0093004, clock:0xffffffff
ofst[124]:err_code:0xa0093004, clock:0xffffffff
ofst[ 0]:err_code:0xa0093004, clock:0xffffffff
ofst[ 4]:err_code:0xa0093004, clock:0xffffffff
ofst[ 8]:err_code:0xa0093004, clock:0xffffffff
ofst[ 12]:err_code:0xa0313032, clock:0xffffffff
ofst[ 16]:err_code:0xa0313032, clock:0xffffffff
ofst[ 20]:err_code:0xa0313032, clock:0xffffffff
ofst[ 24]:err_code:0xa0313032, clock:0xffffffff
ofst[ 28]:err_code:0xa0313032, clock:0xffffffff
ofst[ 32]:err_code:0xa0313032, clock:0xffffffff
ofst[ 36]:err_code:0xa0313032, clock:0xffffffff
ofst[ 40]:err_code:0xa0313032, clock:0xffffffff
ofst[ 44]:err_code:0xa0313032, clock:0xffffffff
ofst[ 48]:err_code:0xa0313032, clock:0xffffffff
ofst[ 52]:err_code:0xa0313032, clock:0xffffffff
ofst[ 56]:err_code:0xa0313032, clock:0xffffffff
ofst[ 60]:err_code:0xa0313032, clock:0xffffffff
ofst[ 64]:err_code:0xa0313032, clock:0xffffffff
ofst[ 68]:err_code:0xa0313032, clock:0xffffffff
ofst[ 72]:err_code:0xa0313032, clock:0xffffffff
ofst[ 76]:err_code:0xa0313032, clock:0xffffffff
ofst[ 80]:err_code:0xa0313032, clock:0xffffffff
ofst[ 84]:err_code:0xa0313032, clock:0xffffffff
[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
[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]: 0xa0313032
Press Ctrl+C to exit
>$
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
FurumFum
Forum Noob
Hello all,
I'm with a COK-002 (CECHE01) board that was bought cheap due to "not showing any image". This isn't my first time attempting to investigate SYSCON errors and I've successfully resurrected a couple of boards; nonetheless, here I am with (I think) a strange case:
Console turns on, no YLOD or RLOD, buttons respond normally and I can even hear the bips while trying to go into recovery mode but no image on screen with both HDMI or AV, the power button (not the rocker) turns the console off gracefully if pressed. Interior had signs of someone else having a go at repairing and even managed to spot this beautiful attempt:
Lovely... Reading the SYSCON before doing anything else got me these results:
So, for those 1001 and 1002 along the piggyback caps on the GPU I've decided to change all TOKINS for tantalizers and it went well. Console turned on and the 1002 stopped, but alas, no image still.
Now I only got 0xa0801001s and a random 0xa0902203 that are most likely caused by me turning on and off trying to troubleshoot the board. No fuses are blown and the voltages are all ok as far as I tested and the overall look of the board is quite good. Did the pressure test and it changed nothing. I've delidded the GPU and there are no cracks or visible damage, didn't do the CPU because I don't have the tools nor guts. Sorry for not posting more pics I didn't take them while the console was being worked on but if need be I can open it again.
To me all tends to suggest it's a RSX GLOD or an erase mod that went wrong but as far as I understand not only I wouldn't be able to turn the console off without pulling the cord but there would be a bit more evidence and errors to insinuate that, so now I'm at a loss... I have some spare CECHA boards and know-good 90mm RSX's but I don't have the tools to do myself and repair shops are way too expensive. I guess this could be some random IC or SMD that I could replace but my hope is low.
Any advice would be greatly appreciated, thanks in advance!
I'm with a COK-002 (CECHE01) board that was bought cheap due to "not showing any image". This isn't my first time attempting to investigate SYSCON errors and I've successfully resurrected a couple of boards; nonetheless, here I am with (I think) a strange case:
Console turns on, no YLOD or RLOD, buttons respond normally and I can even hear the bips while trying to go into recovery mode but no image on screen with both HDMI or AV, the power button (not the rocker) turns the console off gracefully if pressed. Interior had signs of someone else having a go at repairing and even managed to spot this beautiful attempt:
Lovely... Reading the SYSCON before doing anything else got me these results:
Code:
>$ errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0x2821de29 2021/05/02 22:03:21
ofst[ 8]:err_code:0xa0801001, clock:0x2821deab 2021/05/02 22:05:31
ofst[ 12]:err_code:0xa0801001, clock:0x2821e37b 2021/05/02 22:26:03
ofst[ 16]:err_code:0xa0801001, clock:0x2821e3a4 2021/05/02 22:26:44
ofst[ 20]:err_code:0xa0801001, clock:0x2821e400 2021/05/02 22:28:16
ofst[ 24]:err_code:0xa0801001, clock:0x2821e581 2021/05/02 22:34:41
ofst[ 28]:err_code:0xa0801001, clock:0x2821e623 2021/05/02 22:37:23
ofst[ 32]:err_code:0xa0801002, clock:0x2e49d6a5 2024/08/10 07:43:33
ofst[ 36]:err_code:0xa0801002, clock:0x2e4a5496 2024/08/10 16:40:54
ofst[ 40]:err_code:0xa0801002, clock:0x0b48b859 2005/12/31 03:32:41
ofst[ 44]:err_code:0xa0801002, clock:0x0b48bbc5 2005/12/31 03:47:17
ofst[ 48]:err_code:0xa0801001, clock:0x0b48d1ef 2005/12/31 05:21:51
ofst[ 52]:err_code:0xa0801001, clock:0x0b48d270 2005/12/31 05:24:00
ofst[ 56]:err_code:0xa0801001, clock:0x0b48d319 2005/12/31 05:26:49
ofst[ 60]:err_code:0xa0801001, clock:0x0b5c35f4 2006/01/14 22:21:40
ofst[ 64]:err_code:0xa0801001, clock:0x0b5c499c 2006/01/14 23:45:32
ofst[ 68]:err_code:0xa0801001, clock:0x0b5c4b16 2006/01/14 23:51:50
ofst[ 72]:err_code:0xa0801001, clock:0x0b5c6193 2006/01/15 01:27:47
ofst[ 76]:err_code:0xa0801001, clock:0x0b5c684a 2006/01/15 01:56:26
ofst[ 80]:err_code:0xa0801001, clock:0x0b5c6d7a 2006/01/15 02:18:34
ofst[ 84]:err_code:0xa0801001, clock:0x0b62b1d9 2006/01/19 20:23:53
ofst[ 88]:err_code:0xa0901001, clock:0x0b4e5343 2006/01/04 09:34:59
ofst[ 92]:err_code:0xa0901001, clock:0x0b4a8c6b 2006/01/01 12:49:47
ofst[ 96]:err_code:0xa0801001, clock:0x0b4a8f1c 2006/01/01 13:01:16
ofst[100]:err_code:0xa0801001, clock:0x0b48868c 2005/12/31 00:00:12
ofst[104]:err_code:0xa0801001, clock:0x0b488c88 2005/12/31 00:25:44
ofst[108]:err_code:0xa0801001, clock:0x0b488d8f 2005/12/31 00:30:07
ofst[112]:err_code:0xa0801001, clock:0x0b488db0 2005/12/31 00:30:40
ofst[116]:err_code:0xa0801001, clock:0x0b548366 2006/01/09 02:13:58
ofst[120]:err_code:0xa0801001, clock:0x0b5483dc 2006/01/09 02:15:56
ofst[124]:err_code:0xa0801001, clock:0x0b548424 2006/01/09 02:17:08
ofst[ 0]:err_code:0xa0801001, clock:0x0b5484a4 2006/01/09 02:19:16
Code:
>$ becount
becount
Bringup : 1941 times
Shutdown: 1247 times
Power-on: 79day 22hour 53min 53sec
[mullion]$
Code:
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[SSM] Bringup mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Setup called.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[SSM] state: 0201 -> 0102
[SSM] state: 0102 -> 0202
[SSM] state: 0202 -> 0103
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x21e2
Press Ctrl+C to exit
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.1.0 (Build ID: 2709,28222, Build Data: 2007-12-05_13:32:28)
Copyright(C) 2007 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
[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 NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[mullion]$
Press Ctrl+C to exit
>$
[mullion]$
Press Ctrl+C to exit
>$ powerstate
powerstate
ATA Power : ON
PCI Power : OFF
RSX Power : ON
XDR Power : ON
Eurus Power : ON
SB Power : ON
RSX Thermal Sensor : AVAILABLE
BE Thermal Sensor : AVAILABLE
[mullion]$
Press Ctrl+C to exit
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000000F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
Code:
>$ hdmi chstat 0
hdmi chstat 0
[HDMI] ----------------------------
[HDMI] -- HDMI Channel 0 Context --
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[System Management]
[HDMI] - SSM Task ID : 13
[HDMI] * Task Status : WAITING
[HDMI] * Wait Cause : EVENT FLAG
[HDMI] - SSM State : WaitResolution
[HDMI] - SSM Mutex Information : ID[2] LockTID[0] WaitTID[0]
[HDMI] - SSM Event Flag Info : ID[2] WaitTID[13] FlagPattern[0]
[HDMI] - SSM Mode : HDMI
[HDMI] ------------------------------------------------------------------------------------
[HDMI] - Authentication Status : NotStart
[HDMI] - Repeater : Sink
[HDMI] - KSVs : 0
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[Interrupt]
[HDMI] - External Interrupt Number of Mullion : 7
[HDMI] - Interrupt Mask Pattern in SiI : [0x0000E0]
[HDMI] - Interrupt Register Size : 3
[HDMI] - Interrupt Task ID : 12
[HDMI] * Task Status : WAITING
[HDMI] * Wait Cause : SLEEPING
[HDMI] - Semapho Information : ID[38] WaitingTID[0] Count[1]
[HDMI] - Plug Status : PowerOn
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[SiIType]
[HDMI] - Chip Type : 9132
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[EDID]
[HDMI] - EDID Mutex ID : 3
[HDMI] - EDID Mutex Information : ID[3] LockTID[0] WaitTID[0]
[HDMI] - EDID Block Size : 2
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[I2C Bus]
[HDMI] - Device Address 0x72(0) 0x7A(1)
[HDMI] - Semapho Information : ID[36] WaitingTID[0] Count[1]
[HDMI] ------------------------------------------------------------------------------------
[HDMI] +-[AV Setting]
[HDMI] - Audio Setting State : Unset
[HDMI] Mute ; Mute
[HDMI] - Video Setting State : Unset
[HDMI] Mute ; Mute
[HDMI] Setting : 00 00 00 00 00 00 00 00 00 00 00 00
[HDMI] : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[HDMI]
[mullion]$So, for those 1001 and 1002 along the piggyback caps on the GPU I've decided to change all TOKINS for tantalizers and it went well. Console turned on and the 1002 stopped, but alas, no image still.
Now I only got 0xa0801001s and a random 0xa0902203 that are most likely caused by me turning on and off trying to troubleshoot the board. No fuses are blown and the voltages are all ok as far as I tested and the overall look of the board is quite good. Did the pressure test and it changed nothing. I've delidded the GPU and there are no cracks or visible damage, didn't do the CPU because I don't have the tools nor guts. Sorry for not posting more pics I didn't take them while the console was being worked on but if need be I can open it again.
To me all tends to suggest it's a RSX GLOD or an erase mod that went wrong but as far as I understand not only I wouldn't be able to turn the console off without pulling the cord but there would be a bit more evidence and errors to insinuate that, so now I'm at a loss... I have some spare CECHA boards and know-good 90mm RSX's but I don't have the tools to do myself and repair shops are way too expensive. I guess this could be some random IC or SMD that I could replace but my hope is low.
Any advice would be greatly appreciated, thanks in advance!
Code:
errlog
ofst[ 24]:err_code:0xffffffff, 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:0xa0404002, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0404002, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0404002, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0404002, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0404002, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0404002, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0404002, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0404002, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0404002, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0404002, clock:0xffffffff
ofst[116]:err_code:0xa0403034, clock:0xffffffff
ofst[120]:err_code:0xa0404002, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[ 0]:err_code:0xa0404002, clock:0xffffffff
ofst[ 4]:err_code:0xa0403034, clock:0xffffffff
ofst[ 8]:err_code:0xa0404002, clock:0xffffffff
ofst[ 12]:err_code:0xa0403034, clock:0xffffffff
ofst[ 16]:err_code:0xa0404002, clock:0xffffffff
ofst[ 20]:err_code:0xa0403034, clock:0xffffffff
[mullion]$
Press Ctrl+C to exit
>$ becount
becount
Bringup : 3317 times
Shutdown: 3046 times
Power-on: 117day 17hour 10min 47sec
[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:0x21e2
Press Ctrl+C to exit
>$ shutdown
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[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]: 0xa0404002
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
Ganjo
Member
You have bad RSX TOKINs. This model has TOKINs only on the RSX IIRC. The CELL needs a delid too
Ganjo
Member
Bad RSX
Starship2
Member
2113 is a problem with clock generator. you have to check IC5004 and its environment. as you can see its a step#09 error, so it occurs in a pretty early state when chips try to sync with each other and phase lock loop should be done. look for voltages and shorts on IC5004.
.. but your errorlog doesnt show up a 092113 error? is that your actual recent errlog? not sure if the error message tell us the same as errlog does. looks like the same format but im not sure about that.
however, your errorlog is telling me about a defective rsx/bga.
Last edited:
Joenard Belleza
Member
Hello, Guys.
Can someone maybe point me in the right direction?
I have this CECHL00 VER001 with only an error code 3003, I tried to remove all the nec tokin in the CELL side and used a Multimeter to read their ohms. On the VDDC side I've got 5.20 mega ohms but on the Cell side I've got the same reading as the ground which is 0.6 Ohms, is the CELL supposed to have a reading like that without the tokins or I have a dead CELL/shorted board?
Can someone maybe point me in the right direction?
I have this CECHL00 VER001 with only an error code 3003, I tried to remove all the nec tokin in the CELL side and used a Multimeter to read their ohms. On the VDDC side I've got 5.20 mega ohms but on the Cell side I've got the same reading as the ground which is 0.6 Ohms, is the CELL supposed to have a reading like that without the tokins or I have a dead CELL/shorted board?
NextJack0325
Member
like RSX Pinouts to have the same color codeI updated the following RSX Pinouts to have the same color code. It was confusing to use them for cross-reference before.
Also here are some resistance measurements I took of a 90nm and 40nm RSX. I can't guarantee they are good, but they look okay. I also added a 65nm RSX that looked OK, thanks to @SkaziChris who measured it. Please note that these were probed at the following testpoints...
Last edited:
i dont know if i am forming this right but i have a tll uart connector sauldered into my ps3 slim and every time i atach ground i cant access it on my pc and any time i connect my pc first and then the uart connector it just dosent work i know i have the wires correctly sauldered and i have flipped them 100+ times im wondering if there is a way i could get into a quick call with someone or someone has the same issue because every time i use cmd to connect with the Windows64_gui_ps3_syscon_uart_script propgram it says auth 1 responce invalid and everywhere i look it says change the wireing but that just dosent work and i have tryed every witch way to connect the ground no ground yes ground but every time i touch it to the ps3s ground it dose something sometimes it turns all the lights off sometimes it turns on the green lights on the connector i just dont know where im going wrong sorry english isnt my first language sorry for spelling mistakes
Similar threads
-
PS3 Kohada - A repair & tuning toolkit for the PS3 syscon- Started by sagemono
- Replies: 2
-
PS3 [Tutorial] How to use an ESP32 as a SYSCON UART Bridge- Started by GrGeorge
- Replies: 0
-
-
