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

LSL said:
No. Each probe on each side on fuse
Click to expand...
ps3xbox said:
Hi
Ok so I have gone through all the points and measured them
some of the points voltage I get different readings each time I turn the ps3 on
The ps3 has ylod and I have only a few seconds to get the reading
I notice after turning on and off I get a high reading but it takes time to get them
Some readings I get the same each time

JL6063some times gets to 1.1v but sometimes it is less about 0.3v
JL6103gets to 0.9v after turning on and off few times
JL6114 0.3 to 0.9v same after turning and off few times
JL9654 0.2v to 1.1v, some times gets to 1.4v
JX96010.4v but Gets to 1.2v after turning on and off few times
JL6201 0.2v to 1.8v, some times gets to 3.3v
JL6208 0.1v to 0.4v, sometimes gets to 0.4v but after turning on and off
JL60480.4v to 1.3v, sometimes gets to 1.3v but after turning on and off
JL60560.3, 0.9 but gets to 1.2v, sometimes gets to 1.2v but after turning on and off
JL9651 0.2v, gets to 1.1v after turning on and off
JL9656 0.2v to 1.1v, some times gets to 1.2v
JL6058 3.2v
JL60602.4v
JL60611.7v
JL96481.1v
JL9647 1.7v
JL96520.5 to 1.1v, sometimes gets to 1.1v but after turning on and off
Click to expand...

This oscillation is normal with the voltmeter. I don't know if with True RMS voltmeter it shows this oscillation. The ideal is to measure with an oscilloscope.
 
db260179 said:
So whats the readings for your southbridge?

Its possible the Hd controller is broken?

As far as im aware there is no detection from syscon on the periphals that connect to the southbridge, so the HD controller could be faulty?

As you are in safe mode means the RSX is working and the HDMI chip is ok, other possible is faulty RAM on either the RSX or CELL

In safe mode, can you format a new drive? or system update?
Click to expand...
the reading seems to be good i don't know for sure i have a shitty cheap multimeter but the read was pretty close to the one you gave and the chip heat up for sure
i don't know if the hd controller is broken or not but the hard drive is working great once formatted in windows... i have a spare cok-002 motherboard with a broken cell and a ir bga rework station so i can try swapping the chip if is possible but i already tried to initialize the ps3 but nothing
i don't know for the update i don't have the original blueray drive but a working one from another console i don't know if the update stops giving error i was planning to remarry the drive

I want to remind that the console stay on for a few minutes with no signal at all and then the hd dirive led blinks then turn off without beeping

one last thing what i need to connect to the ps3 to boot? hd, psu and nothing? what is the bare essential to boot the ps3 menù?

UPDATE: i tested the safe mode without hard drive and it said that an hard drive is needed to boot so maybe the hd controller isn't fried because with an hd inside the safe mode boot and the ps3 just turn off himself without beeping even without the hd inside the console was working great 2 week ago and was never opened before
 
Last edited:
Ok, so to do an update without a working Blueray, use a noBD cfw firmware if its on cfw.

You need to do a format of the drive in safe mode on the ps3, not on another pc as that only verifys the drive and not the ps3 controller.

A dodgy hd will create a blank screen, so swap with the other drive and format it in the ps3 on safe mode, do this and come back.

Also do a nand dump if you can, double check if its ok with the pychecker

DomyGX said:
the reading seems to be good i don't know for sure i have a shitty cheap multimeter but the read was pretty close to the one you gave and the chip heat up for sure
i don't know if the hd controller is broken or not but the hard drive is working great once formatted in windows... i have a spare cok-002 motherboard with a broken cell and a ir bga rework station so i can try swapping the chip if is possible but i already tried to initialize the ps3 but nothing
i don't know for the update i don't have the original blueray drive but a working one from another console i don't know if the update stops giving error i was planning to remarry the drive

I want to remind that the console stay on for a few minutes with no signal at all and then the hd dirive led blinks then turn off without beeping

one last thing what i need to connect to the ps3 to boot? hd, psu and nothing? what is the bare essential to boot the ps3 menù?

UPDATE: i tested the safe mode without hard drive and it said that an hard drive is needed to boot so maybe the hd controller isn't fried because with an hd inside the safe mode boot and the ps3 just turn off himself without beeping even without the hd inside the console was working great 2 week ago and was never opened before
Click to expand...
 
Last edited:
db260179 said:
Ok, so to do an update without a working Blueray, use a noBD cfw firmware if its on cfw.

You need to do a format of the drive in safe mode on the ps3, not on another pc as that only verifys the drive and not the ps3 controller.

A dodgy hd will create a blank screen, so swap with the other drive and format it in the ps3 on safe mode, do this and come back.

Also do a nand dump if you can, double check if its ok with the pychecker
Click to expand...
The ps3 has no cfw on it and the update say 4.50 so i think no update or i will "brick" i have no flash dumper/writer hardware. But the drive is working once is connected i can put a disk without problem but like i said is not the mb married one. Formattig the drive just let the ps3 turnig off even before now i don't know why but now i have some syscon error and i'm gonna post the startup log. Ok even strange thing now that i have formatted the drive by selecting initialize ps3 now i can't press anymore that button because is said no drive found

>$ 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
>$
[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
[mullion]$
>$
[SERV THERM] NOTIFY_MODE CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV DEVPM] CONTROL_PCI_BUS_POWER_STATE CMD
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 000002F4, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
 
Last edited:
Ok, so type 'errlog' and 'lasterrlog' in the syscon terminal and post here.

Try and get the 4.50 ofw firmware (https://archive.midnightchannel.net...5af9/CEX_CRC[4018725b]_FW[v4.50]_PS3UPDAT.PUP) and put on a usb stick, try to get to the safe mode and do a system update. Dont worry you have no blueray, this is to establish if your hd controller is working or related components like the nand or nor.

So for me this looks like, faulty hd controller, corrupt nand or intermittant southbridge issue.

DomyGX said:
The ps3 has no cfw on it and the update say 4.50 so i think no update or i will "brick" i have no flash dumper/writer hardware. But the drive is working once is connected i can put a disk without problem but like i said is not the mb married one. Formattig the drive just let the ps3 turnig off even before now i don't know why but now i have some syscon error and i'm gonna post the startup log. Ok even strange thing now that i have formatted the drive by selecting initialize ps3 now i can't press anymore that button because is said no drive found
Click to expand...
 
LSL said:
This oscillation is normal with the voltmeter. I don't know if with True RMS voltmeter it shows this oscillation. The ideal is to measure with an oscilloscope.
Click to expand...
Hi
Can anyone else let me know what might be causing these voltages to be so low, please
I cant get to a scope right now

I am thinking to replace
ic6201, ic6202, ic6203
 
db260179 said:
Ok, so type 'errlog' and 'lasterrlog' in the syscon terminal and post here.

Try and get the 4.50 ofw firmware (https://archive.midnightchannel.net...5af9/CEX_CRC[4018725b]_FW[v4.50]_PS3UPDAT.PUP) and put on a usb stick, try to get to the safe mode and do a system update. Dont worry you have no blueray, this is to establish if your hd controller is working or related components like the nand or nor.

So for me this looks like, faulty hd controller, corrupt nand or intermittant southbridge issue.
Click to expand...
Ok but what if the system actually update? Will i brick the ps3 to an update loop due to bd drive missing?

i got those error "1001, 1103, 14FF, 1701, 3010" and still i can't get the tsensor 2 command give the southbridge temp the cell and rsx one are ok
 
No this is the official ps3 firmware update, so no bricking - the boot loop will happen regardless with no blue ray drive if you need to reinstall.

If you want to play it safe you will need to dump the nand using a hardware flasher - teensy is easier as readly available.

I'm afraid the fact your southbridge is not showing any temps, means there is something wrong with it. And the fact it keeps not detecting the drive properly is a tell tell sign.

Not much else i can advise, im afraid.

DomyGX said:
Ok but what if the system actually update? Will i brick the ps3 to an update loop due to bd drive missing?

i got those error "1001, 1103, 14FF, 1701, 3010" and still i can't get the tsensor 2 command give the southbridge temp the cell and rsx one are ok
Click to expand...
 
db260179 said:
No this is the official ps3 firmware update, so no bricking - the boot loop will happen regardless with no blue ray drive if you need to reinstall.

If you want to play it safe you will need to dump the nand using a hardware flasher - teensy is easier as readly available.

I'm afraid the fact your southbridge is not showing any temps, means there is something wrong with it. And the fact it keeps not detecting the drive properly is a tell tell sign.

Not much else i can advise, im afraid.
Click to expand...
is the southbridge replaceable? because i already have a spare one that is surely working
 
So hopefully you are good a reballing?

You will need an IR or at least a preheater to remove both. A profile IR heater is the best if u can afford it, otherwise preheater will have to do - the trick is to get enough heat underneath then a quick blast on the top to remove, without killing the chip

DomyGX said:
is the southbridge replaceable? because i already have a spare one that is surely working
Click to expand...
 
db260179 said:
So hopefully you are good a reballing?

You will need an IR or at least a preheater to remove both. A profile IR heater is the best if u can afford it, otherwise preheater will have to do - the trick is to get enough heat underneath then a quick blast on the top to remove, without killing the chip
Click to expand...
i have a t-862++ i know is cheap but i think will work fine
 
Hi, now my ps3 has ylod... i didn't change the southbridge yet but i delided the cell and no mistake were made no broken trace i have done a good job but i get those 2 error code 3034,4401 is this maybe a poor bga problem made by the force used to delid? Is a well made reflow enough to solve the problem?
 
Both errors point to a fault with the CELL, why did you delid?

You have probably made things worse now, delid is only needed when you have everything working and have heat issues.

DomyGX said:
Hi, now my ps3 has ylod... i didn't change the southbridge yet but i delided the cell and no mistake were made no broken trace i have done a good job but i get those 2 error code 3034,4401 is this maybe a poor bga problem made by the force used to delid? Is a well made reflow enough to solve the problem?
Click to expand...
 
db260179 said:
Both errors point to a fault with the CELL, why did you delid?

You have probably made things worse now, delid is only needed when you have everything working and have heat issues.
Click to expand...
the console hit high temperature very fast and in 5 minute shutdown it self, delid was needed even to do the system update and like i said no damage to upper trace was made. anyway are those a bga error true? so a reflow or a reball is required?

UPDATE: i forgot to say that actually the tsensor command work only after the chip "initialize" for example if you have just connected the console to pc the temperature is 0 but after booting up the console the temperature show up for the chip used
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top