This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Redboot for ATLAS (MIPS 4Kc)
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: "Michael Anburaj" <embeddedeng at hotmail dot com>
- Cc: ecos-discuss at sources dot redhat dot com
- Date: 05 May 2003 10:28:17 +0100
- Subject: Re: [ECOS] Redboot for ATLAS (MIPS 4Kc)
- References: <Law15-F21Qy4U7Kx1lE00002f28@hotmail.com>
"Michael Anburaj" <embeddedeng@hotmail.com> writes:
> Hi,
>
> I tried building Redboot in BIG endian mode for the MIPS Atlas 4Kc platform.
>
> Opened a new cconfiguration (.ecc), chose the Atlas 4Kc template,
> Changed the default endiness under "ECOS HAL -> MIPS Architecture ->
> MIPS Variant ->
> Endian Format" to use BIG endian, saved it & imported
> "/packages/hal/mips/atlas/current/misc/redboot_ROM.ecm", added CRC
> package & then issues the build library command from the Configtool.
Generally the endianness gets set by the platform HAL package, which
will also handle other endianness issues like changing the compiler
options. While we have certainly supported big endian MIPS targets in
the past, I do not believe any of the current ones are BE. So I would
not expect it to work straight out of the box. Of course you will also
have to work out how to flip the endianness of the Atlas devices,
unless this happens automatically when you set the CPU endianness.
>
>
> Please tell me from where does the -EL build C flag got inserted. If I
> made a mistake do let me know.
>
It comes from the custom make rules in the flash device driver. This
is an example of the LE-only bias of the current targets.
--
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