PS3 Fault finding YLOD with the SYSCON - First steps and Error reporting

[VicCatarino]

Please help !

I got a CECH-2511A MotherBoard JTP-001, I got if it was already disassembled, the previous owner opened it and didn't close, he claimed it was working and he disassembled it for cleaning but damaged the power/reset flat cable, it had some rust on the RF shield but the board was very clean.

I retrieved the errlog, and the bringup here...

>$ errlog
00000000
# CODE     CLOCK
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF
# A0404403 FFFFFFFF
# A0403034 FFFFFFFF

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [PowSeq] Error:A101
# [SSM] PS0 ng.
# [SSM] Cond/Fatal received, msg=24D0.
# [SSM] Fataldown Start.

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
NG E00000E0
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

I found that A0403034 associated with A0404402 is an RXS BGA problem and A0403034 associated with A0404401 is a CELL BGA problem, but couldn't find what is A0403034 associated with A0404403
Any help would be appreciated.

 

[RIP-Felix]

suffix 3 is usually referring to the Southbridge. I would be cautious about making a 100% diagnosis based on the data error associated with the 3034, but it "may" work that way. More data is needed to be sure that RSX failures do not cause 1 or 3 errors...and etc.

Check for damage to the CPU. Delidding damage is a common way errors like this occur and especially in the case of a console that was opened before, hastily put bact together (they were were fed up and didnt care, signaling it was borked), and lied about it's condition. OTOH it's possable it's a BGA defect that was held together by pressure when the last tested it. You should trh a pressure test on CPU, SB, and RSX to see if there is any difference in behavior.

 

[Rufis_]

Hello again. Since I'll be able to get my hands on an oscilloscope tomorrow, I'd like to know what's the correct procedure to confirm that it's the NEC/Tokins which are causing the problem. While I'm at it, I'd like to check if the caps on the CPU side are healthy or if they'll need to be replaced soon as well.
From what I understand I should see ripples or noise on the power line(s?), but I'm not completely sure where should I probe. I imagine I could check on one side of any capacitor, but on which terminal?

Edit: I wasn't able to reply to previous posts for some reason, but my problem seem to be bad caps on the RSX

 

[RIP-Felix]

Hello again. Since I'll be able to get my hands on an oscilloscope tomorrow, I'd like to know what's the correct procedure to confirm that it's the NEC/Tokins which are causing the problem.

Here read this. I did a bunch of scoping in that and explained far more that you probably want to sift through, but it's there.

 

[Raidmax]

Just dug up this CECHL04 out of storage and rebuilt it recently. I find it very hard to believe this has had no errors in its life.
I didn't tamper with it besides transferring to another case (from a defunct GLOD-ing H04) as the original L04 shell was too far gone.

Firmware Version: 4.90 (build 50747)
Platform ID: CokF10
Product Code: 00 85
Product Sub Code: 00 08
Hardware Config: 000000000307BCBF
Syscon Firmware Version: 065D.0000000000000000 (EEPROM: 0000000000000000)

Bringup Count: 2814, Shutdown Count: 2618
Runtime: 109 Days, 9 Hours, 19 Minutes, 42 Seconds

Error Log
01: FFFFFFFF  Sat Jan  1 01:59:59 2000
02: FFFFFFFF  Sat Jan  1 01:59:59 2000
03: FFFFFFFF  Sat Jan  1 01:59:59 2000
04: FFFFFFFF  Sat Jan  1 01:59:59 2000
05: FFFFFFFF  Sat Jan  1 01:59:59 2000
06: FFFFFFFF  Sat Jan  1 01:59:59 2000
07: FFFFFFFF  Sat Jan  1 01:59:59 2000
08: FFFFFFFF  Sat Jan  1 01:59:59 2000
09: FFFFFFFF  Sat Jan  1 01:59:59 2000
10: FFFFFFFF  Sat Jan  1 01:59:59 2000
11: FFFFFFFF  Sat Jan  1 01:59:59 2000
12: FFFFFFFF  Sat Jan  1 01:59:59 2000
13: FFFFFFFF  Sat Jan  1 01:59:59 2000
14: FFFFFFFF  Sat Jan  1 01:59:59 2000
15: FFFFFFFF  Sat Jan  1 01:59:59 2000
16: FFFFFFFF  Sat Jan  1 01:59:59 2000
17: FFFFFFFF  Sat Jan  1 01:59:59 2000
18: FFFFFFFF  Sat Jan  1 01:59:59 2000
19: FFFFFFFF  Sat Jan  1 01:59:59 2000
20: FFFFFFFF  Sat Jan  1 01:59:59 2000
21: FFFFFFFF  Sat Jan  1 01:59:59 2000
22: FFFFFFFF  Sat Jan  1 01:59:59 2000
23: FFFFFFFF  Sat Jan  1 01:59:59 2000
24: FFFFFFFF  Sat Jan  1 01:59:59 2000
25: FFFFFFFF  Sat Jan  1 01:59:59 2000
26: FFFFFFFF  Sat Jan  1 01:59:59 2000
27: FFFFFFFF  Sat Jan  1 01:59:59 2000
28: FFFFFFFF  Sat Jan  1 01:59:59 2000
29: FFFFFFFF  Sat Jan  1 01:59:59 2000
30: FFFFFFFF  Sat Jan  1 01:59:59 2000
31: FFFFFFFF  Sat Jan  1 01:59:59 2000
32: FFFFFFFF  Sat Jan  1 01:59:59 2000

Maybe I'm just paranoic or something, but how can a log be this empty, with no SYSCON intervention beforehand? (as in cleaning log)
It's legitimately the only console I have logged in my consoles spreadsheet that's this clean.
The other 8 units I own, all have at least one or two error codes at a minimum (e.g one of my CECHK04 has at least four 1001s in the log with no date)
I'd have thought it was used as a server... but would it have such a high bringup and shutdown count if that was the case?

Thoughts?

 

[Pestaur]

Hi,

i'm trying to find the fault on a PS3 slim (cech 2004a dyn-001). It is a mystery for me...

After the start, the blinking RED (YLOD) is after 42sec. Yes, so long.. But the syscon error log is just FFFFFF

>$ version
00000000
# Sherwood Version = 1.11.0

Press Ctrl+C to exit
>$ tsensor
00000006

Press Ctrl+C to exit
>$ thrm
00000000
# FanCon_0, T=39.75, Duty=0%(0x00) - Mode:Minimun
# FanCon_1, T=28.75, Duty=0%(0x00) - Mode:Minimun

Press Ctrl+C to exit
>$ nonfatalerror
F0000006

Press Ctrl+C to exit
>$ errlog
00000000
# CODE     CLOCK
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF
# FFFFFFFF FFFFFFFF

after turning it on, and aster the 42sec, the errlog command is gives a long answer, but so long, that it does not fot into the terminal buffer....

>$ errlog
FFFFFFFF Answer length
Press Ctrl+C to exit
>$ powersw
00000000

Press Ctrl+C to exit
>$ shutdown
00000000
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Press Ctrl+C to exit
>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

Press Ctrl+C to exit
>$

.
.
.
.
.

#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!
#!PTC_DUMP
#!0000
#!0000
#!0ab5
#!0b1b
#!0000
#!0000
#!0a65
#!0acd
#!0000
#!0000
#!09c3
#!0a2c
#!0000
#!0000
#!0a65
#!0acc
#!0000
#!0000
#!0a5d
#!0ac3
#!0000
#!0000
#!0a9c
#!0b05
#!0000
#!0000
#!0a58
#!0ac0
#!0000
#!0000
#!0aa8
#!0b0b
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0a75
#!0adb
#!0000
#!0000
#!0aac
#!0b14
#!0000
#!0000
#!09ca
#!0a2f
#!0000
#!0000
#!0a65
#!0acd
#!0000
#!0000
#!09d4
#!0a35
#!0000
#!0000
#!0a62
#!0ace
#!0000
#!0000
#!09cd
#!0a31
#!0000
#!0000
#!0a67
#!0ad0
#!0000
#!0000
#!0000
#!0000
#!0000
#!0000
#!0a02
#!0a66
#!0000
#!0000
#!09c0
#!0a28
#!0000
#!0000
#!09e7
#!0a4f
#!0000
#!0000

Press Ctrl+C to exit
>$ errlog
FFFFFFFF Answer length
Press Ctrl+C to exit

Any ideas? How can i get the reason for this?

Thanx!

 

[DexHonda]

Hi there,
Finally got confirmation mail so I can ask for help here. Got old fat ps3 and only first star is problem, always is freeze system.
Here pic of my system trough ps3 tool set.

Thanks

 

[Nixievi]

Hello everyone, i hope you all are having a good christmas, if you don't celebrate christmas i hope you are doing well!

i was wondering if anyone can help me figure this issue out, my ps3 has a 4 second ylod but can rarely boot with a black screen

i had a friend try doing a repair to the nec tokins, not hoping any luck out of it

i recieved it and i tried turning it on when

it would cut off all power
Red to green then black in not even a second.

can anyone help me with this thanks!

 

[Centrinus]

Good afternoon and Merry Christmas to all.

I apologize if this is not the correct way to proceed when writing a message in the forum since this is my first time here.

I have been researching around the forum and have been able to connect to SYSCON to extract some information that I think may be relevant. I tell you the story of my first PS3...
It is a CECHG04 console with SEM-001 board. I got the YLOD for the first time while playing and, after a few months, I took it to fix (I was too young and I do not know if they did reballing, reflow, delid or all at once haha). It worked then normally until one day it didn't turn on: HDD led lights up for a moment, three beeps and then yellow light.
I am very fond of this console and I would like to ask you if it could be fixed (I am not an expert in electronics like many of you but I know the basics). I have seen that there are more commands and more ways to proceed besides mine, but I would like to ask you for advice first, since you have much more experience than me. This is my last CMD session with all the interesting stuff I got after fixing checksum and entering in CXRF mode:

>$ AUTH
Auth successful
Press Ctrl+C to exit
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x1596
Addr:0x000034fe should be 0x86d6
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
Press Ctrl+C to exit
>$ errlog
errlog
ofst[104]:err_code:0xffffffff, clock:0xffffffff
ofst[108]:err_code:0xa0902120, clock:0xffffffff
ofst[112]:err_code:0xa0313032, clock:0xffffffff
ofst[116]:err_code:0xa0902120, clock:0xffffffff
ofst[120]:err_code:0xa0313032, clock:0xffffffff
ofst[124]:err_code:0xa0902120, 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: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
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
[mullion]$
Press Ctrl+C to exit
>$ becount
becount
Bringup : 2704 times
Shutdown: 2614 times
Power-on: 145day 07hour 19min 01sec
[mullion]$
Press Ctrl+C to exit
>$
Exiting...

I have seen that error 2120 is related to HDMI and 3032 is related to CELL... How would you proceed in this case? What would be my next steps? Any advice?

Thank you so much.

 

[Tomatarto]

O

Hi there,
Finally got confirmation mail so I can ask for help here. Got old fat ps3 and only first star is problem, always is freeze system.
Here pic of my system trough ps3 tool set.

Thanks

Oscilloscope NEC/TOKINS and check if they are good

 

[Tomatarto]

Hello everyone, i hope you all are having a good christmas, if you don't celebrate christmas i hope you are doing well!

i was wondering if anyone can help me figure this issue out, my ps3 has a 4 second ylod but can rarely boot with a black screen

i had a friend try doing a repair to the nec tokins, not hoping any luck out of it

i recieved it and i tried turning it on when

it would cut off all power
Red to green then black in not even a second.

can anyone help me with this thanks!

Gotta tell us the console model and dump the SYSCON

 

[OneFix]

CECHA GLOD problem. Only one beep. Replaced RSX 40nm twice and same problem. Does anyone know the solution?

As you can see below SB uart is very short? Defect CELL?

SB uart:

Boot Loader SE Version 4.8.9 (Build ID: 5366,50740, Build Date: 2022-02-04_12:51:26)
SDK Version: 489.000
Copyright(C) 2021 Evilnat [Akatsuki]. Happy CFW moments. 05/10/2022  .
[INFO]: === eXtreme Data Rate Memory Subsystem ===
[INFO]: (Configured Memory Size per single XIO channel: 128 MBytes.)
[INFO]: XIO channel[0] is available.
[INFO]: XIO channel[1] is available.
[INFO]: ---> Total 256 MBytes are now in use.
[INFO]: SPU enable [0, 1, 2, 5, 6, 7] 11101111
[INFO]: BE:3.1, SB:DX3.1
Device: PATAC0:Cable Not Connect

Bringup log:

[IMG]https://www.psx-place.com/file:///C:/Users/pake6/AppData/Local/Packages/Microsoft.Windows.Photos_8wekyb3d8bbwe/TempState/ShareServiceTempFolder/SB%20uart.jpeg[/IMG]
Bringup log
Connection\PS3_Syscon_(Mullion_Sherwood)_script.py" COM3 CXRF
> AUTH
Auth successful
> 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
> powerstate
[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
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]$
> shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000002F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>

 

[saseca]

hello
im not an expert in technology but, here is my error codes:
my ps3 is FAT VER - 001
the ps3 cant turn on

>$ errlog
00000000
# CODE     CLOCK
# A0802124 0B49D808
# A0801002 0B49D808
# A0802124 0B49D823
# A0801002 0B49D822
# A0802124 0B49D809
# A0802124 0B49D808
# A0801002 0B49D808
# A0802124 0B49D80A
# A0801002 0B49D809
# A0802124 0B4A1C59
# A0801002 0B4A1C59
# A0112024 0B4A0741
# A0112124 0B4A0740
# A0112124 0B4A0740
# A0112124 0B4A073F
# A0112124 0B4A073F
# A0112124 0B4A073E
# A0112124 0B4A073E
# A0112024 0B4A073D
# A0112124 0B4A073D
# A0112124 0B4A073C
# A0112124 0B4A073C
# A0112124 0B4A073B
# A0112124 0B4A073B
# A0112024 0B4A073A
# A0112124 0B4A073A
# A0112124 0B4A0739
# A0112124 0B4A0739
# A0112124 0B4A0738
# A0112124 0B4A0738
# A0112124 0B4A0737

A0802124 - 6
A0801002 - 5 POWER RSX (NET TOKENS??)
A0112024 - 3 AV
A0112124 - 11 AV

>$ shutdown
00000000
# [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.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2687.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

Any help is apreciated!!
Thx

 

[Soppn]

This is from my CECH03 which was bought second hand not too long after EU release (maybe winter 07/early 08). It developed the YLOD issue some time in 2015/16 and was opened up once in 2016 (no repairs attempted, just cleaned). Decided to open it up again and record the logs:

ofst[100]:err_code:0xffffffff, clock:0x1ff306f6  2016/12/25 22:38:46
ofst[104]:err_code:0xa0901001, clock:0x1ff306f6  2016/12/25 22:38:46
ofst[108]:err_code:0xa0801701, clock:0x1ff30718  2016/12/25 22:39:20
ofst[112]:err_code:0xa0801601, clock:0x1ff30718  2016/12/25 22:39:20
ofst[116]:err_code:0xa0901001, clock:0x1ff30718  2016/12/25 22:39:20
ofst[120]:err_code:0xa0404422, clock:0x1ff3071f  2016/12/25 22:39:27
ofst[124]:err_code:0xa0403034, clock:0x1ff3071f  2016/12/25 22:39:27
ofst[  0]:err_code:0xa0801701, clock:0x1ff3072c  2016/12/25 22:39:40
ofst[  4]:err_code:0xa08014ff, clock:0x1ff3072c  2016/12/25 22:39:40
ofst[  8]:err_code:0xa0801601, clock:0x1ff3072c  2016/12/25 22:39:40
ofst[ 12]:err_code:0xa0901001, clock:0x1ff30799  2016/12/25 22:41:29
ofst[ 16]:err_code:0xa0801701, clock:0x1ff307b5  2016/12/25 22:41:57
ofst[ 20]:err_code:0xa08014ff, clock:0x1ff307b5  2016/12/25 22:41:57
ofst[ 24]:err_code:0xa0801601, clock:0x1ff307b5  2016/12/25 22:41:57
ofst[ 28]:err_code:0xa08014ff, clock:0x1ff307f2  2016/12/25 22:42:58
ofst[ 32]:err_code:0xa0801701, clock:0x1ff307f2  2016/12/25 22:42:58
ofst[ 36]:err_code:0xa0801701, clock:0x1ff30919  2016/12/25 22:47:53
ofst[ 40]:err_code:0xa08014ff, clock:0x1ff3091a  2016/12/25 22:47:54
ofst[ 44]:err_code:0xa0801601, clock:0x1ff3091a  2016/12/25 22:47:54
ofst[ 48]:err_code:0xa0801701, clock:0x1ff4158f  2016/12/26 17:53:19
ofst[ 52]:err_code:0xa0801601, clock:0x1ff4158f  2016/12/26 17:53:19
ofst[ 56]:err_code:0xa0901001, clock:0x1ff4158f  2016/12/26 17:53:19
ofst[ 60]:err_code:0xa0404402, clock:0x2d1e5741  2023/12/27 03:32:17
ofst[ 64]:err_code:0xa0403034, clock:0x2d1e5741  2023/12/27 03:32:17
ofst[ 68]:err_code:0xa0404402, clock:0x2d1e6213  2023/12/27 04:18:27
ofst[ 72]:err_code:0xa0403034, clock:0x2d1e6213  2023/12/27 04:18:27
ofst[ 76]:err_code:0xa0404402, clock:0x2d1e6225  2023/12/27 04:18:45
ofst[ 80]:err_code:0xa0403034, clock:0x2d1e6225  2023/12/27 04:18:45
ofst[ 84]:err_code:0xa0404402, clock:0x2d1e623b  2023/12/27 04:19:07
ofst[ 88]:err_code:0xa0403034, clock:0x2d1e623b  2023/12/27 04:19:07
ofst[ 92]:err_code:0xa0404402, clock:0x2d1e636a  2023/12/27 04:24:10
ofst[ 96]:err_code:0xa0403034, clock:0x2d1e636a  2023/12/27 04:24:10

becount
Bringup : 1901 times
Shutdown: 1722 times
Power-on: 157day 16hour 32min 11sec

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
>$
[POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS
[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]: 0xa0404402
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

Is RSX still most likely even though it started with 1001/1701/1601 before 3034/4xxx started appearing?

I only have access to a hot air station, no full rework setup.

 

[Raidmax]

The 14FF associated with 1601 and 1701 say it all - RSX was in its early stages of failure.

3034/4402 is when it failed completely.

I assume you experienced funny green stuff on the screen before failure? One of the cases I had with it (an very abused CECHG04) did that before going belly up forever.

 

[Edge101]

Hi all,

my first attempt at figuring out what's going on with my YLOD PS3 backwards (CECHC03) COK1.

This was immensely helpful and a fantastic guide! I am assuming with all the recent 1002 errors its related to NEC tokens, but want to confirm and am a little stuck...

I was able to successfully access External mode obtaining the below log, but unable to access Internal mode:

I used the command EEP SET 3961 01 00 - Was able to confirm it was set to 00, turned off console, connected Diag to Ground on my USB. Turned on 3 beeps and flashing Red light. all as per guide.

However, when attempting to connect to CXRF i get the following error on auth command, any ideas how to fix?

C:\Downloads\ps3syscon-master\ps3syscon-master\Linux>ps3_syscon_uart_script.py COM3 CXRF
Press Ctrl+C to exit
>$ auth
Traceback (most recent call last):
File "C:\Downloads\ps3syscon-master\ps3syscon-master\Linux\ps3_syscon_uart_script.py", line 217, in <module>
main(len(sys.argv), sys.argv)
File "C:\Downloads\ps3syscon-master\ps3syscon-master\Linux\ps3_syscon_uart_script.py", line 194, in main
print(ps3.auth())
^^^^^^^^^^
File "C:\Downloads\ps3syscon-master\ps3syscon-master\Linux\ps3_syscon_uart_script.py", line 152, in auth
auth1r = auth1r[1][0].split('\r')[1][1:]
~~~~~~~~~~~~~~~~~~~~~~~~^^^
IndexError: list index out of range




EXTERNAL LOG:
>$ ERRLOG GET 00
00000000 A0231002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 01
00000000 A0231002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 02
00000000 A0231002 FFFFFFFF
Press Ctrl+C to exit
>$ ERRLOG GET 03
00000000 A0801002 0B4886F2
Press Ctrl+C to exit
>$ ERRLOG GET 04
00000000 A0801002 0B4886E8
Press Ctrl+C to exit
>$ ERRLOG GET 05
00000000 A0801002 0B488692
Press Ctrl+C to exit
>$ ERRLOG GET 06
00000000 A0801002 0B488680
Press Ctrl+C to exit
>$ ERRLOG GET 07
00000000 A0801001 265B33CA
Press Ctrl+C to exit
>$ ERRLOG GET 08
00000000 A0801002 2659A422
Press Ctrl+C to exit
>$ ERRLOG GET 09
00000000 A0801001 2631E599
Press Ctrl+C to exit
>$ ERRLOG GET 0A
00000000 A0801001 1B25F82F
Press Ctrl+C to exit
>$ ERRLOG GET 0B
00000000 A0801001 1B1891BA
Press Ctrl+C to exit
>$ ERRLOG GET 0C
00000000 A0801001 1AED3789
Press Ctrl+C to exit
>$ ERRLOG GET 0D
00000000 A0801001 1AE547E9
Press Ctrl+C to exit
>$ ERRLOG GET 0E
00000000 A0801001 1AE40015
Press Ctrl+C to exit
>$ ERRLOG GET 0F
00000000 A0801001 14ABDCF9
Press Ctrl+C to exit
>$ ERRLOG GET 10
00000000 A0801001 14ABDCC7
Press Ctrl+C to exit
>$ ERRLOG GET 11
00000000 A0801001 14A8AAC3
Press Ctrl+C to exit
>$ ERRLOG GET 12
00000000 A0801001 14A8932A
Press Ctrl+C to exit
>$ ERRLOG GET 13
00000000 A0902120 14A79CB1
Press Ctrl+C to exit
>$ ERRLOG GET 14
00000000 A0801001 14A79CB1
Press Ctrl+C to exit
>$ ERRLOG GET 15
00000000 A0A02031 14A5429A
Press Ctrl+C to exit
>$ ERRLOG GET 16
00000000 A0A02030 14A54299
Press Ctrl+C to exit
>$ ERRLOG GET 17
00000000 A0801001 14051146
Press Ctrl+C to exit
>$ ERRLOG GET 18
00000000 A0801001 13F18840
Press Ctrl+C to exit
>$ ERRLOG GET 19
00000000 A0801001 13C91C21
Press Ctrl+C to exit
>$ ERRLOG GET 1A
00000000 A0901001 13C9094F
Press Ctrl+C to exit
>$ ERRLOG GET 1B
00000000 A0801001 13C5D242
Press Ctrl+C to exit
>$ ERRLOG GET 1C
00000000 A0801001 13C32D74
Press Ctrl+C to exit
>$ ERRLOG GET 1D
00000000 A0801001 13BB5C6A
Press Ctrl+C to exit
>$ ERRLOG GET 1E
00000000 A0801001 139FD18E
Press Ctrl+C to exit

 

[vyktormvmpay25]

Could be something to do with software. Few things to test before jumping to flash nands. If you press 10 seconds to enter recovery/safe mode and it act as it should, there is no software issues. Looking for that short sb log is confusing but should be like rsod corruption of nands.
Any errorlog? Not sure if will create any errors on syscon as it boot lv0 and it stops like on lv1.
It look like you had done this before and worked for previous units?
What rework station you use? Powers of bottom /top?
I've killed many rsx in different tests with my rework but once set it on a specific distance with mobo and right time it works perfect. Watch Computer Booter have same rework station as mine.
Now you can't fry 2 rsx in row with "special glod", this doesn't look like special glod when rsx is dead but sb uart log will say soft loaded complete without any errors on syscon.
Can't see photo attached from phone/tapatalk, not big deal.
@OneFix

 

[OneFix]

Could be something to do with software. Few things to test before jumping to flash nands. If you press 10 seconds to enter recovery/safe mode and it act as it should, there is no software issues. Looking for that short sb log is confusing but should be like rsod corruption of nands.
Any errorlog? Not sure if will create any errors on syscon as it boot lv0 and it stops like on lv1.
It look like you had done this before and worked for previous units?
What rework station you use? Powers of bottom /top?
I've killed many rsx in different tests with my rework but once set it on a specific distance with mobo and right time it works perfect. Watch Computer Booter have same rework station as mine.
Now you can't fry 2 rsx in row with "special glod", this doesn't look like special glod when rsx is dead but sb uart log will say soft loaded complete without any errors on syscon.
Can't see photo attached from phone/tapatalk, not big deal.
@OneFix

Thanks for the comments @vyktormvmpay25 ! Console does not enter to recovery/safe mode. I have now reballed cell, but no differences. I am using ACHI IR PRO station with elstein's heaters (2400w + 400w). Next I will check corruption of nands.

 

[Totigag]

Hello, this is my ps3 slim with ylod output, last 2 codes (3001) its just testing, now its only giving 1002 code. Would replacing nec/tolkin help?

Mobo: (DYN-001)

>$ errlog
00000000
# CODE     CLOCK
# A0003001 FFFFFFFF
# A0003001 FFFFFFFF
# A0801002 FFFFFFFF
# A0801002 FFFFFFFF
# A0801002 FFFFFFFF
# A0801002 FFFFFFFF
# A0801002 FFFFFFFF
# A0801002 FFFFFFFF
# A0A02024 FFFFFFFF
# A0801002 FFFFFFFF
# A0801002 0B49D800
# A0A02024 FFFFFFFF
# A0801002 0B49D996
# A0902024 0B49D98F
# A0801002 0B49D818
# A0902024 0B49D812
# A0801002 0B49D801
# A0A02024 FFFFFFFF
# A0801002 0B49D814
# A08014FF 0B49D814
# A0902024 0B49D80C
# A0801002 0B49D800
# A0A02024 FFFFFFFF
# A0801002 0B49E663
# A0801002 0B49E650
# A0801002 0B49E643
# A0801002 0B49E633
# A0801002 0B49E624
# A0801002 0B49E616
# A0801002 0B49E5D5
# A08014FF 0B49E5D5

>$ bringup
00000000
# [SSM] Bringup Start.
# [SSM] PS0 ok.
# [SSM] PS1 ok.
# [SSM] PS2 ok.

>$ shutdown
00000000
# [SSM] PS3 ok.
# [SSM] PS4 ok.
# (PowerOn State)
OK 00000000
#!
#!Boot Loader SE Version 2.7.0
#!(Build ID: 3517,38879,
#!Build Date: 2009-03-24_23:51:55)
#!
#!Copyright(C) 2009 Sony Computer Entertainment Inc.All Rights Reserved.
#!
#![INFO]: Connecting to Debug Device (SB UART)
# [SSM] Cond/Fatal received, msg=2663.
# [SSM] Fataldown Start.
# [SSM] Fataldown ok.
# (PowerOff State) (Fatal)
# [SSM] Clearfatal Start.
# [SSM] Clearfatal ok.
# (PowerOff State)

 

[vyktormvmpay25]

Thanks for the comments @vyktormvmpay25 ! Console does not enter to recovery/safe mode. I have now reballed cell, but no differences. I am using ACHI IR PRO station with elstein's heaters (2400w + 400w). Next I will check corruption of nands.

Yes really good rework, like I said it has to be more software issue not so good there but will see.