public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Christopher Harvey <charvey@matrox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] request for some debugging hints
Date: Wed, 29 Jun 2011 08:55:44 -0400	[thread overview]
Message-ID: <4E0B20D0.4070000@matrox.com> (raw)

kernel version: 2.6.38
u-boot version: 2011.06

I've got an ARM (armv7) kernel that I can boot under QEMU without
problems, but refuses to boot with a bootm command under u-boot.

All I see is "Uncompressing Linux... done, booting the kernel.", then
nothing else.

I'm also hitting a bug very similar to the following with gdb, so I'm
having a hard time figuring out exactly which lines are blocking the
kernel.
http://sourceware.org/ml/gdb-patches/2011-02/msg00048.html
but that patch doesn't fix it in my case.

Basically I was hoping for some hints in case somebody here has already
dealt with a similar problem and could provide some tips to help me
figure out how to spend my debugging time.

I was under the impression that the second a working kernel got passed
the "Uncompressing Linux... done, booting the kernel." point there was
very little that could go wrong since it means the kernel was completely
loaded into memory and the entry point was picked properly.

The kernel is a very standard kernel, and uboot is a very minimal uboot
build with no extra soc or board initializations besides memory size.
eg:
lowlevel_init is blank
reset_cpu is an infinite loop
timers aren't used

any hints or ideas appreciated,
Chris

             reply	other threads:[~2011-06-29 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29 12:55 Christopher Harvey [this message]
2011-06-29 13:42 ` [U-Boot] request for some debugging hints Wolfgang Denk
2011-06-29 14:08 ` Chander Kashyap
2011-06-29 14:17 ` Christopher Harvey

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=4E0B20D0.4070000@matrox.com \
    --to=charvey@matrox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox