linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Phil <ibm405.linux@laposte.net>
To: frowand@mvista.com
Cc: Tom Rini <trini@kernel.crashing.org>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: More walnut boottime "fun" and BDI2000
Date: Wed, 05 Dec 2001 14:28:51 +0100	[thread overview]
Message-ID: <3C0E2113.779E89DF@laposte.net> (raw)
In-Reply-To: 3C0D06F8.57DD8837@mvista.com


Frank Rowand a écrit :
>
> Phil wrote:
> >
> > I resync the kernel sources today at 7:15 am GMT.
> > Any idea ?
> >
> > Tom Rini a écrit :
> > >
> > > On Tue, Dec 04, 2001 at 02:46:46PM +0100, Phil wrote:
> > >
> > > > I'am trying to boot the latest linuxppc_2_4_devel kernel version
> > > > (2.4.27-pre2).
> > >
> > > What date?  This isn't a problem anymore, at least on a few walnuts I've
> > > gotten people to test.
>
> Rev 1.731 of linuxppc_2_4_devel(mid-day California time yesterday) boots
> fine on my walnut.
>
> HHL2.0 toolchain and ibm OpenBios.
>
> I used an almost default configuration (I was working on a KGDB
> problem so I enabled KGDB):
>
>    make walnut_config
>    make menconfig
>         select KGDB
>         select CONFIG_MORE_COMPILE_OPTIONS
>    make dep
>    make zImage
>
> (I needed to fix config.in to allow CONFIG_MORE_COMPILE_OPTIONS - see
> the patch I posted yesterday.)
>
> You shouldn't have to enable KGDB.
>
> Do you have KGDB enabled by mistake?  If you do, it will sit at the
> "Now booting the kernel" console message until KGDB connects to the
> target.


Thanks Frank
You're right. It works fine with
    make walnut_config
    make menconfig
    make dep
    make zImage
and the ibm openbios
but i want to use my BDi 2000  Abatron debugger to debug the kernel.
So, i select the following options :
         select CONFIG_BDI_SWITCH
         select CONFIG_MORE_COMPILE_OPTIONS
I download the kernel with the debugger(latest 1.07 firmware). It works
fine (i can put for
example a breakpoint in start_kernel or in do_init_bootmem, it stops at
the right address)
If i continue, nothing happened, the 405GP seems locked in the __udelay
routines.
Is it a debugger config file pb ?
Any idea ? Thanks

-Phil.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-12-05 13:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 23:30 More walnut boottime "fun" Simon Winwood
2001-11-27  5:17 ` Tom Rini
2001-11-27 12:07   ` Matt Porter
2001-11-27 15:41     ` Tom Rini
2001-11-27 19:18     ` Simon Winwood
2001-11-27 19:26       ` Tom Rini
2001-12-04 13:46     ` Phil
2001-12-04 14:11       ` Tom Rini
2001-12-04 14:24         ` Phil
2001-12-04 14:45           ` Tom Rini
2001-12-04 16:46             ` Phil
2001-12-04 17:07               ` Tom Rini
2001-12-04 17:25           ` Frank Rowand
2001-12-05 13:28             ` Phil [this message]
2001-12-04 19:34           ` Armin Kuster

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=3C0E2113.779E89DF@laposte.net \
    --to=ibm405.linux@laposte.net \
    --cc=frowand@mvista.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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).