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

RIP-Felix said:
Should be fine.
Click to expand...
ok so how do I apply them I was reading @Naked_Snake1995 post and he mention that processors side one are usually ok and bottom ones should be tested first but mine gives a 1002 error 3003 and 3004 indicating rsx caps on both side and cell on one side. Should I first try piggyback the tantalums on nec first if yes then how can you give a diagram
 
Fallen777 said:
Well if that's a concern I do not know about fats but from cech 2500x to cech 4300x have Sherwood 2 or 3 syscon and use same tmp411 a and b. But question is if I swap a tmp411 a from a cech 3000x kte-001 motherboard with my pqx-001 tmp411a. Would it be successful transplant or not . I am questioning compadibility.what do you say @sandungas @RIP-Felix .
Click to expand...
Just found out after harboring my fat cech k04 dia-002 for 1.5 years it houses a tmp411 A and tmp411 B and @RIP-Felix does RSX 65mm CXD2982GB fall in bumpgate timeline.
 

Attachments

  • IMG_20230111_130448.jpg
    IMG_20230111_130448.jpg
    1.1 MB · Views: 94
  • IMG_20230111_130416.jpg
    IMG_20230111_130416.jpg
    1.1 MB · Views: 117
  • IMG_20230111_130311.jpg
    IMG_20230111_130311.jpg
    1.8 MB · Views: 84
  • IMG_20230111_130448.jpg
    IMG_20230111_130448.jpg
    1.1 MB · Views: 82
Fallen777 said:
ok so how do I apply them I was reading @Naked_Snake1995 post and he mention that processors side one are usually ok and bottom ones should be tested first but mine gives a 1002 error 3003 and 3004 indicating rsx caps on both side and cell on one side. Should I first try piggyback the tantalums on nec first if yes then how can you give a diagram
Click to expand...
3004 is just a more serious version of 1002. it's the same story with 1001/3003. It doesn't tell you anything about which side of the MB the tokens have failed.

Side B is easier to access and remove.
 
RIP-Felix said:
3004 is just a more serious version of 1002. it's the same story with 1001/3003. It doesn't tell you anything about which side of the MB the tokens have failed.

Side B is easier to access and remove.
Click to expand...
alright i 'll try to piggyback first when I declear the msx-001 as scraped if I don't fix the 3010 1701 and 14ff error within the next month got any clues where to poke.
 
Sent my ps3 to transfer 40nm from slim to cecha. Technician delided 40nm, could this be a damaged ram?
Before bittraining fix
BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID

After bittraining fix
BitTraining BE:RRAC:RX1:GLOBAL1:RX_STATUS
0xa0403034

What trace is responsible for this error, i don't know methodology how to trace it, some of the previous post managed to find it, but wasn't clear to me.

Possible solution: reball or reflow?

For R2135, instead of scratching ground pad, i made a shunt to ground pad near bluray wide ribbon connector.
 
mimi said:
Sent my ps3 to transfer 40nm from slim to cecha. Technician delided 40nm, could this be a damaged ram?
Before bittraining fix
BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID

After bittraining fix
BitTraining BE:RRAC:RX1:GLOBAL1:RX_STATUS
0xa0403034

What trace is responsible for this error, i don't know methodology how to trace it, some of the previous post managed to find it, but wasn't clear to me.

Possible solution: reball or reflow?

For R2135, instead of scratching ground pad, i made a shunt to ground pad near bluray wide ribbon connector.
Click to expand...

I did find it! The bit training traces are all on both sides of the space between cell and rsx (and there are some between cell and southbridge). They're really simple, straight short traces. Your issue is less likely to be the trace, and more likely going to be solder joint. Reflow or reball depends on what you want— some people just want a reflow that works long enough to get saves out, and some people want a long term fix, but reballs are expensive. There's been a great many flame wars over the subject….
 
marciolsf said:
I did find it! The bit training traces are all on both sides of the space between cell and rsx (and there are some between cell and southbridge). They're really simple, straight short traces. Your issue is less likely to be the trace, and more likely going to be solder joint. Reflow or reball depends on what you want— some people just want a reflow that works long enough to get saves out, and some people want a long term fix, but reballs are expensive. There's been a great many flame wars over the subject….
Click to expand...

Reflow is tempting, because of reheating cycles rudeced compared to reball, but with reball could inspect if there are any lifted pads.
Is there a tutorial to lear to trace error like: BE:RRAC:RX1:GLOBAL1:RX_STATUS to a physical trace?
Also, could you can tell which BGA point is responsible for this error, so a technician would inspect it.

I have seen your image in previous post. with highlighted traces for RX0 if i remember correctly.

Thanks!
 
mimi said:
Reflow is tempting, because of reheating cycles rudeced compared to reball, but with reball could inspect if there are any lifted pads.
Is there a tutorial to lear to trace error like: BE:RRAC:RX1:GLOBAL1:RX_STATUS to a physical trace?
Also, could you can tell which BGA point is responsible for this error, so a technician would inspect it.

I have seen your image in previous post. with highlighted traces for RX0 if i remember correctly.

Thanks!
Click to expand...
I don't think there's a tutorial, just discussions between Felix and I. The RX0, RX1, etc, are sequential (and there's 4 lanes, so 0-3), so it shouldn't be hard to figure out which trace leads to which pad. If you already found my screenshot, that's a great starting point.

As far as which side (cell/be or rsx), I think your particular error indicates that cell isn't receiving from RX1, which would indicate a failure on receiving from tx1 on the rsx side. In other words, tx1 on rsx side is bad.

All that being said, I would take anything I say with a grain of salt, my memory is famously bad and it's been a while since I last thought about this.
 
RIP-Felix said:
Can you explain? This should be 10k to GND. And a long wire could cause issues.
Click to expand...

I used thin insulated winding wire. It measures slightly below 10K, on and off board.
I made crude illustration with drawn resistor, because i sent board for reflowing, maybe it will fix it. Ace repair had similar errors with aliexpress chips, crushing my hopes. 40nm was harvested from working slim.

https://imgbox.com/GNmIjTuf
 
Last edited:
RIP-Felix said:
0xb0002001 (FATAL) XDR Link not initilized.

I'm getting the same error on a console at the moment. I shelved it until a thermal camera arrives, because I'm operating under the assumption that an XDR memory module has failed. When booting it should be the only one that doesn't heat up. I'll first try replacing that, but if that doesn't work it could be the CPU's BGA pads from the XDR.

ACE Console repairs had this happen to him recently. In his case it looked like drop damage, because the CPU pads were completly torn.
Click to expand...

Hi [mention]RIP-Felix [/mention]
Did you get your thermal camera?
Have you tested those Shelved consoles with the XDR Link errors?
 
Hey guys. Looking for some quick pointers on a CECHA with the infamous YLOD.

Im in Europe so these are pretty rare as we only got the CECHC models. Anyways syscon is currently showing 2 different codes.

A0093003 and most predominantly A0A02031.
NEC/TOKEN have been replaced as the A0093003 was the most frequent error and now it appears to be 2031. Is it worth replacing the temperature sensor or is it likely a dead RSX chip?

I'm typing on mobile so not sure how to attach the log.

Thanks guys.
 
tomsava said:
Hey guys. Looking for some quick pointers on a CECHA with the infamous YLOD.

Im in Europe so these are pretty rare as we only got the CECHC models. Anyways syscon is currently showing 2 different codes.

A0093003 and most predominantly A0A02031.
NEC/TOKEN have been replaced as the A0093003 was the most frequent error and now it appears to be 2031. Is it worth replacing the temperature sensor or is it likely a dead RSX chip?

I'm typing on mobile so not sure how to attach the log.

Thanks guys.
Click to expand...
I have repaired a CECHH model with a0a02031 errors. And replacing thermal sensor IC does fix the console.

My syscon logs for reference:
>$ bringup
bringup
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[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
[ERROR]: 0xa0502131
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 2.1.0 (Build ID: 2709,28222, Build Data: 2007-12-05_13:32:28)
Copyright(C) 2007 Sony Computer Entertainment Inc.All Rights Reserved.
[SERV SETCFG] XDR (CH0,CH1) ASSERT
[SERV SETCFG] XDR (CH0,CH1) DEASSERT
[SERV NVS] READ CMD
[ERROR]: 0xa0802031
[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 NVS] READ CMD
[SERV THERM] NOTIFY_MODE CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
>$
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[mullion]$ [ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SERV NVS] READ CMD
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[mullion]$
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[mullion]$ [ERROR]: 0xa0802131
>$
[mullion]$
>$
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802031
[ERROR]: 0xa0802031
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[mullion]$ [ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
>$
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[ERROR]: 0xa0802131
[SSM] *** Unrecoverable FATAL ERROR by thermal***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0802131
[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff

So if you see multiple 2031 or 2131 spit out when doing bringup, that's likely is the thermal sensor error. By the way, thermal sensor is powered even in standby mode(red led on). This makes it easy to probe to see if anything obviously wrong without heatsink or fan.
 
Dariush Aghaee said:
Hi [mention]RIP-Felix [/mention]
Did you get your thermal camera?
Have you tested those Shelved consoles with the XDR Link errors?
Click to expand...

Yes I did. All 4 XDR light up and so does the CPU. Unfortunately that doesn't help me much. That could mean the issue lies under the CPU, BGA to XDR is broken (IDK if console was dropped or not. Don't think @squeept said). He said it was a warranty return IIRC, which means it was working when he sold it to begin with? So maybe in shipping the banging broke a BGA. IDK, I haven't had time to investigate further. If it were an XDR module that would be fairly quick to replace. But I don't see any obvious reason to suspect them. It's looking at a CPU reball at least, and possibly full XDR replacement too.

I'm procrastinating!
 
Hi, can anyone help (new with some error codes of syscon)
I got a PS3 fat Cechh01 (Dia-001), I made syscon read today, I got 2030-2031-2033 (thermal SB, RSX and Cell BE), what does that mean, what I need to check or replace.
And a another thing is my PS3 when I plug in after some seconds automatic power on but I can't turn it on by pushing the sensors, help
 
SkewbTf2 said:
Hi, can anyone help (new with some error codes of syscon)
I got a PS3 fat Cechh01 (Dia-001), I made syscon read today, I got 2030-2031-2033 (thermal SB, RSX and Cell BE), what does that mean, what I need to check or replace.
And a another thing is my PS3 when I plug in after some seconds automatic power on but I can't turn it on by pushing the sensors, help
Click to expand...
See my previous post: https://www.psx-place.com/threads/f...nd-error-reporting.30100/page-163#post-353795

But 3 thermal sensor all faulty at the same time seems impossible. There might be something else going on.

You mentioned your machine automatically turns on. Phat consoles uses capacitive sensor to turn on, and that can probably mean your metal pin is rusty or touch sensor IC is faulty, check the touch sensor pin and the bottom metal part from the cover case to see if it's rusty. Rust like this can be filed away and easy to deal with. I have seen too many dusty and rusty CECHH and CECHK. Humidity can damage the machine badly so better clean the board first if it is the case.
 
You must log in or register to reply here.

Similar threads

Back
Top