From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Cragie <rcc@jennic.com>
Cc: sid@sources.redhat.com
Subject: Re: Trying to run on pid7t board
Date: Thu, 22 Aug 2002 06:22:00 -0000 [thread overview]
Message-ID: <20020822092212.A8731@redhat.com> (raw)
In-Reply-To: <NDBBLOIOMLKELOJBAPAGMEIBCOAA.rcc@jennic.com>; from rcc@jennic.com on Thu, Aug 22, 2002 at 12:48:55PM +0100
[-- Attachment #1: Type: text/plain, Size: 1999 bytes --]
Hi -
On Thu, Aug 22, 2002 at 12:48:55PM +0100, Robert Cragie wrote:
> [...]
> Adding the -normalmap argument worked - thanks. I will point this out on the
> eCos mailing list, as the default sid flags for the RAM build won't work.
This may not concern (interest) the eCos guys. SID can do a better job
of emulating the RAM startup environment that eCos expects. This
"normalmap" option is just one possibility. Another one is to actually
run a copy of RedBoot or cygmon or whatever on SID. Then you can upload
your application via a simulated serial port, making it look to gdb etc.
much more like it was a real board.
> Next step is to try to work out why printf() doesn't work, however this
> seems to be an eCos issue. However, while I'm here, can you tell me how the
> serial ports work on the simulation (i.e. what happens when I write a
> character), or point me at some appropriate docs.?
For the pid7t configuration, sid models two uarts. The arm-elf-sid script
can take options to let you tell it how you'd like these simulated uarts
to be connected to the real world. This is done with more --board options.
For example "--board=pid7t-uart1:stdio-uart2:3000" would connect the
simulated uart1 to the simulator's console, and uart2 to a tcp (listening)
socket at port 3000. One can also add a tk-based terminal window, or add
one after startup if using tksm.
> > Please be aware that in your given mode, sid is attempting to
> > emulate a board just after powerup. If your application assumes that it's
> > being loaded by an already-running monitor, such mismatches need to be
> > corrected some way.
>
> I think I misunderstood the way the gloss component works - I guess it's
> more like an on-chip ICE than a debug monitor.
I suspect that the sid gloss component proper (simulated system calls) is
not even used in these configurations. If you mean the usual simulator
debugging interface, then yes, that's right.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-22 13:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-21 9:24 Robert Cragie
2002-08-21 9:35 ` Frank Ch. Eigler
2002-08-21 11:15 ` Robert Cragie
2002-08-21 11:31 ` Frank Ch. Eigler
2002-08-22 4:48 ` Robert Cragie
2002-08-22 6:22 ` Frank Ch. Eigler [this message]
2002-08-22 7:11 ` Ben Elliston
2002-08-22 10:09 ` Robert Cragie
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=20020822092212.A8731@redhat.com \
--to=fche@redhat.com \
--cc=rcc@jennic.com \
--cc=sid@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).