linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: alebas@televes.com
To: Mark Chambers <markc@mail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6.10-rc1 yet not running on ads8272
Date: Tue, 30 Nov 2004 14:08:24 +0100	[thread overview]
Message-ID: <1101820104.41ac70c86a847@webmail.televes.com:443> (raw)
In-Reply-To: <006b01c4d61e$707f2440$0301a8c0@chuck2>

Dan,

I have finally found what I was doing wrong.
Checking mem as you suggested I found that
the breakpoint I was setting to virtual
address 0xc00035f8 has to be set to physical
0x000035f8, otherwise it doesn't stop.

So problem was here with BDI2000 debugging,
MMU and me. Sorry about my misknowledge.

Nevertheless kernel is still hanging.
Now I have continued debugging and I have
arrived to start_kernel ... and go on till
do_basic_setup. But still seeing nothing in
the serial console before kernel hanging.

I think I have some problem with serial
console I have to solve before going on.

Thanks

Alex

Citando Mark Chambers <markc@mail.com>:

> So it's not the simple stuff.  Never is.
>
> I probably shouldn't jump in here, I'm over my head,
> but in the spirit of brainstorming:  Is there any chance
> the bl load_up_mmu instruction isn't in memory at
> physical address 35f8?  It looks like this code is
> bouncing back to physical addressing after having
> the mmu enabled - maybe look at physical
> memory at 35f8 and see if there's a problem?
>
> Mark
>

      parent reply	other threads:[~2004-11-30 12:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 19:06 Kernel 2.6 hangs at m82xx_board_init alebas
2004-11-23 20:13 ` Dan Malek
2004-11-29 12:51   ` Kernel 2.6.10-rc1 yet not running on ads8272 alebas
2004-11-29 13:26     ` Mark Chambers
2004-11-29 13:58       ` alebas
     [not found]       ` <1101736520.41ab2a48a710a@webmail.televes.com:443>
     [not found]         ` <006b01c4d61e$707f2440$0301a8c0@chuck2>
2004-11-30 13:08           ` alebas [this message]

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='1101820104.41ac70c86a847@webmail.televes.com:443' \
    --to=alebas@televes.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=markc@mail.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).