From: "Mark A. Greer" <mgreer@mvista.com>
To: bradbosch@attbi.com
Cc: Q-ha Park <qha@infoeq.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: using bdi2000 to debug ppcboot on mpc7455
Date: Thu, 25 Sep 2003 11:27:40 -0700 [thread overview]
Message-ID: <3F73339C.4050007@mvista.com> (raw)
In-Reply-To: <16242.64239.133401.668446@waldo.lisle.iphase.com>
bradbosch@attbi.com wrote:
>Once you get all this working, could you please do me a favor and let
>me know if you ever have any problems with single step ("mon ti" or
>"stepi") not working? I have a lot of trouble with this with my
>7447/Discovery II combo and I am trying to figure out if it is a board
>issue or a processor issue or a BDI issue.
>
>
Hi Brad.
I almost exclusively use the telnet interface (and hard breakpoints) to
the bdi b/c I do a lot of early on debug. I have noticed with certain
processors that a single step will occasionally go several instructions
before stopping. Unfortunately, I don't remember which processors I see
that on and I've never had a 7447 to try. What I'm getting at is: a)
yes, I have seen some [minor] breakpoint problems with the bdi (or
possibly the breakpoint implementation on the processor); and b) try
using the telnet interface to eliminate a possible gdb-related problem.
Just my $0.02.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-25 18:27 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
2003-09-25 14:25 ` bradbosch
2003-09-25 18:27 ` Mark A. Greer [this message]
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=3F73339C.4050007@mvista.com \
--to=mgreer@mvista.com \
--cc=bradbosch@attbi.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.