From: "Grant Likely" <grant.likely@secretlab.ca>
To: aauer1 <aauer1@gmx.at>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linux booting problem on Xilinx ppc
Date: Tue, 16 Oct 2007 13:37:58 -0600 [thread overview]
Message-ID: <fa686aa40710161237t54688b71g9c7cf9acdac2b744@mail.gmail.com> (raw)
In-Reply-To: <13239003.post@talk.nabble.com>
On 10/16/07, aauer1 <aauer1@gmx.at> wrote:
>
> The on-chip memories are disabled. Only the BRAM is enabled. Now, we also use
> the ELDK 4.1 from Denx and the included cross compiler. The result is the
> same... the Kernel stops at "Now booting the kernel". Now, we also have an
> USB JTAG cable. So, we can debug the memory.
> Probably, anyone has another idea.
There are two common reasons for this behaviour:
1. kernel crashes before the console is configured
2. the console is not configured correctly.
In both cases; finding a way to look at __log_buf is the fastest way
to figure out what is going on.
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
next prev parent reply other threads:[~2007-10-16 19:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 21:26 Linux booting problem on Xilinx ppc Junqiang Hu
2007-09-15 21:29 ` Junqiang Hu
2007-09-16 3:09 ` Grant Likely
2007-09-16 4:39 ` Junqiang Hu
2007-09-16 15:37 ` Stelios Koroneos
2007-10-15 18:46 ` aauer1
2007-10-15 19:17 ` Koss, Mike (Mission Systems)
2007-10-15 19:20 ` Grant Likely
2007-10-16 15:08 ` Sergey Oleynichenko
2007-10-16 18:02 ` aauer1
2007-10-16 19:37 ` Grant Likely [this message]
2007-10-16 20:12 ` T Ziomek
2007-10-16 20:14 ` Grant Likely
2007-10-16 20:13 ` Ack, sorry! [was Re: Linux booting problem on Xilinx ppc] T Ziomek
2007-10-17 12:09 ` Linux booting problem on Xilinx ppc aauer1
2007-10-17 14:54 ` Grant Likely
2007-10-17 18:12 ` aauer1
2007-10-17 18:23 ` Grant Likely
2007-10-17 18:56 ` aauer1
2007-10-18 23:27 ` 转发: " keng_629
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=fa686aa40710161237t54688b71g9c7cf9acdac2b744@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=aauer1@gmx.at \
--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).