PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

perfect. yes ps2 slim 7500x eegs rams are compatible with cecha. but that leaves a lot to ask you see ps2 is a console that never had issues with eegs or rams. why cecha? and there are lot with no ps2 playback. could be overvoltage? i dont know
 
Paolo said:
Hi guys greetings from Italy.
I wanna share my exp on a cok-001 frankestein did one week ago, it was my first cecha frankestein (i always worked on cok-002) , after 40nm replacement i had the infamous no ps2 game issue, black screen but able to return back to XMB.. i watched a lot of post in this group and on psx-place about this issue , so i ve reballed the same eegs, replaced rdram, replaced cxd9208, cxm4024, reballed a new rsx 65nm and again a new 40nm.. still black screen.. eegs uart log was perfectly fine, so i started to probe data lines between rsx and i ve found an open line on a data line.. i ran a jumper between rsx and eegs as you can see in the photo coz the internal trace was broken (maybe during reballing process?) but nothing.. still black screen.. so the last option was replacing the eegs but i ve ran out of spare ic's , so i ve bought a broken ps2 75004 from ebay in order to harvest a new eegs but the code on it was different (cxd9833 instead of cxd9228.. i dont Remember..) i soldered both rdram and eegs from the ps2 on the cok.. et voilà, ps2 game now work with no issues.. just my experience so i can help someome in the future..
drLt98y

jbx4QDQ
Click to expand...
Assume you are good tech and know your tools for further reference and if you deal often with cok boards you can build for your lab one rsx universal rsx tester on socket.
Best board and compatible with all 3 rsx is sem001. I believe slims and nor model are bit sensitive for length of cheap pogo pins. Stick with this model unless you want to build it on another model. 3k model wont accept 65nm or 90nm. Sony cut something more to get it working.
For those who reball often I think same thing must be created for one ps2 interposer with pogo pins.
https://s.go.ro/8lcdk9cq
That should be a project for those who know more than me ps2 model of EE compatibility list.
 
Last edited:
truemaster said:
perfect. yes ps2 slim 7500x eegs rams are compatible with cecha. but that leaves a lot to ask you see ps2 is a console that never had issues with eegs or rams. why cecha? and there are lot with no ps2 playback. could be overvoltage? i dont know
Click to expand...

Idk. Maybe heat during desoldering has killed my eegs or rdram...
 
Hey everyone, just attempted my first RSX swap on a COK-001 board. I have good ohms on the board, or at least close enough where applicable like RSX PLL, but my system won't boot, here's my syscon bringup

From what I understand, FLEXIO_ID should be solved with the 65nm training data, but it evidently has not been. The error is in BX0, so the system isn't even seeing the new RSX. I confirmed the resistor mods are good, so I don't know why this would be the case.

Anybody have any advice?

>$ 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
Press Ctrl+C to exit
>$
[SSM] state: 0103 -> 0203
[SSM] ssmCb_BeforeBeOn() called.
[SSM] state: 0203 -> 0104
Psbd_SbTransMode_Half:0x20e2
[POWERSEQ] Error : BitTraining RSX:RRAC:BX0:BX:FLEXIO_ID
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
 
Paolo said:
Hi guys greetings from Italy.
I wanna share my exp on a cok-001 frankestein did one week ago, it was my first cecha frankestein (i always worked on cok-002) , after 40nm replacement i had the infamous no ps2 game issue, black screen but able to return back to XMB.. i watched a lot of post in this group and on psx-place about this issue , so i ve reballed the same eegs, replaced rdram, replaced cxd9208, cxm4024, reballed a new rsx 65nm and again a new 40nm.. still black screen.. eegs uart log was perfectly fine, so i started to probe data lines between rsx and i ve found an open line on a data line.. i ran a jumper between rsx and eegs as you can see in the photo coz the internal trace was broken (maybe during reballing process?) but nothing.. still black screen.. so the last option was replacing the eegs but i ve ran out of spare ic's , so i ve bought a broken ps2 75004 from ebay in order to harvest a new eegs but the code on it was different (cxd9833 instead of cxd9228.. i dont Remember..) i soldered both rdram and eegs from the ps2 on the cok.. et voilà, ps2 game now work with no issues.. just my experience so i can help someome in the future..
drLt98y

jbx4QDQ
Click to expand...


It is nothing new. I have fixed one cok-001 with no ps2 playback the same way, by swapping faulty EEGS, but nobody seems to care when I say it... I did not swap rdrams because I took EEGS from another cok board. EEGS can be at fault more often than people think...
 
DeadEnd said:
It is nothing new. I have fixed one cok-001 with no ps2 playback the same way, by swapping faulty EEGS, but nobody seems to care when I say it... I did not swap rdrams because I took EEGS from another cok board. EEGS can be at fault more often than people think...
Click to expand...
yes eegs on cok1 seems to have a lot of issues. but thats not the case on actual ps2. i can think of overvoltage in ps3 that kill eegs sooner.
 
Got a COK001 motherboard with YLOD,I check syscon use bringup command I got 1002, I fixed 1002 with Felix Tantalizer, then turn it on and got display artifacts/flashes, turn it off and turn on I got GLOD, subsequent tests triggered A0403034 and A0902120, which seems to be a typical bad RSX, you can see the system has only 2 days and 13 hours of runtime, this is crazy, I tried to make a 40nm Frankenstein with it, I think this motherboard may be running on firmware lower than 3.55, is the NAND only patchable now with a hardware refresher?

4dxd30H.jpeg


I got a 5301DGB for slim, is it healthy? Here are the resistance values I measured, with the multimeter auto-ranging.
FBVDDQ:468.8
VDDC:2.4
VDDR:570.2
VDDIORW/YC_RC_VDDIO:7.14k
VDDA:10.47k
VDDIO:1.6k
PLL:44.83m
Is the PLL too high?thanks!
 
Last edited by a moderator:
Paolo said:
Hi guys greetings from Italy.
I wanna share my exp on a cok-001 frankestein did one week ago, it was my first cecha frankestein (i always worked on cok-002) , after 40nm replacement i had the infamous no ps2 game issue, black screen but able to return back to XMB.. i watched a lot of post in this group and on psx-place about this issue , so i ve reballed the same eegs, replaced rdram, replaced cxd9208, cxm4024, reballed a new rsx 65nm and again a new 40nm.. still black screen.. eegs uart log was perfectly fine, so i started to probe data lines between rsx and i ve found an open line on a data line.. i ran a jumper between rsx and eegs as you can see in the photo coz the internal trace was broken (maybe during reballing process?) but nothing.. still black screen.. so the last option was replacing the eegs but i ve ran out of spare ic's , so i ve bought a broken ps2 75004 from ebay in order to harvest a new eegs but the code on it was different (cxd9833 instead of cxd9228.. i dont Remember..) i soldered both rdram and eegs from the ps2 on the cok.. et voilà, ps2 game now work with no issues.. just my experience so i can help someome in the future..
drLt98y

jbx4QDQ
Click to expand...


Could you reupload photos please? I'm more interested in this jumper you made from rsx to eegs. Thank you.

Edit:

Nevermind. I figured out how to see the photos.
 
Last edited:
Did anyone manage to figure out the no PS2/black screen issue? I recently bought a frankie CECHA00 done by Sony and it had some problems with playing PS2 games. I've "solved" it by having the fan use SYSCON settings when starting a PS2 game, and while playing, it can ramp up as much as it wants without anything crashing. It seems to be directly related to the fan settings and not the temperature since I've tried launching games around the same temperature, but with both SYSCON and custom settings, it doesn't work with the latter. Plus, like I said, during gameplay, the fan is at 40%, and the game runs smoothly.
 
You're never going to have one clean magical fix for nops2. It could be anything from a broken internal trace, missing component(s), eegs, bridge chip, ramm, etc...
 
CECHA01 board with YLOD

>$ 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
Press Ctrl+C to exit
>$ becount
[POWERSEQ] Error : BitTraining RSX:RRAC:RX3:GLOBAL1:RX_STATUS
[SSM] state: 0104 -> 0304
[SSM] ssmCb_AfterBeOn2() called.
[SSM] PowSeq Fail : Detected !
[SSM] state: 0304 -> 0700
[POWSEQ] AV Backend Letup
[SSM] Shutdown mode : syspm_stat=00000000/00000000
[ERROR]: 0xa0403034
[POWSEQ] PowerSeq_Letup called.
[SSM] state: 0700 -> 0600
(PowerOff State) (Fatal)
>$ errlog
errlog
ofst[116]:err_code:0xffffffff, clock:0x0b4d8bf2 2006/01/03 19:24:34
ofst[120]:err_code:0xa0403034, clock:0xffffffff
ofst[124]:err_code:0xa0403034, clock:0xffffffff
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0403034, clock:0xffffffff
ofst[ 8]:err_code:0xa0403034, clock:0xffffffff
ofst[ 12]:err_code:0xa0801701, clock:0x0b5df4d2 2006/01/16 06:08:18
ofst[ 16]:err_code:0xa08014ff, clock:0x0b5df4d2 2006/01/16 06:08:18
ofst[ 20]:err_code:0xa0801601, clock:0x0b5df4d2 2006/01/16 06:08:18
ofst[ 24]:err_code:0xa0801802, clock:0x0b5df4e0 2006/01/16 06:08:32
ofst[ 28]:err_code:0xa0403034, clock:0x0b5df4f6 2006/01/16 06:08:54
ofst[ 32]:err_code:0xa0403034, clock:0x0b5df52f 2006/01/16 06:09:51
ofst[ 36]:err_code:0xa0403034, clock:0x0b5df536 2006/01/16 06:09:58
ofst[ 40]:err_code:0xa0403034, clock:0x0b5df53a 2006/01/16 06:10:02
ofst[ 44]:err_code:0xa0403034, clock:0x0b5df5b9 2006/01/16 06:12:09
ofst[ 48]:err_code:0xa0403034, clock:0x0b5e93c2 2006/01/16 17:26:26
ofst[ 52]:err_code:0xa0801701, clock:0x0b95101e 2006/02/27 01:19:26
ofst[ 56]:err_code:0xa0801601, clock:0x0b95101e 2006/02/27 01:19:26
ofst[ 60]:err_code:0xa0503036, clock:0x0b95103b 2006/02/27 01:19:55
ofst[ 64]:err_code:0xa0801001, clock:0x0b48869a 2005/12/31 00:00:26
ofst[ 68]:err_code:0xa0801103, clock:0x0b488746 2005/12/31 00:03:18
ofst[ 72]:err_code:0xa0801001, clock:0x0b488698 2005/12/31 00:00:24
ofst[ 76]:err_code:0xa0801701, clock:0x0b488786 2005/12/31 00:04:22
ofst[ 80]:err_code:0xa0801601, clock:0x0b488786 2005/12/31 00:04:22
ofst[ 84]:err_code:0xa0403034, clock:0x0b4887c1 2005/12/31 00:05:21
ofst[ 88]:err_code:0xa0403034, clock:0xffffffff
ofst[ 92]:err_code:0xa0403034, clock:0xffffffff
ofst[ 96]:err_code:0xa0403034, clock:0xffffffff
ofst[100]:err_code:0xa0403034, clock:0xffffffff
ofst[104]:err_code:0xa0403034, clock:0xffffffff
ofst[108]:err_code:0xa0403034, clock:0xffffffff
ofst[112]:err_code:0xa0403034, clock:0xffffffff
>$ lasterrlog
lasterrlog
Last Error Code:0xa0403034, Time:0xffffffff
>$ becount
becount
Bringup : 2169 times
Shutdown: 2068 times
Power-on: 173day 13hour 44min 08sec

any suggestions? 0xa0403034 - look like common dead RSX error. I have a spare 40nm RSX - should I try to make a swap?
 
That board needs a Frankenstein mod. Some people claim reballing a 90nm is just as effective. I don't have any first hand experience to support that theory. I could be wrong, but it sounds like you haven't done the Frankenstein process before. Might want to practice on some donor boards first. Before you delam a viable candidate like this one.
 
Yes, there is no personal previous experience. Is there any guide for A01 40nm RSX swap? What else must be done? Any step-by-step tutorial? I'm thinking to try by myself vs asks a professional for a service (35$ for RSX swap service).
 
I would be skeptical of anyone offering an rsx swap for $35. You do realize you need to spend well over $1000 in equipment just to perform this mod right? It doesn't make sense to buy all that equipment just to Franky your own personal console. You're also posting in a Frankenstein mega thread which had a detailed guide by rip FELIX:

https://www.psx-place.com/threads/f...cecha-with-40nm-rsx.28069/page-76#post-324546

Be aware that this guide doesn't necessarily cover the process on removing the 90nm rsx or soldering the 40nm rsx. That is something you need to experience first hand with trial and error..

My personal opinion, pay someone to do this for you. You're going to most likely spend thousands of dollars and kill several boards before you get the hang of it.
 
I have a friend in HP service center. He mostly does notebooks and other PC stuff. I asked for assistance with RSX swap. That's why this price is low.
I have a lot of A01 boards, that is collected 7-8 years ago. Decided to finally take a hand on them and try a frankenstein mod.
Thanks for a link.
 
>$ becount
becount
Bringup : 3304 times
Shutdown: 3130 times
Power-on: 277day 05hour 36min 50sec
[mullion]$
>$ errlog
errlog
ofst[ 56]:err_code:0xffffffff, clock:0x1c36fe34 2014/12/31 18:34:28
ofst[ 60]:err_code:0xa0801001, clock:0x1c38f0a2 2015/01/02 06:01:06
ofst[ 64]:err_code:0xa0801001, clock:0x1c3b6f99 2015/01/04 03:27:21
ofst[ 68]:err_code:0xa0801001, clock:0x1c3c5c54 2015/01/04 20:17:24
ofst[ 72]:err_code:0xa0801001, clock:0x1c3f0a8e 2015/01/06 21:05:18
ofst[ 76]:err_code:0xa0801001, clock:0x1c41e977 2015/01/09 01:20:55
ofst[ 80]:err_code:0xa0801001, clock:0x1c422e38 2015/01/09 06:14:16
ofst[ 84]:err_code:0xa0801001, clock:0x1c42339b 2015/01/09 06:37:15
ofst[ 88]:err_code:0xa0801001, clock:0x1c452496 2015/01/11 12:09:58
ofst[ 92]:err_code:0xa0801001, clock:0x1c55ebc8 2015/01/24 05:36:08
ofst[ 96]:err_code:0xa0801001, clock:0x1c73e8d7 2015/02/15 23:31:35
ofst[100]:err_code:0xa0801001, clock:0x1c777439 2015/02/18 16:03:05
ofst[104]:err_code:0xa0801001, clock:0x1c77fef7 2015/02/19 01:55:03
ofst[108]:err_code:0xa0801701, clock:0x1c87b17c 2015/03/02 23:40:44
ofst[112]:err_code:0xa08014ff, clock:0x1c87b17d 2015/03/02 23:40:45
ofst[116]:err_code:0xa0801601, clock:0x1c87b17d 2015/03/02 23:40:45
ofst[120]:err_code:0xa0801701, clock:0x1c87b220 2015/03/02 23:43:28
ofst[124]:err_code:0xa08014ff, clock:0x1c87b220 2015/03/02 23:43:28
ofst[ 0]:err_code:0xa0801601, clock:0x1c87b220 2015/03/02 23:43:28
ofst[ 4]:err_code:0xa0801701, clock:0x1c87b264 2015/03/02 23:44:36
ofst[ 8]:err_code:0xa08014ff, clock:0x1c87b264 2015/03/02 23:44:36
ofst[ 12]:err_code:0xa0801601, clock:0x1c87b264 2015/03/02 23:44:36
ofst[ 16]:err_code:0xa0403034, clock:0x1c87b284 2015/03/02 23:45:08
ofst[ 20]:err_code:0xa0403034, clock:0x1c87b2a2 2015/03/02 23:45:38
ofst[ 24]:err_code:0xa0403034, clock:0x1c8a3e13 2015/03/04 22:05:07
ofst[ 28]:err_code:0xa0403034, clock:0x1c8e669c 2015/03/08 01:47:08
ofst[ 32]:err_code:0xa0403034, clock:0x1c95eec2 2015/03/13 18:53:54
ofst[ 36]:err_code:0xa0403034, clock:0x1da708c0 2015/10/06 22:33:36
ofst[ 40]:err_code:0xa0403034, clock:0x1da70920 2015/10/06 22:35:12
ofst[ 44]:err_code:0xa0403034, clock:0x1da82e06 2015/10/07 19:24:54
ofst[ 48]:err_code:0xa0403034, clock:0xffffffff
ofst[ 52]:err_code:0xa0403034, clock:0xffffffff

other CECHA01 board. 1st one - currntly in service center. Will try to install RIP-Felix Tantalizers first, as master told me - these little fuckers are a common problem in notebooks. I will post results here.
 
That's not what the syscon error log is telling you. Why even bother dumping it if you're just going to do a random "fix" anyways. The only way tokens will fix that console is if you use heat at some point to remove/add them. Sometimes people use so much heat they end up temprarily fixing the rsx.
 
You must log in or register to reply here.

Similar threads

Back
Top