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

You were right marciolsf! It was the PS6001 fuse.

I replaced it with one from a scrap board and after I cleared the errors it now shows this:
Code: 
nyislander:~/Desktop/PS3_Files$ python ps3_syscon_uart_script.py /dev/ttyUSB0 CXRF
>$ auth
Auth successful
>$ disp_err
disp_err
CheckStop:     None
PLLUnlock:     0
RSX Int:       None
PowerSeq:      00
[mullion]$
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[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]$

I partially reassembled it and connected to my TV. Front panel power on and the green led stays on but there is no video using HDMI/component cable. The fan starts slow then steps up high - I only have it on for ~30secs.

Could it be a corrupt NAND? I believe the last person to work on this board was trying to marry a BD to it. Would it be possible to read the NANDs with a Teensy++ and repair them? If repairing the NANDs is possible - it might be easier to remove them from the board to flash because some of the solder points are hard to reach on the COK-001. I always had problems using the X360 clip. I would use a TSOP48 to DIP48 adapter connected to the Teensy++.

I welcome all your comments/suggestions.
 
Well done!

Forgot that AUTH is case sensitive - doh!

Cant see your attachment for some reason?

nyislander said:
Thank you db260179 & LSL.

First thing I tried worked - swapping TX and RX. Using AUTH/auth doesn't matter.

My PS3 mother board is a CECHA 1-871-868-32. To allow internal mode I changed:
>$ EEP GET 3961 01
00000000 FF
>$ EEP SET 3961 01 00
00000000
>$ EEP GET 3961 01
00000000 00

View attachment 27065

Then I grounded the "DIAG" pin, rebooted, fixed the checksum and listed the errors.
View attachment 27066
Error: 2110 Clock Generator Error (IC5001)
Guess I need to check around IC5001, bad components & VCC.

I also tried using "bringup" and the PS3 shutdown also immediately.
View attachment 27068
Click to expand...
 
OH my, i'm afraid you might have a faulty southbridge.

to check that, look at the back of the network and audio tsop connector see if the leds blink when coming out of standby. if not blinking then try measuring the test points around the southbridge. Any low resistance level - 0.6 means dead southbridge.

I've had a board that shows no syscon error codes but the southbridge was faulty - only tell tell sign was no led blinking and incorrect resistance values on the testpoints. The 2M values are the most important as thats the core of the southbridge

Heres photos of values on a working southbridge for COK-001 and 002

https://imgur.com/a/G7Egapc

You can put the board into tristate mode - two pins, Tristate and GND, this bypasses the southbridge - if the situation is the same then its a faulty southbridge.

nyislander said:
You were right marciolsf! It was the PS6001 fuse.

I replaced it with one from a scrap board and after I cleared the errors it now shows this:
Code: 
nyislander:~/Desktop/PS3_Files$ python ps3_syscon_uart_script.py /dev/ttyUSB0 CXRF
>$ auth
Auth successful
>$ disp_err
disp_err
CheckStop:     None
PLLUnlock:     0
RSX Int:       None
PowerSeq:      00
[mullion]$
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[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]$

I partially reassembled it and connected to my TV. Front panel power on and the green led stays on but there is no video using HDMI/component cable. The fan starts slow then steps up high - I only have it on for ~30secs.

Could it be a corrupt NAND? I believe the last person to work on this board was trying to marry a BD to it. Would it be possible to read the NANDs with a Teensy++ and repair them? If repairing the NANDs is possible - it might be easier to remove them from the board to flash because some of the solder points are hard to reach on the COK-001. I always had problems using the X360 clip. I would use a TSOP48 to DIP48 adapter connected to the Teensy++.

I welcome all your comments/suggestions.
Click to expand...
 
Last edited:
Thanks db260179. I will check the southbridge.

AUTH does not need to be in capital letters. Here is a re-post of post #179 with the missing attachments.

First thing I tried worked - swapping TX and RX. Using AUTH/auth doesn't matter.

My PS3 mother board is a CECHA 1-871-868-32. To allow internal mode I changed:
>$ EEP GET 3961 01
00000000 FF
>$ EEP SET 3961 01 00
00000000
>$ EEP GET 3961 01
00000000 00

Code: 
nyislander:~/Desktop/PS3_Files$ python ps3_syscon_uart_script.py /dev/ttyUSB0 CXR
>$ AUTH
Auth successful
>$ exit
nyislander:~/Desktop/PS3_Files$ python ps3_syscon_uart_script.py /dev/ttyUSB0 CXR
>$ auth
Auth successful
>$ EEP GET 3961 01
00000000 02
>$ EEP SET 3961 01 00
00000000
>$ exit

Then I grounded the "DIAG" pin, rebooted, fixed the checksum and listed the errors.

Code: 
nyislander:~/Desktop/PS3_Files$ python ps3_syscon_uart_script.py /dev/ttyUSB0 CXRF
>$ auth
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
sum:0x0100
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ w 39FE 38 0f
w 39FE 38 0f
w complete!
[mullion]$
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x52b7
Addr:0x000034fe should be 0x7115
Addr:0x000039fe should be 0x0f38
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff[
>$ errlog
errlog
ofst[ 36]:err_code:0xffffffff, clock:0xffffffff
ofst[ 40]:err_code:0xa0022110, clock:0xffffffff
ofst[ 44]:err_code:0xa0022110, clock:0xffffffff
ofst[ 48]:err_code:0xa0022110, clock:0xffffffff
ofst[ 52]:err_code:0xa0022110, clock:0xffffffff
ofst[ 56]:err_code:0xa0022110, clock:0xffffffff
ofst[ 60]:err_code:0xa0022110, clock:0xffffffff
ofst[ 64]:err_code:0xa0022110, clock:0xffffffff
ofst[ 68]:err_code:0xa0022110, clock:0xffffffff
ofst[ 72]:err_code:0xa0022110, clock:0xffffffff
ofst[ 76]:err_code:0xa0022110, clock:0xffffffff
ofst[ 80]:err_code:0xa0022110, clock:0xffffffff
ofst[ 84]:err_code:0xa0022110, clock:0xffffffff
ofst[ 88]:err_code:0xa0022110, clock:0xffffffff
ofst[ 92]:err_code:0xa0022110, clock:0xffffffff
ofst[ 96]:err_code:0xa0022110, clock:0xffffffff
ofst[100]:err_code:0xa0022110, clock:0xffffffff
ofst[104]:err_code:0xa0022110, clock:0xffffffff
ofst[108]:err_code:0xa0022110, clock:0xffffffff
ofst[112]:err_code:0xa0022110, clock:0xffffffff
ofst[116]:err_code:0xa0022110, clock:0xffffffff
ofst[120]:err_code:0xa0022110, clock:0xffffffff
ofst[124]:err_code:0xa0022110, clock:0xffffffff
ofst[  0]:err_code:0xa0022110, clock:0xffffffff
ofst[  4]:err_code:0xa0022110, clock:0xffffffff
ofst[  8]:err_code:0xa0022110, clock:0xffffffff
ofst[ 12]:err_code:0xa0022110, clock:0xffffffff
ofst[ 16]:err_code:0xa0022110, clock:0xffffffff
ofst[ 20]:err_code:0xa0022110, clock:0xffffffff
ofst[ 24]:err_code:0xa0022110, clock:0xffffffff
ofst[ 28]:err_code:0xa0022110, clock:0xffffffff
ofst[ 32]:err_code:0xa0022110, clock:0xffffffff
[mullion]$/CODE]

Error: 2110 Clock Generator Error (IC5001) 
Guess I need to check around IC5001, bad components & VCC.

I also tried using "[I]bringup[/I]" and the PS3 shutdown also immediately.
 
db260179 said:
OH my, i'm afraid you might have a faulty southbridge.

to check that, look at the back of the network and audio tsop connector see if the leds blink when coming out of standby. if not blinking then try measuring the test points around the southbridge. Any low resistance level - 0.6 means dead southbridge.

I've had a board that shows no syscon error codes but the southbridge was faulty - only tell tell sign was no led blinking and incorrect resistance values on the testpoints. The 2M values are the most important as thats the core of the southbridge

Heres photos of values on a working southbridge for COK-001 and 002

https://imgur.com/a/G7Egapc

You can put the board into tristate mode - two pins, Tristate and GND, this bypasses the southbridge - if the situation is the same then its a faulty southbridge.
Click to expand...
Hi
Where is the tristate pin on the cok-002 motherboard pls
 
Ok thanks. And no problem.

Also that imgur link i sent i've done a photo of my teensy +++ nand reader/writer setup using a 360 clip and regulator.
I've found connecting to a usb 3.0 slot gives enough power to do the teensy and the nand chip. But you need a good clamp to hold it down.

nyislander said:
Thanks db260179. I will check the southbridge.

AUTH does not need to be in capital letters. Here is a re-post of post #179 with the missing attachments.

First thing I tried worked - swapping TX and RX. Using AUTH/auth doesn't matter.
Click to expand...
 
I am working on another ps3 motherboard cok-002 and keep getting
Auth1 response invalid

I have looked at the wire, the solder points
Ive made sure it is connected right
Any ideas, please
 
db260179 said:
Ok thanks. And no problem.

Also that imgur link i sent i've done a photo of my teensy +++ nand reader/writer setup using a 360 clip and regulator.
I've found connecting to a usb 3.0 slot gives enough power to do the teensy and the nand chip. But you need a good clamp to hold it down.
Click to expand...

The network led flashes momentarily when coming out of standby then goes out. The COK-002 board is different than a COK-001 board. Can you share the COK-001 test points for the southbridge if you have them, otherwise I'll match them using the schematics.
https://drive.google.com/file/d/1tCYAQerZao7YMBPX10C1NHp0OJNHVDAk/view?usp=sharing

I will ground the Tristate and check the network led.

I have a similar Teensy++ setup. I've dremeled the X360 clip to fit over the smd components near the NANDs & applied too much pressure in the past so it now it does not work at all and that's why I might just remove the NANDs and use a TSOP48 to DIP48 adapter connected to the Teensy++.
 
OK, so part of your southbridge is working, you will still need to do the resistance checks as it could be the hdd controller not getting data. Does your hdd flash when you get out of standby.

Your nands could be at fault as well? - so try that path.

I dont have a COK-001 board, but the values should be similiar? - just work on judgement that no Mega ohms means the core is not good.

Hopefully someone that has a COK-001 board can do the resistance check on the test points and share here!

nyislander said:
The network led flashes momentarily when coming out of standby then goes out. The COK-002 board is different than a COK-001 board. Can you share the COK-001 test points for the southbridge if you have them, otherwise I'll match them using the schematics.
https://drive.google.com/file/d/1tCYAQerZao7YMBPX10C1NHp0OJNHVDAk/view?usp=sharing

I will ground the Tristate and check the network led.

I have a similar Teensy++ setup. I've dremeled the X360 clip to fit over the smd components near the NANDs & applied too much pressure in the past so it now it does not work at all and that's why I might just remove the NANDs and use a TSOP48 to DIP48 adapter connected to the Teensy++.
Click to expand...
 
nyislander said:
The network led flashes momentarily when coming out of standby then goes out. The COK-002 board is different than a COK-001 board. Can you share the COK-001 test points for the southbridge if you have them, otherwise I'll match them using the schematics.
https://drive.google.com/file/d/1tCYAQerZao7YMBPX10C1NHp0OJNHVDAk/view?usp=sharing

I will ground the Tristate and check the network led.

I have a similar Teensy++ setup. I've dremeled the X360 clip to fit over the smd components near the NANDs & applied too much pressure in the past so it now it does not work at all and that's why I might just remove the NANDs and use a TSOP48 to DIP48 adapter connected to the Teensy++.
Click to expand...
The file is locked
 
ps3xbox said:
I am working on another ps3 motherboard cok-002 and keep getting
Auth1 response invalid

I have looked at the wire, the solder points
Ive made sure it is connected right
Any ideas, please
Click to expand...

Shut off the rear power to the motherboard. Exit from the python script. Swap the TX & RX connectors coming from the PC to the motherboard. Power up the motherboard from the rear, execute the python script and type "auth".
 
nyislander said:
Shut off the rear power to the motherboard. Exit from the python script. Swap the TX & RX connectors coming from the PC to the motherboard. Power up the motherboard from the rear, execute the python script and type "auth".
Click to expand...
Perfect That worked

Which command do I run to get the codes please
 
This is My log
>$ 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]$
>$ 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] fatalreq delayed.
[ERROR]: 0xa0051004
[SSM] fatalreq delayed.
[ERROR]: 0xa0071002
[SSM] state: 0101 -> 0301
[SSM] *** Power Fail RS ***
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093003
>$
 
ps3xbox said:
[ERROR]: 0xa0051004
[SSM] fatalreq delayed.
[ERROR]: 0xa0071002
[SSM] state: 0101 -> 0301
[SSM] *** Power Fail RS ***
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093003
Click to expand...

1002 → Probably RSX NECs
1004 → When Power On but something causes Power to fail, for example touching some components on the board, especially near the Power / Reset board connector (COK-001 / COK-002)
3003 → Power CELL or probably CELL NECs
 
You must log in or register to reply here.

Similar threads

Back
Top