From: Deaf Beed <deafbeed@gmail.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sourceware.org
Subject: Re: Loading image-file in SID.
Date: Wed, 18 Aug 2010 17:43:00 -0000 [thread overview]
Message-ID: <AANLkTinw3s-yGNXrKwFJASfzvneuSmhb_u1fp1WvkEpG@mail.gmail.com> (raw)
In-Reply-To: <20100719110938.GB12047@redhat.com>
Hi
Thanks. That worked out well for me. Really appreciated the response.
I now generate a sid configuration and edit it to add my component.
>$ arm-elf-sid --board=pid7t-normalmap --load cpu=program.x --no-run
The 'program.x' is a bunch of prints, linked with the eCos OS built
for pid7t. The program executes and I can trace the prints at the
UART.
However, once the prints have executed, the control passes to, I
think, the OS idle loop and the simulation does not exit on its own. I
have to stop it. Is there a way to make the simulation exit/finish on
its own? maybe by programming some sid simulation component.
-Shamik
On Mon, Jul 19, 2010 at 4:39 PM, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> On Mon, Jul 19, 2010 at 04:34:44PM +0530, Deaf Beed wrote:
>> I have been playing around with SID for a while and have created a
>> component of mine. [...]
>
> Great. Please feel free to contribute any pieces you are able.
>
>> [...] I realize that the PC also needs to be set and tried to do
>> that using "set cpu pc (int of)0x8040" but without any
>> success. Could you please suggest the required changes,
>> etc. required to load and run and arbitrary image using SID alone?
>
> Certainly. See the sw-load-elf component, for example as configured
> by the bsp/configrun-sid perl script. It connects to a memory mapper
> bus (to write into memory), and a CPU (the start-pc-set! pins)
>
> - FChE
>
next prev parent reply other threads:[~2010-08-18 17:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 11:04 Deaf Beed
2010-07-19 11:09 ` Frank Ch. Eigler
2010-08-18 17:43 ` Deaf Beed [this message]
2010-08-18 20:34 ` Frank Ch. Eigler
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=AANLkTinw3s-yGNXrKwFJASfzvneuSmhb_u1fp1WvkEpG@mail.gmail.com \
--to=deafbeed@gmail.com \
--cc=fche@redhat.com \
--cc=sid@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).