PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

[Pacorretaco]

Something interesting has been happening with my first Frankenstein!!
65nm on a COK-002. All done by the book.
It booted fine after setting it all up.
After 3rd boot this morning it threw the YLOD. Syscon log showed 3013/2120. I replaced the RSX again with a fresh CXD2991 and it booted again. Until 3rd boot it YLOD again ‍
It seems to be frying the RSX's
It has done it 3 times now.
It's either 3013/2102 and or 2120,2120 has never been related to the HDMI IC for me as the SONY chart says,its always been the RSX but I removed the HDMI IC just to double check but went back to 2102 without it,telling me that the RSX is fried. 2102 has always been a dead RSX for me.
I'm going to convert this unit back to a 90nm and try again on the next one and hope that it's just a one off. Tried converting back and no joy. Since I have tried converting to a 40nm and get 3013/2120 again which in my experience is telling me the RSX is no good.
It's chewing into my 65nm RSX's lol
Will try again tomorrow with a different RSX
Keep in mind I have 1000's of reballs under my belt so i'm not a newbie fooking things up

yeah it's recapped already
It was a cok-002 i fully refurbished and went ahead with the rsx swap
It was running fine prior to the frankenstein
So I don't see the board having an issue. It's got me beat
I will try another unit and see if the result is the same to rule out or confirm it's me,the process or the board

I wouldn't know but it is just too easy to follow the stream and always blame the RSX too quick. Yes RSX can be swapped now for different model but that doesnt mean RSX always need to be swapped.

These machines are incredibly complex. Hoping that different RSX will solve all present and future problems is just not sensible. (I am talking in general, not anybody specifically. You seem to have lots of experience)

Sometimes even RSX related errors are not "because" of the RSX chip itself. Even 3034 can have root in the CPU side for example etc... It is a data error, failed communication "between" the two.

And especially 3013/21xx errors I have only seen in cases where it has nothing to do with RSX. Sometimes a random component, or yes totally destroyed CPU I have seen with those errors.

 

[vyktormvmpay25]

Well I hope one or more from 5 IOR can be our problem. Will see results when he gets time to investigate.

 

[RIP-Felix]

Something interesting has been happening with my first Frankenstein!!
65nm on a COK-002. All done by the book.
It booted fine after setting it all up.
After 3rd boot this morning it threw the YLOD. Syscon log showed 3013/2120. I replaced the RSX again with a fresh CXD2991 and it booted again. Until 3rd boot it YLOD again ‍
It seems to be frying the RSX's
It has done it 3 times now.
It's either 3013/2102 and or 2120,2120 has never been related to the HDMI IC for me as the SONY chart says,its always been the RSX but I removed the HDMI IC just to double check but went back to 2102 without it,telling me that the RSX is fried. 2102 has always been a dead RSX for me.
I'm going to convert this unit back to a 90nm and try again on the next one and hope that it's just a one off. Tried converting back and no joy. Since I have tried converting to a 40nm and get 3013/2120 again which in my experience is telling me the RSX is no good.
It's chewing into my 65nm RSX's lol
Will try again tomorrow with a different RSX
Keep in mind I have 1000's of reballs under my belt so i'm not a newbie fooking things up

The 3013 makes me think CPU

 

[vyktormvmpay25]

Yes Felix, Aki and my engineer friend given kind same advice that IOR should have totally short like David got in first unit fixed.
I tend to believe delamination /deformation or pressure on die of cell cause that. User alty is on experts group as well so he will say if he test or passed to another mobo.
Rsx pwm controller for IOR drive is IC6201 and iC6103 is for IOR cell side. That section of power lines in boot kind related to those ic, I just can't tie that section with ic's numbers.
In slims I'll assume PS0, PS1 are related to rsx and PS2, PS3, PS4 related to cell.

 

[M4j0r]

Let me add that Dr. vyktor frankies are the best, he is not afraid of breaking genetic rules

Btw do you remember the exact RSX model you reballed into the PS3 you send to @M4j0r?. Im curious about it because when M4j0r published the patches he said there are 2 posible identifyers for the 40nm RSX:
21EB = 40nm RSX I
21EC = 40nm RSX II

He suggested to start trying with the identifyer 21EC (the second 40nm RSX version)... but the weird detail of it is the second 40nm RSX version doesnt have IHS. This made me wonder there are 2 posible reasons why he wrote it that way, either because:
Option 1) You took a 40nm RSX from a superslim motherboard (without IHS), and you sticked a IHS from a PS3 slim in it
Option 2) The order in how @M4j0r suggested to try the identifyers doesnt matters... he just said to start trying with 21EC but he applyed the patches for 21EB because his 40nm RSX is the version 1 (with IHS from factory, not added by you)

As far i understand 5300 and 5301 (with IHS) are using identifyer 21EB
And 5302 (without IHS) is 21EC

So is a lot more probable to find a 40nm RSX with identifyer 21EB, probably was produced a lot more than the others with identifyer 21EC because was used only in motherboards MPX-001 and MSX-001 (PS3 models CECH-40xx only)

The SW2-302 only supports the 21 EC, the 21 EB was added with the SW2-303 which means the SUR-001 board only supports 21 EC.

Later i will take a look at the DECR-1000 patches... at which offset are located the 2 (partially unknown) rsx bytes inside the thermal config region ?, the last time we was talking about that you didnt mentioned, i bet is better to add it, but im guessing you could not identify his offset, so we can forget about this detail by now, right ?

I don't know where they're located, but it works without changing them.


FYI: These are the different RSX FlexIO training data used by Syscon (after applying the platform specific patches). The refurbished 40nm units use the same data like the super slim boards.

 

[truemaster]

also what if new fw update (if evere released) applied to those frankensteins? will the patched syscon be an issue?

 

[DeadEnd]

Just installed a 40nm CXD5301 with felix and victor and this was the results @sandungas @M4j0r @RIP-Felix @vyktormvmpay25

40nm CXD5301
1st bringup
>$ 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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 THERM] NOTIFY_MODE CMD

[mullion]$
>$ powerstate
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ 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]$
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Unset
[HDMI VBS] ( 1) Command Module          : Unset
[HDMI VBS] ( 2) I2C Module              : Unset
[HDMI VBS] ( 3) Interrupt Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module   : Unset
[HDMI VBS] ( 6) State Machine Module    : Unset
[HDMI VBS] ( 7) EDID Read Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Unset
[HDMI VBS] ( 9) FRAME Module            : Unset
[HDMI VBS] (10) HW Module               : Unset
[HDMI VBS] (11) SET Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Unset
[HDMI VBS] (13) REQ Module              : Unset
[HDMI VBS] (14) SystemEvent Module      : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Unset
[HDMI VBS] (17) CH1 Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Unset
[HDMI VBS] (25) EEPROM Module           : Unset
[HDMI VBS] (30) Hdmi System             : Unset
[HDMI VBS] (31) Hdmi ERROR              : Unset
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$ errlog
errlog
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
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0a02031, clock:0x0b49d89c  2006/01/01 00:02:36
ofst[ 12]:err_code:0xa0a02031, clock:0xffffffff
[mullion]$
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$

#2 bringup
>$ 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 -> 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 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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

[mullion]$ [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
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] READ 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]$
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Unset
[HDMI VBS] ( 1) Command Module          : Unset
[HDMI VBS] ( 2) I2C Module              : Unset
[HDMI VBS] ( 3) Interrupt Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module   : Unset
[HDMI VBS] ( 6) State Machine Module    : Unset
[HDMI VBS] ( 7) EDID Read Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Unset
[HDMI VBS] ( 9) FRAME Module            : Unset
[HDMI VBS] (10) HW Module               : Unset
[HDMI VBS] (11) SET Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Unset
[HDMI VBS] (13) REQ Module              : Unset
[HDMI VBS] (14) SystemEvent Module      : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Unset
[HDMI VBS] (17) CH1 Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Unset
[HDMI VBS] (25) EEPROM Module           : Unset
[HDMI VBS] (30) Hdmi System             : Unset
[HDMI VBS] (31) Hdmi ERROR              : Unset
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$ 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]$

 3rd bringup

>$ 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 -> 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 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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 THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED

[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
>$ powerstate
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]$
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Unset
[HDMI VBS] ( 1) Command Module          : Unset
[HDMI VBS] ( 2) I2C Module              : Unset
[HDMI VBS] ( 3) Interrupt Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module   : Unset
[HDMI VBS] ( 6) State Machine Module    : Unset
[HDMI VBS] ( 7) EDID Read Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Unset
[HDMI VBS] ( 9) FRAME Module            : Unset
[HDMI VBS] (10) HW Module               : Unset
[HDMI VBS] (11) SET Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Unset
[HDMI VBS] (13) REQ Module              : Unset
[HDMI VBS] (14) SystemEvent Module      : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Unset
[HDMI VBS] (17) CH1 Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Unset
[HDMI VBS] (25) EEPROM Module           : Unset
[HDMI VBS] (30) Hdmi System             : Unset
[HDMI VBS] (31) Hdmi ERROR              : Unset
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$ 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]$
>$

What's the history there? What were the steps done ? It boots but you got nothing on display ? did you use modchip or the syscon code?

 

[DeadEnd]

I wouldn't know but it is just too easy to follow the stream and always blame the RSX too quick. Yes RSX can be swapped now for different model but that doesnt mean RSX always need to be swapped.

These machines are incredibly complex. Hoping that different RSX will solve all present and future problems is just not sensible. (I am talking in general, not anybody specifically. You seem to have lots of experience)

Sometimes even RSX related errors are not "because" of the RSX chip itself. Even 3034 can have root in the CPU side for example etc... It is a data error, failed communication "between" the two.

And especially 3013/21xx errors I have only seen in cases where it has nothing to do with RSX. Sometimes a random component, or yes totally destroyed CPU I have seen with those errors.

Indeed, sometimes it's easy to damage something on the board during the swap. They bubble easily from high heat and other components are also sensitive to heat. Even RSX itself can die if you're not careful installing/delidding.

Also small corrections. 3034 isn't a data error. It's fatal booting sequence error. Data errors start with "40". Also 3034 is almost never CPU.

 

[Pacorretaco]

Indeed, sometimes it's easy to damage something on the board during the swap. They bubble easily from high heat and other components are also sensitive to heat. Even RSX itself can die if you're not careful installing/delidding.

Also small corrections. 3034 isn't a data error. It's fatal booting sequence error. Data errors start with "40". Also 3034 is almost never CPU.

Yes.
Well I'm sure there's people here that know this in more depth but, as far as I understand 3034 itself just means failed CPU bittraining.
Which yes, happens at step 40 in the boot sequence (full error code would be 40 3034) and normally comes with an additional error code that makes it a bit less vague. Example: 40 3034 + 40 44XX

Failed CPU<--->RSX BitTraining
(Wrong or no "data" sent or recieved between CPU and... RSX in this case (because of 44XX)) But even if it could be fair to start suspecting RSX... In reality the RSX itself could still be fine.
There are still many places and reasons why this communication can fail. One of them being the CPU even if rare yes. Or the data lines in between. Even the SYSCON has something to do there.

Case in point:
The famous RSX_FLEXIO_ID ERROR that M4j0r geniusly solved by patching the bittraining "data" inside the SYSCON EEPROM. Still a 3034 error, except
The RSX is OK only that when asked to "identify itself" by the CPU, the ID "data" that it provides is not recognized as correct because it is expecting something else. A 90nm "ID" instead of newer 65 for example.
So bittraining failed. 40 3034 error.

At this stage it is fair to say it is a data error. Because this intermediate CPU BitTraining stage (40 of 80) Only happens "after" the individual basic checks to the Syscon, where the most of the obvious failures such as power failures are detected. Including RSX and CPU individually

 

[alty75]

The 3013 makes me think CPU

3013 has never been CELL related for me
Here is my list of errors and confirmed fixes from over the past 12 months logging the syscon and applying a repair

 

[alty75]

Of

Well I hope one or more from 5 IOR can be our problem. Will see results when he gets time to investigate.

an IOR were short it would have the YLOD and the console would not boot

 

[marciolsf]

as far as I understand 3034 itself just means failed CPU bittraining.

Not necessarily... it seems that way, but we haven't collected enough bootlog messages to know that for sure. In my case, I do have 40-3034, but not anything else.

 

[DeadEnd]

Not necessarily... it seems that way, but we haven't collected enough bootlog messages to know that for sure. In my case, I do have 40-3034, but not anything else.

And not always CPU bittraining, in some cases it shows RSX bittraining that's failed.

 

[Pacorretaco]

Not necessarily... it seems that way, but we haven't collected enough bootlog messages to know that for sure. In my case, I do have 40-3034, but not anything else.

And not always CPU bittraining, in some cases it shows RSX bittraining that's failed.

Yes necesarily and yes always, that's the thing. That's why it is a little ambiguous hehehe.

Because the BitTraining is always done by the CPU. There is no "RSX bittraining" because it is something that goes both ways.
It happens Not only between the CPU and the RSX, but also between the CPU and the Southbridge.

That's why 3034 alone is not deterministic information. Not enough. Now if you look at the bringup sequence, there will be some more useful details, and maybe RSX mentioned along with associated 44xx error if it is CPU<--->RSX bittraining. Sometimes even more useful details (Like in FLEXIO_ID case)

But still there is that little ambiguity. The hamburger loving friend (RSX) is being called but not answering properly. Maybe he finally had his cardiac arrest. But maybe he is alive and his phone is just broken... Maybe somebody cut the wires. Or maybe your own phone is broken? Maybe you have gone deaf from that ear? (CPU)
You knew his hamburger habit was going to end badly soon... But after all he also had a habit of dropping his phone a lot with his greasy fingers... Hmm...

 

[RIP-Felix]

Just installed a 40nm CXD5301 with felix and victor and this was the results @sandungas @M4j0r @RIP-Felix @vyktormvmpay25

40nm CXD5301
1st bringup
>$ 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
[SSM] state: 0104 -> 0204
[SSM] state: 0204 -> 0105
[SSM] state: 0105 -> 0400
(PowerOn State)
[SERV NVS] READ CMD

Boot Loader SE Version 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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 THERM] NOTIFY_MODE CMD

[mullion]$
>$ powerstate
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] READ 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]$
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Unset
[HDMI VBS] ( 1) Command Module          : Unset
[HDMI VBS] ( 2) I2C Module              : Unset
[HDMI VBS] ( 3) Interrupt Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module   : Unset
[HDMI VBS] ( 6) State Machine Module    : Unset
[HDMI VBS] ( 7) EDID Read Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Unset
[HDMI VBS] ( 9) FRAME Module            : Unset
[HDMI VBS] (10) HW Module               : Unset
[HDMI VBS] (11) SET Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Unset
[HDMI VBS] (13) REQ Module              : Unset
[HDMI VBS] (14) SystemEvent Module      : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Unset
[HDMI VBS] (17) CH1 Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Unset
[HDMI VBS] (25) EEPROM Module           : Unset
[HDMI VBS] (30) Hdmi System             : Unset
[HDMI VBS] (31) Hdmi ERROR              : Unset
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$ errlog
errlog
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
ofst[  0]:err_code:0xa0403034, clock:0xffffffff
ofst[  4]:err_code:0xa0403034, clock:0xffffffff
ofst[  8]:err_code:0xa0a02031, clock:0x0b49d89c  2006/01/01 00:02:36
ofst[ 12]:err_code:0xa0a02031, clock:0xffffffff
[mullion]$
>$ clearerrlog
clearerrlog
ERRLOG CLEARED
[mullion]$
>$

#2 bringup
>$ 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 -> 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 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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

[mullion]$ [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
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] READ 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]$
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Unset
[HDMI VBS] ( 1) Command Module          : Unset
[HDMI VBS] ( 2) I2C Module              : Unset
[HDMI VBS] ( 3) Interrupt Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module   : Unset
[HDMI VBS] ( 6) State Machine Module    : Unset
[HDMI VBS] ( 7) EDID Read Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Unset
[HDMI VBS] ( 9) FRAME Module            : Unset
[HDMI VBS] (10) HW Module               : Unset
[HDMI VBS] (11) SET Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Unset
[HDMI VBS] (13) REQ Module              : Unset
[HDMI VBS] (14) SystemEvent Module      : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Unset
[HDMI VBS] (17) CH1 Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Unset
[HDMI VBS] (25) EEPROM Module           : Unset
[HDMI VBS] (30) Hdmi System             : Unset
[HDMI VBS] (31) Hdmi ERROR              : Unset
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$ 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]$

 3rd bringup

>$ 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 -> 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 0.9.5 (Build ID: 1634,16289, Build Data: 2006-09-21_19:11:09)
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 THERM] NOTIFY_MODE CMD
[SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED

[mullion]$ [SERV NOTIF] CONTROL_LED
[SERV NOTIF] RING_BUZZER
[SERV NOTIF] CONTROL_LED
[SERV NVS] READ CMD
[SERV NVS] READ CMD
[SERV NVS] WRITE CMD
[SERV NVS] READ CMD
[SERV NVS] READ CMD
>$ powerstate
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]$
>$ hdmi vbs
hdmi vbs
[HDMI VBS] Code:00000000
----------------------------------------------------------------
[HDMI VBS] ( 0) BE Module               : Unset
[HDMI VBS] ( 1) Command Module          : Unset
[HDMI VBS] ( 2) I2C Module              : Unset
[HDMI VBS] ( 3) Interrupt Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 4) Interrupt Module System : Unset
[HDMI VBS] ( 5) Authentication Module   : Unset
[HDMI VBS] ( 6) State Machine Module    : Unset
[HDMI VBS] ( 7) EDID Read Module        : Unset
----------------------------------------------------------------
[HDMI VBS] ( 8) DDC Module              : Unset
[HDMI VBS] ( 9) FRAME Module            : Unset
[HDMI VBS] (10) HW Module               : Unset
[HDMI VBS] (11) SET Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (12) STATUS Module           : Unset
[HDMI VBS] (13) REQ Module              : Unset
[HDMI VBS] (14) SystemEvent Module      : Unset
----------------------------------------------------------------
[HDMI VBS] (16) CH0 Module              : Unset
[HDMI VBS] (17) CH1 Module              : Unset
----------------------------------------------------------------
[HDMI VBS] (24) DVE Module              : Unset
[HDMI VBS] (25) EEPROM Module           : Unset
[HDMI VBS] (30) Hdmi System             : Unset
[HDMI VBS] (31) Hdmi ERROR              : Unset
[mullion]$
>$ shutdown
shutdown
[SSM] state: 0400 -> 0500
[POWSEQ] AV Backend Letup
[SSM] ssmCb_AfterBeOn() called.
[SSM] Shutdown mode ... req_wake_src = 00000074, ctxt=00/00
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0500 -> 0000
(PowerOff State)
>$ 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]$
>$

Some history. It was a 3034 he relowed it and installed tantalums. It was working for 6months and came back to him with a short VDDC line. The errorlog showed 3034 & 1001/3003 errors consistant with the work history. There are some 1701, 14FF, and 1601 too. Those are consistant with the console YLOD'ing from BGA defects while the console was on (check stops, BE attention, and Livelock detection). That just means a solder connection was interfering with the PLL and caused it to lose lock during normal use. Probably the customer would have seen artifacting and freezing before it refused to power back on. Then there are a bunch of 3004's indicating bad VDDC (RSX VRM module). I think that's consistant with trash yellow AVX caps causing the VRM and RSX work harder. There would be higher ripple and more heat. They likely wore out the RSX, which was weakend by use and the reflow.

Anyway, since it was working before, we thought it was the best candidate for a 40nm CXD5301. The replacment went well, I had him measure all the relevent RSX voltages (ohms test) to confirm. They seemed fine. So we proceeded with the Frankenstein attempt.

@M4j0r @sandungas This COK-001 has a 40nm CXD5301. I had him test before we wrote any of the RSX Training Data. He got a "BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID ERROR (3034, by itself. No data error)."

First I had him write the 40nm RSX training data...

w 3242 03 61 82 80 01 91​

Then I had him try the v1 RSX write command...

w 3254 21 EB​

Then he tested a bringup command, which yielded the same result, Sole 3034 with "BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID" ERROR. So we then tried the write for the v2 RSX...

w 3254 21 EC​

After the "EC" write it cleared BitTraining. The console is still a GLOD, but I don't think that has anything to do with BitTraining. Looks like it worked, but there is an unresolved issue causing a GLOD. It's just not the RSX_ID anymore.

However at some point in here he managed to get some 2031 RSX thermal monitor errors. He did mess around with some different power butons and used the shutdown command. That kinda halts immedietly, not gracefully. He left the console on fo maybe a minute and teh console shut itself off. That may have been when the 2031 occured also. Actually that seemed likly. Maybe the unchanged thermal config data was triggering the automatic shutdown and 2031. I wanted to be sure it wasn't related to the thermal config, so I had him write the additional data @sandungas reccomended...

w 348B 8B
w 34AF 8B​

The results was still a GLOD, but we didn't get any RSX thermal monitor errors after that (no more 2031) and the console didn't automatically shutdown after that. Still GLOD, but it stays on and never gave another error. @vyktormvmpay25 calls this a "Special GLOD." That's where we left off.

I told booter to post the logs and that you 2 may have questions for him

 

[Pacorretaco]

Not necessarily... it seems that way, but we haven't collected enough bootlog messages to know that for sure. In my case, I do have 40-3034, but not anything else.

40-3034 appearing alone without the associated 40-44xx error typical of the funny RSX issues may actually be an early board with an early syscon. Logging the same issue in a slightly different way.
Assuming some things etc etc of course.
You need to look at the bringup for more info.

Is it a CECHA or B with a 201GB syscon?

Edit: sorry perhaps this could start to clutter this thread. I think trying to identify RSX problems to know when to replace is relevant, and the 201GB is still not 100% confirmed or understood... But maybe not the highest priority now

 

[Pacorretaco]

Some history. It was a 3034 he relowed it and installed tantalums. It was working for 6months and came back to him with a short VDDC line. The errorlog showed 3034 & 1001/3003 errors consistant with the work history. There are some 1701, 14FF, and 1601 too. Those are consistant with the console YLOD'ing from BGA defects while the console was on (check stops, BE attention, and Livelock detection). That just means a solder connection was interfering with the PLL and caused it to lose lock during normal use. Probably the customer would have seen artifacting and freezing before it refused to power back on. Then there are a bunch of 3004's indicating bad VDDC (RSX VRM module). I think that's consistant with trash yellow AVX caps causing the VRM and RSX work harder. There would be higher ripple and more heat. They likely wore out the RSX, which was weakend by use and the reflow.

Anyway, since it was working before, we thought it was the best candidate for a 40nm CXD5301. The replacment went well, I had him measure all the relevent RSX voltages (ohms test) to confirm. They seemed fine. So we proceeded with the Frankenstein attempt.

@M4j0r @sandungas This COK-001 has a 40nm CXD5301. I had him test before we wrote any of the RSX Training Data. He got a "BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID ERROR (3034, by itself. No data error)."

First I had him write the 40nm RSX training data...

w 3242 03 61 82 80 01 91​

Then I had him try the v1 RSX write command...

w 3254 21 EB​

Then he tested a bringup command, which yielded the same result, Sole 3034 with "BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID" ERROR. So we then tried the write for the v2 RSX...

w 3254 21 EC​

After the "EC" write it cleared BitTraining. The console is still a GLOD, but I don't think that has anything to do with BitTraining. Looks like it worked, but there is an unresolved issue causing a GLOD. It's just not the RSX_ID anymore.

However at some point in here he managed to get some 2031 RSX thermal monitor errors. He did mess around with some different power butons and used the shutdown command. That kinda halts immedietly, not gracefully. He left the console on fo maybe a minute and teh console shut itself off. That may have been when the 2031 occured also. Actually that seemed likly. Maybe the unchanged thermal config data was triggering the automatic shutdown and 2031. I wanted to be sure it wasn't related to the thermal config, so I had him write the additional data @sandungas reccomended...

w 348B 8B
w 34AF 8B​

The results was still a GLOD, but we didn't get any RSX thermal monitor errors after that (no more 2031) and the console didn't automatically shutdown after that. Still GLOD, but it stays on and never gave another error. @vyktormvmpay25 calls this a "Special GLOD." That's where we left off.

I told booter to post the logs and that you 2 may have questions for him

Remember the alternative way of solving this error. Botakompongs way with a modchip. Maybe worth trying if run out of ideas? This is still uncharted territory.

Also I vaguely remember him talking about possible GLOD and some resistors? But you probably have this way more controlled than in my memory. Maybe another thing to double check in case you havent already

 

[sandungas]

Hmmm, there are 2 details of what you explained that are calling my attention, i guess what im going to say is not going to help fix that PS3 but i have to ask @M4j0r about this details anyway and this is a good timing

@M4j0r @sandungas This COK-001 has a 40nm CXD5301. I had him test before we wrote any of the RSX Training Data. He got a "BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID ERROR (3034, by itself. No data error)."

First I had him write the 40nm RSX training data...

w 3242 03 61 82 80 01 91​

Then I had him try the v1 RSX write command...

w 3254 21 EB​

Then he tested a bringup command, which yielded the same result, Sole 3034 with "BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID" ERROR. So we then tried the write for the v2 RSX...

w 3254 21 EC​

After the "EC" write it cleared BitTraining. The console is still a GLOD, but I don't think that has anything to do with BitTraining. Looks like it worked, but there is an unresolved issue causing a GLOD. It's just not the RSX_ID anymore.

So the RSX CXD5301 identifyer is 21EC ?, then i guess what i said here is wrong:

Yes SUR-001 (from CECH-21xx PS3 model) was the first with a 40nm RSX. I been updating some related pages in wiki today, if we order them by "series" (ignoring the suffixes) there are 3 groups made at 40nm:

CXD5300xxx (RSX 40nm, with IHS, 4 VRAM chips)
Motherboards: SUR-001, JTP-001, JSD-001

CXD5301xxx (RSX 40nm, with IHS, 4 VRAM chips)
Motherboards: KTE-001

CXD5302xxx (RSX 40nm, without IHS, 4 VRAM chips)
Motherboards: MSX-001, MPX-001

As far i understand 5300 and 5301 (with IHS) are using identifyer 21EB
And 5302 (without IHS) is 21EC

So is a lot more probable to find a 40nm RSX with identifyer 21EB, probably was produced a lot more than the others with identifyer 21EC because was used only in motherboards MPX-001 and MSX-001 (PS3 models CECH-40xx only)

Anyway... i was asking about it because by looking at the photos all the 40nm RSX models seems to have the same dimmensions, so i guess is posible to do the combo i mentioned:
40nm RSX from a superslim (MSX-001, MPX-001) + the IHS from a slim (SUR-001, JTP-001, JSD-001, or KTE-001)

It seems to be the other way around ?
5300 and 5301 (with IHS) are using identifyer 21EC
And 5302 (without IHS) is 21EB

Is weird because it seems are in the inverse order, but what @M4j0r said here is weird too

The SW2-302 only supports the 21 EC, the 21 EB was added with the SW2-303 which means the SUR-001 board only supports 21 EC.

You need to be more explicit this time, are you telling the patches in my previous post for SUR-001 are wrong, needs to be modifyed, or something like that ?

If you told that to make me speculate about it and try to deduce what sony was doing... i guess is having the opposite effect, is making me wonder if everything i know is wrong
I mean... if what you wrote doesnt have any typo... you are telling that the 21EC was used in retail production before 21EB... so they inverted the order of the IDs for some weird reason ?

I did read your post some hours ago and i been thinking in this, but now after reading RIP-Felix post it seems it matches with what you said, so...
5300 and 5301 (with IHS) are using identifyer 21EC ?
And 5302 (without IHS) is 21EB ?

However at some point in here he managed to get some 2031 RSX thermal monitor errors. He did mess around with some different power butons and used the shutdown command. That kinda halts immedietly, not gracefully. He left the console on fo maybe a minute and teh console shut itself off. That may have been when the 2031 occured also. Actually that seemed likly. Maybe the unchanged thermal config data was triggering the automatic shutdown and 2031. I wanted to be sure it wasn't related to the thermal config, so I had him write the additional data @sandungas reccomended...

w 348B 8B
w 34AF 8B​

The results was still a GLOD, but we didn't get any RSX thermal monitor errors after that (no more 2031) and the console didn't automatically shutdown after that. Still GLOD, but it stays on and never gave another error.

That bytes related with rsx inside the thermal config are still unknown, i use to say are partially unknown to short the story. What happens is i cant give a short explanation with a solid argument about why we need to do it... but is something sony was doing in all the syscon dumps from the official refurbishements we got, and we know how to replicate it in the same way sony was doing
Personally... im the kind of person that prefers to dont modify things that i dont understand... but this is the opposite case... you know... is like at the start of this thread with the resistors, we was not sure what the resistors was doing, but the rule we applyed is "ok im not sure how it works, so im going to copy it", lol

I never heard of a error 2031 associated with an incorrect rsx byte identifyer inside the thermal config... but nobody was doing this frankensteins with the syscon patches before
If someone can clarify if the error 2031 is really associated with that bytes maybe it could help to figure what the bytes means
We will see, more tests needed

 

[vyktormvmpay25]

I misunderstanding something Cxd5301 uses 21 EC, Cxd5302 uses 21 EB? I thought Last bit "B" is lower than "C" so those coming in that order but seems not?Like order of hex column? Oh I'm out of this as I really s*uck on programming so I will follow orders on this side.

 

[RIP-Felix]

I never heard of a error 2031 associated with an incorrect rsx byte identifyer inside the thermal config... but nobody was doing this frankensteins with the syscon patches before
If someone can clarify if the error 2031 is really associated with that bytes maybe it could help to figure what the bytes means
We will see, more tests needed

Keep in mind that it may not be related at all. He did say he may have shorted the bottom of the power board to the RF shield, so that could have triggered the error too. So IDK. I just know he got the errors around that time. We were kinda disjointed at that point and trying a bunch of things instead of making one change at a time and testing the result.