public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Grant Likely <glikely@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Cannot boot from a uImage on the lite5200
Date: Wed, 20 Apr 2005 17:35:21 -0600	[thread overview]
Message-ID: <528646bc050420163579a4fefd@mail.gmail.com> (raw)
In-Reply-To: <20050420201516.3D55DC1510@atlas.denx.de>

On 4/20/05, Wolfgang Denk <wd@denx.de> wrote:
> In message <528646bc0504201254fade191@mail.gmail.com> you wrote:
> >
> > What specifically needs to be done to configure a kernel for use with
> > u-boot?  From the documentation I could only find references to using
> > mkimage to prepare an image (which I've done).
> 
> You must use the raw  kernel  image,  without  the  kernel  bootstrap
> stuff.  And  you  must  make  sure  to  pass the parameters correctly
> (struct bd_info). See also the FAQ at
> http://www.denx.de/twiki/bin/view/DULG/LinuxHangsAfterUncompressingKernel

Do you mean the bootstrap stuff that's wrapped around a vmlinux.gz to
create a zImage, or do you mean arch/ppc/kernel/setup.c and others? 
I'm building the uImage directly from the vmlinux.gz, so I don't have
any of the zImage stuff.

> 
> > but it made no difference.  I could not find anything in the kernel
> > config file related to u-boot for this port.  The file
> 
> This is probably the problem.
> 
> > Documentation/powerpc/mpc52xx.txt in the kernel tree states that a
> > 'make uImage' should build an image bootable by u-boot.  (The Makefile
> > simply calls mkimage for the uImage target)
> 
> This is probably not enough. At least  you  must  make  sure  not  to
> include any bootstrap stuff.

I've got weird stuff happening here now.  With the same uImage I've
now seen three different behavious:
1. (most frequently) get initial setup banners ("id arch", et all). 
Crashes w/ board reset before kernel version banner
2. locks up before printing anything
3. kernel boots fine.

It's looking more like I've got a problem with the hardware
configuration on the Linux side now.  Time to step through init
code....

g.

  reply	other threads:[~2005-04-20 23:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <528646bc0504181457210d8af@mail.gmail.com>
2005-04-19 16:45 ` [U-Boot-Users] Cannot boot from a uImage on the lite5200 Grant Likely
2005-04-19 19:33   ` Wolfgang Denk
2005-04-20 19:54     ` Grant Likely
2005-04-20 20:15       ` Wolfgang Denk
2005-04-20 23:35         ` Grant Likely [this message]
2005-04-21  8:08           ` Wolfgang Denk
2005-04-21 14:58             ` Grant Likely
2005-04-21 19:21               ` Grant Likely

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=528646bc050420163579a4fefd@mail.gmail.com \
    --to=glikely@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox