From: wavecom wavecom <wavecomw@yahoo.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: ecos-discuss@ecos.sourceware.org
Subject: Re: [ECOS] eCos and AT91SAM7S-EK
Date: Mon, 02 Jul 2007 06:51:00 -0000 [thread overview]
Message-ID: <238287.22532.qm@web60724.mail.yahoo.com> (raw)
In-Reply-To: <703052.59517.qm@web60719.mail.yahoo.com>
> > > Andrew, could you describe me your method of
> > running
> > > and debugging eCos application, maybe I'm able
> to
> > > reproduce it on my hardware.
> > > I'd like to ask about configuration of outgoing
> > > messages. Where can I check if the output of
> > prontf
> > > commands is ARM-COM1?
> >
> > I use Linux, not M$.
> >
> > I build ROM applications, which for the AT91SAM7
> > platforms is the
> > default. I use the toolchain which you can
> download
> > from the eCos
> > website. I use a JTAG device to load the image
> into
> > the target. The
> > JTAG device i use understands ELF, so i just give
> it
> > a URL and the
> > device grabs the elf file, converts it as
> necessary,
> > and loads it onto
> > FLASH. I then use gdb, to connect to the JTAG
> device
> > in much the same
> > way as you did. I there use the gdb version you
> > download as part of
> > the toolchain, or sometimes i use a newer version
> > which i built
> > myself. I would recommend you use the pre-build
> > version to start with
> > since it is known to work.
>
> Where can I find such pre-build version?
I have insalled
bu-2.17_gcc-4.2.0-c-c++_nl-1.15.0_gi-6.6.exe from
www.gnuarm.org . Is it enough for eCos build?
>
> >
> > The default configuration of the AT91SAM7SEK is to
> > use the debug port
> > for I/O.
> >
> > Andrew
> >
> > --
> > Before posting, please read the FAQ:
> > http://ecos.sourceware.org/fom/ecos
> > and search the list archive:
> > http://ecos.sourceware.org/ml/ecos-discuss
> >
> >
>
>
>
>
>
____________________________________________________________________________________
> Fussy? Opinionated? Impossible to please? Perfect.
> Join Yahoo!'s user panel and lay it on us.
>
http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
>
>
>
> --
> Before posting, please read the FAQ:
> http://ecos.sourceware.org/fom/ecos
> and search the list archive:
> http://ecos.sourceware.org/ml/ecos-discuss
>
>
____________________________________________________________________________________
Get the Yahoo! toolbar and be alerted to new email wherever you're surfing.
http://new.toolbar.yahoo.com/toolbar/features/mail/index.php
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2007-07-02 6:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070630220134.GC8004@lunn.ch>
2007-07-01 7:50 ` wavecom wavecom
2007-07-01 9:36 ` wavecom wavecom
2007-07-01 12:33 ` Andrew Lunn
2007-07-01 22:07 ` wavecom wavecom
2007-07-02 6:51 ` wavecom wavecom [this message]
2007-07-02 9:14 ` Andrew Lunn
2007-06-30 18:13 wavecom wavecom
2007-06-30 20:40 ` Andrew Lunn
2007-06-30 21:40 ` wavecom wavecom
2007-06-30 22:01 ` Andrew Lunn
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=238287.22532.qm@web60724.mail.yahoo.com \
--to=wavecomw@yahoo.com \
--cc=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
/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).