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

[Jose Denilson Nog F]

Getting two error codes on a 3001B system from every shutdown, in this order:

A0801701
A08014FF

Dev wiki says 14FF is likely RSX bumps (on a 40nm? damn)... but is it possible it could be hard drive I/O related? Let me explain.

Background:

Shutdown usually happens soon after power on, but I found I can get to the XMB if I start with a safe mode and reformat.

And after that reformat, I've been able to allow Shadow of the Colossus to run for hours with no errors.

But when I try to play Vanquish, PS3 crashes early in the tutorial stage, before you get out of first person mode. Same two errors.

The difference between Vanquish and SotC? Vanquish installs a lot of files onto the hard drive.

Another strange event: I had a very old 30GB SSD that I've used for various things in a variety of PCs, including as portable storage. But it immediately fried when I tried to use it in the PS3. Couldn't use it again in a PC

After that I got a modern SSD that is holding up so far. Before all this I removed HDD that the system came with because googling had told me that could be the problem, I've never actually tried to put it back in. I noticed I can read SMART data off it. I don't if that's normal or not.

So, between the frying of the old SSD, and the difference in behavior between Vanquish and SotC, is it possible this could be a faulty circuit going to the SATA port?

I guess the difference between the two games could just also be down to how they tax the RSX?

You could try look for shorts or wrong voltages near the HDD circuit, if there is a service manual avaible or some information about it on yt or something like that. Dont really know how to help but this would be my first guess in your situation.

 

[Emil Tuzla]

Getting two error codes on a 3001B system from every shutdown, in this order:

A0801701
A08014FF

Dev wiki says 14FF is likely RSX bumps (on a 40nm? damn)... but is it possible it could be hard drive I/O related? Let me explain.

Background:

Shutdown usually happens soon after power on, but I found I can get to the XMB if I start with a safe mode and reformat.

And after that reformat, I've been able to allow Shadow of the Colossus to run for hours with no errors.

But when I try to play Vanquish, PS3 crashes early in the tutorial stage, before you get out of first person mode. Same two errors.

The difference between Vanquish and SotC? Vanquish installs a lot of files onto the hard drive.

Another strange event: I had a very old 30GB SSD that I've used for various things in a variety of PCs, including as portable storage. But it immediately fried when I tried to use it in the PS3. Couldn't use it again in a PC

After that I got a modern SSD that is holding up so far. Before all this I removed HDD that the system came with because googling had told me that could be the problem, I've never actually tried to put it back in. I noticed I can read SMART data off it. I don't if that's normal or not.

So, between the frying of the old SSD, and the difference in behavior between Vanquish and SotC, is it possible this could be a faulty circuit going to the SATA port?

I guess the difference between the two games could just also be down to how they tax the RSX?

A0801701 and A08014FF together usually means hdd problem or software problem (if you have homebrew apps installed, it can make software conflicts).
If its RSX bumps you would get something like A0803034

 

[Fallen777]

Anyone had A0801200 errors after fixing tokins?
I got console with a lot 1001 and 1002 errors and after replacing tokins now its glod and getting only A0801200 errors.

CECHH04
DIA-001 MB

===================================
ERR 00: 00000000 A0801200 FFFFFFFF
ERR 01: 00000000 A0801200 FFFFFFFF
ERR 02: 00000000 A0801200 FFFFFFFF
ERR 03: 00000000 A0801200 FFFFFFFF
ERR 04: 00000000 A0801200 FFFFFFFF
ERR 05: 00000000 A0801200 FFFFFFFF
ERR 06: 00000000 A0801200 FFFFFFFF
ERR 07: 00000000 A0801200 FFFFFFFF
ERR 08: 00000000 A0801004 1D201CC5
ERR 09: 00000000 A0801004 FFFFFFFF
ERR 10: 00000000 A0801004 0B741FBC
ERR 11: 00000000 A0801004 0B740998
ERR 12: 00000000 A0801004 1D172E22
ERR 13: 00000000 A0801004 1D16F734
ERR 14: 00000000 A0801004 0B6D0BE8
ERR 15: 00000000 A0801004 1C0F8D06
ERR 16: 00000000 A0801004 0B682B33
ERR 17: 00000000 A0801002 FFFFFFFF
ERR 18: 00000000 A0801004 1D0F4905
ERR 19: 00000000 A0801001 1D0F382B
===================================

Afraid not only a couple of consoles have been recovered by replacing tmp411a that's the thermal monitor my own console suffer the exact condition

Rule of thumb would be to check if syscon gets the tmp right on UART should be under 50 on idle if that's the case then its not thermal paste but rather the circuitry between syscon pin 83 and cell thermal alert pad you'll have to trace it all the way back to cell I am under the impression that this pin 83 thermal alert should maintain a stable signal that should be driven low but its not a one to one direct connection to cell there should be filter or cap right next to it on syscon and there should be a regulation circuit that needs to be traced out and values to be reference from a working board my guess is the main disruption would be there a busted filter or resistor probably a shorted cap would be a short to ground on entire circuit
But it depends down on the consoles value to you whether you are desperate to trace it all back for your sanity or work on it for money either way it will be great service to all if anyone decides to do so
I am considering doing it in coming days some weeks from now

 

[Bazookaben]

A0801701 and A08014FF together usually means hdd problem or software problem (if you have homebrew apps installed, it can make software conflicts).
If its RSX bumps you would get something like A0803034

OK, I don't know if the previous owner had homebrew or not, but I've just been running it formatted on new SSD with OFW.

I can start probing HDD-related parts of the motherboard, but I can't find an schematics for 3xxx systems to help me out there

Do we only have service manuals available for fat models?

Also, if you guys have links to posts where people found hard-drive related motherboard problems, I'd love to take a look. Google isn't helping me very much here.

 

[Divano]

Good evening,
I followed the guide to extract data using "syscon". It worked, and I extracted the following errors:

# CODE CLOCK
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF

In these errors there is also the error "A0403034," which as I understand it usually refers to a communication error with the "RSX." I attempted to perform a reflow, and since I did the error has changed to error "A0111B02". I can't figure out what it refers to....
Can anyone help me?

My console is a cechl ver-001

 

[Tomatarto]

Good evening,
I followed the guide to extract data using "syscon". It worked, and I extracted the following errors:

# CODE CLOCK
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0111B02 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF
# A0403034 FFFFFFFF
# A0404002 FFFFFFFF

In these errors there is also the error "A0403034," which as I understand it usually refers to a communication error with the "RSX." I attempted to perform a reflow, and since I did the error has changed to error "A0111B02". I can't figure out what it refers to....
Can anyone help me?

My console is a cechl ver-001

From previous posts it seems that a 1B01 error code relates to a short with the CELL-BE or a component directly related to it. Thus it wouldn't be too out there if we assumed that a 1B02 relates to a short with the RSX or a component directly related to it. The step number 11 could also suggest a short of the RSX thermal monitor. Maybe damage of a component around the RSX due to the attempted reflow?

3034 and 4xxx errors typically represent BGA failures but the step number would have me believe that this is not the issue especially when considering that you have a 65nm RSX. Does the board and specifically the area around the RSX have what appears to be pockets of air underneath its surface, what is known as popcorning? Did you preheat the board beforehand?

 

[Tomatarto]

Getting two error codes on a 3001B system from every shutdown, in this order:

A0801701
A08014FF

Dev wiki says 14FF is likely RSX bumps (on a 40nm? damn)... but is it possible it could be hard drive I/O related? Let me explain.

Background:

Shutdown usually happens soon after power on, but I found I can get to the XMB if I start with a safe mode and reformat.

And after that reformat, I've been able to allow Shadow of the Colossus to run for hours with no errors.

But when I try to play Vanquish, PS3 crashes early in the tutorial stage, before you get out of first person mode. Same two errors.

The difference between Vanquish and SotC? Vanquish installs a lot of files onto the hard drive.

Another strange event: I had a very old 30GB SSD that I've used for various things in a variety of PCs, including as portable storage. But it immediately fried when I tried to use it in the PS3. Couldn't use it again in a PC

After that I got a modern SSD that is holding up so far. Before all this I removed HDD that the system came with because googling had told me that could be the problem, I've never actually tried to put it back in. I noticed I can read SMART data off it. I don't if that's normal or not.

So, between the frying of the old SSD, and the difference in behavior between Vanquish and SotC, is it possible this could be a faulty circuit going to the SATA port?

I guess the difference between the two games could just also be down to how they tax the RSX?

Classic combo yet again. the 14FF and 1701 errors happen when the CPU drives the BE ATTENTION signal high which in this case probably happened when it reached a checkstop state. I'm guessing this was due to a failure to communicate with the harddrive

yes it is possible that the SATA circuit could have something faulty but I don't think it is the issue that lead to that 30gb SSD blowing up. I think that SSD just blew up because of old age or maybe the PS3 was treating it as a harddrive and giving it the incorrect voltage, but that being said i have no evidence to base that claim.

Without service manuals for the slims it is hard to diagnose the SATA circuit obviously

Keep using it and backing it up periodically, if this SSD dies or you get these codes when trying to bringup and read then come back here. It might be safer to use a drive that is less valuable for the time being

 

[Bazookaben]

Keep using it and backing it up periodically, if this SSD dies or you get these codes when trying to bringup and read then come back here. It might be safer to use a drive that is less valuable for the time being

This is a free PS3 I'm trying to get in working order for my cousin, so nothing on it to back up. Just trying to figure out how to get it operational and reliable.

I've booted it many times since I got it and it's the same two codes every time, so I don't think there is much more work to be done as far as generating error codes. I just need to try and find some faulty components that would be causing the codes.

And the crashes are pretty predictable, only two triggers so far:

I usually get a crash before booting into XMB. I can more reliably get to the XMB if it's right after a system restore(option 5 in safe mode)

And I get a crash very early in the tutorial stage in Vanquish (haven't tried many other games), though I haven't glanced down at the light to see if it's accessing the HDD at that moment

Installing the game doesn't cause a crash or any errors. Only playing it.

Without service manuals for the slims it is hard to diagnose the SATA circuit obviously

I wonder how much overlap there could be with the fat models. Like if any of the chips for the SATA interface are the same/similar.

 

[Divano]

From previous posts it seems that a 1B01 error code relates to a short with the CELL-BE or a component directly related to it. Thus it wouldn't be too out there if we assumed that a 1B02 relates to a short with the RSX or a component directly related to it. The step number 11 could also suggest a short of the RSX thermal monitor. Maybe damage of a component around the RSX due to the attempted reflow?

3034 and 4xxx errors typically represent BGA failures but the step number would have me believe that this is not the issue especially when considering that you have a 65nm RSX. Does the board and specifically the area around the RSX have what appears to be pockets of air underneath its surface, what is known as popcorning? Did you preheat the board beforehand?

I honestly didn't notice any bubbles or bulges in the pcb, except in the front left corner of the board, but it had it even when it was working.

What components or sensors should I check for short circuits?

In case, do you happen to know anyone who sells a "VER-001" motherboard?

P.S. forgot to mention, that I preheated the motherboard evenly for a few minutes, in order to prevent any damage due to heavy thermal differences

 

[Tomatarto]

This is a free PS3 I'm trying to get in working order for my cousin, so nothing on it to back up. Just trying to figure out how to get it operational and reliable.

I've booted it many times since I got it and it's the same two codes every time, so I don't think there is much more work to be done as far as generating error codes. I just need to try and find some faulty components that would be causing the codes.

And the crashes are pretty predictable, only two triggers so far:

I usually get a crash before booting into XMB. I can more reliably get to the XMB if it's right after a system restore(option 5 in safe mode)

And I get a crash very early in the tutorial stage in Vanquish (haven't tried many other games), though I haven't glanced down at the light to see if it's accessing the HDD at that moment

Installing the game doesn't cause a crash or any errors. Only playing it.



I wonder how much overlap there could be with the fat models. Like if any of the chips for the SATA interface are the same/similar.

That is strange how a specific game causes it to crash at a specific point. While this may seem obvious, if you installed it from a disk did you check it for scratches? I have played games from disk where they install fine but halfway through progression they just crash for no reason.

It really doesn't seem to be the flash as the step number is too late but the step number also makes sense of why you can't boot into the XMB as that's when it loads it.

Sorry if im sending you down a rabbit hole but i just want to consider all possibilities.
And yes i guess it is possible that they might share a similar interface as there is not much you have to change typically for something like a SATA port

 

[Nator]

I'll also post here the message i left under the video tutorial about Rip-Felix's syscon. I hope it is correct.
I have a problem after assembling the console. It turns on but the led remains green and i can't see anything in the video(hdmi). I inserted a disk and it took it but if i try to eject it the blue light flashes and makes 3 beeps. Sometimes there is 720x576 video signal but the screen is black. During the assembly phase i broke the lever where the flat cable of the Blu-ray is insert, fixed it by attaching a sticker on it. I leave you the entire sequence of commands bringup, powerstate, errlog, tmp get 0 and tmp get 1, duty get 0.

Microsoft Windows [Versione 10.0.19045.3448]
C:\Users\Pc\Desktop\sysc\ps3syscon-master\ps3syscon-master\Linux>python ps3_syscon_uart_script.py COM3 CXRF
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ becount
becount
Bringup : 2970 times
Shutdown: 1834 times
Power-on: 104day 23hour 29min 08sec
[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
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
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
[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
[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

[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
>$ tmp get 0
tmp get 0
*** Invalid Argument ***
[mullion]$
Press Ctrl+C to exit
>$ tmp get 1
tmp get 1
*** Invalid Argument ***
[mullion]$
Press Ctrl+C to exit
>$ duty get 0
duty get 0
CrntDuty(0x0):20%(0x33)
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 24]:err_code:0xffffffff, clock:0x1b9cc1e3  2014/09/05 18:48:03
ofst[ 28]:err_code:0xa0801004, clock:0x1baf102c  2014/09/19 16:02:52
ofst[ 32]:err_code:0xa0801004, clock:0x1bbc2621  2014/09/29 14:16:01
ofst[ 36]:err_code:0xa0801004, clock:0x1bc227e9  2014/10/04 03:37:13
ofst[ 40]:err_code:0xa0801004, clock:0x1c320565  2014/12/28 00:03:49
ofst[ 44]:err_code:0xa0801001, clock:0x1c32d931  2014/12/28 15:07:29
ofst[ 48]:err_code:0xa0801004, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 52]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 56]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 60]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 64]:err_code:0xa0801001, clock:0x1c80ca64  2015/02/25 18:01:08
ofst[ 68]:err_code:0xa0801004, clock:0x1c82604d  2015/02/26 22:53:01
ofst[ 72]:err_code:0xa0801004, clock:0x1c826123  2015/02/26 22:56:35
ofst[ 76]:err_code:0xa0801004, clock:0x1c962726  2015/03/13 22:54:30
ofst[ 80]:err_code:0xa0801004, clock:0x1cfc0ce2  2015/05/30 05:53:38
ofst[ 84]:err_code:0xa0801004, clock:0x1d0f4931  2015/06/13 20:04:01
ofst[ 88]:err_code:0xa0801004, clock:0x1d0f4c84  2015/06/13 20:18:12
ofst[ 92]:err_code:0xa0801004, clock:0x1d0f835d  2015/06/14 00:12:13
ofst[ 96]:err_code:0xa0801004, clock:0x1d7372d6  2015/08/28 19:28:22
ofst[100]:err_code:0xa0801004, clock:0x1db94915  2015/10/20 18:48:53
ofst[104]:err_code:0xa0801001, clock:0x1dba9ce9  2015/10/21 18:58:49
ofst[108]:err_code:0xa0801001, clock:0x1dbbe883  2015/10/22 18:33:39
ofst[112]:err_code:0xa0801001, clock:0x1e6cdc60  2016/03/04 23:53:04
ofst[116]:err_code:0xa0801001, clock:0x1ff560c8  2016/12/27 17:26:32
ofst[120]:err_code:0xa0801004, clock:0x1ff89df8  2016/12/30 04:24:24
ofst[124]:err_code:0xa0801004, clock:0x1ffaf612  2016/12/31 23:04:50
ofst[  0]:err_code:0xa0801001, clock:0x208406da  2017/04/14 22:16:58
ofst[  4]:err_code:0xa0801001, clock:0x2c0668ae  2023/05/28 19:31:58
ofst[  8]:err_code:0xa0801001, clock:0x2c0668c4  2023/05/28 19:32:20
ofst[ 12]:err_code:0xa0801001, clock:0x2c079cc7  2023/05/29 17:26:31
ofst[ 16]:err_code:0xa0801004, clock:0x2c79357a  2023/08/23 21:24:10
ofst[ 20]:err_code:0xa0801001, clock:0x0b488702  2005/12/31 00:02:10
[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)
Press Ctrl+C to exit
>$

I find it strange that a last error with the date 2005/12/31 has been added to the error history, which is quite strange given that the console did not exist on that date. Then in the powerstate sequence the PCI Power (which i have no idea what it is) is OFF.

 

[Nascar1243]

I'll also post here the message i left under the video tutorial about Rip-Felix's syscon. I hope it is correct.
I have a problem after assembling the console. It turns on but the led remains green and i can't see anything in the video(hdmi). I inserted a disk and it took it but if i try to eject it the blue light flashes and makes 3 beeps. Sometimes there is 720x576 video signal but the screen is black. During the assembly phase i broke the lever where the flat cable of the Blu-ray is insert, fixed it by attaching a sticker on it. I leave you the entire sequence of commands bringup, powerstate, errlog, tmp get 0 and tmp get 1, duty get 0.

Microsoft Windows [Versione 10.0.19045.3448]
C:\Users\Pc\Desktop\sysc\ps3syscon-master\ps3syscon-master\Linux>python ps3_syscon_uart_script.py COM3 CXRF
Press Ctrl+C to exit
>$ auth
Auth successful
Press Ctrl+C to exit
>$ becount
becount
Bringup : 2970 times
Shutdown: 1834 times
Power-on: 104day 23hour 29min 08sec
[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
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 1.5.0 (Build ID: 1798,18531, Build Data: 2007-01-10_12:09:26)
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
[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
[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

[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
>$ tmp get 0
tmp get 0
*** Invalid Argument ***
[mullion]$
Press Ctrl+C to exit
>$ tmp get 1
tmp get 1
*** Invalid Argument ***
[mullion]$
Press Ctrl+C to exit
>$ duty get 0
duty get 0
CrntDuty(0x0):20%(0x33)
[mullion]$
Press Ctrl+C to exit
>$ errlog
errlog
ofst[ 24]:err_code:0xffffffff, clock:0x1b9cc1e3  2014/09/05 18:48:03
ofst[ 28]:err_code:0xa0801004, clock:0x1baf102c  2014/09/19 16:02:52
ofst[ 32]:err_code:0xa0801004, clock:0x1bbc2621  2014/09/29 14:16:01
ofst[ 36]:err_code:0xa0801004, clock:0x1bc227e9  2014/10/04 03:37:13
ofst[ 40]:err_code:0xa0801004, clock:0x1c320565  2014/12/28 00:03:49
ofst[ 44]:err_code:0xa0801001, clock:0x1c32d931  2014/12/28 15:07:29
ofst[ 48]:err_code:0xa0801004, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 52]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 56]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 60]:err_code:0xa0902203, clock:0x1c4d9b25  2015/01/17 22:13:57
ofst[ 64]:err_code:0xa0801001, clock:0x1c80ca64  2015/02/25 18:01:08
ofst[ 68]:err_code:0xa0801004, clock:0x1c82604d  2015/02/26 22:53:01
ofst[ 72]:err_code:0xa0801004, clock:0x1c826123  2015/02/26 22:56:35
ofst[ 76]:err_code:0xa0801004, clock:0x1c962726  2015/03/13 22:54:30
ofst[ 80]:err_code:0xa0801004, clock:0x1cfc0ce2  2015/05/30 05:53:38
ofst[ 84]:err_code:0xa0801004, clock:0x1d0f4931  2015/06/13 20:04:01
ofst[ 88]:err_code:0xa0801004, clock:0x1d0f4c84  2015/06/13 20:18:12
ofst[ 92]:err_code:0xa0801004, clock:0x1d0f835d  2015/06/14 00:12:13
ofst[ 96]:err_code:0xa0801004, clock:0x1d7372d6  2015/08/28 19:28:22
ofst[100]:err_code:0xa0801004, clock:0x1db94915  2015/10/20 18:48:53
ofst[104]:err_code:0xa0801001, clock:0x1dba9ce9  2015/10/21 18:58:49
ofst[108]:err_code:0xa0801001, clock:0x1dbbe883  2015/10/22 18:33:39
ofst[112]:err_code:0xa0801001, clock:0x1e6cdc60  2016/03/04 23:53:04
ofst[116]:err_code:0xa0801001, clock:0x1ff560c8  2016/12/27 17:26:32
ofst[120]:err_code:0xa0801004, clock:0x1ff89df8  2016/12/30 04:24:24
ofst[124]:err_code:0xa0801004, clock:0x1ffaf612  2016/12/31 23:04:50
ofst[  0]:err_code:0xa0801001, clock:0x208406da  2017/04/14 22:16:58
ofst[  4]:err_code:0xa0801001, clock:0x2c0668ae  2023/05/28 19:31:58
ofst[  8]:err_code:0xa0801001, clock:0x2c0668c4  2023/05/28 19:32:20
ofst[ 12]:err_code:0xa0801001, clock:0x2c079cc7  2023/05/29 17:26:31
ofst[ 16]:err_code:0xa0801004, clock:0x2c79357a  2023/08/23 21:24:10
ofst[ 20]:err_code:0xa0801001, clock:0x0b488702  2005/12/31 00:02:10
[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)
Press Ctrl+C to exit
>$

I find it strange that a last error with the date 2005/12/31 has been added to the error history, which is quite strange given that the console did not exist on that date. Then in the powerstate sequence the PCI Power (which i have no idea what it is) is OFF.

So the only reason there is one with the date 2005 is likely because the system clock got reset, looking at the error log there isn't anything that looks concerning at all, 1001 is typically improper shutdowns and shouldn't be anything to worry about until it causes a YLOD during use and produces a 1001 code.


Sent from my iPad using Tapatalk

 

[Nator]

So the only reason there is one with the date 2005 is likely because the system clock got reset, looking at the error log there isn't anything that looks concerning at all, 1001 is typically improper shutdowns and shouldn't be anything to worry about until it causes a YLOD during use and produces a 1001 code.
Sent from my iPad using Tapatalk

Maybe the system clock has reset because i have tolot the CMOS battery for days. I get nothing from the errors, i'm just stuck at the solid green light. Even if i try to enter recovery mode, i hear the beep but nothing appears on the screen. I'd say it's worrying.

 

[Nascar1243]

Maybe the system clock has reset because i have tolot the CMOS battery for days. I get nothing from the errors, i'm just stuck at the solid green light. Even if i try to enter recovery mode, i hear the beep but nothing appears on the screen. I'd say it's worrying.

Depending on the model the RSX might be going bad, if it is an A-H model or some of the M models then the RSX might need to be replaced, that or a bga defect under one of the chips


Sent from my iPad using Tapatalk

 

[Nator]

Depending on the model the RSX might be going bad, if it is an A-H model or some of the M models then the RSX might need to be replaced, that or a bga defect under one of the chips

Is it possible for it to happen like this suddenly on a working ps3 just because i changed the thermal paste? and then why if it's a bga problem etc, syscon doesn't detect it?

 

[Nascar1243]

Is it possible for it to happen like this suddenly on a working ps3 just because you changed the thermal paste? and then why if it's a bga problem etc, syscon doesn't detect it?

You may have broken one of the connections that won't generate a YLOD, Syscon only records an error if the bga defect causes the YLOD, GLOD is never logged and only Southbridge logs can tell you what exactly is going on and what causes GLOD, but likely if you were changing paste you could have easily broken a solder ball and thus why you aren't getting video, to verify this you can try adding pressure on the rsx, if that fails then the cell, but the first step is to see if it works on AV or HDMI, it may work on one but not the other


Sent from my iPad using Tapatalk

 

[Nator]

You may have broken one of the connections that won't generate a YLOD, Syscon only records an error if the bga defect causes the YLOD, GLOD is never logged and only Southbridge logs can tell you what exactly is going on and what causes GLOD, but likely if you were changing paste you could have easily broken a solder ball and thus why you aren't getting video, to verify this you can try adding pressure on the rsx, if that fails then the cell, but the first step is to see if it works on AV or HDMI, it may work on one but not the other

Ok i'll get an AV cable so i can proceed in order. How can i get southbridge logs? Does it have anything to do with the writing i got "[INFO]: Connecting to Debug Device (SB UART)" under the syscon bringup command?

 

[Nascar1243]

Ok i'll get an AV cable so i can proceed in order. How can i get southbridge logs? Does it have anything to do with the writing i got "[INFO]: Connecting to Debug Device (SB UART)" under the syscon bringup command?

Someone made a guide somewhere, I forget where it is, but it does involve soldering, but you have to write a code to the syscon (code varies from board to board) to access the southbridge logs first, then you need to solder to the point on the southbridge, then you need to use an app called putty and go to 115200 baud and it should display a full log and what FW its on, again there is a guide but rn I am not sure where on here it is.


Sent from my iPad using Tapatalk

 

[Nator]

You may have broken one of the connections that won't generate a YLOD, Syscon only records an error if the bga defect causes the YLOD, GLOD is never logged and only Southbridge logs can tell you what exactly is going on and what causes GLOD, but likely if you were changing paste you could have easily broken a solder ball and thus why you aren't getting video, to verify this you can try adding pressure on the rsx, if that fails then the cell, but the first step is to see if it works on AV or HDMI, it may work on one but not the other


Sent from my iPad using Tapatalk

by the way, what do you mean by applying pressure on the RSX and CELL?

 

[Nascar1243]

by the way, what do you mean by applying pressure on the RSX and CELL?

Basically you can push on the backside of the clamps or on the chips themselves (recommend just the clamps) to see if you can get video from pressure, may take little pressure, may take more than you'd like, just don't go overkill on the pressure, this would determine if it is bga/bump


Sent from my iPad using Tapatalk