PS3 B01 troubles of a different kind

Just to add to this again, I measured the voltage at the capacitor pads on an a01 motherboard and I'm getting the same 1.15v as I am on the problematic motherboard.

I'm confused as to why I have 2 boards with the same voltages yet one won't work... any ideas?

Sent from my SM-G965U using Tapatalk
 
RCWD21 said:
Ok so me seeing 1.15v is obviously way too low then.

Besides the tantalums where else should I check for voltage to see if something else on the board is bad or failing?

Sent from my SM-G965U using Tapatalk
Click to expand...
There are also fuses all over the motherboard all there numbers start with F. They are very small and white in color, also the cpu requirements for voltage are about 1.5 volt. So 1.15 is to low IMO. If you are checking for voltage after the tantalums. And it isn't at least 1.5 the tantalums aren't holding enough voltage, they are like tiny batteries that discharge their voltage rapidly. So they must be able to keep up with the cpu voltage demand. The more clean esr voltage the more efficient the cpu will run also maybe slightly cooler.
RCWD21 said:
Just to add to this again, I measured the voltage at the capacitor pads on an a01 motherboard and I'm getting the same 1.15v as I am on the problematic motherboard.

I'm confused as to why I have 2 boards with the same voltages yet one won't work... any ideas?

Sent from my SM-G965U using Tapatalk
Click to expand...
Possible dead cpu or a short or a cut trace bga solder Crack and many other possibilities to many to list.


The voltage can be that low for the tantalums or tokens but they need to keep up with the demand.
 
Yugonibblit said:
There are also fuses all over the motherboard all there numbers start with F. They are very small and white in color, also the cpu requirements for voltage are about 1.5 volt. So 1.15 is to low IMO. If you are checking for voltage after the tantalums. And it isn't at least 1.5 the tantalums aren't holding enough voltage, they are like tiny batteries that discharge their voltage rapidly. So they must be able to keep up with the cpu voltage demand. The more clean esr voltage the more efficient the cpu will run also maybe slightly cooler.

Possible dead cpu or a short or a cut trace bga solder Crack and many other possibilities to many to list.


The voltage can be that low for the tantalums or tokens but they need to keep up with the demand.
Click to expand...
I keep thinking the power switch may be the problem have you tried another ribbon and switch? But I could be completely off base .
 
Yugonibblit said:
I keep thinking the power switch may be the problem have you tried another ribbon and switch? But I could be completely off base .
Click to expand...
I have another ps3 that I just checked voltages on and in a non load state the voltage was 1.15v just like the board I'm having problems with so I dont think its too low to operate since they CELL and RSX are of the same vintage (A and B model).

Also I've tried swapping the power supply (again), the ribbon and the switch board and no change.

Your idea of it being a BGA failure is looking a lot more likely the more I try things.

I dont think its a fuse as it would show up in the powerstate test via syscon,

Do you happen to know if the thermal limit of 91c apply to every area of the CELL? Like if 9 out of 10 areas were 85c but one popped up to 91c, would that 1 area at 91c cause the system to go into thermal shutdown?

Sent from my SM-G965U using Tapatalk
 
RCWD21 said:
I have another ps3 that I just checked voltages on and in a non load state the voltage was 1.15v just like the board I'm having problems with so I dont think its too low to operate since they CELL and RSX are of the same vintage (A and B model).

Also I've tried swapping the power supply (again), the ribbon and the switch board and no change.

Your idea of it being a BGA failure is looking a lot more likely the more I try things.

I dont think its a fuse as it would show up in the powerstate test via syscon,

Do you happen to know if the thermal limit of 91c apply to every area of the CELL? Like if 9 out of 10 areas were 85c but one popped up to 91c, would that 1 area at 91c cause the system to go into thermal shutdown?

Sent from my SM-G965U using Tapatalk
Click to expand...
Good question , I have delid all 3 cpu. And have had good luck.

91 that's hot probably
 
Yugonibblit said:
Good question , I have delid all 3 cpu. And have had good luck.

91 that's hot probably
Click to expand...
I've yet to delid this particular board as I didn't want to disturb anything until I could get it working again. I may go ahead and do that just to make sure.

And yes, 91c is definitely hot, its what Sony sets the thermal shutdown temp at on these things in the syscon. Linda crazy if you ask me.

I ask about the zones because if it is indeed a thermal reading that's telling the console to shut down I can try the command for thermal limit on or off (I forget the exact name) and see if it stays on even a few seconds longer. That would be done after a delid of course

Sent from my SM-G965U using Tapatalk
 
RCWD21 said:
I've yet to delid this particular board as I didn't want to disturb anything until I could get it working again. I may go ahead and do that just to make sure.

And yes, 91c is definitely hot, its what Sony sets the thermal shutdown temp at on these things in the syscon. Linda crazy if you ask me.

I ask about the zones because if it is indeed a thermal reading that's telling the console to shut down I can try the command for thermal limit on or off (I forget the exact name) and see if it stays on even a few seconds longer. That would be done after a delid of course

Sent from my SM-G965U using Tapatalk
Click to expand...
I use a regular razor blade, really a PTA! Just gotta be super careful.
 
Yes, but never had a good dump to replace chip.
Have replaced chips and flashed them before providing I had a good dump. With other boards.
 
Here are a few logs I've just pulled from syscon:

getrtc
Y/M/D(Day)H:M:S : 00/01/04(WED) PM 11:43:35
Clock : 0x00000001
RTC Error:Battery Low Occured
RTC Error:Clock Stop Occured

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

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]$


I hope this helps anyone with questions, if you need other specific logs please let m know and I'll post them.
 
RCWD21 said:
A few years ago I bought a working b01 ps3 on 2.83 ofw
Click to expand...
What a disgrace man..

Why didn't you update to 3.55 instead of 4.xx?

I read many times that @Coro said you need to update to 3.55 because it was safer than going with a newer one.

I'm pretty sure your console is bricked. So there wasn't any reason to go in the hardware aspect apart of taking a NAND backup or remove them.
 
ElGris said:
What a disgrace man..

Why didn't you update to 3.55 instead of 4.xx?

I read many times that @Coro said you need to update to 3.55 because it was safer than going with a newer one.

I'm pretty sure your console is bricked. So there wasn't any reason to go in the hardware aspect apart of taking a NAND backup or remove them.
Click to expand...
I don't really get how it's a disgrace when you're the first person to ever mention that updating from a pre 3.55 FW is a bad idea when going into the 4.xx and up stuff. Not once have I ever seen mention of that.

And besides I highly doubt me picking 3.55 over 4.87 would have made a difference in this instance.

And how is my console firmware bricked when I'm getting a constant power error in syscon?

Sent from my SM-G965U using Tapatalk
 
RCWD21 said:
I don't really get how it's a disgrace when you're the first person to ever mention that updating from a pre 3.55 FW is a bad idea when going into the 4.xx and up stuff. Not once have I ever seen mention of that.

And besides I highly doubt me picking 3.55 over 4.87 would have made a difference in this instance.

And how is my console firmware bricked when I'm getting a constant power error in syscon?

Sent from my SM-G965U using Tapatalk
Click to expand...
It's a disgrace for a console that imo is the best looking model Sony ever made.

On the topic, there're a lot of threads made by users asking on how to going up from a very old firmware version to a newer one. You didn't do your homework, but it's not your fault. The previous and post behaviour of your console is a clue (GLOD with countdown), and pretty obvious if you ask me.

That 1001 you see on syscon could be related to a bad tokins change, or bga damage when you replaced them. It's gonna be hard to recover this one.
 
i found an old post by @DeViL303. i don't know anything about it.

DeViL303 said:
It's worth noting that while we do not have safe mode on lower firmwares, we do have full FSM jig capabilities on OFW under 3.55. This means even more serious bricks can be recovered on those FWs than with safe mode. You do however need some form of hardware to emulate the service mode jig. This can be an android device, PSP or a teensy for example, that's if you do not have a purpose built device like an e3 card reader or jailbreak dongle.
Click to expand...

if you think the update actually wrote any files, then i would try to get into recovery mode one time. worth a shot.
 
Coro said:
i found an old post by @DeViL303. i don't know anything about it.



if you think the update actually wrote any files, then i would try to get into recovery mode one time. worth a shot.
Click to expand...
It is old method with FSM to install OFW 3.55, also I think there is no video just HDD light flashing. There is a video on YouTube BY NSC very well known ps3 hobbyist.
 
You must log in or register to reply here.

Similar threads

Back
Top