Cart-console interaction

[Alptraum]

Hi guys, I'm new to the forum so I'm sorry if this is in the wrong place.
I'm trying to get my head around the interaction between the cart and the console.. does the console put the ROM into its RAM or does it take it straight from the cart? Is the internal cart architecture standardized? I know that there are different mbit games, but is this the program or a change in architecture?
I'm looking at all of this for a possible cartridge emulator.. even if it's one cartridge for each mbit size.. but to do that I need to know exactly how they interface.
Any info would be greatly appreciated!

[snowpenguin]

Well the first thing I'd do is read marshallh's cart emulator thread, and then realize you shouldn't bother as he's been doing this for years and knows all about the n64 and will probably be selling cart-emus when he's done.

[kibble]

Here's the thread Stuntpenguin is talking about: http://forums.benheck.com/viewtopic.php?f=5&t=33012" onclick="window.open(this.href);return false;

And to quickly answer one of your questions, the ROM stays on the cart. The console basically asks the cart for a set of data and the cart spits it out to the console for processing. The ROM doesn't get dumped into the RAM as most games wouldn't fit in that small space anyway. Streaming data from an electronic memory device is much faster than reading from a disk, so that's why there's no loading screens with cart based games.

[Alptraum]

Thanks, I have read the cart emulator thread and have been digging around on the internet for answers to this... having not found anything after several hours of searching, I thought it would be best to ask some real people..
And I know that I have basically no knowledge compared to marshallh's vast repository, and that I could buy one, but I was more interested in the way it works in terms of how one would go about making a cart emulator or a flash cart. Everyone seems to not be able to do it, and I wanted to know why.
If the console requests the file, why is it so hard to have some sort of request processing thing that waits for the request from the console, takes the relevant data from some sort of flash memory and spits it back to the console? Yes, I know it's a naïve idea that probably holds water as well as a sieve, but I would like to know why it doesn't work..

[kibble]

I was more interested in the way it works in terms of how one would go about making a cart emulator or a flash cart. Everyone seems to not be able to do it, and I wanted to know why.

It's not that it can't be done, it's that most people don't have any experience in coding for N64. Marshall is someone who actually has experience in coding for this console.

If the console requests the file, why is it so hard to have some sort of request processing thing that waits for the request from the console, takes the relevant data from some sort of flash memory and spits it back to the console? Yes, I know it's a naïve idea that probably holds water as well as a sieve, but I would like to know why it doesn't work..

Once again, it comes down to being able to code for the N64. Think of it this way; Say you go to a bank and just walk in and say: "I want money." First of all, they're probably going to give you a funny look and if they haven't sounded off the alarm by then, they'll probably also ask if you have a bank account with them. Ok, maybe that wasn't the best example.... bottom line is; they'll have a hard time with your request if you don't ask in a certain way. However, if you go to the bank and say: "Here's my bank account number, I'd like X amount of dollars from my checking account." Then they'll know exactly what needs to be done and they will release X amount that you requested from their supply of cash.

Same deal with the N64 and a cart. The device, cart emulator (the bank in our scenario), needs to be able to understand what the console (account holder) is asking for. Once the device knows what data it needs to pass onto the console, it retrieves that data from the ROM and releases it to the console. So, you need to understand what sort of communication goes on between the two devices before you can know how to code for it. Not many of us here know this information and that's why you don't really see anyone other than Marshall working on this particular type of device.

[timmeh87]

http://crazynation.org/N64/n64_cart_info.htm" onclick="window.open(this.href);return false;

Enjoy.

[Alptraum]

You're a God, timmeh. Thankyou! *bows*