Alright, so first off...my goal is to have a GC environment much like how wiiload operates on wii. The problem is, I have become spoiled over time and now the PSO method is simply extruciating. After poking around on some old assemblergames threads, it seems like something much like this (perhaps even faster, if you account for the ms difference between wifi and ethernet... ) was possible via the Qoob chip and the BBA. So...considering I would like my code to run as soon as possible after boot(even replacing BS2 if possible), what is the way to do this? Perhaps now I should mention why I put "modern" in the thread title... For a while, the keystream generator used for encrypting the bootrom has been reversed by segher. We even use his RE'd routine in dolphin. This should make it quite a bit easier to succesfully get my code in there while BS1 is loading it But I digress....mainly, I am looking for a way to efficiently run code - preferably as early in the bootup as possible, and with the easiest connection to the PC for r/w access (I assume the BBA would make a sd/usb gecko useless, so this could be a non-issue). Finally...assuming the Qoob is all I really need...where should I get one from?
Can't you run GameCube homebrew on the Wii? That's essentially what devkitPPC is, it's libogc and they've added Wii extensions, but it's still primarily GameCube code AFAIK.
Myself I've got a standard gamecube with the original viper installed, upgraded the bios to cobra-1.6 with the GCOS plugin and I stream DOLs over to it using NC (netcat) which will work in *nix or windows. Though since I got myself a DDH the other week, there's no longer any need to use my old setup
I use a GC with a Qoob chip and an application I wrote which accepts DOL files over USB-Gecko. Time from power-on to loading a DOL is about 2 seconds.
Alright, I've ordered a Qoob. (Being brave/cheap and will try to use BBA instead of purchasing a USB-Gecko tho) Thanks everyone
Finally got the qoob in the mail (and installed it). Few questions: I have a revision A GC board, so I went off of these instructions: According to the relevant patent, "C" is grounding the EXTIN line (that's the SP1 pinout)...which seems kinda important for BBA to function correctly. So before messing with it a lot, I just tested BBA functionality with a retail game, and what do you know: http://i29.tinypic.com/10pp09i.png Then I tested the network functionality of the qoob v1.3c IPL, and as expected, it worked fine (I could rip a disc and send dols). So pretty much my question is just: wtf is that bridging/grounding accomplishing? The other question is how to replace the "BIOS" with my own code. The file format seems easy and is documented in yagcd. The data section appears to be xor'd with the ipl keystream in the normal way...however when I decrypted the data section, the plaintext only seemed to be the initial bootloader (i.e. BS1). Anyone know how the BS2/IPL is stored? Slightly off topic: Who is/was behind the qoob? I enjoy how their readme files desperately try to say it's all their own work...ya right!
