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

[vyktormvmpay25]

Unfortunately resistance there still unchanged after removing ic6006.
About 2.2 Kohm
Should be rising to about 50 Kohm.

Maybe I'll try replacing with another one from another board. But I don't think it will work.


Well in my case the board looks untouched. And the power draw was only about 1 watt more than normal. So obviously nothing mega hot.

Remarry process will be a PITA. Is something very unclear to me. Collecting all info around psdevwiki, here on forums and still not good enough to dump a good working syscon full capacity. Probably someone will do a full tutorial with it or not.
edit something that i didnt test to apply pach for dump and capture data right when ps3 it starts

 

[hrist]

Hi all, first post here but long time lurker.

Got an original japanese CECHA00 that got an instant YLOD (Green light, then yellow light, three beets and blinking red light) after i did the eraser mod on the CPU (maybe the added pressure messed up a component or something).

Looking for advice for these errors:

===================================
ERR 00: FFFFFFFF Magic
ERR 01: 00000000 A0101001 FFFFFFFF
ERR 02: 00000000 A0101001 FFFFFFFF
ERR 03: 00000000 A0101001 FFFFFFFF
ERR 04: 00000000 A0101001 FFFFFFFF
ERR 05: 00000000 A0101001 FFFFFFFF
ERR 06: 00000000 A0101001 FFFFFFFF
ERR 07: 00000000 A0101001 FFFFFFFF
ERR 08: 00000000 A0101001 FFFFFFFF
ERR 09: 00000000 A0313031 FFFFFFFF
ERR 10: 00000000 A0101001 FFFFFFFF
ERR 11: 00000000 A0101001 FFFFFFFF
ERR 12: 00000000 A0902120 FFFFFFFF
ERR 13: 00000000 A0313031 FFFFFFFF
ERR 14: 00000000 A0902120 FFFFFFFF
ERR 15: 00000000 A0313031 FFFFFFFF
ERR 16: 00000000 A0101001 FFFFFFFF
ERR 17: 00000000 A0313031 FFFFFFFF
ERR 18: 00000000 A0101001 FFFFFFFF
ERR 19: 00000000 A0101001 FFFFFFFF
===================================

Thanks in advance!

 

[DeadEnd]

I have an untouched COK 001 board suspicious of SYSCON problems. No red light. 5v Ok. 3.3v OK but 1.8v is 3+v! Resistance there is about 2kohms instead of rising to about 50k

Total power draw is about 3w instead of the normal 1.8w from the wall.

Anybody has seen something similar?

I guess worst case involves replacing Syscon, but then also CPU and NAND?
Because if it's actually a bad Syscon, then that's the only way right?

If the Syscon itself is actually OK, you think the 1.8v regulator could be causing the issue? Even if it were, the overvoltage is worrying

Not exactly the same as in your case, but when I had trouble with 3.3v line on RXD or TXD (was getting 1.6v), it was related to one resistor next to syscon and quartz. It looked like it was soldered ,but actually it was loose on one end. And there was no way to see without microscope. But the reason this happened was lack of care when lifting syscon ( I apparently "knocked" that resistor slightly out of phase). The symptom was the same though, no red light.

 

[hrist]

Hi all, first post here but long time lurker.

Got an original japanese CECHA00 that got an instant YLOD (Green light, then yellow light, three beets and blinking red light) after i did the eraser mod on the CPU (maybe the added pressure messed up a component or something).

Looking for advice for these errors:

===================================
ERR 00: FFFFFFFF Magic
ERR 01: 00000000 A0101001 FFFFFFFF
ERR 02: 00000000 A0101001 FFFFFFFF
ERR 03: 00000000 A0101001 FFFFFFFF
ERR 04: 00000000 A0101001 FFFFFFFF
ERR 05: 00000000 A0101001 FFFFFFFF
ERR 06: 00000000 A0101001 FFFFFFFF
ERR 07: 00000000 A0101001 FFFFFFFF
ERR 08: 00000000 A0101001 FFFFFFFF
ERR 09: 00000000 A0313031 FFFFFFFF
ERR 10: 00000000 A0101001 FFFFFFFF
ERR 11: 00000000 A0101001 FFFFFFFF
ERR 12: 00000000 A0902120 FFFFFFFF
ERR 13: 00000000 A0313031 FFFFFFFF
ERR 14: 00000000 A0902120 FFFFFFFF
ERR 15: 00000000 A0313031 FFFFFFFF
ERR 16: 00000000 A0101001 FFFFFFFF
ERR 17: 00000000 A0313031 FFFFFFFF
ERR 18: 00000000 A0101001 FFFFFFFF
ERR 19: 00000000 A0101001 FFFFFFFF
===================================

Thanks in advance!

Did the steps to get into internal mode:

Spoiler: Bringup

> 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] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0101001
[SSM] *** Power Fail BE ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
> bestat
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
bestat
(Error State) (Power Fail)
[mullion]$
> shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

Spoiler: errlog

> errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xa0101001, clock:0xffffffff
ofst[ 12]:err_code:0xa0313031, clock:0xffffffff
ofst[ 16]:err_code:0xa0902120, clock:0xffffffff
ofst[ 20]:err_code:0xa0313031, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0101001, clock:0xffffffff
ofst[ 32]:err_code:0xa0101001, clock:0xffffffff
ofst[ 36]:err_code:0xa0313031, clock:0xffffffff
ofst[ 40]:err_code:0xa0313031, clock:0xffffffff
ofst[ 44]:err_code:0xa0101001, clock:0xffffffff
ofst[ 48]:err_code:0xa0313031, clock:0xffffffff
ofst[ 52]:err_code:0xa0313031, clock:0xffffffff
ofst[ 56]:err_code:0xa0313031, clock:0xffffffff
ofst[ 60]:err_code:0xa0313031, clock:0xffffffff
ofst[ 64]:err_code:0xa0101001, clock:0xffffffff
ofst[ 68]:err_code:0xa0101001, clock:0xffffffff
ofst[ 72]:err_code:0xa0101001, clock:0xffffffff
ofst[ 76]:err_code:0xa0101001, clock:0xffffffff
ofst[ 80]:err_code:0xa0101001, clock:0xffffffff
ofst[ 84]:err_code:0xa0101001, clock:0xffffffff
ofst[ 88]:err_code:0xa0101001, clock:0xffffffff
ofst[ 92]:err_code:0xa0101001, clock:0xffffffff
ofst[ 96]:err_code:0xa0101001, clock:0xffffffff
ofst[100]:err_code:0xa0101001, clock:0xffffffff
ofst[104]:err_code:0xa0101001, clock:0xffffffff
ofst[108]:err_code:0xa0101001, clock:0xffffffff
ofst[112]:err_code:0xa0101001, clock:0xffffffff
ofst[116]:err_code:0xa0101001, clock:0xffffffff
ofst[120]:err_code:0xa0101001, clock:0xffffffff
ofst[124]:err_code:0xa0101001, clock:0xffffffff
ofst[ 0]:err_code:0xa0101001, clock:0xffffffff

So the errors are mainly a0101001 then a0313031 and a0902120.
I was almost ready to try a reflow before finding this Syscon post, but know i have doubts as the errors seem to be more low-level/power related.
As i stated the YLOD was caused after i did the eraser mod on the CPU, does it made sense it could have lost contact on a power related pin on the BGA and does need a reflow?

 

[RIP-Felix]

Did the steps to get into internal mode:

Spoiler: Bringup

> 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] fatalreq delayed.
[SSM] state: 0101 -> 0201
[POWSEQ] AV Backend Setup
[ERROR]: 0xa0101001
[SSM] *** Power Fail BE ***
[SSM] state: 0201 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
> bestat
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
bestat
(Error State) (Power Fail)
[mullion]$
> shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)

Spoiler: errlog

> errlog
errlog
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
ofst[ 8]:err_code:0xa0101001, clock:0xffffffff
ofst[ 12]:err_code:0xa0313031, clock:0xffffffff
ofst[ 16]:err_code:0xa0902120, clock:0xffffffff
ofst[ 20]:err_code:0xa0313031, clock:0xffffffff
ofst[ 24]:err_code:0xa0902120, clock:0xffffffff
ofst[ 28]:err_code:0xa0101001, clock:0xffffffff
ofst[ 32]:err_code:0xa0101001, clock:0xffffffff
ofst[ 36]:err_code:0xa0313031, clock:0xffffffff
ofst[ 40]:err_code:0xa0313031, clock:0xffffffff
ofst[ 44]:err_code:0xa0101001, clock:0xffffffff
ofst[ 48]:err_code:0xa0313031, clock:0xffffffff
ofst[ 52]:err_code:0xa0313031, clock:0xffffffff
ofst[ 56]:err_code:0xa0313031, clock:0xffffffff
ofst[ 60]:err_code:0xa0313031, clock:0xffffffff
ofst[ 64]:err_code:0xa0101001, clock:0xffffffff
ofst[ 68]:err_code:0xa0101001, clock:0xffffffff
ofst[ 72]:err_code:0xa0101001, clock:0xffffffff
ofst[ 76]:err_code:0xa0101001, clock:0xffffffff
ofst[ 80]:err_code:0xa0101001, clock:0xffffffff
ofst[ 84]:err_code:0xa0101001, clock:0xffffffff
ofst[ 88]:err_code:0xa0101001, clock:0xffffffff
ofst[ 92]:err_code:0xa0101001, clock:0xffffffff
ofst[ 96]:err_code:0xa0101001, clock:0xffffffff
ofst[100]:err_code:0xa0101001, clock:0xffffffff
ofst[104]:err_code:0xa0101001, clock:0xffffffff
ofst[108]:err_code:0xa0101001, clock:0xffffffff
ofst[112]:err_code:0xa0101001, clock:0xffffffff
ofst[116]:err_code:0xa0101001, clock:0xffffffff
ofst[120]:err_code:0xa0101001, clock:0xffffffff
ofst[124]:err_code:0xa0101001, clock:0xffffffff
ofst[ 0]:err_code:0xa0101001, clock:0xffffffff

Model?
Time from PWR to YLOD?


So the errors are mainly a0101001 then a0313031 and a0902120.
I was almost ready to try a reflow before finding this Syscon post, but know i have doubts as the errors seem to be more low-level/power related.
As i stated the YLOD was caused after i did the eraser mod on the CPU, does it made sense it could have lost contact on a power related pin on the BGA and does need a reflow?

When you say "eraser mod" do you mean you put a foreign object into the hole in the MB under the CPU?

If so, there are a bunch of important ceramic capacitors that decouple noise on the CPU. They could very well cause a BE PWR fail if they were damaged. Rubber shouldn't be conductive unless it was used to erase graphite from a pencil. So if you used a "used" eraser it could have shorted. I would try removing the eraser and clean. While you're in there check to see if the die is cracked! Perhaps the added pressure damaged the die. If the caps are all intact and die looks fine, I would test to see if the problem persists. If it does, I would try reflowing the CPU. You could try reflowing just the MLCC's, but a full CPU reflow will eliminate more possibilities and rework cycles. Just do it once (the right way) and eliminate the BGA, MLCC' Joints, etc. all at once.

 

[hrist]

When you say "eraser mod" do you mean you put a foreign object into the hole in the MB under the CPU?

If so, there are a bunch of important ceramic capacitors that decouple noise on the CPU. They could very well cause a BE PWR fail if they were damaged. Rubber shouldn't be conductive unless it was used to erase graphite from a pencil. So if you used a "used" eraser it could have shorted. I would try removing the eraser and clean. While you're in there check to see if the die is cracked! Perhaps the added pressure damaged the die. If the caps are all intact and die looks fine, I would test to see if the problem persists. If it does, I would try reflowing the CPU. You could try reflowing just the MLCC's, but a full CPU reflow will eliminate more possibilities and rework cycles. Just do it once (the right way) and eliminate the BGA, MLCC' Joints, etc. all at once.

Yeah. Used a new, cuttend eraser following Naked Snake1995's guide
I will try to reflow tomorrow, thank you!

 

[RIP-Felix]

I will try to reflow tomorrow, thank you!

Hold your horses there young wiper snapper. Don't thank me yet. I hope you carefully consider how you go about a reflow before attempting it. Please don't use a heat gun! Please reflow responsible! If you reflow at all! Here's my ghetto setup, but it does provide consistent results with practice and is reball capable if one is experienced enough. I'm not quite there yet.

Did you clean? Did you delid and inspect the die, like I told you to? A reflow should be the last thing you try! And only using the proper equipment. I don't want to assume you daon't have the right equipment, but most people mangle and ruin their console following that Ifixit guide on youtube! Ridiculously terrible advice.

On the subject of the eraser mod. Did you follow his guide because you don't want to delid? The reason I ask is because that's a pis poor way to to achieve the same temps you can by deliding. It's easy with the right tool (depending on your console). Also it seems like a bad idea, because it changes the way the chip was engineered to thermal cycle. Who knows what effect that can have on an already fragile BGA? Well, you might...I guess. But then again your BGA might have been on the edge of death anyway.

 

[hrist]

Hold your horses there young wiper snapper.

Woah, your ghetto setup is definitely something, i don't have dedicated gear at all for this kind of setup like you do.

Please don't use a heat gun!

What are you using instead, do you have a dedicated BGA heater or something?

No, still haven't touched the console I'll review everything today after work, will clean and inspect everything beforehand. Will definitelly leave a reflow as the last option.

I already delid the RSX and CELL before doing the eraser mod and did it because "why not" and it looked harmless. Already saw some ppl using ice cream sticks in the past.

Regarding a reflow, i never did one before. I do have a heat gun an infrared thermometer, no-clean flux and a syringe to apply already. If i try a reflow will definitely follow your advice of using thermal tape and covering the pcb with foil.

 

[hrist]

Just opened and checked the board. Can't see anything wrong with the naked eye (there are some dots painted with a marker, console had the original seal though).

Spoiler: Front

Spoiler: Bottom

 

[Pacorretaco]

Remarry process will be a PITA. Is something very unclear to me. Collecting all info around psdevwiki, here on forums and still not good enough to dump a good working syscon full capacity. Probably someone will do a full tutorial with it or not.
edit something that i didnt test to apply pach for dump and capture data right when ps3 it starts

Hmm it looks like the worst case yeah...
I also removed nearby capacitor but the resistance still didn't change. About 2.2k ohms instead of rising to 50k.
After that it seems like the 1.8v line is going directly to the hidden internal layers of the board. Probably to the SYSCON chip.

Just for curiosity I also tried replacing the suspicious 1.8v regulator and the capacitor with another one from another board. And now the voltage is correct 1.8v instead of abnormal 3+v.
Total system standby power draw about the normal 1.5v now. It was ~3W before.

However it still not working of course.
Can't think of anything else to try, looks like SYSCON itself is bad. Probably the ic6006 was guilty but the overvoltage caused permanent damage to Syscon

 

[vyktormvmpay25]

Hmm it looks like the worst case yeah...
I also removed nearby capacitor but the resistance still didn't change. About 2.2k ohms instead of rising to 50k.
After that it seems like the 1.8v line is going directly to the hidden internal layers of the board. Probably to the SYSCON chip.

Just for curiosity I also tried replacing the suspicious 1.8v regulator and the capacitor with another one from another board. And now the voltage is correct 1.8v instead of abnormal 3+v.
Total system standby power draw about the normal 1.5v now. It was ~3W before.

However it still not working of course.
Can't think of anything else to try, looks like SYSCON itself is bad. Probably the ic6006 was guilty but the overvoltage caused permanent damage to Syscon

Does this board do any kind of sound when power is pressed? If can be something that is directly tied to syscon killing his power, or have you tried with another front power board? Not very often syscon found dead.
By now myself didn't got any dead syscon and we have many fluctuations on main power 210 ~255. But it should give any beep only with 5v cable only. There is something else bad there. Or a simple test swap with another syscon from a scrap, it should stay on standby at least.
Or look at schematic and start testing /swapping diodes, transistors or ic's tied to it. At page 21 on pdf. Now there are many possible cases faster for me will be to test an scrap one.
An possible would be thermal ic from cpu or rsx or even SB. Its quite complex problem.

 

[Pacorretaco]

Does this board do any kind of sound when power is pressed? If can be something that is directly tied to syscon killing his power, or have you tried with another front power board? Not very often syscon found dead.
By now myself didn't got any dead syscon and we have many fluctuations on main power 210 ~255. But it should give any beep only with 5v cable only. There is something else bad there. Or a simple test swap with another syscon from a scrap, it should stay on standby at least.
Or look at schematic and start testing /swapping diodes, transistors or ic's tied to it. At page 21 on pdf. Now there are many possible cases faster for me will be to test an scrap one.
An possible would be thermal ic from cpu or rsx or even SB. Its quite complex problem.

No, no sound at all and the button daughterboard is OK. Actually there is 3.3v on the eject and power buttons but no response when manually shorted the pads in the big board to ground.
I think the power issue is solved now, but SYSCON is not responding because it got damaged by overvoltage perhaps

Yes next step is to remove and replace SYSCON chip to see if at least get standby light to confirm the problem. Then try remarry or... replace CPU and NANDs as well...
But I don't think I'm ready for that kind of adventure yet.
In theory any Mullion Syscon should work yes? Even from SEM board for example? Or at least COK 002?
Or all needs to be exact same from COK 001?

I thought there was no more suspicious components because the 1.8v line is going directly to the internal board layers and then to the SySCON... but I'll check again.
Edit: I've checked again and yes the manual only shows 6 more capacitors under Syscon and then the Syscon. But nothing more. I checked all those small capacitors and they all have the correct 1.8v. So really I think there's nothing else. Syscon there should have 50k ohms not 2.2 k. Probably something is shorted inside Syscon or something.

 

[vyktormvmpay25]

No, no sound at all and the button daughterboard is OK. Actually there is 3.3v on the eject and power buttons but no response when manually shorted the pads in the big board to ground.
I think the power issue is solved now, but SYSCON is not responding because it got damaged by overvoltage perhaps

Yes next step is to remove and replace SYSCON chip to see if at least get standby light to confirm the problem. Then try remarry or... replace CPU and NANDs as well...
But I don't think I'm ready for that kind of adventure yet.
In theory any Mullion Syscon should work yes? Even from SEM board for example? Or at least COK 002?
Or all needs to be exact same from COK 001?

I thought there was no more suspicious components because the 1.8v line is going directly to the internal board layers and then to the SySCON... but I'll check again.

We been advised that mullion syscon can be remarried so it means they can work. At least on hardware side they should work. Now thinking at rest of parts that on Sem001 board aren't (ps2 hardware emulator).
Test it just to see if is board or syscon ic for the moment.

 

[WhatATopic]

I accidentally pulled the Rx pad off. Is there an alternative point I can use or am I screwed?

I forgot to say the board is a COK-001

 

[RIP-Felix]

What are you using instead, do you have a dedicated BGA heater or something?

It's a cheap hot air station, but allows you to manually control the temperatures easier than a hot air gun. I got a 45x45mm BGA nozzle for it and a swing arm to hold it in place above the chip. This way I can be hands free to nudge the chip the moment it flows. The real key is the IR heat plate underneath. It's what keeps the board from warping and allows the chip to flow properly. Highly recommended for lots of soldering projects where there is a thick ground plane.

Regarding a reflow, i never did one before. I do have a heat gun an infrared thermometer, no-clean flux and a syringe to apply already. If i try a reflow will definitely follow your advice of using thermal tape and covering the pcb with foil.

IR thermometer won't be much help. You can't monitor both bottom and topside temps at the same time and it's hard to know exactly where the thermometer is even reading temps from (the laser is inaccurate and it gets reflected by aluminum anyway). I suggest you read my posts about reflowing/replacing the RSX on PS3#8. I explain what I'm doing and why, so that you can get a sense of the purpose of each piece of equipment.

 

[hrist]

IR thermometer won't be much help. You can't monitor both bottom and topside temps at the same time and it's hard to know exactly where the thermometer is even reading temps from (the laser is inaccurate and it gets reflected by aluminum anyway).

Thanks for the links and insights! Really considering getting some of the stuff or just looking for a reliable place to do the job for me. One doubt: Are you putting back the IHS for the reflow or these consoles were never delided?

 

[Pacorretaco]

Thanks for the links and insights! Really considering getting some of the stuff or just looking for a reliable place to do the job for me. One doubt: Are you putting back the IHS for the reflow or these consoles were never delided?

Hmm so it was all fine but after putting pressure on CPU to "make it cooler" you are getting CPU errors and CPU power fail...

Did you check the voltages coming to the CPU at least?

Thinking about messing or "reflowing" CPU is pretty much admitting that there's nothing else to do. It is the last most dangerous thing you can do to a board so keep that in mind. Especially if you want go at it with a heatgun or whatever. One one foot on the landfill waiting for the next foot hehe.

Just adjust your expectations. Even if it were just a connection under the CPU like you are hoping, it's still possible that a "reflow" will not be enough, and the chances of something going terribly wrong are high.
Then again I always thought the center power pads were more or less redundant, just to carry more current and OK if 1 or two break.
Check the voltages first

 

[RIP-Felix]

Thanks for the links and insights! Really considering getting some of the stuff or just looking for a reliable place to do the job for me.

If you can find someone that knows what they are doing and is trustworthy, then by all means do that instead. It's going to be much cheaper. The equipment I had to buy to gear up for a bare-bones reballing capable ghetto setup is $350 minimum! You can buy a new BC console for that!

I only recommend you gear up if you're into electronics projects and want to push your soldering/reworking sklils. Or if you plan to buy/fix/sell consoles. If you do the latter, you should consider getting an actual BGA rework machine instead. The cheapest ones are only a few hundred dollars more and can run profiles! I have to simulate one as best I can, which leads to inferior bonds because my frail human ability cannot substitute for the robotic precision automation provides! It's good enough with experience for my own consoles and a few I might sell off, but it's not good enough for anyone looking to do this professionally.

One doubt: Are you putting back the IHS for the reflow or these consoles were never delided?

That console was a frankenstein mod. So I was removing an RSX that had never been delided, because I wasn't interested in keeping it. I debated on removing the IHS of the 40nm RSX before installing it, but decided that I would emulate how they are installed by the factory. They come from the mnf. with the IHS glued on and pre-balled. They are meant to be put on that way. It shouldn't matter, really, but I thought maybe the extra weight might help the balls to stick to the pads better, but cerebrally I know surface tention and cohesion dictate the distance the chip floats above the MB. The IHS isn't going to squish them down any more than that. And if it does, it's minuscule. So that was the first reason.

The other reason is that the IHS radiates the heat down to the substrate evenly. I'm not sure if my BGA nozzle is heating evenly (I haven't tried holding a piece of paper under it to see if it browns evenly or not). What I do know is that my last attempt at reballing failed. The chip partially adhered to the pads, sinking down in place on one side, but not on the other. Now the balls didn't self center and I believe that's the main reason. I think they merged under the chip on one side and that's why it did that. I could actually slip a piece of paper under that side! I could see merged balls on the end that was soldered down. Or it's possible that one side of the chip melted first, sank down into position, pulling the side that hadn't flowed yet up. Tombstoning, but instead of 90-degrees it only tilted maybe 5-degrees. Then as the other's began flowing they had an incline that "might" have squeezed them closer to a nearby ball and cause them to merge. I don't know, but wanted to prevent the possibility by being sure the chip heated uniformly. And that's the real reason I left the IHS on this one.

On previous attempts the temps I needed to remove the chip were less, since they were all delided. I had to use higher temp settings on both the hot air and Preheater to get the IHS covered chips to flow. Like I said, it's trial and error. I killed 2 consoles before this one learning how to safely get the chips off the board without ripping traces up with them! So I suggest you don't try it on a board you care about until you have practiced it enough to confidently make an attempt.

 

[Stryder]

Hello everyone, first of all thanks a lot for this topic, I got some issue with my personal PS3 and I would like to confirm from you that I need an RSX reballing !

here's my syscon chip log :

> ERRLOG GET 01 00000000 A0801200 FFFFFFFF
> ERRLOG GET 02 00000000 A0801200 FFFFFFFF
> ERRLOG GET 03 00000000 A0801200 FFFFFFFF
> ERRLOG GET 04 00000000 A0801200 FFFFFFFF
> ERRLOG GET 05 00000000 A0801200 FFFFFFFF
> ERRLOG GET 06 00000000 A0801200 FFFFFFFF
> ERRLOG GET 07 00000000 A0801200 FFFFFFFF
> ERRLOG GET 08 00000000 A0801200 FFFFFFFF
> ERRLOG GET 09 00000000 A0902203 FFFFFFFF
> ERRLOG GET 10 00000000 A0404412 FFFFFFFF
> ERRLOG GET 11 00000000 A0403034 FFFFFFFF
> ERRLOG GET 12 00000000 A0404412 FFFFFFFF
> ERRLOG GET 13 00000000 A0403034 0B7E2866
> ERRLOG GET 14 00000000 A0404412 0B7E2866
> ERRLOG GET 15 00000000 A0403034 0B7E2036
> ERRLOG GET 16 00000000 A0404412 0B7E2036
> ERRLOG GET 17 00000000 A0403034 0B7E2024
> ERRLOG GET 18 00000000 A0404412 0B7E2024
> ERRLOG GET 19 00000000 A0403034 0B7E0D28

I tried to reflow at some point, please tell me I did not destroyed her ;_; (Shame on me if I did)

Thanks a lot for your reply, special thanks to Paco and NSC for showing me the way of how to do it

HO! Btw is the errlog 19 the most recent and the 00/01 the most older? Would make sence since this PS3 got delided because of overheating, that would mean my overheating cell is not some error due to my reflow! (which look like a fail to me since I got some bga error If I understood correctly)

EDIT : thanks for the quick approval admin !

 

[Pacorretaco]

Hello everyone, first of all thanks a lot for this topic, I got some issue with my personal PS3 and I would like to confirm from you that I need an RSX reballing !

here's my syscon chip log :

> ERRLOG GET 01 00000000 A0801200 FFFFFFFF
> ERRLOG GET 02 00000000 A0801200 FFFFFFFF
> ERRLOG GET 03 00000000 A0801200 FFFFFFFF
> ERRLOG GET 04 00000000 A0801200 FFFFFFFF
> ERRLOG GET 05 00000000 A0801200 FFFFFFFF
> ERRLOG GET 06 00000000 A0801200 FFFFFFFF
> ERRLOG GET 07 00000000 A0801200 FFFFFFFF
> ERRLOG GET 08 00000000 A0801200 FFFFFFFF
> ERRLOG GET 09 00000000 A0902203 FFFFFFFF
> ERRLOG GET 10 00000000 A0404412 FFFFFFFF
> ERRLOG GET 11 00000000 A0403034 FFFFFFFF
> ERRLOG GET 12 00000000 A0404412 FFFFFFFF
> ERRLOG GET 13 00000000 A0403034 0B7E2866
> ERRLOG GET 14 00000000 A0404412 0B7E2866
> ERRLOG GET 15 00000000 A0403034 0B7E2036
> ERRLOG GET 16 00000000 A0404412 0B7E2036
> ERRLOG GET 17 00000000 A0403034 0B7E2024
> ERRLOG GET 18 00000000 A0404412 0B7E2024
> ERRLOG GET 19 00000000 A0403034 0B7E0D28

I tried to reflow at some point, please tell me I did not destroyed her ;_; (Shame on me if I did)

Thanks a lot for your reply, special thanks to Paco and NSC for showing me the way of how to do it

HO! Btw is the errlog 19 the most recent and the 00/01 the most older? Would make sence since this PS3 got delided because of overheating, that would mean my overheating cell is not some error due to my reflow! (which look like a fail to me since I got some bga error If I understood correctly)

EDIT : thanks for the quick approval admin !

Glad you found it helpful.

About your machine, no I don't think you destroyed it yet hehe.
Does it need RSX reballing?
Actually this question is a bit more complex. Yes you have been having the typical RSX problems unfortunately.
But ... the reballing can wait because this is not exactly the problem you are having right now.

Looking at your partial error log, it seemes like actually you are having CPU overheating! (Error 1200) But this error that you are having "now" is happening in the POWER ON state (prefix 80).
This means that the power up squence was completed successfully, including the CPU RSX bittraining (stage 40).

Long story short, first you need to make sure that your CPU temperatures are under control, and then see what happens. Put the heatsink properly and check. It might just work for now.

Also you probably want to enable Diag mode to run internal commands. Such as bringup, tmp...
And get the full errlog (32 errors). Good thing you reminded me.
(You can also copy and paste this batch of commands from External mode if you want)

Good luck