PS3 Frankenstein PHAT PS3: CECHA with 40nm RSX

if it were a laser issue the PS2 game wouldnt recognize and load. The HW related noPS2 scenarios I'm referring to will load to a black screen, so it cant be the laser. Just wanted to clearify.

Also, make sure that you are using defaut video settings and upscaling. Performing a video reset will put it into a state that should always work.[/QUOTE]
i have disable all upscaling and smooth i put ps2 DVD and only show black screen and only shows menu
upload_2024-3-2_17-26-11.png
upload_2024-3-2_17-27-38.png
upload_2024-3-2_17-28-11.png
upload_2024-3-2_17-28-47.png
 
dvd video works i puted GT4 prologue dvd and works so its can be an cxd9208gp problem or an need some program or patch for rsx 40nm i don't know is something the real masterminds can discover i only an amateur
upload_2024-3-2_17-39-50.png
upload_2024-3-2_17-41-21.png
 

Attachments

  • 41028-f5256483d42ece5a4f6748a361aac4f2.png
    41028-f5256483d42ece5a4f6748a361aac4f2.png
    11.1 KB · Views: 51
maybe is cxd9208gp chip faulty or need some patch this chip communicate with RSX 40nm i dunno but what i've searched in internet many frankenstein CECHA has problems with ps2 maybe someone will find the solution but i believe some cxd9208gp can be uncompatible with newer RSX maybe
 
ha there was a case when this cxd9208gp also known as ps2 bridge chip was causing issues. the bad thing about this chip is it can be harvested only from ps3. unlike ee/gs or rams that can be found on ps2 slim 7500x and possible on ps2 7700x
 
Like I said. This has nothing to do with the mod. It's not limited to the mod. It will happen to unmodified consoles too.

If GT4 plays (a ps2 game) then this isnt a no ps2 issue. More likely an issue with your laser, or disc. Maybe, you are trying to play one of the few games that dont work?
 
Like I said. This has nothing to do with the mod. It's not limited to the mod. It will happen to unmodified consoles too.

If GT4 plays (a ps2 game) then this isnt a no ps2 issue. More likely an issue with your laser, or disc. Maybe, you are trying to play one of the few games that dont work?
I say DVD video from original Disc of Gt4 prologue the dvd extra comes with the box who has original not the game its self
 
It may be a stupid theory, but does ps2_emu.self itself not need to be patched for the new RSX? Some RSX may have different references or different codes, I don't know LOL is somethng strange why some ps3 has no_ps2
 
Hi I am new here, I just wanted to thank all of you who have come up with how to do this mod, I am an intern at a computer repair store who is using these resources to try to do a frankenstein on my own. So far i have been sucessful and learned a lot. My checha01 has the rsx codes using the uart to syscon method, so I am currently sourcing the 65nm one. I already have done the preliminary resistor mod, I will let you all know how my first reball and my first frankenstein goes (I expect failure, but have hopes). I made myself do it as an internship project because I really wanted the challenge, even though I was expected to sit and replace a phone screen once in a while. Thanks to this thread, I can attempt to do something crazy with a chance of success.
 
When writing the syscon training data what part is changing my CELL fan speed, step 1&2, to 100%. This is the second unit thats its happened on.
This is what I wrote to syscon
w 3242 03 61 82 80 01 91
w 3254 21 EC
w 348B 8B
w 34AF 8B

This is my fan table
fantbl getini 0
fancon No:00
P0: TempD:0.0(0x0000) - TempU:74.0(0x4a00) duty:100%(0xff)
P1: TempD:60.0(0x3c00) - TempU:75.0(0x4b00) duty:100%(0xff)
P2: TempD:61.0(0x3d00) - TempU:76.0(0x4c00) duty:28%(0x48)

After I changed the syscon data it started up to the menu and the fan was normal. I did the voltage mod and then it went turbo.
 
Last edited:
What codes should I see if bittraining failed? is it 404002 and 403034?

This E01 has instant YLOD after putting a 5301A1GB on it. If I use EB instead of EC I get 404002 and 403034, with EC I get 404102 and 403034.

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

My CPU VDDC was 2.2 ohms, BE_PLL line was only 250k, MC_VDDIO 3.5K. Dead CPU? RSX measurements were good, both on and off the board.

before the RSX replacement
errlog
ofst[ 0]:err_code:0xa0403034, clock:0xffffffff
ofst[ 4]:err_code:0xa0801701, clock:0x0b48869f 2005/12/31 00:00:31
ofst[ 8]:err_code:0xa08014ff, clock:0x0b48869f 2005/12/31 00:00:31
ofst[ 12]:err_code:0xa0801004, clock:0x0b4cf207 2006/01/03 08:27:51
ofst[ 16]:err_code:0xa0802022, clock:0x0b4e148d 2006/01/04 05:07:25
ofst[ 20]:err_code:0xa0802022, clock:0x0b4e1584 2006/01/04 05:11:32
ofst[ 24]:err_code:0xa0801001, clock:0x0bd08f16 2006/04/13 04:24:54
ofst[ 28]:err_code:0xa0801701, clock:0x0dada065 2007/04/10 01:09:57
ofst[ 32]:err_code:0xa08014ff, clock:0x0dada065 2007/04/10 01:09:57
ofst[ 36]:err_code:0xa0801701, clock:0x0dada402 2007/04/10 01:25:22
ofst[ 40]:err_code:0xa08014ff, clock:0x0dada402 2007/04/10 01:25:22
ofst[ 44]:err_code:0xa0801701, clock:0x0dada782 2007/04/10 01:40:18
ofst[ 48]:err_code:0xa08014ff, clock:0x0dada782 2007/04/10 01:40:18
ofst[ 52]:err_code:0xa0801701, clock:0x105c787e 2008/09/12 00:46:54
ofst[ 56]:err_code:0xa08014ff, clock:0x105c787e 2008/09/12 00:46:54
ofst[ 60]:err_code:0xa0801001, clock:0x0b4887cd 2005/12/31 00:05:33
ofst[ 64]:err_code:0xa0801701, clock:0x11d0376e 2009/06/21 00:12:30
ofst[ 68]:err_code:0xa0801601, clock:0x11d0376f 2009/06/21 00:12:31
ofst[ 72]:err_code:0xa0801701, clock:0x11d0379a 2009/06/21 00:13:14
ofst[ 76]:err_code:0xa0801601, clock:0x11d0379a 2009/06/21 00:13:14
ofst[ 80]:err_code:0xa0404402, clock:0x11d03825 2009/06/21 00:15:33
ofst[ 84]:err_code:0xa0403034, clock:0x11d03825 2009/06/21 00:15:33
ofst[ 88]:err_code:0xa0404402, clock:0x11d0383c 2009/06/21 00:15:56
ofst[ 92]:err_code:0xa0403034, clock:0x11d0383c 2009/06/21 00:15:56
ofst[ 96]:err_code:0xa0404402, clock:0x11d038b8 2009/06/21 00:18:00
ofst[100]:err_code:0xa0403034, clock:0x11d038b8 2009/06/21 00:18:00
ofst[104]:err_code:0xa0404402, clock:0x141179c5 2010/09/01 20:53:25
ofst[108]:err_code:0xa0403034, clock:0x141179c5 2010/09/01 20:53:25
ofst[112]:err_code:0xa0404402, clock:0x14117a1c 2010/09/01 20:54:52
ofst[116]:err_code:0xa0403034, clock:0x14117a1c 2010/09/01 20:54:52
ofst[120]:err_code:0xa0404402, clock:0x14117a2a 2010/09/01 20:55:06
ofst[124]:err_code:0xa0403034, clock:0x14117a2a 2010/09/01 20:55:06
 
Last edited:
Honestly I believe these resistance reading are worthless outside of open and shorts in various circuits. Ive installed chips way outside of the "good" values and they have worked fine.
+1 has a pll short and is bad, #3 is questionable with that low reading. Are those VDDC values correct? They should be 2-4 ohms not K ohms
 
Honestly I believe these resistance reading are worthless outside of open and shorts in various circuits. Ive installed chips way outside of the "good" values and they have worked fine.
+1 has a pll short and is bad, #3 is questionable with that low reading. Are those VDDC values correct? They should be 2-4 ohms not K ohms
lol yes ohms sry did this early this morning, tanxs
 
This E01 MG is kicking my butt. I put the RSX on another E01 and it worked fine. I put a different 5301A1GB and now im getting 404402 and 403034. Its not instant though, I can hear the fan about to kick into full speed then YLOD.

Reflowed chip same error same time frame. Just checked and my CELL VDDC is now 1.2 ohms so it looks like the CELL is dead.

Err something on the bottom of the board ignited. I heard of poof sound like when you start a gas burner and I looked under the board to see a drop of fire on my IR heater. Turned the board over and there is black scorching around the TOKINS. Odd, the board hadn't even reached 180C on bottom. Using my normal LF profile. Never seen this before in the nearly 2k PS3s I've reballed.
 
Last edited:
This E01 MG is kicking my butt. I put the RSX on another E01 and it worked fine. I put a different 5301A1GB and now im getting 404402 and 403034. Its not instant though, I can hear the fan about to kick into full speed then YLOD.

Reflowed chip same error same time frame. Just checked and my CELL VDDC is now 1.2 ohms so it looks like the CELL is dead.

Err something on the bottom of the board ignited. I heard of poof sound like when you start a gas burner and I looked under the board to see a drop of fire on my IR heater. Turned the board over and there is black scorching around the TOKINS. Odd, the board hadn't even reached 180C on bottom. Using my normal LF profile. Never seen this before in the nearly 2k PS3s I've reballed.

What codes should I see if bittraining failed? is it 404002 and 403034?

This E01 has instant YLOD after putting a 5301A1GB on it. If I use EB instead of EC I get 404002 and 403034, with EC I get 404102 and 403034.

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

Your Bringup log isn't complete, what is the error message from the Bittraining line?
 
Hello, RIP-Felix
Did you find a way to fix PS2 games with Frankie mod? I modded mine CECHA00 model, after this PS2 games stopped working: I have blackscreen, but I can open menu and close the game.
I have the same problem as you and the coincidences are not just that, my PS3 is an A00 with a 40nn RSX but unlike yours, mine was not made by Sony, anyway after a few months it started to present problems with o the ps2 games, first freezing during the game and now just a black screen... sometimes the ps2 logo appears, other times not, but the menu is accessible... I was thinking about reballing the EE+GS... a final coincidence and that I'm Brazilian too, I'll send a PM so we can exchange information
 
Oh, boy! That's a big topic and it takes a long time to learn all the tricks. It all depends on what you're trying to use and how much time you are willing to put into practicing.

Tips...
  1. Bake MB and Donor board for 24-48hours at 125C to thoroughly dry them both prior to rework. This is very important. Rework must be completed within 8 hours after baking or the moisture will seep back in and require baking again.
  2. Use a MB support jig
  3. preheat MB to at least 180C-200C, with thermocouple placed away from the top heater so it doesnt interfere with the preheat temp.
  4. Lead free SAC305 melts at 218C and depending on your thermocouple and top heat method (hot air or IR) it could read higher before reflowing.
  5. Reballing the RSX is hard. You need a jig and stencil. Getting a thin layer of flux is important. Using a microscope helps alot. There are lot's of little tricks during this stage that you will have to learn and for me was/is the most frustrating part.
  6. Nudge the Reflow. Giving a gentile nudge on 2 corbers of the chip to see if it springs back before lifting helps to know it's ready to be lifted. The same when soldering back on tellys you it's actually reflowed compeletly and can also help to force balls that are being stubbarn to wick to their pads. Good surface prep should avoid this but it's a good idea anyway. GENTILE nudge! Dont merge the balls tapping too hard.
  7. use good flux and thoroughly clean it off afterward! Rosin Mild Activity flux is "mildly" acidic and can damage the pads eventually. Many people don't clean properly. An ultrasonic cleaner is reccomended.
  8. much more...
Beware all ye who enter. BGA rework is difficult AF and expensive to get right.
Felix, a friend of mine, did an experiment after realizing that his Cech b's CELL was beyond repair due to oxidation of the pads. instead of just changing the board for one from a cech A, he replaced both the damaged cell and the nand and the syscon from cech a to b, to top it off he made a frankie with a 65 rsx... the whole procedure was a success except that it doesn't work via cable or network, the bluetooth works after 5 minutes of trying to connect.... have you ever come across a case like this in Frankie's Frankie?
 
Back
Top