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

AnteLo said:
Okay, thanks.
Excuse my ignorance but is this what you want?
https://ibb.co/r55PHzH
Click to expand...

Ok this new picture is a bit clearer? did you run 'clearerrlog' ?, if you did it will clear previous history.

Anyway it doesnt matter, so based on your errors

A0093003 CELL_POW_FAIL

The 2030 - 31 errors are thermal sensor errors, but these will be a cause of the main issue of the cell power not correct.

This is most likely caused by not having the NEC tokins soldered on?

So have that nec tokins or equalivant installed, then check the errlog again once this is done.
 
@db260179 My console is : CECHG08 (SEM-001 Mother board)
Please Guide me , I am unable to understand the instructions from git repo pdf file.
also the guide has only Rx and Tx pin out image only.

I have bought PL2303HX which has 4 connector pins :
Black (Ground)
Green (Txd)
White (Rxd)
Red (VCC 5V)

Help me connecting to the board. i have gone through all the threads and reply of this post but still i am not understanding.
ground and vcc are still a mystery to me.

I have checked the usb leads with dc setting with multi meter by connecting negative probe to the ground wire (black wire of usb lead- PL2303HX) and postive probe connected to Tx (Green wire of the usb lead - PL2303HX) and measured 3.48V

I have checked the usb leads with dc setting with multi meter by connecting negative probe to the ground wire (black wire of usb lead- PL2303HX) and postive probe connected to Rx (White wire of the usb lead - PL2303HX) and measured 3.72V
and
What next ?
is it safe to proceed ? if so then please guide me. i dont know that to do with the Ground (black wire) and the VCC 5V (red wire)

 
Kazama said:
@db260179 My console is : CECHG08 (SEM-001 Mother board)
Please Guide me , I am unable to understand the instructions from git repo pdf file.
also the guide has only Rx and Tx pin out image only.

I have bought PL2303HX which has 4 connector pins :
Black (Ground)
Green (Txd)
White (Rxd)
Red (VCC 5V)

Help me connecting to the board. i have gone through all the threads and reply of this post but still i am not understanding.
ground and vcc are still a mystery to me.

I have checked the usb leads with dc setting with multi meter by connecting negative probe to the ground wire (black wire of usb lead- PL2303HX) and postive probe connected to Tx (Green wire of the usb lead - PL2303HX) and measured 3.48V

I have checked the usb leads with dc setting with multi meter by connecting negative probe to the ground wire (black wire of usb lead- PL2303HX) and postive probe connected to Rx (White wire of the usb lead - PL2303HX) and measured 3.72V
and
What next ?
is it safe to proceed ? if so then please guide me. i dont know that to do with the Ground (black wire) and the VCC 5V (red wire)

Click to expand...

Ground connect to the ground of your motherboard and don't connect the VCC anywhere.
My motherboard is different but you can see where I connected the ground (white wire).
https://ibb.co/gtVTW6x

It should work the same for you as long as you connect it to the gold ring around the board.
 
AnteLo said:
Ground connect to the ground of your motherboard and don't connect the VCC anywhere.
My motherboard is different but you can see where I connected the ground (white wire).
https://ibb.co/gtVTW6x

It should work the same for you as long as you connect it to the gold ring around the board.
Click to expand...

Your board has 4 pin outs. Rx TX ground and diag.

But my board has only tx rx and diag pin outs. Then which should I connect ? I have 4 wires (tx rx VCC and ground only)
 
Kazama said:
Your board has 4 pin outs. Rx TX ground and diag.

But my board has only tx rx and diag pin outs. Then which should I connect ? I have 4 wires (tx rx VCC and ground only)
Click to expand...

So first step, connect your usb ttl lead - RX , TX and GND to the PS3 motherboard TX, RX and GND (any ground point on the motherboard). Ignore the 5V from the usb lead!
The DIAG from the PS3 will be connected to the GND later!

Then do the EEP SET in CXR mode as explained in the guide.

Once you have done that step, then follow the CXRF mode step which involves connecting the DIAG from PS3 to your USB GND lead.
 
Last edited:
sandungas said:
Search for the error code here.
Sadly the name of the error doesnt gives much info, seems to be related with power anyway, maybe someone with more experience in it could give some hints
Click to expand...

Yeah, I did check it there but it didn't give much hope lol.
Thanks anyway
 
Btw you guys think it would be possible to access these syscon error logs from a working console with CFW?
Even if after the fact, it would still be useful. Otherwise we will still be having problems with myths etc. Sad truth is... People mostly won't bother with this. And thus 15 years later we still have mostly no clue.
At least without some easier video guide or something... It will take time.
Don't get me wrong. It's great work being done here.
Cheers
 
I have a CECHA01 board that gives the following:
Code: 
>$ 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:0x20e2
>$
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0305
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0305 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0603040
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$
>$ exit
It reaches [state: 0105 -> 0305] instead of [state: 0105 -> 0400] and beeps 3 times with a flashing red led. Error A0603040 = Flash controller Error (IC3801). IC3801 is the StarShip2 chip. Any ideas/advice?
 
Could this be a nand flash problem. I downgraded the nands to 3.55 and verified them with PS3DumpChecker before re-flashing and had no errors. I reread the flashed nands and verified them.
 
nyislander said:
Could this be a nand flash problem. I downgraded the nands to 3.55 and verified them with PS3DumpChecker before re-flashing and had no errors. I reread the flashed nands and verified them.
Click to expand...

Its possible the starship2 is either faulty, or incorrect voltage/shorts near it preventing it from working?

Make sure no caps or resistors are missing, its very easy to pop off the caps without realising - did this once on a SEM-001 board, and showed a power fault, turned out one cap was missing and another was high resistance.

So look at the service manual and follow the caps/resistors related to that chip and measure voltage around it.
 
AnteLo said:
Today I tried cleaning the errlog and redoing everything to get it to write errors to the log.
This time it worked and I got "0xa0093003".
What could it be?

https://ibb.co/bNyqXTf
Click to expand...

You need to go voltage and resistance hunting im afraid.

Get the service manual for that board
Do some voltage checks near the NEC tokins, you will need to test the CELL and RSX readings on the postive nec tokins line - they should read 1.0-1.3V. Check that the IC bucks are giving out 5v's.

It will take time, but you need to follow the service manual and work your way around the area you have been touching, eventually you will narrow down the fault.
 
Pacorretaco said:
Btw you guys think it would be possible to access these syscon error logs from a working console with CFW?
Even if after the fact, it would still be useful. Otherwise we will still be having problems with myths etc. Sad truth is... People mostly won't bother with this. And thus 15 years later we still have mostly no clue.
At least without some easier video guide or something... It will take time.
Don't get me wrong. It's great work being done here.
Cheers
Click to expand...

You can access the syscon regardless if the board is booting, it acts as a seperate microprocessor. So OFW or CFW doesnt matter
 
db260179 said:
You can access the syscon regardless if the board is booting, it acts as a seperate microprocessor. So OFW or CFW doesnt matter
Click to expand...
Ahh sorry I think I didn't express it clearly enough. Or perhaps was too impossible... I have no clue after all.

What I meant was accessing these logs... maybe with a piece of homebrew.
That way anyone could be able to check. Even if after the fact we could mitigate the problem of false positives, myths... etc.

Because people never bother with these.
They just want an easy solution always. (Hence 150+ pages of tokin thread)

Hopefully you understand now
 
Post #350-351 update

When I downgraded the nands on my CECHA I removed them and used a TSOP48 programmer (I never had luck with the clip and I dremmeled it so much that it is now useless). The TSOP48 socket provides me with consistent read/writes. My error came from me not thoroughly checking the nand legs after drag soldering them, a few were not soldered. I fixed this error and have made further progress. The console tries to start but shuts down to standby mode with no display.
[SPOILER="syscon">$ 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:0x20e2
>$
[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 THERM] NOTIFY_MODE CMD

[mullion]$
>$
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD

[mullion]$
>$
[SERV THERM] NOTIFY_MODE 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 = 00000274, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)

[mullion]$
>$ errlog
errlog
ofst[ 0]:err_code:0xffffffff, clock:0xffffffff
ofst[ 4]:err_code:0xffffffff, clock:0xffffffff
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
[mullion]$
>$ ][/SPOILER]
 
I did some probing on the board today and this is what I got.

Code: 
JL6208 - 3.93V-4.01V
JL6048 - 0.16V-0.48V
capacitors in between JL6208 and JL6048 - 2.97V
JL9656 - 1.47V
JL9657 - 1.75V
JL6201 - 0.07V
JL9651 - 1.19V

psu plug:

12V BANANA plug - 12.07v


1 - 3.28V - 0v when off, 3.28 while on
2 - GND
3 - GND
4 - 5.07V - always on
5 - 5.07V - always on

I didn't probe anymore because I am tired and I couldn't get to the rest of the pins with the PSU still connected.
I have a COK-002 and some of these voltages seem kinda high, btw my NEC/TOKIN capacitors replacements are still in the mail so this test was done without NEC/TOKIN capacitors.
 
Does anyone have a clue, what can cause my COK-002 problems? (it had graphical glitches, but disappeared after some reflow)
It started as sometimes not detecting the HDD, but after reboot it started ok. Then took a bit more and more time to "warm up" before starting up properly (bringup log showed it started ok just no picture, no HDD activity and not even USB power out -- 5V regulator works - i think the HUB does not power the outputs unless the upstream is present)
After started up, no issues was present.

Then I got error codes 0801701 (BE Attention) and 0801601 (BE Livelock Detection)
(there were a few 0801001 (BE VRAM(?) Power Fail) sprinkled in before -- then I replaced top half of the NEC/TOKIN)

Now it got worse as it seems the BE doesn't even load the Boot Loader -- after (PowerOn State) there is no more [SERV NVS] READ CMD.

So any idea?
 
CodeKiller said:
Does anyone have a clue, what can cause my COK-002 problems? (it had graphical glitches, but disappeared after some reflow)
It started as sometimes not detecting the HDD, but after reboot it started ok. Then took a bit more and more time to "warm up" before starting up properly (bringup log showed it started ok just no picture, no HDD activity and not even USB power out -- 5V regulator works - i think the HUB does not power the outputs unless the upstream is present)
After started up, no issues was present.

Then I got error codes 0801701 (BE Attention) and 0801601 (BE Livelock Detection)
(there were a few 0801001 (BE VRAM(?) Power Fail) sprinkled in before -- then I replaced top half of the NEC/TOKIN)

Now it got worse as it seems the BE doesn't even load the Boot Loader -- after (PowerOn State) there is no more [SERV NVS] READ CMD.

So any idea?
Click to expand...

How do you know the issue is "not detecting the hdd"?
To me it sounds like a typical GLOD, which indeed has to do with the artifacts.

Sadly it is extremely common in these models. I have 3 of those

Edit: Oh sorry now I realize you decided to try the tokin "fix". Etc.
 
Last edited:
You must log in or register to reply here.

Similar threads

Back
Top