public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "adon@walkersun" <adon@walkersun.com>
Cc: eCos discussion <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] build Tx39xx program
Date: Mon, 11 Sep 2000 10:55:00 -0000	[thread overview]
Message-ID: <39BD1C8C.5961F6D1@redhat.com> (raw)
In-Reply-To: <00ab01c01888$a2587960$24e7f1d2@walkersun>

"adon@walkersun" wrote:
> 
>     Maybe I have to change the question that is, what are the cygmon could
> do for me??? Does the program just serve for downloading program from the
> host to the target, so I should link another cygmon program into my program,
> and after I do that so, I could debug my program at my target???

CygMon is a ROM monitor. As far as you are concerned, it is what you
program into ROM so that you can load your application. When the
application is run, CygMon loses control. Although in some cases, it
"co-operates" with the program to allow the program to be debugged. eCos is
capable of this.

CygMon is only there to be programmed into flash/ROM. You don't link with
it. It is an application in its own right.

Perhaps you are getting the concept confused with having to link your
program differently if you are using it with a board running CygMon in ROM.
While this doesn't always happen, for GNUPro, for example, you sometimes
have to use a different linker script (specified with -Tcygmon.ld on the
link command line) to indicate that this is what your program is doing.
This isn't the same as linking with cygmon itself.

BTW, remember to CC the list. Don't e-mail me directly please.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault

  parent reply	other threads:[~2000-09-11 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-03 21:07 adon@walkersun
2000-09-04  6:21 ` Jonathan Larmour
     [not found]   ` <00ab01c01888$a2587960$24e7f1d2@walkersun>
2000-09-11 10:55     ` Jonathan Larmour [this message]
2000-09-06 21:54 adon@walkersun

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=39BD1C8C.5961F6D1@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=adon@walkersun.com \
    --cc=ecos-discuss@sources.redhat.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).