From: Steve Heflin <sheflin@newagemicro.com>
To: linuxppc-embedded@ozlabs.org
Subject: Re: Sequoia build with KDBG
Date: Fri, 29 Feb 2008 19:36:35 -0500 [thread overview]
Message-ID: <20080301003610.99532DDE19@ozlabs.org> (raw)
At 05:51 PM 2/29/2008, you wrote:
>On Fri, 29 Feb 2008 17:31:10 -0500
>Steve Heflin <sheflin@newagemicro.com> wrote:
>
> > At 04:35 PM 2/29/2008, Josh Boyer wrote:
> > >On Fri, 29 Feb 2008 16:34:09 -0500
> > >Steve Heflin <sheflin@newagemicro.com> wrote:
> > >
> > > > I attempted to enable the kernel debugger on my Sequoia board, and I
> > > > get build errors:
> > > > /linux-2.6.25-rc3/arch/powerpc/kernel/setup_32.c:254: undefined
> > > > reference to `set_debug_traps'
> > > > /linux-2.6.25-rc3/arch/powerpc/kernel/setup_32.c:259: undefined
> > > > reference to `breakpoint'
> > > >
> > > > Josh: I assume you have used the kernel debugger with your 44x
> > > > boards, how did you build it?
> > >
> > >Why would you assume that? I've never used kgdb on arch/powerpc
> > >kernels, nor have I ever tried to build it.
> >
> > I assumed that because I've always needed a debugger when
> > implementing kernel level components. Since you've implemented kernel
> > level support for several 44x processors, I just assumed that you
> > needed kdbg at some point. So you're saying that your additions
>
>Nope. I did the poor man's method of manually poking characters out of
>the serial port.
>
> > worked right out of the gate and you never needed a
> debugger? You're my hero!
>
>I largely stood on the shoulders of those that came before me. Porting
>has become trivial lately, mostly due to the collective work lots of
>people have put in.
>
>That all being said, I'm not opposed to having kgdb work on 4xx. I
>just have never personally looked at it yet. Patches welcome :).
>
>josh
poor man's debugging works fine if a serial port is available, but my
Sequoia platform doesn't get that far! I use u-boot to download and
boot my image, and I don't get any serial output after the boot completes:
=> bootm 0x500000
## Booting image at 00500000 ...
Image Name: Kernel and Ramdisk
Created: 2008-03-01 0:09:57 UTC
Image Type: PowerPC Linux Multi-File Image (gzip compressed)
Data Size: 2430248 Bytes = 2.3 MB
Load Address: 00000000
Entry Point: 00000000
Contents:
Image 0: 1471523 Bytes = 1.4 MB
Image 1: 958712 Bytes = 936.2 kB
Verifying Checksum ... OK
Uncompressing Multi-File Image ... OK
Loading Ramdisk to 07e42000, end 07f2c0f8 ... OK
------
console port is now dead.
------
next reply other threads:[~2008-03-01 0:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 0:36 Steve Heflin [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-21 21:33 MODPOST section mismatches Steve Heflin
2008-02-22 16:12 ` Steve Heflin
2008-02-22 20:52 ` Josh Boyer
2008-02-29 21:34 ` Sequoia build with KDBG Steve Heflin
[not found] ` <200802292133.m1TLXqv3012273@e36.co.us.ibm.com>
2008-02-29 21:35 ` Josh Boyer
2008-02-29 22:31 ` Steve Heflin
2008-02-29 22:58 ` Scott Wood
2008-02-29 23:28 ` Jon Loeliger
2008-03-01 0:16 ` Wolfgang Denk
2008-03-01 1:48 ` Steve Heflin
[not found] ` <200802292230.m1TMUk4I005462@e31.co.us.ibm.com>
2008-02-29 22:51 ` Josh Boyer
[not found] ` <200803010023.m210NHwr011345@e2.ny.us.ibm.com>
2008-03-01 2:30 ` Josh Boyer
2008-03-01 2:55 ` Steve Heflin
2008-03-02 14:47 ` Wolfgang Denk
2008-03-01 5:02 ` Olof Johansson
2008-03-01 13:13 ` Josh Boyer
2008-03-01 15:57 ` Olof Johansson
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=20080301003610.99532DDE19@ozlabs.org \
--to=sheflin@newagemicro.com \
--cc=linuxppc-embedded@ozlabs.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).