PS2 Reprinting/Cloning CrystalChip 2.0SLE

[R3Z3N]

As I prepare to move my CrystalChip 2.0 SLE from my 79000 slim to a 70012 for a Retrogem Shiny, Methylene and iFlashPS2 I had a thought:

Lend the CrystalChip 2.0 SLE to someone that has the ability to reverse engineer and print new copies,populate the board, and flash it with the legal FW. Legal and Hacked R34v2 can be found, I have them both backed up along with Boot Manager...

I hate being stuck with Modbo/Infinity(whatever crap clone is out now) when history had so much better. I have been on the hunt for a second Crystal Chip but alas no such luck for the project.

So....thoughts on who best to work with to get this done? I would love to reintroduce one of the best modchips that also has a laser fix built in! Imagine if we can up the storage from 2MB to something larger as well....

 

[Berion]

CrystalChips 2.0 have i.e issues with USBD. Now it will be super annoying since BDM is incompatible with it. Just FYI.

There is a chance to make CC src opened.

 

[R3Z3N]

Being that USB Drive compatibility/playability is one of the worst methods to play currently, I am not worried about that. Either way I know I haven't seen any issues with USBD via my crystal chip that is abnormal outside of USBD. Simply load OPL onto the Crystal Chip and load from there...or put OPL on a memcard and point the CrystalChip to OPL.....same difference as using FreeMcBoot

Have been using SMB but going to move forward with iFlash PS2 along with the newer NBD? Methods I do not think what you mentioned is a problem, especially as one can install OPL onto the chip itself. Though I have not kept up please inform me if needed.

I too agree with making this as open as possible so that options abound.

As far as source dissasembly, I do believe it can be done. We did it with my BMWs ECU which required a sneakernet theft of the definition file in shorthand german for a version that never existed, and now the ecu can run in any chassis. AI was a blessing there to help find shifting blocks of code as every version moved maps and map sizes around. It always depends on the right people getting involved and this scene is bigger than the 6 that disassembled the BMW code.

 

[El_isra]

Being that USB Drive compatibility/playability is one of the worst methods to play currently,

keep in mind that if the chip messes with USBD.IRX it means that not only playing games through it will be affected. any I/O op will have issues. even just basic file browsing

 

[R3Z3N]

Luckily I have not had that issue. I messaged someone who was part of the CC development, but they have not been active where I found them since 2023, and sadly the drive that has source is needing data recovery. I luckily have DeepSpar for data recovery but alas they need to respond.

 

[Luisile]

No point in recreating those. Modbo 5 will do a way better job and they are cheap. I only use modbo exclusively

 

[El_isra]

The ideal thing is a bootROM replacement.

And a modchip soli for messing with the Mechacon and DSP and whatever.

That would allow backups playing without breaking ANY homebrew

(Of course, biggest problem is, again: who the hell will make it?)

 

[R3Z3N]

No point in recreating those. Modbo 5 will do a way better job and they are cheap. I only use modbo exclusively

Quoted for the laughs. I've installed many of the clones, was involved 2002-2007, but luckily was also involved in the good ol days and the CC is the one to beat...until you've had one you will never know. Looking at archived sites, theres a small handfull that I have not installed and used extensively. Matrix/modbo are ok at best, only installed due to cheap cost. I think the CC was only $60 when I got them in batches.

BTW CC has a mechacon fix built in...either way I still use a picfix but haven't used a disc for over 10 years.

 

[Luisile]

Quoted for the laughs. I've installed many of the clones, was involved 2002-2007, but luckily was also involved in the good ol days and the CC is the one to beat...until you've had one you will never know. Looking at archived sites, theres a small handfull that I have not installed and used extensively. Matrix/modbo are ok at best, only installed due to cheap cost. I think the CC was only $60 when I got them in batches.

BTW CC has a mechacon fix built in...either way I still use a picfix but haven't used a disc for over 10 years.

Quoted for the laughs. Recreate old modchip for 100 or use the best what is today for literaly 2euro and will do better job? no thaks im staying with modbo.

 

[R3Z3N]

keep in mind that if the chip messes with USBD.IRX it means that not only playing games through it will be affected. any I/O op will have issues. even just basic file browsing

Was re familiarizing myself with functions of the chip, and you can easily choose to load usbd.irx or not. Even lets you install it onto other devices. The PBAT script for BootManager can be edited to add/remove more options as well. From there the gui allows load these IRX to USB/Flash,Mass: Flash, USB, PC HOST, FTP, iLink. I should buy a capture card and do a YT vid on it....

keep in mind that if the chip messes with USBD.IRX it means that not only playing games through it will be affected. any I/O op will have issues. even just basic file browsing

Should have updated quite a long time ago. Using your BDM Assault IRXs just fine with BootManager.... However no such luck yet if I wish to boot BootManager from USB by editing makeit_nocd for DEV Mode 2 (boot BM from USB) Was just trying for fun.

 

[R3Z3N]

So after talking to several companies and even willing to send ~$30-50K to try to reverse engineer even just 1 chip and sacrifice the 4 that I have, the companies I was in talks with in SV convinced me the chances with this FPGA are so very slim it would be better off to get with others and create a whole new modchip and set of code. Not willing to get the company involved in something more gray area so dead end.

I will still spend ~3-4k to help me build another pcb for my CC2.0s as one seems to potentially have trace rot on underside though works fine still.

Either way here:
https://github.com/saildot4k/Crystal-Chip-R34-v3

Made the FW builder script to build the FW for booting BM from MC0 and MC1 (singular choice) Working on failover instead later
FW upgrade options only show chip specific options (IE CC2.0 no longer showing CC1.x options)
Using BDM assault
Changed CD recovery mode to allow run/install/remove apps from all interfaces
Changed scripts so that any chip specific features (IE dataflash or running from BM from memcard) are hidden from respective choices for end user
Using __common instead of +Crystal partition so that user has 1 less step which should already be done for any prior HDD install
Changed USB HDD text to just USB
Few more things for cleanup/ease of use

Hopefully next biggest change will be failover if mc0:/BM/BM2.ELF doesnt launch to then try to launch mc1:/BM/BM2.ELF
I have FW tests to do for the larger 1056byte page 8MB dataflash, and I believe the team got the expected values wrong for opcode D7H to calculate which dataflash was installed hence the 2MB using the incorrect page size and random losing FW. Basicially takes the 8bit opcode shifts right 3 and masks LSB7-3 and team said values should be 0x01-0x06. Notes are actually wrong as well showing 2 4MB options with differering pages, not true. 8MB Dataflash is actually 0x07...soo just waiting for my microsoldering expert to hotplate and hot air the flash off for the larger 8MB. Already have code for that logic and larger page size ready to test....but not on github yet.

and maybe just maybe follow the UMCS and SAS standards


Future discussion from me will be here:
https://www.psx-place.com/threads/crystal-chip-r34-v3-development.45472/