All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Q-ha Park <qha@infoeq.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: using bdi2000 to debug ppcboot on mpc7455
Date: Wed, 24 Sep 2003 19:33:43 -0700	[thread overview]
Message-ID: <3F725407.3020907@mvista.com> (raw)
In-Reply-To: <004c01c382ff$de2da2f0$2a21a8c0@qha>


Q-ha Park wrote:

>I'm new to BDI2000, and after reading a manual that came with the tool,
>I tried to debug ppcboot using bdi2000 and gdb. The problem is I just
>can't set the breakpoint whether be it software or hardware breakpoint;
>For example, when I set the break point at "boot_cold" and type
>"continue", the program just runs without ever stopping at the
>breakpoint where it's supposed to stop!
>
>
Well, I haven't used the gdb interface with the 745x but I do know that
that with the telnet interface, you have to specify whether you're
setting a breakpoint on a virtual or physical addr (virtual is default,
IIRC).  How you would do this with the gdb interface, I know not but
take a close look at the manual for the 745x--it *is* different from the
7410, etc--and you may find the answer.

Mark


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2003-09-25  2:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25  0:56 using bdi2000 to debug ppcboot on mpc7455 Q-ha Park
2003-09-25  2:33 ` Mark A. Greer [this message]
2003-09-25 14:25   ` bradbosch
2003-09-25 18:27     ` Mark A. Greer
2003-09-26  5:52     ` Q-ha Park
2003-09-30 21:35       ` Wolfgang Denk
2003-09-30 21:32     ` Wolfgang Denk
2003-10-01  6:57     ` Q-ha Park
2003-10-01 10:29       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2003-09-30 22:39 Rod Boyce
2003-09-30 23:38 ` Wolfgang Denk

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=3F725407.3020907@mvista.com \
    --to=mgreer@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=qha@infoeq.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.