I've readt some threads about N64 RAM expansion and Xbox RAM expansion. Now I would like to know if it possible to do this with the Gamecube. I know the TDEV has twice as much RAM as the normal Gamecubes and NR- and NPDP-Readers. I don't know if the TDEV uses 2 RAM chips like the retail cubes, but if it does it shouldn't be too hard to hunt these chips down and transplant them into a retail/NR/NPDP gamecube. Am I right?
Games are hard-coded to use 24MB, like xbox games are hard-coded to use 64MB of RAM, and hacks were needed if a faster CPU or more RAM was used. The double ram in the TDEV; afaik half is used for debugging only, not sure if it can be used by the code running on the console itself or only outputted to USB or whatnot. My DDK has 48MB of RAM, and shows this when booting up on the ORCA-OUT debug port, never used it seeing as I don't know how to code or anything about memory management. Why'd you want more RAM anyway, it's only uses would be for debugging (which you can't really do with the normal GC anyway) or if you were to run linux on it, in which it'd help quite a bit.
The XBox and the N64 both had the ability to use the extra ram for various purposes. The GameCube really doesn't.
You can't use the NR as a TDEV. And how're you doing to do debugging when you've got no way to transfer the data to anything? If you've got a BBA then you can debug on that direct to any logging program you make. If you've got the SN Systems USB cable then you can debug directly on that (when using ProDG) via the virtual TTY outputs.
I have the BBA, so I can use metrowerks for debugging. But I think I need 48 MB RAM for that, so that's why I need/want RAM expansion.
Make your own, there's example in the Dolphin SDK about how to communicate with the PC, just send whatever you need over ethernet to the PC and have a simple logger program running. Or just log into memory and read the memory and debug that way, I'm pretty sure you won't be using 24MB of RAM when you start coding.
