PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

yeah, for sure. I'm hoping to pay someone for a reball or 40nm replacement with no strings attached, that's all. Id take care of the rest (power mods, tantalizers, etc)

I would absolutely love to set you up with a 40nm fatty! As stated I am relatively new to reballing and would really love more experience but I have a feeling that I'll always feel that way about reballing RSX since there are so many issues. I've got a bunch of 40nm that I've taken readings off and will be choosing the best looking one to do my next orbis. If that goes well then I'll have two of three successful transplants and that's pretty good success rate if that continues. The first one I've done has been switched on for over 24 hours doing data transfer and it's as quiet as a mouse. Stay tuned on my YouTube as I am planning on doing the second successful orbis, Jah Willing, this week.


Sent from my iPhone using Tapatalk
 
I made a list of the patches to clarify it, are 5 in total. Im not mentioning the DECR-1000 with the "F" syscons because im not sure if the offsets are the same than retail
I added the offsets to the wiki.
By reading about what you said of that (non-problematic) errors that happens with this patches in the communications in between syscon and rsx i can deduce what you are doing is not exactly how is supposed to be made, is the kind of "eureka" enlightment you had while looking at how it works, this is why i was optimistic, there was some probabilities for something like this to happen, specially because the orbis chip is "nerfing" that rsx training communications too
I looked through some prototype ebootroms and noticed that the TestBench SDK contains some XIO (XDR interface) training routines. That's something you'd use to generate the training data used on retail systems.
But I noticed that the actual code is missing, only the "setup" code is there not the actual generating code.
I remembered that CEB mainboards do have a LabStation port which is meant for the Rambus Labstation hardware. And that's where the magic happens, on prototype units this external LabStation is doing the XIO/FlexIO Calibration and generates the needed data. On normal designs Syscon is just using the hardcoded data/algorithm.
So Sony uses the Rambus LabStation to generate the training data.
I thought: Hmm does Sony even have access to some deeper information about XIO/FlexIO or are they just licensing it and using the Rambus Solution to make their life easier?
If you take a look at the fallback data (https://www.psdevwiki.com/ps3/Talk:Rambus_Registers) you'll see that the 28nm and 65nm and the patched 90nm use the same main training data. The 40nm and 28nm also share the patched training data. So even though in theory they all use different surrounding training data and algorithms, the main part is the same.
I guess Rambus receives $$$ for each "new" design and the 65nm, 40nm and 28nm RSX all contain a "new" design, that's why Sony needed a new Syscon, to accommodate the "new" training data and algorithms.
That's nothing new, Renesas also sold a "new" drive controller to Sony: R8J32810 vs "R8J32820" (https://weaponre.com/blog.html).
 
I would absolutely love to set you up with a 40nm fatty! As stated I am relatively new to reballing and would really love more experience but I have a feeling that I'll always feel that way about reballing RSX since there are so many issues. I've got a bunch of 40nm that I've taken readings off and will be choosing the best looking one to do my next orbis. If that goes well then I'll have two of three successful transplants and that's pretty good success rate if that continues. The first one I've done has been switched on for over 24 hours doing data transfer and it's as quiet as a mouse. Stay tuned on my YouTube as I am planning on doing the second successful orbis, Jah Willing, this week.


Sent from my iPhone using Tapatalk
I'll definitely keep an eye on your channel!
 
Next development will be kind of socket test jig universal board. I did not tested socket with syscon as you already see not need anymore. I just need months to get those parts coming. I have good feeling that will work as well, if cpu in laptops work on that it should work for me as well.
 
Last edited:
Let me add that Dr. vyktor frankies are the best, he is not afraid of breaking genetic rules :D

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)
 
@sandungas I can't remember but I'm pretty sure was in kte001. Most of them were kte001 boards that work well. In 2500 is something strange happening with that special glod to often now, I can't explain why, you know did different swaps and got same special glod status.Even measurements are same for working rsx.
Anyway that Id 21 EB/EC people should test both. I think first rsx 21 EB is found in sur001 board.
As well installed condition we know right after installing 40nm rsx without modify syscon it can be powered and will say 3034 /4002 errors, also David did measurements around rsx on board and out. He got pretty much same values, this was my hint over years.
Comparing good values with ic you are working.
After all this people can test write syscon.
 
I think first rsx 21 EB is found in sur001 board.
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)
 
Last edited:
@M4j0r i updated this post with 3 more patches, please review them

Are patches for PS3 models: CECH-21xx, CECH-25xx, CECH-30xx, and CECH-40xx
The point is... all this PS3 models have a 40nm RSX from factory, but there are 2 different identifyers for the 40nm RSX models (v1 or v2)
So... for repairing purposes we can replace a 40nm RSX v1 by a 40nm RSX v2 (or the other way around) by applying a syscon patch

The first 2 patches are an upgrade because allows to use the 40nm RSX v2 from a superslim in a slim (is needed to add the IHS)
And the other patch is a a bit like a downgrade because is the other way around, allows to use the 40nm RSX v1 from a PS3 slim in a superslim (by removing the IHS) but handy anyway :)

----------------
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 ?
 
Last edited:
@sandungas remember I've tested rsx from superslim models into kte001. It is starting fine but after few minutes will overheat. Reason is because none ihs will reach ic die in middle of rsx, rsx from superslim is thin in middle then previous model rsx in kte001.
OK took out cleaning and by looking at lights will see space between rsx and ihs. On normal kte001 rsx you won't see that space after delid.
 
Just installed a 40nm CXD5301 with felix and victor and this was the results @sandungas @M4j0r @RIP-Felix @vyktormvmpay25.

EDIT: Turns out these errors were due to not performing the necessary Resistor modifications needed for either Orbis or Franken mods to work.


Code:
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]$
>$
 
Last edited:
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
 
Ok what if those are in vcore line issue either cell or rsx, try to remove all IOR and test them off board, add photos in Faulty syscon thread so we can be in right thread. You are confident with reball but all important improvements have to be done like recaping totally. I do that on all since I got my first rsx swap working few days then ylod 1002.
 
Ok what if those are in vcore line issue either cell or rsx, try to remove all IOR and test them off board, add photos in Faulty syscon thread so we can be in right thread. You are confident with reball but all important improvements have to be done like recaping totally. I do that on all since I got my first rsx swap working few days then ylod 1002.

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
 
Back
Top