From: Leon Pollak <leonp@plris.com>
To: insight@sourceware.cygnus.com
Subject: Virtual memory and gdb/Insight
Date: Wed, 31 May 2000 01:13:00 -0000 [thread overview]
Message-ID: <4.3.0.20000531102122.00aa5c70@plris.com> (raw)
Hello, all.
Please, excuse me, if the theme I arise is solved already, but I didn't
see any reminiscences about this.
I am using Insight for remote debugging of my PowerPC (MPC860) target via
BDM interface. I don't think that this is important, but still - the scheme
is as following:
[Linux PC with Insight] <------->Ethernet<----------->[Windows PC with
rproxy]<--------->Wiggler BDM<---------->[Target Board].
To clarify: rproxy is the program working as remote target for gdb and as
BDM controller for target (see http://www.std.com/qqi/ ).
Now, everything worked fine up to the moment when I switched on the MMU,
which was supposed to translate some addresses in my application (I wanted
to unite to banks of RAM with the space between them).
At that moment, the following occurs - when I stop the program via BDM, the
MMU is disabled (that is what Motorola states and this happens), so that
looking in to variables, memory and etc. shows nothing but 0xFFFF...,
because the virtual address isn't translated into real one.
My question to Motorola staff was answered as following: your problem can
be solved only by the intelligent software debugger.
Consult this with vendor of your debug system.
And that is what I am doing.
Any reply will be highly appreciated.
leonp@plris.com
next reply other threads:[~2000-05-31 1:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-31 1:13 Leon Pollak [this message]
2000-05-31 2:34 ` Steven Johnson
2000-05-31 2:57 ` Andrew Cagney
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=4.3.0.20000531102122.00aa5c70@plris.com \
--to=leonp@plris.com \
--cc=insight@sourceware.cygnus.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).