linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Tangermann <marcus.tangermann@web.de>
To: linux-embedded@vger.kernel.org
Subject: Re: Kernel boot problem on IXP422 Rev. A
Date: Fri, 13 Jun 2008 21:07:46 +0200	[thread overview]
Message-ID: <4852C582.9000508@web.de> (raw)
In-Reply-To: <4851BC65.4030501@snapgear.com>

Hi Greg,

first, thanks for the hints.
>
> The most common problem like this I have seen are that the
> ARM machine type set by the boot loader does not match those
> compiled into the kernel. Also make sure that the RAM
> size being passed to the kernel is correct too.
>
This seems to be set correctly.

> Enable the kernels CONFIG_DEBUG_LL and it may give you some
> early debug output (like an id not supported message). That
> assumes a serial console...
Will try that,
Today I downloaded the snapgear distribution and tried whether i can 
generate a kernel image that works with it...and it boots (2.4 and 2.6)  
:-) Then I downloaded a fresh 2.6.25 kernel and compiled it with 
toolchain from the snapgear homepage...and it does not boot. Are there 
any special patches in the 2.6.19-uc1 from the snapgear distribution 
that might have influence on a IXP422 based board?
Additionally, it seems that we may have a little problem in the 
bootloader (uboot) when passing kernel parameters (e.g."setenv bootargs 
console=ttyS0,115200"). Setting such a paramter causes the same problem 
with a dying kernel. Maybe there is a relation.

Regards
Marcus

  reply	other threads:[~2008-06-13 19:07 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 19:35 Kernel boot problem on IXP422 Rev. A Marcus Tangermann
2008-06-12 20:04 ` Mike Frysinger
2008-06-12 21:28   ` Glenn Henshaw
2008-06-12 21:35     ` Mike Frysinger
2008-06-12 21:43     ` Craig Hollabaugh
2008-06-12 21:43     ` Alexey Zaytsev
2008-06-12 22:15     ` David Woodhouse
2008-06-13 17:33     ` Rob Landley
2008-06-13 20:05       ` Tim Bird
2008-06-15 19:17         ` Rob Landley
2008-06-13  0:13   ` Glenn Henshaw
2008-06-13  0:16 ` Greg Ungerer
2008-06-13 19:07   ` Marcus Tangermann [this message]
2008-06-14  7:17     ` Greg Ungerer
2008-06-19 17:59       ` Marcus Tangermann
2008-06-20  0:08         ` Greg Ungerer
2008-06-13  2:10 ` George G. Davis

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=4852C582.9000508@web.de \
    --to=marcus.tangermann@web.de \
    --cc=linux-embedded@vger.kernel.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).