The whole point of the key chips is to restrict the use of the GD-ROM disks. Each GD-ROM has a unique key chip that "unlocks" it.
- Thread starter rtw
- Start date
i think he's concerned about contact wear on the socket - whitch is a shitty pressed-pin type too.
i wonder if an adapter could be thrown together that holds say 10 chips and switches between them.
it would be better though to just switch to CF cards.
i wonder if an adapter could be thrown together that holds say 10 chips and switches between them.
it would be better though to just switch to CF cards.
Let me try explaining.
Every GD-ROM title is encrypted using a unique encryption key (think very long password) the key chip stores the decryption key (password). You can't mix and match keys and titles.
The deal with the zero key is for preservation using copied titles. GD-ROMs at this point are dying like flies. Naomi etc don't have an option to *not* decrypt titles. So, the community agreed that all copied titles would be encrypted using the same key (password): all zeros. Zero key.
of course... and the netdimm images are modified to use zero pic .
I'll remember to post after having coffee
RadiantAnsel
Student
Oh, thanks! I appreciate.
I only own a Naomi (without any GD Rom or such) at the moment, but want to get into the library mostly because of Senko no Ronde SP, TriZeal and other games I play very frequently.
Pretty sad to see the actual GD Rom dying, but that's just how technology works.
These settings worked for me with Xgpro v11.30 and the TL866II Plus programmer.success #2
clintkolodziej
Enthusiast
I'm reasonably certain that the attached hex files should produce a single PIC that will allow both netbooting and CF loading (ABC.BIN) of decrypted game files. One should just have to set the DIMM jumpers accordingly.
I've included two versions; a 'normal' one and a byteswapped one. I had to use the byteswapped one with GQ USB Programmer software and my GQ-4X programmer, writing to a PIC16F628A chip.
I've tested CF loading on NAOMI with a 4.02 net DIMM. I'll leave netboot testing for someone else to try.
I'd also appreciate someone testing both CF loading and netbooting on Triforce and Chihiro setups, since I don't have either!
Just sharing my experience using the GQ-4x4 to create a zero pic. I just picked up this programmer and used the OP's BIN files and settings and wasn't having any luck. When I tried using the byte swap function on the buffer before writing it wouldn't verify (this was mentioned as a possible thing to check). I found idc's post and used the HEX files that were provided and that wrote just fine and worked on my Naomi NetDimm (via netboot).
I did notice three things:
- With this HEX file it auto populates the Configuration automatically, which has a different 0x0082 value due to some "CP" bits set OFF (you can see this by clicking the Configure Device button and scrolling down in the Standard CFG Word Configuration box). I tried doing the same with the BIN image but it kept failing to verify when I did that.
- The buffer with the HEX file and the BIN from the OP with byteswap applied looked similar, but some of it was different. Byteswap definitely looked like it was probably necessary but I can't account for the differences unless the code for each PIC used to create the BIN/HEX was slightly different. Both were for the NET/CF version.
- The "USER ID" in the idc image had 4 "3FF0" settings, where as the original BIN posted had "3FFF" for each
If anyone knows the settings for the GQ software to make the original BIN files to work that would be great to know and document, but for any others with this device you may want to check out the HEX files posted by idc. It would also be useful to know what the difference between idc and rtw's files are as far as functionality, to explain the difference in the buffer code.
I can't post this without a big thanks to idc and rtw and everyone else for the info here, it helped me fumble my way thought getting this done.
Casselfornia
Student
I am in Germany, so shipping wouldn't totally kill it. The Zerokey is the same for Naomi/Chihiro/Triforce?
ShootTheCore
Legendary
I can make you one if you're willing to pay for the shipping from the US to France.
Last edited:
I can confirm here that the net version of bin file in the first post works with Type3 Triforce. I converted it to Intel hex file and burned it with PICKIT software. Being able to play VS 2002 for the time being since you need analogue IO for other games.
Last edited:
well since there are no pic16f628A around, I had bought some pic16f628 (no A!) and darn it, the TL866 II plus does not support without the A ... so I had to use my GQ-4x4 and the byte swapped hex and no go with these settings on a Chihiro.
Device: PIC16F628A
The archive contains 2 files:
ABC_BIN_0000000000000000.bin
Suitable for CF and standard GD-ROM, DES KEY = 0000000000000000, Loader name: ABC.BIN
ABC_BIN_0000000000000000_NET.bin
Suitable for Net-Booting, DES KEY = 0000000000000000
archive: View attachment naomi_pic.zip
The following programmer settings should be used.
Oscillator: HS
WDTE (watchdog) disabled.
PWRTE (power up timer) enabled.
Code Protect: All protected
MCLRE should be set to internal also called "disabled"
BOREN/BODEN (brown-out reset) disabled.
LVP (low-voltage programming) enabled.
CPD should be 0, meaning that data code protection is on
This should give a config word of: 0x1e82
Huge thanks to @zeruel85 for verifying these settings
Verified Compatibility:
CF and standard GD-ROM
NAOMI1, NAOMI2, Chihiro, Triforce
Net-Boot
NAOMI1, NAOMI2, Chihiro, Triforce
Note:
The Net-Boot version: ABC_BIN_0000000000000000_NET.bin works with Chihiro and Triforce in both CF,GD-ROM and Net-Boot mode.
It is only the NAOMI system which requires: ABC_BIN_0000000000000000.bin for CF and GD-ROM.
I tried with this set:
but dont work:
Last edited:
@nonosto please see this post:
https://www.arcade-projects.com/thr...n-naomi-chihiro-and-triforce.6611/post-198196
https://www.arcade-projects.com/thr...n-naomi-chihiro-and-triforce.6611/post-198196
