From: Ben Elliston <bje@redhat.com>
To: Scott Dattalo <scott@dattalo.com>
Cc: sid@sources.redhat.com
Subject: Re: SID and eCos
Date: Tue, 18 Jun 2002 18:46:00 -0000 [thread overview]
Message-ID: <15631.57966.122255.2563@tooth.toronto.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206181526290.14647-100000@ruckus.brouhaha.com>
Hi Scott,
>>>>> "Scott" == Scott Dattalo <scott@dattalo.com> writes:
Scott> The Makefile I used to create the executable is part of eCos. I
Scott> specifically target Atmel's AT91EB40 evaluation board. The generic, out of
Scott> the box, SID arm emulation knows nothing about an AT91EB40. The error
Scott> reported above is telling me that the executable accesses RAM that doesn't
Scott> exist (hey, I think I like that:). So I added a few --memory-region's:
Scott> $ arm-elf-sid --cpu=arm --memory-region=0x2020000,0x20000
Scott> --memory-region=0xfffe0000,0x1ffff --gdb=2000 -EL hello
Scott> And that worked!
You're right. The problem is that the default ARM configuration does
not include as expansive memory regions as the GDB simulator, so your
program was writing into unmapped regions.
Scott> So now it looks like I have not one, but two (mostly) independent ways to
Scott> simulate my source. I like the SID approach because of the added
Scott> flexibility; specifically the ability to profile.
Great! I'm pleased that you've seen SID for what it is.
Scott> sid appears to be an extraordinarily powerful tool. Is there any reason
Scott> why it's not more popular? Judgeing from the mailing list archives, it
Scott> appears that not too many people are using it.
I believe there are at least a couple of factors:
* it has only been out on the net for a year or so; and
* I don't think it is very widely known about.
Scott> investigate to what extent it's possible to leverage our two projects.
Scott> Specifically, I'd like to incorporate the abstract hardware interface that
Scott> sid supports with gpsim. And to reciprocate, I can add some of gpsim's
Scott> modules to sid!
That'd be terrific! Can you summarise what gpsim modules you have?
Regards, Ben
next prev parent reply other threads:[~2002-06-19 1:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 13:51 Scott Dattalo
2002-06-18 15:59 ` Scott Dattalo
2002-06-18 18:46 ` Ben Elliston [this message]
2002-06-18 22:06 ` Scott Dattalo
2002-06-19 14:19 ` Ben Elliston
2002-06-19 20:42 ` Scott Dattalo
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=15631.57966.122255.2563@tooth.toronto.redhat.com \
--to=bje@redhat.com \
--cc=scott@dattalo.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).