From: Scott Wood <scottwood@freescale.com>
To: Shawn Jin <shawnxjin@gmail.com>
Cc: ppcdev <linuxppc-dev@ozlabs.org>
Subject: Re: machine check in kernel for a mpc870 board
Date: Thu, 01 Jul 2010 12:42:45 -0500 [thread overview]
Message-ID: <4C2CD395.90409@freescale.com> (raw)
In-Reply-To: <AANLkTilZm-TRkjgYBc0xj9iFYUJl7bb19Zvrcj2R-wJd@mail.gmail.com>
On 07/01/2010 02:50 AM, Shawn Jin wrote:
> Hi Scott,
>
>> How do I find the address, reg, and range for nodes like localbus,
>> soc, eth0, cpm, serial etc.?
If your CCSRBAR is 0xfa200000, then pretty much anywhere you see
0xff0xxxxx change it to 0xfa2xxxxx.
> I managed to proceed a little bit further.
> Memory<-<0x0 0x8000000> (128MB)
> ENET0: local-mac-address<- 00:09:9b:01:58:64
> CPU clock-frequency<- 0x7270e00 (120MHz)
> CPU timebase-frequency<- 0x393870 (4MHz)
> CPU bus-frequency<- 0x3938700 (60MHz)
>
> zImage starting: loaded at 0x00400000 (sp: 0x07d1ccd0)
> Allocating 0x186bdd bytes for kernel ...
> gunzipping (0x00000000<- 0x0040c000:0x00591c30)...done 0x173b18 bytes
>
> Linux/PowerPC load: root=/dev/ram
> Finalizing device tree... flat tree at 0x59e300
>
> The gdb showed deadbeef.
> (gdb) target remote ppcbdi:2001
> Remote debugging using ppcbdi:2001
> 0xdeadbeef in ?? ()
> (gdb)
>
> The kernel doesn't seem to start. What could go wrong here?
Pretty much anything. :-)
Make sure that you've got Linux platform code enabled that matches the
top-level compatible of your device tree. Try enabling
PPC_EARLY_DEBUG_CPM, making sure to update PPC_EARLY_DEBUG_CPM_ADDR to
0xfa202008.
-Scott
next prev parent reply other threads:[~2010-07-01 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 7:59 machine check in kernel for a mpc870 board Shawn Jin
2010-06-29 8:06 ` Joakim Tjernlund
2010-06-29 8:37 ` Shawn Jin
2010-06-29 18:56 ` Scott Wood
2010-06-30 6:14 ` Shawn Jin
2010-06-30 16:16 ` Scott Wood
2010-06-30 22:25 ` Shawn Jin
2010-07-01 7:50 ` Shawn Jin
2010-07-01 17:42 ` Scott Wood [this message]
2010-07-01 20:17 ` Shawn Jin
2010-07-01 20:25 ` Scott Wood
2010-07-02 17:06 ` Shawn Jin
2010-07-02 17:47 ` Scott Wood
2010-07-02 19:16 ` Shawn Jin
2010-07-02 19:41 ` Scott Wood
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=4C2CD395.90409@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=shawnxjin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.