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

db260179

db260179

Member
So I started this thread to have a deep discussion about the YLOD on the PS3 (mostly FAT versions) and how to use the SYSCON to understand further what can be done to repair the ps3.

My main reason that drives me to do this is that I've seen alot of miss informed threads on how to fix YLOD ps3, there is alot of valid pointers but the basics have to be done first.

DISCLAIMER:

Before attempting this procedure, PLEASE PLEASE make sure you are confident in basic soldering and diagnostics, I will not be held responsible for you breaking your ps3!!!

READ THE GUIDE AND ASK QUESTIONS IN THIS FORUM, THANK YOU!

Ok, thats the disclaimer over and done with:

So in case everyone has missed a thread about the syscon discovery - https://www.psx-place.com/threads/s...oxao-what-does-it-mean.26148/page-10#comments

This thread will be more of a deep dive in using the syscon.

What I hope from this thread is that people contribute their error codes they get from their syscon and we can create a database of error code and whats issues are related to that error codes that come out of it.

So to get everyone started, I will share my first draft syscon connection guide:

This guide covers what tools to use, software to use and versions of PS3 boards (known to access syscon) with identification of pins to connect to.

As this thread grows overtime we should have a good grasp of the errors and what needs fixing to keep these old PS3 consoles alive.

SYSCON Guide

https://github.com/db260179/ps3syscon

############################################################################
If you have anything to add, please do a pull request or PM directly so i can add.

Guides preferably in odt or PDF
############################################################################


In this guide we will be:

  1. Identfy the motherboard and its pins - RX, TX, GND and DIAG pin
  2. Solder the jumper cables to the correct pins - RX, TX and GND go to the USB uart serial cable and DIAG get shorted to GND once the eeprom has set its mode to allow diag mode
  3. Run python syscon script to interact with the syscon - 'auth' command is used to access the high level commands on the syscon, and internal and external commands to run actions.
  4. External commands - used mostly to do basic stuff - activate internal commands
  5. Internal commands - Spend most of our time running - 'errlog', 'bringup' and other common used commands to help identify YLOD issues.
  6. Identify the YLOD issue based on the error code - and investigate with basic multimeter - voltage checks, resistance etc
  7. Tweaked fantables - use supplied tweaks from the my gitrepo for each motherboard

Big thanks and shout out to Mina for his help and patience!

Recorded errors (errlog) in the syscon shell:

Go to https://github.com/db260179/ps3syscon for the latest readings!

Please submit your full error messages and what you did to resolve that error!

Further updates: Have improved the python uart script, so now can log your actions in a logfile and exiting is just pressing CTRL+C - checkout the new changes!

Update - 2023 - On my github you will find links to the pre made debian VM that contains my scripts and firmware and tools required to help fix the PS3, including a syscon script that help guides you with diagnosis. Enjoy!

Update! - 2022 - I've been away for a while and a lot has happened since i first posted this!

Since RIP-Felix has done a lot of good work collecting the data etc, i've updated the guide on my git repo to reference his posts and uploaded the pictures of the serial connections to make life easier!

A shout out to Rip-Felix on his new video on the background of this YLOD

 
Last edited:
db260179 said:
So first errors recorded and known related issues:

POWER ERRORS:
0003001 POW_FAIL
A0093004 RSX_POW_FAIL
A0093003 CELL_POW_FAIL

BE ERRORS:
A0213013 BE_SPI DI/DO ERROR
A0213011 BE_SPI CS ERROR
A0203010 BE_INIT OR BE_POWGOOD OR CLOCK ERRORS

RSX ERRORS:
A0404002 RSX_SPI DI/DO ERROR
A0404411 - ERROR ON RSX SPI?
A0403034 and A0404411

SB ERRORS:
A0302203 SB_SPI DI/DO ERROR
A0313032 SB_CLOCK OR INIT ERROR

OTHERS:
A0022110 MK I2C ERROR (OR OTHER CLOCK's ERRORS)
Click to expand...

Me and the user @marciolsf started a few days ago to study the SYSCON errors, we both have PS3 with the error ending in 3034.

We have already checked the sectors for some errors ending:
3001 - Without 12v from the source.
3003 - VRM for CELL with problem. It can be NEC Tokins or PWM or any other component of this sector
3004 - VRM for RSX with problem. It can be NEC Tokins or PWM or any other component in this sector.
 
This guide is great! Thanks for all your work putting it together, there's a ton of good information there. I'm going to patch the eeprom (now that I know how), and report what I get.
 
Ok, so I went over your guide, and noticed some basic differences. I don't know if they're because my board is a COK-001, or if I messed up on setting the initial flag in external mode. When I SET 3961 to 00, and then I GET it back, I get 00, 02. That led to an interesting rabbit hole where my checksum was different than yours, and I had to do an extra write to get the checksum to come clear. Whew!

At first, the ps3 would still fail to boot with bringup. After I did a hard reset and reconnected, voila! bringup now works properly, and I get a boot log

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
>

I looked through errlog, and noticed something new
Code: 
ofst[ 44]:err_code:0xa0061004, clock:0xffffffff
ofst[ 48]:err_code:0xa0093003, clock:0xffffffff

1004 maps out to AC/DC POWER FAIL. I'm going to test the IC's on the DC-DC diagram (page 26 in the service guide) and see if something is amiss there. Or maybe I should be checking elsewhere? For 3003, I'm guessing the failure will be somewhere on VRM for BE (page 24), which also include the infamous nec/tokins...
 
I cant see that in the guide? - it clearly states Motherboard RX goes to UART RX and Motherboard TX to TX UART?

Please point that in the guide out if you could
Thanks

LSL said:
Could you update guide? UART points from COK-001 is the same of COK-002.

One doubt on sector Connecting the serial connection, Rx motheboard should not be soldered on the Tx UART board and Tx motheboard should not be soldered on the Rx UART board? Because I do this on my CP2102 board
Click to expand...
 
So only need to do this once -
EEP SET 3961 01 00 - sets active modes for diag

And then check with eepcsum in internal mode and correct the checksum - as stated in the guide
Remember we are dealing with a little endian system, so bytes are reversed.

Dont worry you will get the hang of it.

Yes your error codes are power fail related, if you have changed the nec tokins to cheapo tantuim capacitors then you will not be getting enough filtering going on!!

So incase you are not aware a new set of NEC tokins have a value of 2000 uf, so you are looking at having a min of 1300uf x 4 RSX and same for CELL. My advise is remove your caps and check their value with a multimeter or tester. If you dont want to do that then keep adding any capacitor say a 1000uf, then turn on and see if the power fails clear.

Retrace your steps on what you did, and yes look at the voltage rails - 12v, 5v and 3.3v identify anything that looks out of working spec.


marciolsf said:
Ok, so I went over your guide, and noticed some basic differences. I don't know if they're because my board is a COK-001, or if I messed up on setting the initial flag in external mode. When I SET 3961 to 00, and then I GET it back, I get 00, 02. That led to an interesting rabbit hole where my checksum was different than yours, and I had to do an extra write to get the checksum to come clear. Whew!

At first, the ps3 would still fail to boot with bringup. After I did a hard reset and reconnected, voila! bringup now works properly, and I get a boot log

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
>

I looked through errlog, and noticed something new
Code: 
ofst[ 44]:err_code:0xa0061004, clock:0xffffffff
ofst[ 48]:err_code:0xa0093003, clock:0xffffffff

1004 maps out to AC/DC POWER FAIL. I'm going to test the IC's on the DC-DC diagram (page 26 in the service guide) and see if something is amiss there. Or maybe I should be checking elsewhere? For 3003, I'm guessing the failure will be somewhere on VRM for BE (page 24), which also include the infamous nec/tokins...
Click to expand...
 
db260179 said:
I cant see that in the guide? - it clearly states Motherboard RX goes to UART RX and Motherboard TX to TX UART?

Please point that in the guide out if you could
Thanks
Click to expand...

I learn that Tx UART (or other communication process) goes to Rx host and the Rx UART goes to Tx host.
On guide seems that TX UART goes to TX motheboard, it is in a table on page 6, that's what I interpreted.
 
@db260179 I knew what means a A0101002 error, I thoughts if you knew the specific problem, same like 3034. All RSX voltages are Ok.

This is my bringup and powerstate
> 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
> powerstate
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD
Boot Loader SE Version 1.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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
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]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
Click to expand...
 
Could you post your errlog, remember after bringup, press the enter key again as it show the remaining last few lines.

I've not seen this error before, but i would say the RSX ram chips are not happy.

You will need to use a multimeter and measure the resistance around RSX chip

https://i.imgur.com/aMdAqNb.jpg

Also check the voltages in the service manual

LSL said:
@db260179 I knew what means a A0101002 error, I thoughts if you knew the specific problem, same like 3034. All RSX voltages are Ok.

This is my bringup and powerstate
Click to expand...
 
db260179 said:
Could you post your errlog, remember after bringup, press the enter key again as it show the remaining last few lines.

I've not seen this error before, but i would say the RSX ram chips are not happy.

You will need to use a multimeter and measure the resistance around RSX chip

https://i.imgur.com/aMdAqNb.jpg

Also check the voltages in the service manual
Click to expand...

A little introduction before answer! I am a console collector's, my favourite PS3 model is the 4 usb model.
I've in my collection:
  • 5x PS3 CECHA
  • 1x PS3 CECHB
  • 2x PS3 CECHE
  • 1x PS3 CECHH
And I've some boards that was danified with tryng resolve YLOD.

Yesterday was my first time with SYSCON internal commands, before I use only external command, like errlog get [index].
I've the error list:
  • A0201001/A0901001 - 2 boards
  • A0403034 - 1 placa**
  • A0232102 - 2 boards
  • A0202120 - 2 boards
  • A0101002/A0061002/A0801002 - 4 boards
  • A0093004 - 4 boards
Is very important analyse voltages on the board. In error xxxx3034 it's sure pin 7(IC6201 - CECHA service Manual) stay 0V. This normal voltage is 3.3v. Before use SYSCON commands I analised the voltage of one board and identified a short in HDMI IC, when I used SYSCON command errlog I got a A0202120(HDMI Error (IC2502)).

** This PS3 had a A0403034 with a 1.5 seconds YLOD, but I pressured RSX's bottom and now it has a error xxxx1002 with a 5 seconds YLOD.

Bringup error xxxx1002
Code: 
>
[SSM] state: 0000 -> 0101
Bringup Mode #0 (0xFF)
[SSM] ssmCb_OnStartingBePowOn() called.
[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.0.0 (Build ID: 1673,16934, Build Data: 2006-10-30_12:39:57)
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
POWER Button released
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SSM] *** Power Fail RS ***
[SSM] state: 0400 -> 0700
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0801002
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)

[mullion]$

errlog error xxxx1002
Code: 
errlog
ofst[ 32]:err_code:0xffffffff, clock:0x0b4887c1  2005/12/31 00:05:21
ofst[ 36]:err_code:0xa0801002, clock:0x0b4887ce  2005/12/31 00:05:34
ofst[ 40]:err_code:0xa0801002, clock:0x0b48884f  2005/12/31 00:07:43
ofst[ 44]:err_code:0xa0801002, clock:0x0b488881  2005/12/31 00:08:33
ofst[ 48]:err_code:0xa0801002, clock:0x0b488890  2005/12/31 00:08:48
ofst[ 52]:err_code:0xa0801002, clock:0x0b48889f  2005/12/31 00:09:03
ofst[ 56]:err_code:0xa0801002, clock:0x0b4888aa  2005/12/31 00:09:14
ofst[ 60]:err_code:0xa0801002, clock:0x0b4888b5  2005/12/31 00:09:25
ofst[ 64]:err_code:0xa0801002, clock:0x0b4888bc  2005/12/31 00:09:32
ofst[ 68]:err_code:0xa0801002, clock:0x0b4888c9  2005/12/31 00:09:45
ofst[ 72]:err_code:0xa0801002, clock:0x0b4888d8  2005/12/31 00:10:00
ofst[ 76]:err_code:0xa0801002, clock:0x0b488972  2005/12/31 00:12:34
ofst[ 80]:err_code:0xa0801002, clock:0x0b488997  2005/12/31 00:13:11
ofst[ 84]:err_code:0xa0801002, clock:0x0b488a0f  2005/12/31 00:15:11
ofst[ 88]:err_code:0xa0801002, clock:0x0b488a22  2005/12/31 00:15:30
ofst[ 92]:err_code:0xa0801002, clock:0x0b488a2c  2005/12/31 00:15:40
ofst[ 96]:err_code:0xa0801002, clock:0x0b488a37  2005/12/31 00:15:51
ofst[100]:err_code:0xa0801002, clock:0x0b488aac  2005/12/31 00:17:48
ofst[104]:err_code:0xa0801002, clock:0x0b488ab4  2005/12/31 00:17:56
ofst[108]:err_code:0xa0801002, clock:0x0b488b1a  2005/12/31 00:19:38
ofst[112]:err_code:0xa0801002, clock:0x0b488b34  2005/12/31 00:20:04
ofst[116]:err_code:0xa0801002, clock:0x0b488ba8  2005/12/31 00:22:00
ofst[120]:err_code:0xa0801002, clock:0x0b488bb4  2005/12/31 00:22:12
ofst[124]:err_code:0xa0801002, clock:0x0b488bc3  2005/12/31 00:22:27
ofst[  0]:err_code:0xa0801002, clock:0x0b488680  2005/12/31 00:00:00
ofst[  4]:err_code:0xa0801002, clock:0x0b488680  2005/12/31 00:00:00
ofst[  8]:err_code:0xa0801002, clock:0x0b488680  2005/12/31 00:00:00
ofst[ 12]:err_code:0xa0801002, clock:0x0b488680  2005/12/31 00:00:00
ofst[ 16]:err_code:0xa0801002, clock:0xffffffff
ofst[ 20]:err_code:0xa0801002, clock:0xffffffff
ofst[ 24]:err_code:0xa0801002, clock:0xffffffff
ofst[ 28]:err_code:0xa0801002, clock:0x0b488680  2005/12/31 00:00:00
[mullion]$

Sorry my bad english. I'm not fluent in English
 
No problem with language, i understand you so no need to worry.

So pin 7 on IC6201 will be 0v when it detects a power fail to the RSX chip, thats a sympton not the cause.

Error A0403034 will be most likely a dried BGA solder point - if you can do a reflow on the RSX chip on the board that has this error and the fact you have pushed down proves a bad joint.

So as your boards seemed to have alot of power fails, you will need to validate from the service manual the - 12v, 5v and 3.3v on each main power IC's

IC6202 and IC6203 are IC Buck regulators, these are important to the flow of voltage and current to the RSX chip - you need to make sure they are getting the correct voltage readings. Underneath the board there are two silver pins - test points
When you power on, use a multimeter and check they read 5v.

Now check the IC's - IC6003 and IC6301 validate on the little test pins correct readings, usually 1.2v, 2.4v etc etc
Also Q6002 check 12v and 5v

Next most important area for power fails on this board - Q6305 Q6304 Q6303 Q6302 Mosfets, these will give one of the errors you a showing.

These IC areas are the main power functions - so identify the voltage points. When i get time i will do a photo edit of what voltages are expected on the power IC's. For now just look at the service manual.

LSL said:
A little introduction before answer! I am a console collector's, my favourite PS3 model is the 4 usb model.

Is very important analyse voltages on the board. In error xxxx3034 it's sure pin 7(IC6201 - CECHA service Manual) stay 0V. This normal voltage is 3.3v. Before use SYSCON commands I analised the voltage of one board and identified a short in HDMI IC, when I used SYSCON command errlog I got a A0202120(HDMI Error (IC2502)).

** This PS3 had a A0403034 with a 1.5 seconds YLOD, but I pressured RSX's bottom and now it has a error xxxx1002 with a 5 seconds YLOD.


Sorry my bad english. I'm not fluent in English
Click to expand...
 
db260179 said:
Could you post your errlog, remember after bringup, press the enter key again as it show the remaining last few lines.
Click to expand...

I think it's better to turn on the PS3 via the button and press enter on the terminal. The information appears in full.

I use openSuse OS!
 
db260179 said:
So pin 7 on IC6201 will be 0v when it detects a power fail to the RSX chip, thats a sympton not the cause.
Click to expand...

These ICs detects a power fail from CELL or RSX in which pin? pins 5 and 11?

When I met @marciolsf whe started do capture some signals. I captured signal of pins:
  • 5 (VFFB)
  • 7 (POWERGOOD)
  • 8 (DRVON)
  • 18 (Gate 4)
  • 19 (Gate 3)
  • 20 (Gate 2)
  • 21 (Gate 1)
  • 29 (ENABLE)
https://imgur.com/a/HqTHsOf (line white a PS3 functional, line blue this PS3 with xxxx1002)

And separated I analised pins 1,2,3,30,31 and 32, because this binary combination indicates the voltage value that detects powergood.
 
db260179 said:
You will need to use a multimeter and measure the resistance around RSX chip

https://i.imgur.com/aMdAqNb.jpg

Also check the voltages in the service manual
Click to expand...

I analised one of PS3's with error xxxx3004 and the resistances are almost the same, except one. Where is 44 Ohm in my board is 0 Ohm. The interesting thing is that the RSX has all the voltages.

We can't say that RSX is dead, because this line(+1.2_YC_RC_VDDIO) is source to CELL, SouthBridge, XDR ram, IC6303 and various capacitors in series with this line. I will waste a long time with this board. This PS3 goes to the end of the queue.

I used an adjustable DC power supply, set 1.0v and 500mA. Power supply indicated short on the line and I increased to 1A, still short, but when I increased to 1.2A theres no short. I will beginning remove IC6303, if still short to ground I will remove the capacitors. I don't get BGA rework machine.
 
You must log in or register to reply here.

Similar threads

Back
Top