From: Robert Shideleff <bigbob@shideleff.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: GDB/mapper cache problems
Date: Wed, 23 Jun 2004 00:51:00 -0000 [thread overview]
Message-ID: <200406222050.55129.bigbob@shideleff.com> (raw)
In-Reply-To: <20040622162307.GF5740@redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> For example, you could use the hw-glue-bus-probe component: wire up one
> instance of it into the bus structure by mapping it at some address;
> use its pin outputs to trigger any desired pin-based event in the simulator.
This worked great for me, and I got my amdcfi component to more or less work,
but have one more hurdle to overcome:
The processor is an arm7t with a 32 bit bus. The flash is a 16 bit device.
(The component can also be an 8 bit device, but I don't need this
particularly.) In our actual hardware, we have a mapper that will read and
register two 16 bit addresses on the flash and shift/concatenate them to form
a single 32 bit word when the processor executes a 32 bit read. (This allows
us to execute non-thumb instructions out of flash for example.) I haven't yet
found a way to make the SID mapper do this. Is this currently possible? Am I
looking in the wrong place? Am I going to have to do some re-writing?
Bob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFA2NPu8XjOGQDr37YRAvXWAKCf9HEMDgWQ6TBAd/BblsIATzqO3QCfVD8R
D6CqwMAHAIaaYC46E/mNTGQ=
=UuG9
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-06-23 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 1:57 Multiple arm7t processors in pbb causes seg fault Robert Shideleff
2004-06-17 21:54 ` Frank Ch. Eigler
[not found] ` <20040622024603.GB22793@redhat.com>
[not found] ` <200406212319.30979.bigbob@shideleff.com>
2004-06-22 16:08 ` GDB/mapper cache problems Robert Shideleff
2004-06-22 16:23 ` Frank Ch. Eigler
2004-06-23 0:51 ` Robert Shideleff [this message]
2004-06-23 1:47 ` Frank Ch. Eigler
2004-06-23 23:35 ` Robert Shideleff
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=200406222050.55129.bigbob@shideleff.com \
--to=bigbob@shideleff.com \
--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).