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

[RIP-Felix]

Did you reball the Cell on that E01 or in the process? I see you tried the video encoder and it didn't clear up the 1701 like it did for that last A01. Too bad! It's never that easy, huh?

BTW, I've always suspected that the CELL BGA should be showing more dammage since it experiances higher Delta T's than does the RSX. Perhaps it doesn't experience as many or varied duty/thermal cycles as the RSX, but it's gotta be brittle and susceptible to thermal cracks during a reball. I wouldn't be surprised if it needs reballed at the same time to ensure long term reliability.

 

[squeept]

Yep, reballed last night even though my stencil was bent and I had to place like 50% of the balls by hand.

Just swapped around the error codes to some of the old ones in the log.

 

[RIP-Felix]

I'm curious about the A01 you started today, with 1001, 1601, and 1701 on the errorlog old. Do you mean the history of old logs? As in it's currently only giving a 3034, but gave those before? Were there days, weeks, or months between errors in the timecode?

 

[squeept]

Yes, the current error(s) goes in their own box, and anything else I find in the previous error list I put in the troubleshooting notes. I stay on external mode because I'm slightly dyslexic so I don't want to typo any of the patching stuff and bork something. I just do "ERRLOG GET xx" over and over. It doesn't give the dates that way, so I just mind the order.

 

[squeept]

Spending NYE in the shop 'cause of 'rona. Debating whether I should even put this one in to the spreadsheet.....

I think they used toothpaste as flux....

 

[squeept]

Spreadsheet has a decent amount of new data. You'll also notice a trend forming (that holds pretty damn well from my memory): once someone gets at it with a heatgun, it can't be fixed. 3 for 4 on warranty seals, 0 for 3 without. I try to only buy warranty sealed consoles, but sometimes the deal is too good to pass up.

Now, you can interpret that one of two ways. Either these were the unfixable consoles that already had a dead GPU and the heatgun is innocent, or the heatgun is the murderer. I think you know where I stand on the issue.

Which got me to thinkin'... when I see previous rework, I nudge the chip a little early to check if it was reballed with lead. I've only ever seen a handful come through that have been previously reballed. Just some more food for thought.

 

[nyislander]

Model: CECHA01
SYSCON Error : a0213013

From post #1 of this thread : "A0213013 BE_SPI DI/DO ERROR - CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead?"

Visual inspecting of the board yields nothing obvious. It does not look like it was heat gunned/reflowed/reballed. I checked voltages and found 0.0V at JL6354-JL6361 pts in the schematic (pg. 26). +3.3V_MISC & +5V_MISC are verified working.

Does the SYSCON need to tell the IC's in this part of the circuit to "turn -on"? Does a dead CELL cause this condition or should I look elsewhere?

 

[Arin]

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!!!

NOT all PS3 boards have the known serial connection or capability to connect!!
So far - COK-001,002, SEM-001 and DIA-001,002 can be connected

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

Further changes are in the git repo

https://github.com/db260179/ps3syscon

Please contribute on this git repo in the issues section
New error messages, python script improvements
NOT PERSONAL SUPPORT ISSUES!

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:

POWER ERRORS:

0003001 POW_FAIL

A0093004 RSX_POW_FAIL

A0201B02 RSX VRAM FAIL - Faulty vrams (core would read a 0.2 ohm reading)

A0093003 CELL_POW_FAIL

BE ERRORS:

A0213013 BE_SPI DI/DO ERROR - CELL not communicating to syscon via SPI (1.2V MC2_VDDIO and 1.2V BE_VCS no output) = Possible shorts on the line, check C4001 and trailing caps. Possible CELL dead?

A0213011 BE_SPI CS ERROR

A0203010 BE_INIT OR BE_POWGOOD OR CLOCK ERRORS

A0801200 CELL overheating - poor thermal paste or no heatsink attached

RSX ERRORS:

A0404002 RSX_SPI DI/DO ERROR

A0404411 - ERROR ON RSX SPI?

A0A02031 - Thermal monitor DI/DO not communicating to RSX (possible dead Diodes in RSX)

A0403034, A0404402,A0404411 - Poor BGA solder connections for RSX ( you will see errors like - [POWERSEQ] Error : BitTraining RSX:RRAC:RX0:GLOBAL1:RX_STATUS )

A0232102 - IC6301 faulty (1.5v RSX_VDDIO) or in that area

SB ERRORS:

A0302203 SB_SPI DI/DO ERROR

A0313032 SB_CLOCK OR INIT ERROR

A0902203 SB GLOD issues, system update to repair nand/nor hashes


OTHERS:

A0022110 MK I2C ERROR (OR OTHER CLOCK's ERRORS)

A0401001 - BE VRAM Power Fail. It can be NEC Tokins

A0401002 - RSX VRAM Power Fail. It can be NEC Tokins

A0402120 - HDMI Error (IC2502)

A0401301 - BE PLL Unlock

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

Look at the git repo - 'syscon error log codes.pdf'

Am I doing something wrong? I have putty, python 2.7 the serial and crypto modules. its wired correctly for external mode. I believe the UART is showing as COM3. I'm new at this and been getting nowhere for weeks. any help is appreciated.

 

[RIP-Felix]

I had to uninstalled every installation of python I had. Then I installed Python 2.7.18 fresh, checking the box to add it to the PATH during installation. Then I opend a wondows CMD prompt and performed a "pip install pycryptodome", which installed sucessfully. It informed me of a pip update and gave me a command to run it, which I did successfully. Then I performed the "pip install pyserial", which completed sucessfully. After that, I was finally able to use change the directory and run the script successfully. It greeted me with >$ instead of the previous error messages.

It looks to me like your are tying to use phthon or putty to communicate with the PS3. Just use the CMD prompt as an adminstrator.

 

[Arin]

I had to uninstalled every installation of python I had. Then I installed Python 2.7.18 fresh, checking the box to add it to the PATH during installation. Then I opend a wondows CMD prompt and performed a "pip install pycryptodome", which installed sucessfully. It informed me of a pip update and gave me a command to run it, which I did successfully. Then I performed the "pip install pyserial", which completed sucessfully. After that, I was finally able to use change the directory and run the script successfully. It greeted me with >$ instead of the previous error messages.

It looks to me like your are tying to use phthon or putty to communicate with the PS3. Just use the CMD prompt as an adminstrator.

Ok I think I'm getting closer but I'm getting this am I typing something in wrong?

 

[squeept]

COM3 and CXR just plain text, no other garbage around them:
python filename.py COM3 CXR

And use the 32 bit Python, even if you have a 64 bit system.

And I have a little ADHD, so I renamed the file to just serial.py so I don't forget what I'm typing by the end of typing it. Obviously that's optional, but other people might be as dumb as me...

 

[DeadEnd]

That's just another result of the ambiguous steps in the guide. It says something like "You need python". No mention how to install it or that after installing, it magically integrates into the command line of Windows and that's all you're going to need... I think we need to just make some kind of a thread or guide v2 that is more comprehensive and is meant for Windows users. I myself would do it, but I have a lot on my plate atm.

 

[db260179]

That's just another result of the ambiguous steps in the guide. It says something like "You need python". No mention how to install it or that after installing, it magically integrates into the command line of Windows and that's all you're going to need... I think we need to just make some kind of a thread or guide v2 that is more comprehensive and is meant for Windows users. I myself would do it, but I have a lot on my plate atm.

I've updated this first page, Linux OS is the supported os to follow this guide.

If anyone wants to add a pull request to add windows instructions, then feel free will gladly add it.

Sorry, but i don't use windows and have no interest in fire fighting its wonderful issues it has.

 

[shawly]

Can nobody tell me how this guy found the necessary pads on a DYN-001 board?

Bump

 

[db260179]

Can nobody tell me how this guy found the necessary pads on a DYN-001 board?

He doesn't say he has, quoted from him ' so I want to see the syscon error log before I go into the NEC-TOKIN replacement endeavor.'

Usually the serial points are underneath the syscon chip, just probe with a multimeter, find the 3.3v or 1.5v. Some newer boards dont expose the uart ports, so probably why its not documented.

 

[shawly]

He doesn't say he has, quoted from him ' so I want to see the syscon error log before I go into the NEC-TOKIN replacement endeavor.'

Well since he already tried running the python script I assumed that he already connected the pads to his serial adapter, why would he try to run the script without connecting the pads?

 

[vyktormvmpay25]

I will come with pads for DYN now if they are not reported.

Not sure which one is Rx and Tx atm it was just quick response with multimeter. This are pins. On SW syscon you need python script from Major and only RX. TX GND from UART to mobo. auth and see what you can get. Swap RX/Tx when get Auth1 error.
What mobos do we need? 2500 is on thread for syscon firmware.
Someone should update pins for mobos after we know they work. I will test dyn001 after reball. I have rsx with artefacts and curious what will say to errlog.

 

[db260179]

I will come with pads for DYN now if they are not reported.

Not sure which one is Rx and Tx atm it was just quick response with multimeter. This are pins. On SW syscon you need python script from Major and only RX. TX GND from UART to mobo. auth and see what you can get. Swap RX/Tx when get Auth1 error.
What mobos do we need? 2500 is on thread for syscon firmware.
Someone should update pins for mobos after we know they work. I will test dyn001 after reball. I have rsx with artefacts and curious what will say to errlog.

Thanks for the pics, I will update my git repo with the newer script and a cropped version of this picture.

 

[vyktormvmpay25]

First test to see which exactly is Rx and Tx.
Edit
Testing dyn001 and got successfully auth.
I had to try multiple times to get auth working and changed my com port to 115200. It is a issue with default speed on 9600. Testing on win7 64bits.

This is normal? This unit starts normally and goes in games. Reballed twice different rsx and still same results with artefacts.
Now I may try eep get 40 by 40.

 

[RIP-Felix]

Spoiler: Before I saw the "SW" mode he's using

Is that internal (CXRF) or external mode (CXR)? I think I got a return something like that when running an internal command in external mode. I like to run the console until it errors, YLOD or whatever. Then while its flasing run a "lasterrlog" in internal (CXRF) mode. It provides more info about the current error. For example:

Also, could you document which pad is which on the motherboard (RX/TX). When you look at your USB to identify which wire goes where, don't forget that the receive (RX) on your USB is connected to the Motherboard's transmit (TX).

EDIT: just noticed you're in "SW" mode. What is that?