PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

In first tested board before uart error era I've also thought so. Reading dump normal, took out another cpu, syscon, nor ported to the board with problems went fine.
This is quite quick then take measurements hours/days.
There are two more unsorted 1802 and 3010 as same situation (didn't test too much). Probably @botakompong can find them in boards and reports more about them.
They seem to be in communication line, I never sorted this with reball and probably was that type of microshortage.
Aha, yeah but if you change CPU and its married set... (Including NOR flash)
You are also changing the NOR and the data inside it. Which could be the real problem (bricked because somebody tried to do CFW on 3000)
Do you think it's possible too?
 
Aha, yeah but if you change CPU and its married set... (Including NOR flash)
You are also changing the NOR and the data inside it. Which could be the real problem (bricked because somebody tried to do CFW on 3000)
Do you think it's possible too?
Yes can be haven't got this situation yet.
It could be that situation but I tested those units with 5fff isn't this case of brick.
@botakompong would you like check but don't post data inside nor, just check dump of nor memory?
 
Yes can be haven't got this situation yet.
It could be that situation but I tested those units with 5fff isn't this case of brick.
@botakompong would you like check but don't post data inside nor, just check dump of nor memory?
Used dump_checker
Bad sector in ros0 and ros1 only
Indeed the 805FFF problem is related to the relationship between cellbe and nor, maybe what victor cased is different from my case, but from checking using an analog tester it can be seen that it is included in rules5
tomorrow at the store, I will take a photo of the results of checking the dump using the dump-checker
IMG_20210615_122141.jpg
 
Last edited:
Oh yeah, before I forget, I want to ask you this, regarding the relationship between cellbe and rsx
IMG_20210614_160319.jpg
It seems that every time it resets it immediately records 8 or 9 errors
If from the analog testes it looks different between 8 errors or 9 errors from the slightly different movement of the needle (rules3 end)
Is it true that 1 x reset can occur 8/9 error?
 
Oh yeah, before I forget, I want to ask you this, regarding the relationship between cellbe and rsx
View attachment 33725
It seems that every time it resets it immediately records 8 or 9 errors
If from the analog testes it looks different between 8 errors or 9 errors from the slightly different movement of the needle (rules3 end)
Is it true that 1 x reset can occur 8/9 error?
Yes, this can happen sometimes with some problems. I had up to 11 at once.(10x 20 2120 + 21 3013)

Multiple error codes can appear from a single YLOD.
All those errors have something to do with RSX. Normally is just 3034/44xx What kind of RSX you have there with so many different errors?
bringup must be interesting.

Haha. (Not funny)
 
Oh yeah, before I forget, I want to ask you this, regarding the relationship between cellbe and rsx
View attachment 33725
It seems that every time it resets it immediately records 8 or 9 errors
If from the analog testes it looks different between 8 errors or 9 errors from the slightly different movement of the needle (rules3 end)
Is it true that 1 x reset can occur 8/9 error?
It seems that specific reball problem and second one unsorted which ic AV/Hdmi. Is not in syscon errors pdf but M4j0r suggest to exchange one of these, I exchanged both and superslim started and running fine. I had only 2024 not together with 3034/44xx
 
Yes, this can happen sometimes with some problems. I had up to 11 at once.(10x 20 2120 + 21 3013)

Multiple error codes can appear from a single YLOD.
All those errors have something to do with RSX. Normally is just 3034/44xx What kind of RSX you have there with so many different errors?
bringup must be interesting.

Haha. (Not funny)
Rsx 530xx, it seems for the damage character to rules3 end, maybe like that, later I will make sure from several different ps3, if from rules3 (initial) I read like this
IMG_20210614_154440.jpg
From superslim rsx 28nm
 
It's interesting you mention this.
He's saying this is a 3000 slim that somebody tried to install cfw on.
I always find it hard to believe that CPU is dead. And I also don't really trusted the ohms so much, as long as it's not short. I have working chips with low ohms, cool running too.

But I believe you of course. I don't really know much about slims anyway.
Maybe can mean more things?
That's in situ (in place). You need to read ohms off the board to know the state of the chip. Ohm test on board is dependent on more components having a solid connection (BGA, Tokins, MLCC bypass caps etc.). This is why the ohms often raise after a reball/reflow and thorough cleaning. Ohm test on the board is a qualitative test (may be useful, taken with a grain of salt). Ohm test off the board is a quantitative test (can diagnose a bad chip).
 
Rsx 530xx, it seems for the damage character to rules3 end, maybe like that, later I will make sure from several different ps3, if from rules3 (initial) I read like this
View attachment 33728
From superslim rsx 28nm

Wow, surprised even the newest 28nm can fail like this. I guess Sony never had a fail-proof production line of PS3s. Does this mean not one model is fully safe from RSX troubles? I don't remember this type of thing happening with PS2s. Apart from laser replacements, those seemed invincible.
 
Last edited:
That's in situ (in place). You need to read ohms off the board to know the state of the chip. Ohm test on board is dependent on more components having a solid connection (BGA, Tokins, MLCC bypass caps etc.). This is why the ohms often raise after a reball/reflow and thorough cleaning. Ohm test on the board is a qualitative test (may be useful, taken with a grain of salt). Ohm test off the board is a quantitative test (can diagnose a bad chip).
I agree, checking ohms is one of the things I often do besides checking the input voltage, this check is related to the input voltage to all ICs, if the ohms are not in accordance with normal, the input voltage will be disturbed, this ohm abnormality, then look for the cause, it could be part the power circuit or the ic itself
 
It's interesting you mention this.
He's saying this is a 3000 slim that somebody tried to install cfw on.
I always find it hard to believe that CPU is dead. And I also don't really trusted the ohms so much, as long as it's not short. I have working chips with low ohms, cool running too.

But I believe you of course. I don't really know much about slims anyway.
Maybe can mean more things?
Yes, I agree, I also don't really care about ohms for certain areas, such as the tantalum ohm area or nec tokin, I often find ps3s that still function normally with a size of 1.2 ohms, especially for the cxd2971 which on average is smaller than the rsx. other. Some of the rsx cxd530xx are also small in ohm size but if it is 1 ohm or below it is usually bad, then for ohm the input voltage R5 is at least 60ohm size, I see it can still work, if it is below 60ohm it is not working well, like the ps3 will go blank or hang (dyn -001), the point is that ohm measurement is important, it has normal limits, from ohm measurement we can trace the problem part
 
Yes, I agree, I also don't really care about ohms for certain areas, such as the tantalum ohm area or nec tokin, I often find ps3s that still function normally with a size of 1.2 ohms, especially for the cxd2971 which on average is smaller than the rsx. other. Some of the rsx cxd530xx are also small in ohm size but if it is 1 ohm or below it is usually bad, then for ohm the input voltage R5 is at least 60ohm size, I see it can still work, if it is below 60ohm it is not working well, like the ps3 will go blank or hang (dyn -001), the point is that ohm measurement is important, it has normal limits, from ohm measurement we can trace the problem part
Yes. After all this resistance would only be the area of the processor "core" to ground. There are many other things that can go wrong. 5 voltages not just 1.
And some normal heat can make everything change too!
Then there's the famous data points that can also be shorted to ground or to each other.
It's much more complex than a single number.

So it's significant of course but can only give an idea. In my opinion if core is more than 1 ohm it can be fine. I've seen 0.9 ohm RSX work fine and run cool. Then I measured again and was 1.2ohm.
And also saw 3.2 and 3.1ohm with problems...

Of course I also found 0.3 ohm RSX core... and sure 0.3 means you should not even try to power on.
But was because somebody totally destroyed it with heat gun and corrosive flux. Looked like a hamburger with lettuce and all.
 

Attachments

  • IMG_20210510_140710~2.jpg
    IMG_20210510_140710~2.jpg
    2.5 MB · Views: 446
  • IMG_20210423_191342~2.jpg
    IMG_20210423_191342~2.jpg
    2.3 MB · Views: 82
Last edited:
Can syscon also be able to record errors that do not cause ylod/lost power?, I think I found that, but I will try again tomorrow to make sure, especially the connection between cellbe and cellbe ram, it seems there is damage to the cellbe, tomorrow I will check
Looks like I have to move to the syscon forum, where can I enter?
 
Can syscon also be able to record errors that do not cause ylod/lost power?, I think I found that, but I will try again tomorrow to make sure, especially the connection between cellbe and cellbe ram, it seems there is damage to the cellbe, tomorrow I will check
Looks like I have to move to the syscon forum, where can I enter?
Yes, we have seen for example when there is a problem between CELL BE and XDR RAM, the syscon will detect an error (XDR init failed). Even if it's not a YLOD. (GLOD).
Can happen when people destroy XDR RAM traces on CELL substrate trying to remove heat spreader for example.
 
Yes, we have seen for example when there is a problem between CELL BE and XDR RAM, the syscon will detect an error (XDR init failed). Even if it's not a YLOD. (GLOD).
Can happen when people destroy XDR RAM traces on CELL substrate trying to remove heat spreader for example.
If that means it's true, I'll try to fix it, I'll share the results later, still remind me of my question about 8-9 errors that occur in 1x reset (lost power), after reball cellbe turns blank, ps3 JTP-001
ERRLOG syscon
IMG_20210615_124636.jpg
 
If that means it's true, I'll try to fix it, I'll share the results later, still remind me of my question about 8-9 errors that occur in 1x reset (lost power), after reball cellbe turns blank, ps3 JTP-001
ERRLOG syscon
View attachment 33747
This is what I meant about AV/Hdmi ic 2024 only, when I have it on superslim. Just try exchange both AV/Hdmi ic and report back please. As you going to investigate those ic's you going to probably find missing signals between them (never had time to investigate)
 
This is what I meant about AV/Hdmi ic 2024 only, when I have it on superslim. Just try exchange both AV/Hdmi ic and report back please. As you going to investigate those ic's you going to probably find missing signals between them (never had time to investigate)
Actually it's related to cellbe and cellbe RAM, usually from cellbe RAM input power (12 ohms) which is not correct, if not from cellbe tin that is not good, cellbe reball is usually enough to fix it, not related to hdmi ic or av ic , the symptoms usually cause, every time the reset is held, you can't get 1 beep, the hdd indicator light doesn't flash, it's included in the rules4 category, but in the case I'm dealing with now it's worse, maybe because the cellbe is damaged or the RAM cellbe is damaged.
 
Back
Top