PS3 20sec YLOD no syscon error

Plermpel

Forum Noob
Hi,

I bought a YLOD CECHG just for fun to learn a bit about PS3 hardware. It came with 1002 errors so I replaced the Proadlizers with MLCC arrays. Now the console turns on for exactly 20 seconds, without video output (which happens to be the exact moment where the HDD LED flashes for the first time) and YLODs again, but there are no further syscon errors, how do I diagnose the system any further?
 
Some easy things I assume you already did:
  • Send "bringup" to the syscon to start the console. After YLOD happens (when the power LED is blinking red) use "shutdown" to clear the error state. It should display the error code.
  • Make a copy of your current syscon error log and then compare that copy to the new log after 3 YLODs. If your CMOS battery is dead and all error codes are the same and have no time attached to them you could try to clear the error log ("clearerrlog" I think?) after making a copy (for archival) and then just look at the new errors.
This might be a GLOD in-between state? IDK. You could also try to check the resistance of the RSX to confirm if it is healthy. I never understood how to do it so someone more knowledgeable will have to explain it.
Maybe post a picture or 2 of the NEC tokin replacements and your current error log? They might give more clues.
 
There are more on the other side, in total 22x220uF MLCCs per chip. I wondered if ESR is too low with these but I guess that would lead to at least some error?
8uKflxb.jpeg

What do you mean by "It should display the error code", Where?
There is no error, it just YLODs, the last errors where a few 1002s from before I switched out the caps, now there is nothing, AFAIK.
What is a little bit weird, sometimes after I "bringup" the console, it starts but syscon only prints gibberish, very likely that this is due to some interferences though.

How should one check the residents of a soldered BGA Chip? There are literally hundrets of factors that will disturb that measurement. I can only say for sure that both chips have no direct short on their VCORE rail.
 
Do you have a part number for the caps? Just to remove any doubts about ESR and impedance. I can see 10 caps (5 for each prodilazer) in the picture so I assume the other side has 12 (6 each) with no bridge?

This is what I mean for what the error state looks like: (red arrow points to it)
Capture.PNG

Actually you just need to hit Enter to receive the queued up up syscon messages and "shutdown" to clear it. That error is what gets logged in the error log. It's not that I don't believe you or something but can you post what you see when you do that? Also can you try to clear the error log after making an archival copy before doing it? A clean log will really confirm if there are any errors getting generated.

The "gibberish" could be the connection wires and bad soldering or maybe a loose ground to diag connection?
 
I see, for some reason, the error never showed up in the log and I did overlook that it it is showed together with the shutdown command.

The error is 2002 - XDR Link not initialized, I did damage a 0,1uF cap next to the CELL, when deliding it and I replaced it, but it looks like somehing went wrong there or I maybe damaged another one, thank you very much!
 
I see, for some reason, the error never showed up in the log and I did overlook that it it is showed together with the shutdown command.

The error is 2002 - XDR Link not initialized, I did damage a 0,1uF cap next to the CELL, when deliding it and I replaced it, but it looks like somehing went wrong there or I maybe damaged another one, thank you very much!
Have you also delided the RSX? 2002 in the wiki just says RSX so maybe you damaged it in some way while doing so? I would not exclude a damaged trace on/next to the CELL too.
2203 is the only error to mention XDR Link not initialized but it could also just be a coincidence.
Here is the schematic for the G model if you haven't seen it yet: https://consolemods.org/wiki/images/6/6b/Sony_ps3_sem-001_3rd.pdf
Maybe it can help you find out if you knocked a component out of alignment.
 
Have you also delided the RSX?

Yes although that was very easy, the IHS almost fell off on it's own after applying a little bit of heat.

2203 is the only error to mention XDR Link not initialized but it could also just be a coincidence.

Interesting, it says:
ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
directly in the syscon. Gonna post the full syscon later today.

Here is the schematic for the G model if you haven't seen it yet: https://consolemods.org/wiki/images/6/6b/Sony_ps3_sem-001_3rd.pdf

No I haven't, again, very helpful, thanks!
 
Interesting, it says:
ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
directly in the syscon. Gonna post the full syscon later today.
HOLD UP WHAT??
0xb0002002
I have NEVER heard of a B error before. They are supposed to always be prefixed with an A according to the devwiki:
The error codes follows the format: ARSTCERR , where:
A (Fixed) = This is always "A"

Could this be why it is not being saved to the error log? Or maybe the STep number being 00?

Someone more knowledgeable is needed for sure! @RIP-Felix, @luaks-hermann (I can't for the life of me figure out how to @ luaks) you 2 are the only people I found who had this issue. Maybe join the convo if you have free time? I read the stories of PS3 #16 and luakss' Slim but both didn't get any endings.

Hopefully it isn't a dead XDR chip and a small component instead...
 
Ok, so here is what my syscon spits out.

plermpel@NOTEBOOK:~/Downloads/ps3syscon-master/Linux$ python3 ps3_syscon_uart_script.py /dev/ttyUSB0 CXRF
Press Ctrl+C to exit
>$ auth
Auth successful
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:0x20e7
Press Ctrl+C to exit
>$ shutdown
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 2.0.0 (Build ID: 2655,27256, Build Data: 2007-10-26_12:10:58)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[ERROR]: 0xb0002002 (FATAL) XDR Link not initilized.
ITC_DUMP000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
PTC_DUMP000000000a710ad7000000000a050a65000000000a180a76000000000a0a0a6d000000000a8c0af3000000000a980afa000000000a880aed000000000aa40b090000000000000000000000000a800ae4000000000a150a750000000009d40a310000000009db0a3f0000000009d10a31000000000a780ada0000000009d70a39000000000a800aec0000000000000000000000000a4f0aae0000000009c00a200000000009dc0a3d0000000009c80a200000000009b20a18000000000a490aa80000000009c40a24000000000a5a0ab60000000000000000000000000a770add0000000009ef0a4d0000000009f40a510000000009e50a43000000000a700ace000000000a4e0ab1000000000a6e0ad0000000000a800ae20000000000000000000000000a650aca0000000009fe0a500000000009e50a3f0000000009c50a21000000000a610acc000000000a730ad7000000000a600ac3000000000a4d0aab0000000000000000000000000a450aaa0000000009eb0a440000000009e10a3f0000000009d20a240000000009bf0a19000000000a400aa00000000009ce0a28000000000a4e0aaf0000000000000000000000000a790adb000000000a040a600000000009c50a260000000009d50a340000000000000000000000000a800ae60000000000000000000000000a800ae00000000000000000000000000aa50b01000000000a070a61000000000a140a71000000000a0e0a67000000000a720ad6000000000aa00b00000000000a980af9000000000ab00b110000000000000000
MIC_DUMP0000000000000000000000000000000000000000000000003200000000000000000000000000000000000000000000000000000fffffff8000000000000120000000000000100000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b400000000000000001b87000000000000140002000000000004810000000000000100000000000000c8000000000000000000000000000000000010000000000000000000000000001b87000000000000140002000000000004810000000000000100000000000000c800000000000000000000000000000000001000000000000000000000000000502000000000000000e00000000000006284055ad6b000005d7000000000000071800210000000000a963d6000000000edd61229594ba6b40000000000000000800000000000000000000000000000000800000000000000080000000000000000000000000000000000000000000000ffc0000000000000061101700000000040000000000000007cfe000000000000e1c0000000000000000000000000000000000000000000000000fd400000000000000280000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000130000000000000000
XIO_DUMP00010002000900000064000001d30000000000140000000000000064000721e109410000000f000f00200000a080000800010008000008540c540000000000010bad000000000000000000000000000c000c000c000c005800580058005800000000000000000110011001100110443944
Press Ctrl+C to exit
>$

6YqNuHN.jpeg


Well...


That will be the reason :(

Is it even worth trying to fix this?
 
Last edited by a moderator:

Similar threads

Back
Top