From: Wolfgang Denk <wd@denx.de>
To: bradbosch@attbi.com
Cc: "Mark A. Greer" <mgreer@mvista.com>, Q-ha Park <qha@infoeq.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: using bdi2000 to debug ppcboot on mpc7455
Date: Tue, 30 Sep 2003 23:32:41 +0200 [thread overview]
Message-ID: <20030930213246.6FC87C59E4@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 25 Sep 2003 09:25:51 CDT." <16242.64239.133401.668446@waldo.lisle.iphase.com>
In message <16242.64239.133401.668446@waldo.lisle.iphase.com> you wrote:
>
> In addition to the issue Mark pointed out, you can't use soft
> breakpoints while you are running from ROM which is the common case
> for the early init parts of U-Boot.
>
> Also, once U-Boot has relocated itself, you need to identify the new
> base address and inform gdb of the new load address.
And not to forget that, in the very early startup code (like the
symbol "boot_cold" mentioned by Q-ha Park), the memory controller is
still running in the reset configuration, i. e. the PC will still
point to the reset vector area (0x0000'01xx or 0xFFF0'01xx), and NOT
yet to the addresses in the U-Boot symbol table. Only after
"in_flash" the symbols are correct.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"A little knowledge is a dangerous thing." - Doug Gwyn
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-09-30 21:32 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
2003-09-26 5:52 ` Q-ha Park
2003-09-30 21:35 ` Wolfgang Denk
2003-09-30 21:32 ` Wolfgang Denk [this message]
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=20030930213246.6FC87C59E4@atlas.denx.de \
--to=wd@denx.de \
--cc=bradbosch@attbi.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mgreer@mvista.com \
--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 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).