From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Shideleff <bigbob@shideleff.com>
Cc: sid@sources.redhat.com
Subject: Re: GDB/mapper cache problems
Date: Tue, 22 Jun 2004 16:23:00 -0000 [thread overview]
Message-ID: <20040622162307.GF5740@redhat.com> (raw)
In-Reply-To: <200406221208.25786.bigbob@shideleff.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hi -
> Alright, I figured the gdb problem. I hadn't connected the gdb yield pins to
> the yield bus. gdb debugging now seems to work perfectly.
OK. I believe that the C++ sid configuration engine in sid/main/dynamic
is not well customized yet for the arm family of targets, so you may
encounter a few such problems.
Regarding interleaving the processors, what you are seeing intentional.
The CPU models are parametrized to allow you to trade off speed versus
accuracy. (Executing N instructions in one CPU before switching context
to the rest of the sim can be significantly faster.)
> I think the second part of my problem where data doesn't seem to reliably
> make its way into the dual port ram is due to mapper cache.
The mapper cache probably does not relate to this - you probably mean
something other than the little internal TLB in the memory-mapper
component that helps classify incoming read/write addresses.
> How can I cause a particular bus access to poke the yield net? [...]
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.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-22 16:23 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 [this message]
2004-06-23 0:51 ` Robert Shideleff
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=20040622162307.GF5740@redhat.com \
--to=fche@redhat.com \
--cc=bigbob@shideleff.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).