All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] no kernel console output !
Date: Sat, 27 Dec 2008 07:45:55 -0500	[thread overview]
Message-ID: <49562383.20902@gmail.com> (raw)
In-Reply-To: <27566628.138081230359348124.JavaMail.coremail@bj163app80.163.com>

Hi Tony,

tjzkzs wrote:
> I use at91sam9260ek board, forgot to mention this. last time I said:
> 
> hi all,
> when i use u-boot 1.1.5 boot kernel 2.6.22, no kernel console output,
> development enviorment i use:
> cross_compiler: arm-2007-eldk.iso

No console output can be caused by several things, all hard to debug 
since you are running blind.

I'm not an arm expert, but u-boot 1.1.5 is suspiciously old, especially 
when trying to boot a fairly recent linux kernel.  Can you upgrade it?

Can you boot an older version of linux with your 1.1.5 u-boot?

Do you get any console output in the linux memory buffer?
   <http://www.denx.de/wiki/view/DULG/LinuxPostMortemAnalysis>

When you halt the processor with your debugger, what is it doing?  Where 
is it?  What procedure is it in?  Can you get a stack trace to see where 
it came from?

Are you passing the right options on the command line to tell linux what 
console parameters are?  (Is your "atag" info right?  I'm ignorant of 
how this works, just know there is something there.)
   <http://www.arm.linux.org.uk/developer/booting.php>


> Best regards,
> Tony Zheng

Good luck,
gvb

  reply	other threads:[~2008-12-27 12:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.2435.1230288433.2783.u-boot@lists.denx.de>
2008-12-27  6:29 ` [U-Boot] no kernel console output ! tjzkzs
2008-12-27 12:45   ` Jerry Van Baren [this message]
2008-12-27 18:39   ` Pawel Pastuszak

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=49562383.20902@gmail.com \
    --to=gvb.uboot@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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.