From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: Warren Jasper <warrenj@tx.ncsu.edu>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] StrongARM SA1110
Date: Mon, 05 Mar 2001 06:22:00 -0000 [thread overview]
Message-ID: <4.3.2.7.2.20010305091158.00b55e30@mail.larwe.com> (raw)
In-Reply-To: <3AA39EB1.72FEC2F1@tx.ncsu.edu>
>1. In your instructions for the tools set, is the default
> Little Endian or Big Endian. Is there a way to tell if
In general it seems Red Hat prefers little-endian. Past discussions on this
list have indicated that not everything is guaranteed to work in big-endian
mode.
> the cross compiler is configured one way or the other by default?
> I know about the -EB and -EL flags. The cross compiler is
> called arm-elf-gcc
Have you tried a simple test program?
int main(void) {
unsigned int u;
unsigned char *p;
u = 0x12345678u;
p = (unsigned char *) &u;
printf("%2X:%2X:%2X:%2X\n",*p,*(p+1),*(p+2),*(p+3));
}
I don't know exact answers to your second question, but if you did an
"ecosconfig new assabet redboot" and then "ecosconfig tree" then "make" you
would wind up with the RedBoot debugger/loader for the Assabet board.
Exactly how to load this onto the target board varies with hardware. I'm
using ARM, not SA, so I can't advise much there :) THe closest document I
can see is
< http://sources.redhat.com/ecos/docs-latest/tutorials/arm/ecos-tutorial.d.html#pgfId=2562385 >.
=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/
"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."
next prev parent reply other threads:[~2001-03-05 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-05 6:13 Warren Jasper
2001-03-05 6:22 ` Lewin A.R.W. Edwards [this message]
2001-03-13 10:26 ` Jonathan Larmour
2001-03-13 10:38 ` Lewin A.R.W. Edwards
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4.3.2.7.2.20010305091158.00b55e30@mail.larwe.com \
--to=larwe@larwe.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=warrenj@tx.ncsu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).