RE: [ECOS] Vr4131 porting issues

["Jurica Baricevic" <jura at INTESIS dot hr>]

Nick Garnett wrote:
> > I downloaded mipsisa32 binaries
> >
> (http://www.mirror.ac.uk/sites/sources.redhat.com/pub/ecos/gnu
> tools/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?
>

Still timeouts over serial port. TCP/IP connection doesn't have such
problems though.


> > 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.

Sounds great. Bart seems much more reserved with this issue though.
He made me think that the mips64vr4100-elf would be the only safe
path to go.


> 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.
>

That would be terrific, since the compatibility between growing
number of MIPS targets is confusing sometimes. Also, the number of
different cross-compilers on my PC would be diminished significantly :-)


> > 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 confirm the problem with TARGET set to mips64vr4300-elf and
mips64vr4100-elf.
Here's part of the output from the mips64vr4300-elf (the same is for vr4100)
when
trying to configure GCC:

[start]
checking whether times is declared... yes
checking for struct tms... yes
checking for clock_t... yes
checking if mkdir takes one argument... no
Configuration mips64vr4300-unknown-elf not supported
Configure in /tmp/build/gcc/gcc failed, exiting.
[end]

I am running Cygwin-1.3.18-1. Tools version (gcc, gdb, binutils, newlib)
and build instructions are as on:
http://sources.redhat.com/ecos/build-toolchain.html.

Did anybody have similar problems when building Vr4300 tools for eCos?
(The problem description sent also to the crossgcc list).


> > 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.

I hope so.

Thanks,
Jura




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