public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jesper Skov <jskov@redhat.com>
To: "Koeller, T." <Thomas.Koeller@baslerweb.com>
Cc: "'ecos-discuss@sourceware.cygnus.com'"
	<ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] PC target
Date: Wed, 24 Jan 2001 02:02:00 -0000	[thread overview]
Message-ID: <otlms1s1xs.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <850597605E79D21182830008C7A4B9CF07D88601@COMM1>

>>>>> "Koeller," == Koeller, T <Thomas.Koeller@baslerweb.com> writes:

Koeller,> I am currently evaluating eCos to see if it's suitable for
Koeller,> an upcoming embedded project. My host environment is Windows
Koeller,> NT / Cygwin. For evaluation purposes only, I am using the PC
Koeller,> target with CYG_HAL_STARTUP set to FLOPPY.  I found that the
Koeller,> cross-development tools I installed (i386-elf) always
Koeller,> generate elf executables (xxx.exe), which is not really
Koeller,> surprising, given the names of those tools. However, the
Koeller,> executables generated cannot be loaded directly on the
Koeller,> target, so I used objcopy to convert them to raw binary
Koeller,> format. This step is not described anywhere in the docs, and
Koeller,> I therefore wonder if I am doing it the way it's supposed to
Koeller,> be done. Any comments?

If you follow the instructions here:

http://sources.redhat.com/ecos/docs-latest/tutorials/i386pc/ecos-tutorial.d.html#pgfId=2565417

You will be able to boot a GDB stub on the target. From then on, you
use GDB to download the files over serial.

Jesper

  parent reply	other threads:[~2001-01-24  2:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-24  1:43 Koeller, T.
2001-01-24  1:59 ` Christian Plessl
2001-01-24  2:02 ` Jesper Skov [this message]
2001-01-24  9:20 Natarajan, Mekala (CTS)

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=otlms1s1xs.fsf@thinktwice.zoftcorp.dk \
    --to=jskov@redhat.com \
    --cc=Thomas.Koeller@baslerweb.com \
    --cc=ecos-discuss@sourceware.cygnus.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).