PS3 2124, 2024 SYSCON errors

R

RedstoneTaken

Forum Noob
Hello,
I have a CECH-L01 PS3 that doesn't turn on, mostly it RLOD/YLOD's after 45 seconds of trying to boot and sometimes it's instant. I hooked up the SYSCON today and read this:

Code: 
>$ errlog
00000000
# CODE     CLOCK
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF

Press Ctrl+C to exit
>$

Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] Msg 2663 : being delayed.
# [PowSeq] Error:8301
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$
>$ powerstate
00000000
# ATA  :OFF
# PCI  :OFF
# PCIex:OFF
# RSX  :OFF
# GDDR :OFF
# XDR  :OFF
# EURUS:OFF
# SB   :OFF

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF

Press Ctrl+C to exit
>$
>$ errlog
00000000
# CODE     CLOCK
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112024 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
# A0112124 FFFFFFFF
Upon googling it, PSdevwiki shows as AV error, specifically HDMI/AV encoder. This makes sense because there is no HDMI output (although there is one 1002 error, but it is less frequent).
I don't have an AV cable at the moment but I ordered one that'll be here tomorrow. If it doesn't work with the AV cable, should I try to replace the chip, or check if there are any blown fuses or bad resistors with a multimeter? It has sat in a basement for a long time and collected dust. Is there a way to tell it not to turn on the hdmi encoder and just use AV by chance? If not, how hard would replacing the chip be? I think it's a surface mount component on this model.
Thanks all!
 
I found the AV cable for my PS2, and connected it to the PS3. Unfortunately, it still RLOD's.

Updated SYSCON from today's tries at a power on:
Code: 
>$ errlog
00000000
# CODE     CLOCK
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF

>$ errlog
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# CODE     CLOCK
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF

>$ errlog
00000000
# CODE     CLOCK
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092114 FFFFFFFF
# A0091002 FFFFFFFF
# A0092014 FFFFFFFF

Press Ctrl+C to exit
Consistently, it appears that 2014/2114 appears before 1002 errors. Does this mean that 1002 is a result of 2014/2114? I had done a CPU and RSX reflow with a hot air gun 2 days ago, which I now know is not the best idea (especially since I have a 65nm RSX, which is less likely to be a problem), but maybe that was why yesterday I was getting less 1002 errors.
 
Last edited by a moderator:
Ok, I had done some research. 1002 meant RSX power filter failure. By removing one of the RSX NEC TOKINs on the back and replacing them with 4 330uF capacitors from eBay (yeah it's recommended to use higher capacitance), with the worst soldering possible, the system actually turned on! the hdmi seems broken, but the AV still works. I am backing up my stuff now, so let's see how long it works. It didn't detect my hard drive, but luckily I had a backup made using a raw backup tool. It seems like the 2124/2024 may indicate HDMI port failure but the AV still works fine. I'll have to do more testing and confirm it's not my tvs hdmi port.
 
This old TV must be broken, because the HDMI works perfectly on another TV. Seems like the 2024 errors for AV/HDMI and the clock errors 2114 are red herrings if you've got bad TOKINs.
 
You must log in or register to reply here.

Similar threads

Back
Top