XenoGC fork

YouTube · Post by **emu_kidid** » Wed Oct 12, 2011 1:47 am

I had a brief chat with the original author. he says that the mn102 code can block the ppc since it masks interrupts whilst it does stuff.

Suggestion is to use the already existing flasher and inject a new .bin into it

870663 · Post by **870663** » Wed Oct 12, 2011 3:32 am

After injecting the drivecode "CMD_InjectCustomDriveCode()" the next action is "CheckDriveState(true)"...
while checking the drive state, "dwIntVec" is equal to 0xDDDDDDDD
thats where it hangs...

you're crashing the drive, DDDD is dummy data returned on timeout. in CMD_InjectCustomDriveCode try reading drive memory (ie 0x804c) to see at which step it crashes. also read back the block at 40d000 to see if its written correctly.

disaster3ad · Post by **disaster3ad** » Wed Oct 12, 2011 1:59 pm

Hi

I program my XENO and AtMegas using simple programmer attached to LPT (printer) port with is a few wires with diodes, to protect these PC lines. The programmer utility called AvrDude (WinXP).

XenoAT.1.05 (hex file or binary)

Have tried other firmwares, but got worked only 1.04 as i remember...

Also tried to flash with xenoflash.dol, by sending it via BBA (QoobPro) but there is a trap, you should reset drive because
QoobPro might interference with custom debug comand (not sure, but i did reset drive and thats help)

dantheman2865 · Post by **dantheman2865** » Fri Oct 14, 2011 5:39 pm

emu_kidid wrote:I had a brief chat with the original author. he says that the mn102 code can block the ppc since it masks interrupts whilst it does stuff

I think I finally understand that. The code I had for DVD_CallFunc() only cleared some existing interrupts (dvd[0] = 0x14) because I didn't understand what I was doing at the time. I believe a lot of the hanging problems, etc., are caused by this. My idea is to enable the interrupts (dvd[0] = 0x2e) so that potentially the drive won't hang up at that point.

As soon as I get my Xeno Reflashed I will test this.

alambriojo · Post by **alambriojo** » Mon Oct 24, 2011 8:02 pm

with r15 its possible to flash xenogc now? wiil be possible to boot swiss from mc?

YouTube · Post by **emu_kidid** » Mon Oct 24, 2011 9:49 pm

Not yet. I am looking into injecting the new .bin into the existing (working) flasher since we know that one works.

megalomaniac · Post by **megalomaniac** » Tue Oct 25, 2011 8:00 am

just to add more to the puzzle:

since the app currently does not flash, i tested to see if it would at least erase.
That attempt initially failed as well, then a bit of success. FlashErase has to be performed twice back to back.
Cannot simply call FlashErase() twice. Must press Z twice to erase.

Code: Select all

		if(buttonsDown & PAD_TRIGGER_Z) {
			// programm the chip
			FlashInit();
			FlashErase();
			//set blue color, black background
			printf("\x1b[36m \x1b[40m");
			printf("\n\nFLASH ERASE Complete !!");
		}

i tried the same to update by pressing A twice as well, but that did not work....maybe this info can be useful as to what is happening. It sounds closely related to our other problem previously corrected by performing a read before exiting CMD_InjectCustomDriveCode()
....

Post by **liquitt** » Tue Oct 25, 2011 3:20 pm

just used FreeMC Boot on a PS2 for the first time - now i'm looking forward to the GC hack to do this ... kind of

hardlifetime · Post by **hardlifetime** » Mon Dec 26, 2011 6:28 pm

Hi folk`s . Sorry if this is a wrong treath but i need quick info. Just build a serial programmer for atmel (atmega8) this link

Code: Select all

http://www.gc-forever.com/wiki/index.php?title=File:SerialBlock.png

didn`t know how to flash .hex with avrdude so i use ponyprog2000 and flash XenoAT.1.05.hex with it. What is the next step ist that it should solder chip now on gc or there is somthing more . P.S. PonyProg finish flashing ok. Thx.

infact · Post by **infact** » Mon Dec 26, 2011 7:04 pm

Well if you got the firmware on the flash, then you are ready to solder it in your cube.
http://www.gc-forever.com/wiki/index.ph ... noGC_Clone

hardlifetime · Post by **hardlifetime** » Mon Dec 26, 2011 7:10 pm

Is this file XenoAT.1.05.hex all i need on chip to start it . For example play my backup? Or i need and eeprom data ?

infact · Post by **infact** » Mon Dec 26, 2011 7:36 pm

it contains everything you need.

megalomaniac · Post by **megalomaniac** » Mon Dec 26, 2011 7:46 pm

yup..
only need the hex file

did you add an LED to your design?
- if yes, does one of them light up when power is applied to the chip?
-- if yes, then solder leads between the atmega and gamecube drive connections and perform the following functional test:
1. put official disk in drive
2. power on
3. hold "start"
4. LEDS should display red then green (depending on your design)
5. should see xeno menu

if all this works, then try a backup disk next..
i suggest you try these steps before trying to mount the chip permanently

hardlifetime · Post by **hardlifetime** » Tue Dec 27, 2011 3:36 pm

Tnx @infact and @megalomaniac. Just back from work now. I am gonna try to solder chip with wires on cube (with led) and post results here soon.

dantheman2865 · Post by **dantheman2865** » Mon Apr 16, 2012 7:34 pm

Hey guys, it's good to be back.

In my absence I have learned a heck of a lot about digital hardware and embedded software so I'm ready to take another crack at this problem. Has anyone made any more progress not posted here? I know there was an effort to sub the old binary in the existing flasher .dol with the new binary... Otherwise, it seems like there is a very solid base here if we can figure out the weird bugs.

Consider this thread revived!

KirovAir · Post by **KirovAir** » Mon Apr 16, 2012 9:12 pm

dantheman2865 wrote:Hey guys, it's good to be back.

In my absence I have learned a heck of a lot about digital hardware and embedded software so I'm ready to take another crack at this problem. Has anyone made any more progress not posted here? I know there was an effort to sub the old binary in the existing flasher .dol with the new binary... Otherwise, it seems like there is a very solid base here if we can figure out the weird bugs.

Consider this thread revived!

Good to hear.

megalomaniac · Post by **megalomaniac** » Mon Apr 16, 2012 10:20 pm

Yo Dan good to see ya back
No updates to the googlecode since last rev 15(?)

We are still stuck in the same place of crashing MN during flash write. All other functions still work.
Still no SD load (as before) and Swiss will be too huge to fit unless severly stripped down and branched out.

YouTube · Post by **emu_kidid** » Mon Apr 16, 2012 11:22 pm

Dan, I did fix the 50/60Hz issues in the shell + re-added the DOL boot support from memcard (untested by me so far).

Our solution to flashing the xeno via DOL was to just inject the newer flash file into the already compiled DOL based flasher (but no one bothered with this yet).

dantheman2865 · Post by **dantheman2865** » Thu May 17, 2012 6:37 pm

I have started to look into compiling from source as a viable option again. Also, my company just bought a couple of logic analyzers, so that should make snooping on the flashing code much much easier.

megalomaniac · Post by **megalomaniac** » Thu May 17, 2012 9:31 pm

hope you find something good...

i think ive come to the realization that a WKF/WODE mod offers more benefits to a cube than the xeno ever could....
mostly because of the dependency requirement that the xeno needs a drive in order to patch...

the other two options acting as a drive replacement really kills xeno....
....and flashing swiss on a WFK murders xeno all day long....

ive even banged my head around the thought of cross compiling the code to a different chip with a larger flash space to add a customized version of swiss...
and/or adding external sd card code to xeno code for an atmega 8 (or other) to access swiss (start button) ....but the bottom line, still need a drive....

my opinion, drive replacement WKF/WODE offers so much more advantages...
dont want to sound negative or deter your efforts....
just voicing my opinion on different thoughts ive had for xeno vs WFK/WODE....

YouTube · Post by **emu_kidid** » Thu May 17, 2012 10:28 pm

not only do you need a drive, you need a disc in the drive!

megalomaniac · Post by **megalomaniac** » Thu May 17, 2012 11:04 pm

right...
even more of a disadvantage,,,

dantheman2865 · Post by **dantheman2865** » Fri May 18, 2012 2:59 pm

That's a good point, an open-source drive-chip would provide more functionality. I am most interested in this because it's my current setup, although it would be nice to provide an upgrade to people who already have Xenos.

Post by **liquitt** » Sun May 20, 2012 5:03 pm

dantheman2865 wrote:That's a good point, an open-source drive-chip would provide more functionality. I am most interested in this because it's my current setup, although it would be nice to provide an upgrade to people who already have Xenos.

with all the knowledge on this forum and on irc we could be a gamecube open source super modchip!

Dragoon · Post by **Dragoon** » Mon May 21, 2012 9:29 am

liquitt wrote:
dantheman2865 wrote:That's a good point, an open-source drive-chip would provide more functionality. I am most interested in this because it's my current setup, although it would be nice to provide an upgrade to people who already have Xenos.
with all the knowledge on this forum and on irc we could be a gamecube open source super modchip!

Then start a project! I think tmbinc's schematic for a modchip will do.

XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork

Re: XenoGC fork