Linux on the Nintendo GameCube and Wii

PATx box <patx_boite <at> hotmail.com> writes:

> I ve noticed that when installing binutils there is a bug ( or i do 
> something wrong ) at make stage ... unfortunatly i don't have the hole 
> outputs but it happens at opcodes :
> 

If you're trying to natively compile binutils you will get out of memory and
wake up the OOM killer.
For such applications it is better to crosscompile or distcc them on a larger
machine.

> I ve also noticed that SDL 1.2.11 were supposed to be updated to the cvs but 
> when i tried to install I had an error regarding the Version !! i picked SDL 
> 1.2.8 instead and it went well so I guess CVS it is NOT updated...

SDL has not been updated for a long time. It is not supposed to be updated to
1.2.11.

> N.B. Saying that i am new to linux doesn't mean i am a complete noob... I ve 
> been in electronics for a while and i ve made some devices already (the 
> xbox8164adapter (original & talismoon version))
> 
> I was looking at the EXI and i was wondering if anyone is willing trying to 
> make a USB port with a MAX3420e from mem. slot,,. I can do the HW part i ve 
> got all needed even a LA... What i don t have is the skills to write new 
> linux drivers...

If you have the hardware and documentation of how it works we can write a Linux
driver for it.

Cheers,
Albert

>If you're trying to natively compile binutils you will get out of memory 
>and
>wake up the OOM killer.
>For such applications it is better to crosscompile or distcc them on a 
>larger
>machine.

Thankx for the hint i will try distcc...

>SDL has not been updated for a long time. It is not supposed to be updated 
>to
>1.2.11.

Maybe it would be good to add the SDL version to the release news on the 
main page as it is confusing.

21 Mar 2006: Simple DirectMedia Layer library updated We have recently added 
double-buffering and automagic vertical retrace sync to the libsdl port. 
This will avoid unwanted frame-tearing when enabled. As a quick test, we 
have re-packaged SuperTux again with these new changes, making the game even 
more enjoyable :-) The new libsdl code is already on CVS , and you can find 
the SuperTux take II  package on sf.net's Files page, as usual.

>If you have the hardware and documentation of how it works we can write a 
>Linux
>driver for it.

I was waiting to see if anyone is interested in it before ordering parts.If 
you are interested, I will order parts and build the adapter, you can email 
me if you need any tests done with it...

Here is my email : patx_boite@...

For info on the MAX3420 and isolating USB look here :

http://www.maxim-ic.com/appnotes.cfm/an_pk/3891

and here is the MAX3420 Datasheet:

http://www.maxim-ic.com/quick_view2.cfm/qv_pk/4751

_________________________________________________________________
Windows Live Spaces: partagez vos photos avec vos amis! 
http://spaces.live.com/?mkt=fr-ca

I read a bit this morning before ordering parts and the MAX3421 will be 
needed instead of the MAX3420 witch is for peripheral devices only ...

here is the Datasheet:

http://www.maxim-ic.com/getds.cfm?qv_pk=3639

I ve ordered parts and i will make a shematic based on figure 21 (datasheet) 
and the memcard pinout...





> >If you're trying to natively compile binutils you will get out of memory
> >and
> >wake up the OOM killer.
> >For such applications it is better to crosscompile or distcc them on a
> >larger
> >machine.
>
>Thankx for the hint i will try distcc...
>
> >SDL has not been updated for a long time. It is not supposed to be 
>updated
> >to
> >1.2.11.
>
>Maybe it would be good to add the SDL version to the release news on the
>main page as it is confusing.
>
>21 Mar 2006: Simple DirectMedia Layer library updated We have recently 
>added
>double-buffering and automagic vertical retrace sync to the libsdl port.
>This will avoid unwanted frame-tearing when enabled. As a quick test, we
>have re-packaged SuperTux again with these new changes, making the game 
>even
>more enjoyable :-) The new libsdl code is already on CVS , and you can find
>the SuperTux take II  package on sf.net's Files page, as usual.
>
> >If you have the hardware and documentation of how it works we can write a
> >Linux
> >driver for it.
>
>I was waiting to see if anyone is interested in it before ordering parts.If
>you are interested, I will order parts and build the adapter, you can email
>me if you need any tests done with it...
>
>Here is my email : patx_boite@...
>
>For info on the MAX3420 and isolating USB look here :
>
>http://www.maxim-ic.com/appnotes.cfm/an_pk/3891
>
>and here is the MAX3420 Datasheet:
>
>http://www.maxim-ic.com/quick_view2.cfm/qv_pk/4751
>
>_________________________________________________________________
>Windows Live Spaces: partagez vos photos avec vos amis!
>http://spaces.live.com/?mkt=fr-ca
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share 
>your
>opinions on IT & business topics through brief surveys-and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Gc-linux-devel mailing list
>Gc-linux-devel@...
>https://lists.sourceforge.net/lists/listinfo/gc-linux-devel

_________________________________________________________________
Participez au concours Tournée Live Mobile dès maintenant! 
http://www.concertmobilelive.ca

PATx box <patx_boite <at> hotmail.com> writes:
> I read a bit this morning before ordering parts and the MAX3421 will be 
> needed instead of the MAX3420 witch is for peripheral devices only ...

Yes, I noticed that too.

> I ve ordered parts and i will make a shematic based on figure 21 (datasheet) 
> and the memcard pinout...

Remember to wire up the irq line too. We'll need that.

My biggest concern is that the controller doesn't support a 32MHz clock
(according to the data sheet it supports a maximum of 26MHz), so we'll have to
run the SPI bus at 16MHz, unless someone figures out how to program the EXI
interface to a intermediate clock speed.

I think it would be a good idea to keep all the details of this mini-project on
the project's wiki. I've started a page specially for that:

http://www.gc-linux.org/wiki/EXI:USBHostAdapter

Cheers,
Albert

I've picked up this excellent idea, and designed a schematic and PCB  
for this USB host interface. Links to the schematic and PCB are on  
the wiki: http://www.gc-linux.org/wiki/EXI:USBHostAdapter . I just  
have to wait for the company where I'm doing my internship at the  
moment to do their next PCB panel, then I can stick some of my PCB's  
on for free.

Also, I'm currently working on a ethernet controller to replace the  
hard-to-get BBA. It will use Microchip's ENC28J60 SPI ethernet  
controller.

I'm starting with the Linux driver modules, but I'm not sure how to  
do the probing/detection. The current EXI driver does (if I  
understand the source correctly):

-select device
-output 0x0000 (request ID)
-read 16 bit ID
-deselect device

-if the read ID is 0 (which happens with MMC/SD cards apparently),  
and the device is on one of the memory cards, EXI_ID_NONE (or  
something) is returned, and all exi-device drivers claiming to  
support that ID are then probed.

Now the problem is, with both the MAX3421 and the ENC28J60, 0x0000  
means just 'read register 0', which could be anything (might be 0x00  
after reset?). Also, both these parts do not have a 'Request ID'  
command, so there's no straight-forward way to probe them. So how do  
we identify these parts? Or could there be an easy way for the user  
to set the exi channel/device manually? Module parameters? What about  
the ethernet controller that might be used to mount the root fs?

I guess there are more experienced driver programmers on this list  
who could tell me the way to go.

Regards,

Rob Reilink



Op 20-mrt-2007, om 3:26 heeft Albert Herranz het volgende geschreven:

> PATx box <patx_boite <at> hotmail.com> writes:
>> I read a bit this morning before ordering parts and the MAX3421  
>> will be
>> needed instead of the MAX3420 witch is for peripheral devices  
>> only ...
>
> Yes, I noticed that too.
>
>> I ve ordered parts and i will make a shematic based on figure 21  
>> (datasheet)
>> and the memcard pinout...
>
> Remember to wire up the irq line too. We'll need that.
>
> My biggest concern is that the controller doesn't support a 32MHz  
> clock
> (according to the data sheet it supports a maximum of 26MHz), so  
> we'll have to
> run the SPI bus at 16MHz, unless someone figures out how to program  
> the EXI
> interface to a intermediate clock speed.
>
> I think it would be a good idea to keep all the details of this  
> mini-project on
> the project's wiki. I've started a page specially for that:
>
> http://www.gc-linux.org/wiki/EXI:USBHostAdapter
>
> Cheers,
> Albert
>
>
>
> ---------------------------------------------------------------------- 
> ---
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to  
> share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php? 
> page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Gc-linux-devel mailing list
> Gc-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel

Rob Reilink <rob <at> reilink.net> writes:
> I've picked up this excellent idea, and designed a schematic and PCB  
> for this USB host interface.
[...]

Nice to hear from you again, Rob.

> Now the problem is, with both the MAX3421 and the ENC28J60, 0x0000  
> means just 'read register 0', which could be anything (might be 0x00  
> after reset?). Also, both these parts do not have a 'Request ID'  
> command, so there's no straight-forward way to probe them. So how do  
> we identify these parts? Or could there be an easy way for the user  
> to set the exi channel/device manually? Module parameters? What about  
> the ethernet controller that might be used to mount the root fs?

The current EXI driver is able to handle both "normal" EXI devices (which can
answer to an exi_get_id() command) and "custom" EXI devices, like MMC/SD cards,
the future USB adapter and your new SPI-based ethernet interface.

"Custom" EXI devices have to be registered with an EXI identifier of
EXI_ID_NONE. They will be initially matched against channel/device only. The
driver probe function is responsible for checking if the device is really a
matching device, and in that case it returns 0.

Look at the MMC/SD card driver for example. It probes if a MMC/SD card is
available by trying the card initialization sequence. If it fails, it assumes no
card is there and the driver forgets about the device.

This could lead to problems in the future if a driver probe sequence for one
device can destroy another one. But, for now I think we can go ahead with what
we have.

Cheers,
Albert

Hi,

Yet another question, this time regarding the EXI hardware. My GC has  
got a 'serial port 2', I believe this is P8 as described in 2.4.1.2  
of YAGCD. For my hardware, I'd like to use ports on different EXI  
channels, so each device can use its channel for 100%. Now, I'm  
wondering to which EXI channel/device this P8 is connected. It's not  
in the EXI device listing in 10.2, and I can't seem to find it  
enywhere else.

Unfortunately, I haven't got Linux running on my 'cube yet because  
I'm still waiting for some hardware to build my own 'modchip' (I  
haven't got my BBA or PSO here in Australia where I'm staying for a  
few moths). Therefore, I'm not able to just measure CS and poke  
around in the EXI registers. Does anyone have more info?

Cheers,

Rob

On Saturday 28 April 2007 07:46, Rob Reilink wrote:
> Hi,
>
> Yet another question, this time regarding the EXI hardware. My GC has
> got a 'serial port 2', I believe this is P8 as described in 2.4.1.2
> of YAGCD. For my hardware, I'd like to use ports on different EXI
> channels, so each device can use its channel for 100%. Now, I'm
> wondering to which EXI channel/device this P8 is connected. It's not
> in the EXI device listing in 10.2, and I can't seem to find it
> enywhere else.
>
> Unfortunately, I haven't got Linux running on my 'cube yet because
> I'm still waiting for some hardware to build my own 'modchip' (I
> haven't got my BBA or PSO here in Australia where I'm staying for a
> few moths). Therefore, I'm not able to just measure CS and poke
> around in the EXI registers. Does anyone have more info?

you are talking about the "high speed port" right? if i recall correctly th=
ats=20
not an exi device, it is memory mapped. there should be some vague info in=
=20
yagcd somewhere, but it was never investigated further since nothing beside=
s=20
the gba player used it.

=2D-=20

http://www.hitmen-console.org
http://www.gc-linux.org/docs/yagcd.html
http://www.pokefinder.org
http://ftp.pokefinder.org

Wer sp=E4ter bremst f=E4hrt l=E4nger schnell

Groepaz <groepaz <at> gmx.net> writes:
> you are talking about the "high speed port" right? if i recall correctly thats 
> not an exi device, it is memory mapped. there should be some vague info in 
> yagcd somewhere, but it was never investigated further since nothing besides 
> the gba player used it.

No, I think he's talking about "Serial Port 2", the connector that was removed
on recent hardware revisions of the console.

I can't tell if it is related to EXI or not. (But my guess is that it is not).

Cheers,
Albert

On Sunday 29 April 2007 00:32, Albert Herranz wrote:
> No, I think he's talking about "Serial Port 2", the connector that was
> removed on recent hardware revisions of the console.

oh...yes ofcourse :)

> I can't tell if it is related to EXI or not. (But my guess is that it is
> not).

mmmh, maybe that one is related to the mysterious "UART" reference? (its even 
in yagcd, god knows where i got that one from =P)

-- 

http://www.hitmen-console.org
http://www.gc-linux.org/docs/yagcd.html
http://www.pokefinder.org
http://ftp.pokefinder.org

I can make it crash!

Groepaz <groepaz <at> gmx.net> writes:
> > I can't tell if it is related to EXI or not. (But my guess is that it is
> > not).
> 
> mmmh, maybe that one is related to the mysterious "UART" reference? (its even 
> in yagcd, god knows where i got that one from =P)

In US patent 6,609,977 (now 7,134,960) there is a reference which could confirm
your theory:

"A multi-pin modem connector 1514 is used to connect the graphics and audio
processor 114 to an external or internal modem.
The boot ROM/real time clock 134 is coupled to the modem connector 1514 and
shares its bus for communication with the graphics and audio processor 114."

1514 is the "Serial Port 2" connector.
So that text is claiming that "Serial Port 2" is related to the EXI0 bus, where
the Boot ROM is located.

Cheers,
Albert

Albert Herranz <albert_herranz <at> yahoo.es> writes:
> 1514 is the "Serial Port 2" connector.
> So that text is claiming that "Serial Port 2" is related to the EXI0 bus, where
> the Boot ROM is located.

Uhmm.. I think I've messed it up.

1514 is the "Serial Port 1" connector.
1520 is the "Serial Port 2" connector.
So "Serial Port 1" should be EXI0 (as we know from the BBA). And "Serial Port 2"
should be EXI2 from the drawings (FIG 26 and FIG 15C).

Cheers,
Albert

It would be great if indeed this appears to be true. In that case,  
three different devices (Ethernet, SD card, USB) can be connected to  
all three EXI busses, so the system performance would be maximized.

I'll design a version of my ethernet controller to fit onto the  
Serial Port 2. It will be soldered onto the mainboard, so it should  
be usable on GC's without this connector as well (I think they just  
removed the connector, the pinout should still be on the mainboard).  
Meanwhile, if someone has a GameCube running Linux with access to the  
mainboard, it should be able to confirm that it is on the EXI2 bus by  
measuring the CS pin voltage and poking 0x0 and 0x380 to 0xCC006828  
to enable/disable all CS pins on the EXI2 channel.

Regarding the port name confusion: I had a look at the wrong cover :- 
S. That's what happens when your 'cube is disassembed. Actually, the  
high speed port might be very interesting as well. The pin  
description from YAGCD resembles that of standard SDRAM IC's. It  
might be possible to expand the GC ARAM. However, I haven't got a  
clue on how to use this in software, or what size of SDRAM is  
supported. Is there perhaps extra RAM in the GB Player?

Cheers,

Rob

Op 30-apr-2007, om 4:32 heeft Albert Herranz het volgende geschreven:

> Albert Herranz <albert_herranz <at> yahoo.es> writes:
>> 1514 is the "Serial Port 2" connector.
>> So that text is claiming that "Serial Port 2" is related to the  
>> EXI0 bus, where
>> the Boot ROM is located.
>
> Uhmm.. I think I've messed it up.
>
> 1514 is the "Serial Port 1" connector.
> 1520 is the "Serial Port 2" connector.
> So "Serial Port 1" should be EXI0 (as we know from the BBA). And  
> "Serial Port 2"
> should be EXI2 from the drawings (FIG 26 and FIG 15C).
>
> Cheers,
> Albert
>
>
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Gc-linux-devel mailing list
> Gc-linux-devel@...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel

On Monday 30 April 2007 00:52, Rob Reilink wrote:

> Regarding the port name confusion: I had a look at the wrong cover :-
> S. That's what happens when your 'cube is disassembed. Actually, the
> high speed port might be very interesting as well. The pin
> description from YAGCD resembles that of standard SDRAM IC's. It
> might be possible to expand the GC ARAM. However, I haven't got a
> clue on how to use this in software, or what size of SDRAM is
> supported. Is there perhaps extra RAM in the GB Player?

its just memory mapped... look at the "external interfaces" patent, and also 
check some N64 docs - the n64 ram expansion uses exactly the same interface.

-- 

http://www.hitmen-console.org
http://www.gc-linux.org/docs/yagcd.html
http://www.pokefinder.org
http://ftp.pokefinder.org

Hard work has a future payoff. Laziness pays off now.