Dumping Nintendo 64 cartridges

[ConsoleFun]

Well i tried last week or so again and i got it work under XP pro SP2
You need to copy two files in the System 32 and Driver Folder and set compatibility Mode to Win 2000. Works great, no Win98SE anymore ^^

Yeah, you need drivers to get access to i/o ports in Microsofts NT-based operating systems.

What I am talking about is the mode of the parallel port (standard SPP, IBM bidirectional, EPP 1.7, EPP 1.9, ECP, EPP+ECP etc.). V64jr requires the parallel port to be EPP 1.9 compatible. Other modes don't work AFAIK. So EPP 1.9 emulation in software is really nice (slow, but working) for those who don't have EPP 1.9 compatible hardware.

[andoba]

What about the other way out? There is some actual way for connecting EPROM's or similar to the N64 withouth using external hardware? With glue logic or a cheap CPLD it could be sorted out, or it's more extensive?

[Calpis]

Yeah, you can make a N64 cartridge from EPROM, but EPROM only go up to 32Mbit and are extremely rare at that size.

[Infrid]

CD64 actually needs a special adapter that sits between the CD64 and the parallel port.

no problem
http://n64.icequake.net/doc/cd64-ppa...rtadaptor.html
Mirror

[TranceDoll]

For those of you interested in using a GameShark to dump, you can refer to this guide I wrote a year ago:
http://ts.death.angel.googlepages.com/gamesharkstuff

If anyone in Europe needs their carts dumped I am located in Norway :P

[WolverineDK]

For those of you interested in using a GameShark to dump, you can refer to this guide I wrote a year ago:
http://ts.death.angel.googlepages.com/gamesharkstuff

If anyone in Europe needs their carts dumped I am located in Norway :P

Damn, you are a Norwegian ? wow I thought there were only one from my northern neighbour country . Cool, now I know there are more Norwegians on board :) (sorry to go offtopic) carry on.

[Sojiroh]

Thanks marshallh for this excellent guide, because of this we may get a banjo kazooie kiosk rom (it seems to have quite a bit of beta stuff in it).

[Jackhead]

hi,
im looking for an IPL-ROM cart of the 64DD dev unit.
After research in the web i was thinking about making an cart by myself with an flash cart. I found this http://www.ic2005.com/shop/product.p...5&cat=0&page=1 . Im not sure if this works when i get my hands on a ipl-rom image from the dev cart?
Also im not sure if someone have an dump of the cart? Or was only the retail ipl image dumped?
Hope you guys can help me.
regards
Chris

[Jackhead]

Thanks so far! Maybe interested in the Partner-N64 env V2.0 ?

[Nintendo]

best dumping method is Z64 if you have it. Use to own one but had to sell it for money.
Work great for dumping the MASK ROM data or EMULATION playing

[CZroe]

I recall requesting the GameShark ROM dump feature from the CMGSCCC guys before it was in the software. I mostly used it for accurate screen shots since I had much better ways to dump, but I thought it was an obviously useful feature for others.

It works :) I just dumped the Kirby dev cart with a V64Jr using ZiyalII. The command line is simply:
ziyalII [CIC-Type]

The CIC-types supported by ziyalII are listed in the included documentation (all CIC-types seem to be supported). Once executed the program will upload the dumping software to the V64jr. Then simply follow the on-screen instructions.

The only snag is that the dumping code needs to run on the N64. So you need a PAL N64 to dump a PAL cart, and a NTSC N64 to dump a USA/JPN cart, if you don't use any import converters or other tricks (i.e. replace the CIC in the cart).

If anyone is curious; there was nothing special on those other two dev carts either. One seems empty / dead. The other booted with a Paradox crack intro, so it was no prototype or beta or anything exciting....


Good to know! You need a PC with an EPP compatible parallel port, or does it do EPP emulation in software?

What I really like about elim and ziyal is the EPP emulation which makes them compatible with all kinds of old and new parallel ports :D

You don't need a PAL N64 to dump a PAL game with a V64jr. You can run a 7101 PAL game on 6102, a 7102 PAL game on 6101 (StarFox 64 was the only one), and all the rest relate directly (for example, 6104 = 7104; 6105 = 7105). Even if you cant see it, the software will boot and the dump should still work.

What would be the best way to do this?

I have a 512Mbit V64 Jr. (ehh, E64 actually). Usually I use elim, because of EPP emulation in software, for uploading code...

As far I as remember elim, ucon64 and wJrWrite don't support dumping....


Did you find an easy way to dump dev carts? :-)

Obsidian made a whole suite of excellent tools with EPP emulation (elim, evek, ziyal, etc). Dextrose blocked their tools because they believed the 8 bytes needed to support each CIC were copyrighted Nintendo code. This was silly because, even if it were protected by copyright, all utilities and homebrew for 6102/7101 games had the standard header bytes for 6102/7101 and no one pulled those. Also, copyright law typically provides an exception for necessary header duplication to allow for code execution. It's why Datel and others could put the Nintendo logo in their unofficial Gameboy stuff to get by the BIOS check on a Gameboy and a NHL Hitz header on the Gamecube.

Thanks so far! Maybe interested in the Partner-N64 env V2.0 ?

That would be: YES!

best dumping method is Z64 if you have it. Use to own one but had to sell it for money.
Work great for dumping the MASK ROM data or EMULATION playing

As established earlier in this thread: No. It isn't. It doesn't even work with dev carts.

[Zoinkity]

A memory dump from ROM uses code 127. IIRC, you can read any address from rdram or ROM using it from within the GS menus. Copied this from my third GS access demo. Stupidly, I did a disassembly of the possible commands, then got a list from one of the devs ;*) Still not brave enough to try uploading a BIOS.

Original was here, 16bit app built in TurboC 2 on win3.1:
http://www.mediafire.com/download.php?71ttht1tjyv85x3
I'll have to double-check this code, but if you were using HCS's code source as a base:

#define AR_MEM_DUMP 127
#define AR_DISCONNECT 'd'
#define AR_END 'e'

int MemDump(FILE * infile, unsigned long size, unsigned long address) {

unsigned long c=0,x=0,y=0;

/*ensure address and size are word-aligned */
address+=3;
address&=-4;
size+=3;
size&=-4;

if (SendCommand(AR_MEM_DUMP)) return 1;
ReadWrite32(address);
ReadWrite32(size);
printf("Writing to file... 0%%");
for (c=0; c < size; c+=4) {

y=ReadWrite32(0);
y=byteswap(y);
fwrite(&y,4,1,infile);
x+=y;
if (c & 0x400) printf("\b\b\b%2d%%",c*100/size);
}

printf("\b\b\bDone.\n");

/*confirm data valid*/
x&=0xFF;
y=ReadWriteByte(0);
if(x!=y) printf("Checksum invalid!\t%02X\t%02X\n",x,y);

return x!=y;
}

int SendCommand(char command) {

if (InitGSComms()) return 1;
ReadWriteByte(command);
return 0;
}

Some other random defines:

/*Defines for some of the commands*/
#define SH_VERSION 'f'
#define SH_UPDATE 'g'
#define SH_NEW_BIOS 'n'
#define TR_SCREENSHOT 'r'
#define SH_D_CODELIST 124
#define SH_U_CODELIST 125
#define SH_ROM_DUMP 126
/*BIOS update modes*/
#define UPDATE_OVERWRITE 0
#define UPDATE_NO_WRITE 1
#define UPDATE_UNENCRYPTED 2

SH_ROM_DUMP is an interesting one. It dumps a given number of bytes from 80500000. So, if you use it, send the command, then a long size. Don't send an address. Not sure if it's targeting the shell or the trainer honestly.

This demo plays tricks with the trainer and isn't nearly as interesting.