[ECOS] Vr4131 porting issues

[Nick Garnett]

"Jurica Baricevic" <jura@INTESIS.hr> writes:

> I downloaded mipsisa32 binaries
> (http://www.mirror.ac.uk/sites/sources.redhat.com/pub/ecos/gnutools/cygwin/e
> coscentric-gnutools-mipsisa32-elf-1.4-2.cygwin.tar.bz2) and now
> Redboot -mpg32 seems to work too.

Excellent. Does gdb connect properly or are you still seeing timeouts?


> I have a dumb question: what should MIPS ISA 32 stand for? I am acquainted
> with the ISA 1/2/3 - but don't get what should ISA 32 exactly represent.
>

Not such a dumb question, I have trouble keeping track of which MIPS
ISA is which, particularly when the device numbering bears no
relationship to it at all :-)

MIPS32 and MIPS64 are newer versions of the ISA specification, aimed
mainly at embedded use. They are essentially MIPS 3 with a little MIPS
4 mixed in. Most recent MIPS implementations, like the NEC VR4XXX
series and the Toshiba TX49, while not explicitly MIPS32/64 compliant,
are at least supersets of these specifications. So the MIPS32/64
toolchain will generate code that will run on them.

Given the way that MIPS is going, I expect that the mipsisa32-elf
toolchain to become the primary configuration and all the others
being of largely historical interest only.


> In addition, tried to build the following GCC 3.2.1 targets, but without
> success:
> mips64vr4100el-elf (target not supported by gcc)
> mips64vr4100-elf (odd problem with newlib)
> mips64vr4300-elf (odd problem with newlib. sounds the same as above)

Yep, looks like this stuff never got put back into the public
distribution, or maybe only bits of it did.

> 
> I guess that we missed something - so we'll keep on trying.
> In the meantime, we are able to use mipsisa32-elf. :-)
>

Yep, mipsisa32-elf looks like the way to go. 

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com/     The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss