From: "Boerner, Brian" <bmb@pirus.com>
To: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Debugging Linux with PPCBoot and the BDI2000
Date: Fri, 17 Aug 2001 10:35:39 -0400 [thread overview]
Message-ID: <200108172021.PAA04309@lists.linuxppc.org> (raw)
I'm trying to debug my kernel using PPCBoot to load the kernel image via
tftpboot and then stop it in start_kernel.
I do the following.
1. Power up the to PPCBoot prompt
2. Load the vmlinux.img image via tftpboot created using the mkimage tool.
3. Load vmlinux into gdb that's connected to the bdi2000 at addr 0xc0000000
4. set a break at start_kernel (breaking on _start didn't work at all).
5. Telling PPCBoot to bootm
6. The debugger stops in start_kernel
Now, when I try to step or next I get the following error from gdb:
Breakpoint 2, start_kernel () at init/main.c:530
(gdb) display/i $pc
1: x/i $pc 0xc0142660 <start_kernel+16>: lis r9,-16364
(gdb) s
Cannot access memory at address 0x1100
I was under the impressions that the MMU has already been initilized at this
point and we should be running with vaddrs, hence the 0xc0000000
start_kernel function. But, it appears that for some reason gdb is confused
about v to p.
What am I doing wrong here?
Confused.
-bmb
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-08-17 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-17 14:35 Boerner, Brian [this message]
2001-08-17 20:38 ` IBM PPC405 - when did the USB disappear? Karsten Jeppesen
2001-08-17 20:57 ` Debugging Linux with PPCBoot and the BDI2000 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=200108172021.PAA04309@lists.linuxppc.org \
--to=bmb@pirus.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).