All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remco Poelstra <remco.poelstra@duran-audio.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problem booting Linux
Date: Thu, 12 Mar 2009 16:11:43 +0100	[thread overview]
Message-ID: <49B9262F.9080802@duran-audio.com> (raw)
In-Reply-To: <49B9224C.6090302@duran-audio.com>

Remco Poelstra schreef:
> Hi all,
> 
> I'm trying to get Linux booting on an ARM7 (NXP LPC2468). I copy the 
> uImage to 0xa1500000 and the romfs.bin to 0xa1800000. I set bootargs to: 
> root=/dev/ram initrd=0xa1800000,4000k console=/dev/ttyS0,115200N8
> When I do 'bootm a1500000', it finds the image and tries to uncompress 
> it, but it goes silent after printing    "Uncompressing Kernel Image ..."
> When I try to create the uImage with
> 'mkimage -A arm -O linux -T kernel -a 0 -e 0 -n "Linux Kernel Image" -d 
> linux.bin uImage', I get the following output (mind the absent -C flag):
> -----------
> Image Name:   Linux Kernel Image
> Created:      Thu Mar 12 15:37:01 2009
> Image Type:   ARM Linux Kernel Image (gzip compressed)
> Data Size:    1986268 Bytes = 1939.71 kB = 1.89 MB
> Load Address: 0x00000000
> Entry Point:  0x00000000
> ---------
> bootm also still thinks that the image is compressed and bootm prints: 
> Uncompressing Kernel Image ... Error: Bad gzipped data
> GUNZIP: uncompress or overwrite error - must RESET board to recover
> 
> How can I make sure that the Linux image can boot?

I just noticed that when I set the load and entry address to 0xa0000000 
(the start address of my external RAM), then bootm prints "starting 
kernel" and then U-boot resets itself twice....
I think I have no idea what's going on here. Is this a problem in my 
U-boot or is it already in the kernel?

Kind regards,

Remco Poelstra

  reply	other threads:[~2009-03-12 15:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12 14:55 [U-Boot] Problem booting Linux Remco Poelstra
2009-03-12 15:11 ` Remco Poelstra [this message]
2009-03-12 18:44   ` Wolfgang Denk
2009-03-12 18:42 ` Wolfgang Denk

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=49B9262F.9080802@duran-audio.com \
    --to=remco.poelstra@duran-audio.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.