From: "Richard Hendricks" <ra6353@email.sps.mot.com>
To: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: LinuxPPC with BDM
Date: Mon, 13 Sep 1999 09:36:17 -0500 [thread overview]
Message-ID: <37DD0BE1.5DA876F@email.sps.mot.com> (raw)
In-Reply-To: 37DC9380.D0A6BA3F@ctam.com.au
The BDM runs into problems when the underlying operating system uses the
MMUs to implement a page table. Since the BDM doesn't understand page
tables, when it stops the core it assumes the PC is pointing into
physical memory. This makes debugging the kernel difficult using BDM.
Using the BDM inherently doesn't change any registers, but MPC8bug may
initialize some registers you don't want it to.
Brendan Simon wrote:
>
> Dan mentioned (in another email) that mpcbug can cause problems when
> running linux. I take it this is a generic BDM problem. Is this true
> ? In theory it shouldn't matter should it, as long as the debugger
> leaves the core in the same condition just before it enters debug mode.
>
> I have been using the BDM to download kernels and running them from RAM
> (stepping through the code, etc). Could this be the cause of the
> strange behaviour I've seen on the ADS boards ?
>
> Should I stear clear of the BDM ? I would prefer to use it as it allows
> alot of low level debugging and control.
>
> Brendan Simon.
>
> BTW. I have been using a beta version of GDB with support for the
> Macraigor Wiggler. I got it from Scott Howard. Unfortunately it will
> only run on a Windows machine due to the wigglers.dll which is
> required. If anyones interested in this then there is more information
> on http://www.objsw.com/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-09-13 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-13 6:02 LinuxPPC with BDM Brendan Simon
1999-09-13 14:36 ` Richard Hendricks [this message]
1999-09-13 17:42 ` Dan Malek
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=37DD0BE1.5DA876F@email.sps.mot.com \
--to=ra6353@email.sps.mot.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 NNTP newsgroup(s).