DeadEnd
Senior Member
I'm not sure if it's been shared yet, but I've posted across various threads that sometimes reading south bridge log can give a few extra hints towards a solution in ps3 fault search. So I decided to share some of the sitations I've come across where it has been helpful along with a few other cases I've repaired.
As always, I happen to work the most on COK-001/002 boards so this is what you need to do to read the log (Click on the spoiler to see the guide).
So what can you get from it ? Well, you can see a booting sequence and what is going on with the system. It can be useful if you have a GLOD and the system seemingly boots, but nothing is displayed. It can also be useful if you have a longer YLOD, where the system nearly booted but then shut down , because some information could still be displayed in the bootloader.
Example 1. I had a console with the following errors. The system nearly booted but then shutdown because of BE livelock condition. (This example was explained in greater detail in the nectokin thread, but here I just want to point out how SB logs can be helpful ).
View attachment 39284
Reading South Bridge output and comparing it to a working console revealed that the damaged board would shut down at the RSX detection step. it's a step where FlexIO Core must be functioning correctly in order to allow detection.The voltage responsible for the FlexIO core is RSX_VDDR, so further diagnostics revealed that this voltage was faulty and outputted 1.6v instead of 0.95 v (Because I swapped the ps3 in question with the 40nm chip, normally it would be 1.2v for 90nm chips ).
View attachment 39285
I'll post more examples later...
As always, I happen to work the most on COK-001/002 boards so this is what you need to do to read the log (Click on the spoiler to see the guide).
- For regular (with stock syscon 201/202 chips) COK-001/002, connect with UART to syscon and enter "w 7202 2" It should say that the write was a success. Turn off the machine and then solder UART wires according to the images below. Remember, you cannot send anything so you only need to connect an RX wire for receiving data and ground.
- The SB log activating command is different for models using later syscons. So for instance Sony refurbished 65 or 40nm COK-001/002 models would have a syscon 303/304, so the command for it is "W 4202 2 ". Same applies for SEM-001 and DIA-00x boards.
- Then connect with Putty or any other terminal reading tool using Serial setting, specify the port of your UART , speed is 115200 baud.
- For COK-001
- For COK-002
So what can you get from it ? Well, you can see a booting sequence and what is going on with the system. It can be useful if you have a GLOD and the system seemingly boots, but nothing is displayed. It can also be useful if you have a longer YLOD, where the system nearly booted but then shut down , because some information could still be displayed in the bootloader.
Example 1. I had a console with the following errors. The system nearly booted but then shutdown because of BE livelock condition. (This example was explained in greater detail in the nectokin thread, but here I just want to point out how SB logs can be helpful ).
View attachment 39284
Reading South Bridge output and comparing it to a working console revealed that the damaged board would shut down at the RSX detection step. it's a step where FlexIO Core must be functioning correctly in order to allow detection.The voltage responsible for the FlexIO core is RSX_VDDR, so further diagnostics revealed that this voltage was faulty and outputted 1.6v instead of 0.95 v (Because I swapped the ps3 in question with the 40nm chip, normally it would be 1.2v for 90nm chips ).
View attachment 39285
I'll post more examples later...
