From: Hollis Blanchard <hollis@penguinppc.org>
To: Reeve Yang <yang.reeve@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: kgdb on mpc834x
Date: Tue, 12 Dec 2006 22:00:56 -0600 [thread overview]
Message-ID: <1165982456.10549.1.camel@diesel> (raw)
In-Reply-To: <198592450612121611o7f7271cbnb1404c7f7f9fda71@mail.gmail.com>
On Wed, 2006-12-13 at 00:11 +0000, Reeve Yang wrote:
> I applied kgdb patch for 2.6.13 to kernel 2.6.14 (since there is no
> patch for 2.6.14), but gdb client cannot connec to it. I turn on all
> necessary kernel hacking options. Our board is customized with
> MPC834x, can someoen who used kgdb to debug kernel on MPC834x help me
> out? Following are the message from linux boot and gdb client.
>
> ## Booting image at ff300000 ...
>
> loaded at: FF300000 FFB71124
> relocated to: 00800000 01071124
> board data at: 007FFF70 007FFFF8
> relocated to: 00805114 0080519C
> zimage at: 00805915 00926A5E
> initrd at: 00927000 0106E242
> avail ram: 01072000 01472000
>
> Linux/PPC load: mem=248M
> Uncompressing Linux...done.
> Now booting the kernel
> mpc834x_sys_init(): exit
> id mach(): done
> MMU:enter
> MMU:hw init
> MMU:mapin
> MMU:setio
> MMU:exit
> setup_arch: enter
> setup_arch: bootmem
>
> (gdb) target remote /dev/ttyS0
> Remote debugging using /dev/ttyS0
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Ignoring packet error, continuing...
> Malformed response to offset query, timeout
Try 'set debug serial 1' in GDB; it will show you the actual data GDB is
receiving.
-Hollis
next prev parent reply other threads:[~2006-12-13 4:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 0:11 kgdb on mpc834x Reeve Yang
2006-12-13 4:00 ` Hollis Blanchard [this message]
2006-12-14 1:08 ` Reeve Yang
2006-12-14 6:22 ` Vitaly Wool
2006-12-14 15:13 ` Jimi Xenidis
2006-12-13 6:18 ` Vitaly Wool
2006-12-13 17:21 ` Geoff Levand
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=1165982456.10549.1.camel@diesel \
--to=hollis@penguinppc.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=yang.reeve@gmail.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).