From: Mathieu Lacage <mathieu_lacage@realmagic.fr>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: running eCos under sid
Date: Fri, 23 Nov 2001 04:53:00 -0000 [thread overview]
Message-ID: <1006520035.9233.48.camel@mathieu> (raw)
Message-ID: <20011123045300.-q3RrdxOyWx5anmxhSa2nM75mhwDDKgTB4WGRozfj6k@z> (raw)
In-Reply-To: <20011123073029.A9819@redhat.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2034 bytes --]
le ven 23-11-2001 à 13:30, Frank Ch. Eigler a écrit :
> Right. This happens because the simulator was not asked to configure
> itself for a model of the "Integrator" board. By default, it provides
I was suspecting something in the like...
> a simple process model, with little in the way of simulated hardware
> peripherals. The SID component (model) library includes parts for
> several ARM flavour peripherals: they were built to model the old
> ARM PID development board. To the extent that this "Integrator" board
> is similar, you may make use of the components by "--board=pid7t" and
> related options. Simulation for different boards involves assembling
> models for all the required parts, and configuring sid to use them:
> this can be a small or big job.
If I understood how sid works, this means writing the components not
available for the new board and writing a configuration file for the
board connecting the relevant pieces together ?
>
> For a taste, try running
> sid arm-pid-redboot-tksm.conf
> (find named file under $prefix/share/sid; it explains its own origins)
> then telnet to localhost:5000 (or connect gdb to localhost:5000; can
> upload a RAM-startup eCos program). This configuration brings up
> the PID board simulation, preloads an older RedBoot ROM image.
> RedBoot shows a command line on uart1, which is connected to TCP
> port 5000. A little tcl/tk gui also appears, so you can
> monitor/interact-with the simulation as it's proceeding.
hrm, sounds cool.
I'll try this later. As a side note, I do not even own an Integrator
board and my target system has nothing to do with traditional boards so
I'll have to hack together a simulation environment myself anyway...
/me wished there was another poor soul in his company to do it :)
thanks a lot for your quick answer,
I'll keep you updated if I can manage to release some GPL code of our
(not-yet-written) modules.
best regards,
Mathieu
>
> - FChE
--
Mathieu Lacage <mathieu_lacage@realmagic.fr>
#p: +33 1 69 19 61 97
next prev parent reply other threads:[~2001-11-23 4:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 14:00 Mathieu Lacage
2001-11-14 0:14 ` Frank Ch. Eigler
2001-11-14 3:43 ` Mathieu Lacage [this message]
2001-11-14 4:00 ` Frank Ch. Eigler
2001-11-23 5:02 ` Frank Ch. Eigler
2001-11-23 4:53 ` Mathieu Lacage
2001-11-23 4:30 ` Frank Ch. Eigler
2001-11-23 1:31 ` Mathieu Lacage
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=1006520035.9233.48.camel@mathieu \
--to=mathieu_lacage@realmagic.fr \
--cc=fche@redhat.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).