From: Gary Thomas <gthomas@ecoscentric.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Tim Drury <tdrury@siliconmotorsports.com>,
"'ecos-discuss@sources.redhat.com'"
<ecos-discuss@sources.redhat.com>,
"'sid@sources.redhat.com'" <sid@sources.redhat.com>
Subject: Re: [ECOS] how to build an eCos library for ARM7tdmi simulator
Date: Mon, 16 Sep 2002 12:54:00 -0000 [thread overview]
Message-ID: <1032206085.10158.36.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20020916154941.B27834@redhat.com>
On Mon, 2002-09-16 at 13:49, Frank Ch. Eigler wrote:
> Hi -
>
> On Fri, Sep 13, 2002 at 09:19:09AM -0400, Tim Drury wrote:
> > > Try running without "--tksm". [...]
> >
> > One problem with this solution is he won't be able to bring
> > up the UART1 console and see the output of the program. Or
> > is there another way to see the output? Redirected to a file
> > would be nice...
>
> The "--board" processing logic allows you to configure the simulated
> UARTs' outputs without tksm. Try adding something like
> "uart1:tty-uart2:stdio" to the long --board option. "uart1:2222"
> connects it to a TCP server socket at port 2222.
Can similar results be easily had using a configuration file?
--
------------------------------------------------------------
Gary Thomas |
eCosCentric, Ltd. |
+1 (970) 229-1963 | eCos & RedBoot experts
gthomas@ecoscentric.com |
http://www.ecoscentric.com/ |
------------------------------------------------------------
next prev parent reply other threads:[~2002-09-16 19:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 23:14 Satish Kumar
2002-09-13 5:32 ` Gary Thomas
2002-09-13 6:23 ` Tim Drury
2002-09-13 6:27 ` Gary Thomas
2002-09-16 12:49 ` Frank Ch. Eigler
2002-09-16 12:54 ` Gary Thomas [this message]
2002-09-16 13:05 ` Frank Ch. Eigler
2002-09-16 17:25 ` T Satish Kumar
2002-09-16 17:36 ` Frank Ch. Eigler
2002-09-16 18:55 ` T Satish Kumar
2002-09-17 3:09 ` Frank Ch. Eigler
2002-09-17 17:02 ` T Satish Kumar
2002-09-16 2:50 ` Robert Cragie
2002-09-16 20:35 T Satish Kumar
2002-09-18 1:29 T Satish Kumar
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=1032206085.10158.36.camel@hermes.chez-thomas.org \
--to=gthomas@ecoscentric.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=fche@redhat.com \
--cc=sid@sources.redhat.com \
--cc=tdrury@siliconmotorsports.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).