From: Mike Frysinger <vapier@gentoo.org>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: lm32 simulator configuration file question
Date: Fri, 03 Apr 2015 01:41:00 -0000 [thread overview]
Message-ID: <20150403014149.GJ22171@vapier> (raw)
In-Reply-To: <551DC087.7040103@oarcorp.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
On 02 Apr 2015 17:19, Joel Sherrill wrote:
> RTEMS has a BSP for the lm32 which runs on the simulator in gdb.
> Based on our wrapper scripts and READMEs, this is how the simulator
> is invoked in gdb:
>
> tar sim --hw-device lm32cpu \
> --hw-device "lm32uart/reg 0x80006000 0x100" \
> --hw-device "/lm32uart > int int0 /lm32cpu" \
> --hw-device "lm32timer/reg 0x80002000 0x80" \
> --hw-device "/lm32timer > int int1 /lm32cpu" \
> --memory-region 0x08000000,0x4000000
you can pass --hw-file to target sim too
> That works great. When we use lm32-rtems4.11-run, you are supposed
> to provide a hw description file matching those arguments. This is
> the file we are using:
>
> ======================
> lm32cpu
> lm32uart/reg 0x80006000 0x100
> /lm32uart > int int0 /lm32cpu
> lm32timer/reg 0x80002000 0x80
> /lm32timer > int int1 /lm32cpu
put a leading / for each one missing it
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-04-03 1:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 22:19 Joel Sherrill
2015-04-03 1:41 ` Mike Frysinger [this message]
2015-04-03 20:21 ` Joel Sherrill
2015-04-03 23:21 ` Mike Frysinger
2015-04-04 0:00 ` Joel Sherrill
2015-04-04 2:57 ` Mike Frysinger
2015-04-04 13:49 ` Joel Sherrill
2015-04-04 21:08 ` Mike Frysinger
2015-04-05 0:27 ` Joel Sherrill
2015-04-05 1:20 ` Mike Frysinger
2015-04-05 1:32 ` Joel Sherrill
2015-04-05 2:05 ` Mike Frysinger
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=20150403014149.GJ22171@vapier \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=joel.sherrill@oarcorp.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).