public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gthomas@cambridge.redhat.com>
To: 김재용 <jaelong@lge.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] porting ecos...
Date: Sat, 24 Feb 2001 04:41:00 -0000	[thread overview]
Message-ID: <XFMail.20010224054134.gthomas@cambridge.redhat.com> (raw)
In-Reply-To: <OFA9B73175.301AD3E7-ON492569FD.001D5254@lge.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1952 bytes --]

On 24-Feb-2001 ±èÀç¿ë wrote:
> Please help me..
> I don't even know concept of porting, but I have to port ecos in EDB7209-2C
> ARM7 board of Cirrus..
> I have followed instruction in redhat Web Site and downloaded ecos-1.3.1
> and
> extracted...
> And compiled, installed binutils, gcc, gdb in arm target, following
> instruction
> of
> http://sources.redhat.com/ecos/install-linux.html and
> http://sources.redhat.com/ecos/tools/linux-arm-elf.html
> executable comes arm-elf-gcc etc.
> 
> and I don't know what I should do next to port ecos.
> I guess I have to cross-compile kernel, but I don't know how to do that.
> Neither document in redhat Web site nor document in ecos package told me
> what
> to do next. and seems to skip..
> Please tell me what I should do next in detail, including command with
> option
> and argument. Sorry, I am beginner in ecos and porting
> I have not much time and urgent.
> And another question..is ecos included in Embedded Linux?
> Please answer..
> I will wait for your answer.

Firstly, for the Cirrus Logic board you mention, no porting is required
at all as this is one of the platforms we support.

Secondly, you would be much better off by using the eCos sources from
anonymous CVS.  See http://sources.redhat.com/ecos/anoncvs.html

Once you've obstained the latest sources and installed both the sources
and the tools on your system (I assume that you are using Linux for
your development host, based on your references above) then you can
create an eCos kernel for your board.  Once you have a kernel, then
you build and run applications on the board by downloading them using
GDB.

This whole process is rather fully explained in the eCos "Getting
Started Guide" and hardware installation notes.  The full text is
available from our web site at:
  http://sources.redhat.com/ecos/docs.html

If you have additional problems or questions, just send them to
this same eCos discussion list.

  reply	other threads:[~2001-02-24  4:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-23 21:22 김재용
2001-02-24  4:41 ` Gary Thomas [this message]
2001-02-24 13:10   ` [ECOS] Porting Result of eCos on NEC DDB-VRC4375 Ling Su
2001-02-26 11:00     ` Jonathan Larmour
2001-02-27 11:19       ` Ling Su
2001-02-27 11:47         ` Jonathan Larmour
2001-02-28  2:41         ` Jesper Skov
2009-01-26 13:55 [ECOS] porting ecos smith jj
2009-03-23 11:36 keerti
2009-03-23 11:59 ` Gary Thomas
     [not found]   ` <4363.121.246.210.150.1237808715.squirrel@webmail11.pair.com>
2009-03-24  8:00     ` Gary Thomas

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=XFMail.20010224054134.gthomas@cambridge.redhat.com \
    --to=gthomas@cambridge.redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=jaelong@lge.com \
    /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).