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

[M13k0_27]

No can be done in external mode

ERRLOG CLEAR

ERRLOG GET 0

I've just done ERRLOG CLEAR and now I only get 3034 and 4001 (both CELL related), so I fixed all the power faults correctly... What do you suggest me to do now? (I have already changed one nec/tokin).
ps
this girl was already "reflowed" by someone before I got it and I really don't know how he did this.

 

[sandungas]

...
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56c7
Addr:0x000034fe should be 0x980c <--- this is the "thermal config" area
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
...

Interesting, this DIA-001 motherboard have a "thermal config" not documented before
Incase you was not aware of it, we can identify the whole "thermal config" area by his checksum (the value that can be seen in the output of the "eepcsum" command at "Addr:0x000034fe")
I was doing some graphs, as you can see i dont have any sample of the thermal config that "should be 0x980C" https://www.psx-place.com/threads/syscon-fan-settings-coordinate-graphs.31188/

So... can you make me a favour and dump that "thermal config" area ?, i think it can be made by running the command:

>$ r 3300 200

Just to be clear... is a "read" command, and the data in that area is generic (doesnt contains any private info) so no worry, is safe
Is going to display lot of bytes, please copypaste them and post them in the forum

 

[RIP-Felix]

UPDATE on a different DIA-001. This DIA-001 had ylod never been touched. The error codes were 3034 and 4322. I did a reflow of the RSX and it came to life. Appears to confirm 3034 to be RSX related. I wonder if I remove the RSx chip whether the 3034 will come back or it will be a different error at this point. My next step is to do internal commands on this live board to see what's what. I'll also test resistance etc since it's a working DIA-001. Hoping it can give me insight into my other DIA-001 with the 22110 error

Well, according to the error code list 20 2110 is a clock generator on IC5001. There is a crystal X5001 that's supposed to be 14.31818MHz. You'd probably need an oscilloscope to verify it though. I suppose you could just replace it if you have a spare. That's where my mind goes immediately, since the "20" 2110 is early in the startup sequence, which I would expect if there was a faulty crystal. It should be pretty easy to find, they have a unique shape. Before that, you could try touching up the pins to rule out cold solder joints and multimeter all the caps, ferite beads, fuses, resistors in the area and replace as necessary. Once they're all good, you could try replacing crystal, and if that doesn't work, IC5001 itself.

 

[k24a1]

Well, according to the error code list 20 2110 is a clock generator on IC5001. There is a crystal X5001 that's supposed to be 14.31818MHz. You'd probably need an oscilloscope to verify it though. I suppose you could just replace it if you have a spare. That's where my mind goes immediately, since the "20" 2110 is early in the startup sequence, which I would expect if there was a faulty crystal. It should be pretty easy to find, they have a unique shape. Before that, you could try touching up the pins to rule out cold solder joints and multimeter all the caps, ferite beads, fuses, resistors in the area and replace as necessary. Once they're all good, you could try replacing crystal, and if that doesn't work, IC5001 itself.

you sir just gave me a wonderful idea; one of my COK-001 boards may POSSIBLY start working if i replace the crystal

Sent from my SM-G965F using Tapatalk

edit: still won't work

 

[Kleon1876]

Interesting, this DIA-001 motherboard have a "thermal config" not documented before
Incase you was not aware of it, we can identify the whole "thermal config" area by his checksum (the value that can be seen in the output of the "eepcsum" command at "Addr:0x000034fe")
I was doing some graphs, as you can see i dont have any sample of the thermal config that "should be 0x980C" https://www.psx-place.com/threads/syscon-fan-settings-coordinate-graphs.31188/

So... can you make me a favour and dump that "thermal config" area ?, i think it can be made by running the command:

>$ r 3300 200

Just to be clear... is a "read" command, and the data in that area is generic (doesnt contains any private info) so no worry, is safe
Is going to display lot of bytes, please copypaste them and post them in the forum

I'll get this to you soon.

 

[Kleon1876]

This is a SEM-001 board. It is missing the RSX chip. I have also replaced a set of tokins with caps (with bridges) on the bottom of the board. There is a possibility this board has a defective CPU as well (i think i might have cut into the chip when deliding). Anyway, here are some findings as they related to possible PSU related error 3001/3003. What are your thoughts?
c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXRF
>$ auth
Auth successful
>$ errlog
errlog
ofst[ 16]:err_code:0xffffffff, clock:0xffffffff
ofst[ 20]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 24]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 28]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 32]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 36]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 40]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 44]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 48]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 52]:err_code:0xa0093003, clock:0xffffffff
ofst[ 56]:err_code:0xa0093003, clock:0xffffffff
ofst[ 60]:err_code:0xa0093003, clock:0xffffffff
ofst[ 64]:err_code:0xa0093003, clock:0xffffffff
ofst[ 68]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 72]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0093003, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 96]:err_code:0xa0a02031, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0093003, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0a02030, clock:0xffffffff
ofst[120]:err_code:0xa0a02031, clock:0xffffffff
ofst[124]:err_code:0xa0093003, clock:0xffffffff
ofst[ 0]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 4]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 8]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 12]:err_code:0xa0a02031, clock:0xffffffff
This is an errlog dump after simply connecting power cord and red light is on. It appears after unplugging console and pluging it back in, the console either resets or runs internal checks and finds 2030/2031 every time because....keep reading
[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] state: 0101 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0093003
The 3003 error has to be some type of a power failure error (not a defective PSU unit). I have confirmed the PSU is a working unit. Note that at this point the PSU is connected into the PCB "forks" lol. All is connected as it should be including the white cable to from the PSU to the PCB.
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0600 -> 0000
[SSM] Error state is cleared.
(PowerOff State)
>$ exit
c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXRF
>$ auth
Auth successful
>$ errlog
errlog
ofst[ 32]:err_code:0xffffffff, clock:0xffffffff
ofst[ 36]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 40]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 44]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 48]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 52]:err_code:0xa0093003, clock:0xffffffff
ofst[ 56]:err_code:0xa0093003, clock:0xffffffff
ofst[ 60]:err_code:0xa0093003, clock:0xffffffff
ofst[ 64]:err_code:0xa0093003, clock:0xffffffff
ofst[ 68]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 72]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0093003, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 96]:err_code:0xa0a02031, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0093003, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0a02030, clock:0xffffffff
ofst[120]:err_code:0xa0a02031, clock:0xffffffff
ofst[124]:err_code:0xa0093003, clock:0xffffffff
ofst[ 0]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 4]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 8]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 12]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 16]:err_code:0xa0093003, clock:0xffffffff
ofst[ 20]:err_code:0xa0093003, clock:0xffffffff
ofst[ 24]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 28]:err_code:0xa0a02031, clock:0xffffffff
After the 3003 error, I simply reconnected to the uart and did an errlog dump. It appears once i reconnected to the uart, the 2030/2031 errors immediately came back post 3003, meaning the the ps3 once connected to power runs its own internal checks and comes up on 2030/2031. I next took the PSU off the forks, but left the white cable from PSU connected to PCB. The red light was still on. I then attempted to start the ps3 and got the following.
>$ bringup
bringup
[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 -> 0301
[SSM] PowSeq Fail : Detected !
[SSM] state: 0301 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0003001
* It appears a PSU off the forks but still connected via white cable gives a 3001 error. My guess is if you get a 3001 error, then it must be defective PSU related.
>$
[mullion]$ [POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
>$ errlog
errlog
ofst[ 44]:err_code:0xffffffff, clock:0xffffffff
ofst[ 48]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 52]:err_code:0xa0093003, clock:0xffffffff
ofst[ 56]:err_code:0xa0093003, clock:0xffffffff
ofst[ 60]:err_code:0xa0093003, clock:0xffffffff
ofst[ 64]:err_code:0xa0093003, clock:0xffffffff
ofst[ 68]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 72]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 76]:err_code:0xa0003001, clock:0xffffffff
ofst[ 80]:err_code:0xa0003001, clock:0xffffffff
ofst[ 84]:err_code:0xa0093003, clock:0xffffffff
ofst[ 88]:err_code:0xa0093003, clock:0xffffffff
ofst[ 92]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 96]:err_code:0xa0a02031, clock:0xffffffff
ofst[100]:err_code:0xa0093003, clock:0xffffffff
ofst[104]:err_code:0xa0003001, clock:0xffffffff
ofst[108]:err_code:0xa0093003, clock:0xffffffff
ofst[112]:err_code:0xa0003001, clock:0xffffffff
ofst[116]:err_code:0xa0a02030, clock:0xffffffff
ofst[120]:err_code:0xa0a02031, clock:0xffffffff
ofst[124]:err_code:0xa0093003, clock:0xffffffff
ofst[ 0]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 4]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 8]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 12]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 16]:err_code:0xa0093003, clock:0xffffffff
ofst[ 20]:err_code:0xa0093003, clock:0xffffffff
ofst[ 24]:err_code:0xa0a02030, clock:0xffffffff
ofst[ 28]:err_code:0xa0a02031, clock:0xffffffff
ofst[ 32]:err_code:0xa0093003, clock:0xffffffff
ofst[ 36]:err_code:0xa0093003, clock:0xffffffff
ofst[ 40]:err_code:0xa0003001, clock:0xffffffff
[mullion]$
>$

 

[Kleon1876]

has anyone isolated the 3003 error and manually fixed it?

 

[MrYadro]

So I've been messing with golang because for some reason not everyone could install python and run scripts on it (No offence) But everyone could run binary file.

I would like to help me with testing go-ps3syscon POC on windows and linux for now it just makes proper auth and prints becount. If you could connect to your PS3 in CXRF mode (because it's easier to implement) just PM me and we can sort this out!

Sent 8 bytes
Read 18 bytes
Successfully opened syscon
SC_READY
Sent 130 bytes
Read 260 bytes
Right response length
Right Auth1 response header
Right Auth1 response body
Sent 130 bytes
Read 283 bytes
Auth successful
Sent 9 bytes
Read 101 bytes
Bringup : 4038 times
Shutdown: 4001 times
Power-on: 371day 22hour 38min 54sec

 

[Kleon1876]

Interesting, this DIA-001 motherboard have a "thermal config" not documented before
Incase you was not aware of it, we can identify the whole "thermal config" area by his checksum (the value that can be seen in the output of the "eepcsum" command at "Addr:0x000034fe")
I was doing some graphs, as you can see i dont have any sample of the thermal config that "should be 0x980C" https://www.psx-place.com/threads/syscon-fan-settings-coordinate-graphs.31188/

So... can you make me a favour and dump that "thermal config" area ?, i think it can be made by running the command:

>$ r 3300 200

Just to be clear... is a "read" command, and the data in that area is generic (doesnt contains any private info) so no worry, is safe
Is going to display lot of bytes, please copypaste them and post them in the forum

Here it is. What does this mean?

c:\Python27\Scripts>python ps3_syscon_uart_script.py COM3 CXRF
>$ auth
Auth successful
>$ eepcsum
eepcsum
Addr:0x000032fe should be 0x56c7
Addr:0x000034fe should be 0x980c
Addr:0x000039fe should be 0x7360
Addr:0x00003dfe should be 0x00ff
Addr:0x00003ffe should be 0x00ff
>$ r 3300 200
r 3300 200
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
-----------------------------------------------
33 40 43 48 4A 50 52 55 57 5A 5C 99 B3 FF FF FF
FF FF FF FF 00 4C 00 4D 00 4E 00 4F 00 50 00 51
00 52 00 53 00 54 00 55 00 56 00 57 00 58 00 5B
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 00 34
80 34 00 35 80 35 00 36 80 36 00 37 80 37 00 38
80 38 00 39 00 51 00 52 FF FF FF FF FF FF FF FF
FF FF FF FF 33 FF 01 00 FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
33 40 43 48 4A 50 52 55 57 5A 5C 99 B3 FF FF FF
FF FF FF FF 00 4E 00 4F 00 53 00 54 00 55 00 57
00 58 00 59 00 5A 00 5B 00 5C 00 5D 00 5E 00 61
FF FF FF FF FF FF FF FF FF FF FF FF 00 00 80 3B
80 3E 00 3F 80 3F 00 40 80 40 00 41 80 41 00 42
80 42 00 43 80 55 00 56 FF FF FF FF FF FF FF FF
FF FF FF FF 33 FF 01 00 FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
33 40 43 48 4A 50 52 55 57 5A 5C 99 B3 FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF 33 FF 01 00 00 FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF 00 4D 14 FF FF FF FF FF 81 FF 00 FF 00 FF
5A 00 5B 00 02 00 60 00 61 00 02 00 FF FF FF FF
FF FF 7D 00 7D 00 02 00 FF FF FF FF FF FF 81 FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0C 98

 

[Kleon1876]

I can confirm error code 3001 is bad PSU. Faulty power supply for sure. You might show the red light on but PSU is dead if you getting 3001.

Also, I can confirm 3034 is straight RSX related.I had the ylod that returned 3034/4322. I did a reflow and the console came back indicating the errors to be RSX related. It could be the come in a set meaning when you get 3034 then you get 4322. But I'm pretty sure 3034 is RSX and needs a reflow. Any other theories on this? Has anyone had a 3034 that's not RSX related?

 

[sandungas]

Here it is. What does this mean?

Thanks, in a first check i can say this thermal config is something unique (very different than any other PS3 retail motherboard), ive seen some samples of DIA-00x motherboards and doesnt looks like this at all, the previous and next retail motherboard models doesnt looks like this either, and it doesnt matches either with another graph i made from a DECR-1400 (DEB-001 motherboard)

At this point i cant imagine why your motherboard have this thermal config values
But im thinking this should be one of the first DIA-001 motherboards manufactured, mostly because this detail im going to mention... sony was increasing the number of "fan steps"
COK-001, COK-002, and SEM-001 motherboards have 10 fan steps
DIA-001, DIA-002, and VER-001 have 16 fan steps

...but your DIA-001 (with csum 0x980C) have 14 fan steps, this means if we order them cronologically we should locate it in between the other groups i mentioned with 10 and 16

 

[sandungas]

@Kleon1876 can you run this 2 commands too please ?, this would help me when doing the image in photoshop

Spoiler

The "fantbl" command does some conversions to the hex values... the speeds are displayed as a percentage, and the temperaures are splitted as a decimal value
For other motherboard models i had to do this conversions with a calculator, is a pita and there is too much room for "human error", is a lot better and easyer for me if you show me the values converted by syscon

>$ fantbl get 0

And...

>$ fantbl get 1

Edit:
Btw, this DIA-001 motherboard was inside a CECHH PS3 model ? (or is a CECHJ or CECHK ?)

 

[Kleon1876]

I can confirm error code 3001 is bad PSU. Faulty power supply for sure. You might show the red light on but PSU is dead if you getting 3001.

@Kleon1876 can you run this 2 commands too please ?, this would help me when doing the image in photoshop

Spoiler

The "fantbl" command does some conversions to the hex values... the speeds are displayed as a percentage, and the temperaures are splitted as a decimal value
For other motherboard models i had to do this conversions with a calculator, is a pita and there is too much room for "human error", is a lot better and easyer for me if you show me the values converted by syscon

>$ fantbl get 0

And...

>$ fantbl get 1

Edit:
Btw, this DIA-001 motherboard was inside a CECHH PS3 model ? (or is a CECHJ or CECHK ?)

so it's interesting u say this. The first eepcsum dump I did was a DIA-001 CECHH01. That's the one you asked me to get info on since that 0x098 showed. Then I had another board DIA-001 again from a CECHL. I did the eepcsum on that and again saw the 0x098 so I thought ok well let me run the command you mentioned. So that's the info I put in the post from the second DIA-001 which is the CECHL. It looks like I have 2 of the same DIA-001. I'll get you the fantbl info soon.

Also, any ideas regarding my previous posts with 2030/2031 error? The board is missing an RSX. I'm thinking about reballing the chip back on. I wonder if I'm successful whether 2030/2031 will go away.

 

[k24a1]

i wonder if anyone has ever got 3034 on anything newer than a DIA-001... surprised my K01 still works with no reflowing crap done to it, just a delid and some arctic MX4 i did later on back in 2019

Sent from my SM-G965F using Tapatalk

 

[Kleon1876]

You ever correct 22110 error? If so what did you do.

just my luck... I shorted 17 and 18 on IC6003, and fried C6025... Testing that cap on the board gives me 0 ohms.

At least we get to add a few more error codes to the list.

The initial "bump" on 17-18 (The slip was during boot), and it triggered the following errors:
401001 - BE VRAM Power Fail
402120 - HDMI Error (IC2502)
401301 - BE PLL Unlick
Since all these errors are in the same step, I'm guessing they were triggered at the same time. I wasn't connected to syscon right then, unfortunately.

The second attempt, same pins during boot, only triggers 1 error, with a fast ylod
022110 - Clock Generator Error (IC5001).

Here's the full errlog (no time stamps on my board, somehow, I just never have them)

errlog
ofst[ 20]:err_code:0xffffffff, clock:0xffffffff
ofst[ 24]:err_code:0xa0403034, clock:0xffffffff
ofst[ 28]:err_code:0xa0403034, clock:0xffffffff
ofst[ 32]:err_code:0xa0403034, clock:0xffffffff
ofst[ 36]:err_code:0xa0403034, clock:0xffffffff
ofst[ 40]:err_code:0xa0403034, clock:0xffffffff
ofst[ 44]:err_code:0xa0403034, clock:0xffffffff
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff
ofst[ 56]:err_code:0xa0403034, clock:0xffffffff
ofst[ 60]:err_code:0xa0403034, clock:0xffffffff
ofst[ 64]:err_code:0xa0403034, clock:0xffffffff
ofst[ 68]:err_code:0xa0403034, clock:0xffffffff
ofst[ 72]:err_code:0xa0403034, clock:0xffffffff
ofst[ 76]:err_code:0xa0403034, clock:0xffffffff
ofst[ 80]:err_code:0xa0403034, clock:0xffffffff
ofst[ 84]:err_code:0xa0403034, clock:0xffffffff
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0401001, clock:0xffffffff
ofst[100]:err_code:0xa0402120, clock:0xffffffff
ofst[104]:err_code:0xa0401301, clock:0xffffffff
ofst[108]:err_code:0xa0403034, 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

The relationship between IC6003 and IC5001 isn't super obvious to me. Pin 46 on IC5001 is labelled SCLK, that's my best guess, but nothing else stands out to me. I mean, there's a good chance i just fried IC6003 altogether (pins 17, 18, 19 and 21 are all dead), but for now I'm hoping that replacing that tiny cap (0.1uf??) will bring things back to its previous state. Hopefully I have one in the scrap pile.

 

[marciolsf]

You ever correct 22110 error? If so what did you do.

There were two times that I shorted PWM pins while probing around the board, and I was able to fix them both. I went back through this thread, and I think for the problem you are having (022110), I mentioned the fix on page 7:

woot! I found my problem... I fried PS6001, the poor sucker is reading a resistance of 27MOhm. The spec is 2A/72V, but this is a "IC Link" type of component, which I'm having a bit of trouble finding a proper replacement for it. Can I use just a regular SMD fuse instead?

So check out PS6001 and report back. If that's not it, let me know... I know I documented it in this thread somewhere (or maybe in the other one, hopefully not on that one!)

 

[sandungas]

so it's interesting u say this. The first eepcsum dump I did was a DIA-001 CECHH01. That's the one you asked me to get info on since that 0x098 showed. Then I had another board DIA-001 again from a CECHL. I did the eepcsum on that and again saw the 0x098 so I thought ok well let me run the command you mentioned. So that's the info I put in the post from the second DIA-001 which is the CECHL. It looks like I have 2 of the same DIA-001. I'll get you the fantbl info soon.

Also, any ideas regarding my previous posts with 2030/2031 error? The board is missing an RSX. I'm thinking about reballing the chip back on. I wonder if I'm successful whether 2030/2031 will go away.

I dont have experience identifying the syscon error codes, sorry for derrailing a bit the talk with the thermal configs but this is very unusual, there is something related with the DIA-001 motherboards that doesnt have in any other motherboard, check the serials for DIA-001 in this link:
https://www.psdevwiki.com/ps3/DIA-00x
1-875-368-xx (the last "xx" is a subversion, we can replace the "xx" by 11, 21, 31, etc...)
1-875-938-xx (the last "xx" is a subversion, we can replace the "xx" by 11, 21, 31, etc...)

Both belongs to DIA-001, but this is weird in itself (it doesnt happen in any other PS3 motherboard), and seems to indicate an important revision

The first DIA-001 motherboards was introduced with the first CECHH PS3 model
After that sony was producing the CECHJ and CECHK models (with DIA-002), so it seems at that point probably they stopped the production of DIA-001
But... there is people reporting CECHM models (many months older than CECHH) with DIA-001... this is weird in itself, im not sure what means, maybe they had a lot of DIA-001 already produced months ago and they decided to use them for CECHM
And now you are saying they used DIA-001 in CECHL models too, this is another weird detail

When they was assembling the PS3 models CECHL, CECHM, CECHP, CECHQ (the last retail PS3 fat models) they was producing motherboard VER-001 (the last retail PS3 fat motherboard)... so in theory L,M,P,Q should have a VER-001 (except the rare ones with a DIA-001)
The chronology can be seen better in this table https://www.psdevwiki.com/ps3/Motherboard_Revisions#Serial_number

This is a bit confusing for me to be honest, not sure if the serial numbers of your's DIA-001 could clarify it a bit

---------
About the checksums reported by the "eepcsum" syscon command, we have two posible ones for DIA-001
0x985B <--- this is the most usual from the few samples i got
0x980C <--- this is yours, i was considering it unusual

But now you are mentioning you have 2 DIA-001 with the 0x980C im wondering which one is the "rare"... maybe it was jsut a coincidence all the samples i got was 0x985B

 

[Kleon1876]

There were two times that I shorted PWM pins while probing around the board, and I was able to fix them both. I went back through this thread, and I think for the problem you are having (022110), I mentioned the fix on page 7:



So check out PS6001 and report back. If that's not it, let me know... I know I documented it in this thread somewhere (or maybe in the other one, hopefully not on that one!)

I will. Silly question but how do I check ps6001 using a multimeter and what am I checking for. I'm pretty sure I shorted something. I had GLOD on the system. I was putting pressure on the rsx and cell with no result. Then I pulled the wifi/usb ribbon out while board was on and put it back in. I wiggled it like a dummy and it shorted and YLOD. Ylod since.

 

[marciolsf]

I will. Silly question but how do I check ps6001 using a multimeter and what am I checking for. I'm pretty sure I shorted something. I had GLOD on the system. I was putting pressure on the rsx and cell with no result. Then I pulled the wifi/usb ribbon out while board was on and put it back in. I wiggled it like a dummy and it shorted and YLOD. Ylod since.

No silly questions, we're all learning around here. I checked for resistance, and it was very, very high -- from my comments, it was around 27MOhms. A fully-open fuse will have infinite resistance. In my case it was burned enough to not be fully open, but also so burned out it wouldn't pass enough current to work properly. I think i compared with another FS fuses on the board (there's one right under the blueray drive, iirc), and the resistance was much, much lower.

If that turns out to be the problem, a few posts later @db260179 suggested a replacement off of ebay, and that worked well enough for me.

 

[M13k0_27]

Hi guys, I've got some news... As I wrote before, I firstly had 3001, 4001 and 3034 (I previously solved a power issue on the board, two shorted caps and then fixed 12V psu).
Last time I only got 4001 and 3034, I reflowed the RSX and nothing changed, then I've done it trough all the others main chips (CELL etc), now I have no more 4001 and 3034 but a new error appeared, the 1004 ! (DC-DC Failure?).
Is It a good sign? Is it better having 1004 compared to 4001 and 3034? What could it be?

Thank you.