The above video goes away if you are a member and logged in, so log in now!
So, did the modified CD just flash the default (CC1.2) firmware?
Originally Posted by pathan
Or did it complain that no CC2.0 firmware is available?
If it is the former, I guess you could try using the modified 29 first and then the normal 31 CD, because I'd guess maybe it won't BSOD with the CC1.2 fw 31 flashed into the dataflash?
Because as far as I can see a dedicated firmware for CC2.0 was introduced first with the firmware 30 CD, with 29 and older you'd flash the CC1.2 firmware for both chip versions (1.2 and 2.0).[/edit]
i have the same exact problem as pathan but i am using an ntsc v15 cc 2.0.
Originally Posted by pathan
i tried doing this but cd 31 would not load after the flash.
Originally Posted by ranmachan
I tried copying the FWARE20.CCI file from the 31 release TMP folder to the 29 release root and renamed it to FWAREDF.CCI and set the read-only flag. I commented out the line in the makeit.bat that calls ccigen.exe for that file and ran it to create a new bin file with the 30/31 firmware. I was able to boot this disc up and select the upgrade/install firmware menu option. The status stayed up a bit longer and I think I got a couple more dots, but I got no error. When I restarted the unit though all I got was a black screen again. I was able to recover back to 29 again thankfully. I wish someone from Crystal would at least acknowledge they are aware and working on this issue somewhere.
GH-051-51 & CC2.0
They are very aware, look at the news post on the homepage: http://crystal-chips.com/main/conten...category/1/29/
Hopefully all the problems will be solved soon, but for now I suggest to stick with FW29. It's really stable, compatible with all homebrew and video fixes are fully functional. The new features are cool but IMHO not worth the trouble. IGR isn't working with all games yet and the button feature is nice but the old one is still ok.
best regards Jones23
At least they acknowledged it is being worked on. That's all I need to know.
Do any of you with CC1.1/1.2 use ps2link to upgrade? If so, please look at the tty output(the text printed to ps2client) and watch for "CC_EEP_Write failed -1" or something similar after upgrading fails. Unfortunately I don't have access to a CC1.1/1.2 at this time and the problem does not seem to occur for me on CC1.0.
To clear up some confusion, Release 29 had the CC2.0 firmware embedded inside of BootManager to help shorten development time. The CC1.2 firmware was still only for CC1.2.
Originally Posted by CrystalChip
I wish I had a CC 1.2 to help you
CrysltaChip : I was reading your request again but how could you upgrade with ps2link while booting in recovery mode ?