Lopandrade
Forum Noob
Hello everyone, I happened to unbury my CECH-3001A PS3 recently, and unfortunately it was not working. It did work before I stopped using it, but now It gives me the red LED on standby but when I power it on it beeps once and then dies. In order to power it on again, I have to unplug it from the outlet and plug it back.
I started troubleshooting by checking power supply and even got another one to test, but that wasn't the issue. I then tried re-flowing the CPU and RSX chips using a heat gun, but that didn't work either.
Then finally I found out about SYSCON and how to use it, so I got myself a UART adapter and managed to access my PS3 error logs.
I first got these error logs and it was basically errors 3034 and 4322. I did some research on them and it seemed like I might have some issue with the RSX chip.
>$ errlog
00000000
# CODE CLOCK
>$ errlog
00000000
# CODE CLOCK
# A0403034 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 1BA6747B
# A0404322 1BA6747B
# A0403034 1BA67439
# A0404322 1BA67439
# A0403034 1BA65F0F
I ran it again and had the same thing, but now it was just FFFFFFFF as the time stamps.
>$ errlog
00000000
# CODE CLOCK
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
Next, I did a bringup command and it gave me this information but I'm not sure if it tells me anything relevant. Hoping someone might tell me something about it.
>$ bringup
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$
F0000003
# [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
# [UCMD] Unknown command.
I also checked the system count information just in case it's relevant.
>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 0C 38 0B F1 01 46 EF 1F
3128 Bringups
3057 Shutdowns
21425951 sec = 248 days
After a few times running the bringup / powersw commands, I tried to run a shutdown command and I heard a beep. I was able to run a powersw command again but this time I had to unplug the power cord in order to reset the test. After this instance I started to get these error messages instead, 2124 and 2024.
Not sure what that means for the previous errors I was seeing since they're no longer there.
Does anyone know what errors would come up first, the 3034 and 4322 from the beginning or the 2124 and 2024 that I get now. I'm trying to understand how one would just stop showing up like that unless this issue just started.
>$ errlog
00000000
# CODE CLOCK
# A0902124 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902124 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
>$ errlog
00000000
# CODE CLOCK
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF[/CODE]
Let me know if anyone can help me with any suggestions!
I started troubleshooting by checking power supply and even got another one to test, but that wasn't the issue. I then tried re-flowing the CPU and RSX chips using a heat gun, but that didn't work either.
Then finally I found out about SYSCON and how to use it, so I got myself a UART adapter and managed to access my PS3 error logs.
I first got these error logs and it was basically errors 3034 and 4322. I did some research on them and it seemed like I might have some issue with the RSX chip.
>$ errlog
00000000
# CODE CLOCK
>$ errlog
00000000
# CODE CLOCK
# A0403034 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 1BA6747B
# A0404322 1BA6747B
# A0403034 1BA67439
# A0404322 1BA67439
# A0403034 1BA65F0F
I ran it again and had the same thing, but now it was just FFFFFFFF as the time stamps.
>$ errlog
00000000
# CODE CLOCK
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
# A0404322 FFFFFFFF
# A0403034 FFFFFFFF
Next, I did a bringup command and it gave me this information but I'm not sure if it tells me anything relevant. Hoping someone might tell me something about it.
>$ bringup
00000000
# [SSM] Bringup Start.
Press Ctrl+C to exit
>$
F0000003
# [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
# [UCMD] Unknown command.
I also checked the system count information just in case it's relevant.
>$ r 800 8
00000000
# +0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
# -----------------------------------------------
# 0C 38 0B F1 01 46 EF 1F
3128 Bringups
3057 Shutdowns
21425951 sec = 248 days
After a few times running the bringup / powersw commands, I tried to run a shutdown command and I heard a beep. I was able to run a powersw command again but this time I had to unplug the power cord in order to reset the test. After this instance I started to get these error messages instead, 2124 and 2024.
Not sure what that means for the previous errors I was seeing since they're no longer there.
Does anyone know what errors would come up first, the 3034 and 4322 from the beginning or the 2124 and 2024 that I get now. I'm trying to understand how one would just stop showing up like that unless this issue just started.
>$ errlog
00000000
# CODE CLOCK
# A0902124 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902124 FFFFFFFF
# A0902024 FFFFFFFF
# A0902024 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
# A0902124 FFFFFFFF
>$ errlog
00000000
# CODE CLOCK
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02024 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF
# A0A02124 FFFFFFFF[/CODE]
Let me know if anyone can help me with any suggestions!