public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@mvista.com>
To: Chetan Kapoor <chetan.kapoor@flextronicssoftware.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Kernel Boot Problem - OMAP 730 P2 - v2.6.9-rc1-omap1
Date: Fri, 21 Apr 2006 09:32:29 -0700	[thread overview]
Message-ID: <4449091D.2030009@mvista.com> (raw)
In-Reply-To: <OFB11CB3E7.FA5ED181-ON65257157.002A9E00-65257157.002C2D03@flextronicssoftware.com>

Chetan Kapoor wrote:
> Hello
> 
> Thanks for the reply.
> 
> Yes, we tried out downloading the zImage to the SDRAM & executing it using 
> 'go' command. And, we did get the kernel boot traces on the terminal. 

This is expeted.  u-boot doesn't pass bootargs when using 'go', only 'bootm'

> the uImage still doesn't seem to execute. uImage was created using the 
> mkimage utility. The command issued (on the development host) to create 
> uImage is:
> 
> mkimage -n 'Linux Kernel Image 2.6.9-rc1-omap1' -A arm -O linux -T kernel 
> -C none -a 0x10008000 -e 0x10008000 -d zImage uImage

You can also use 'make uImage' in the kernel source.  I've done a 'make uImage' 
with the latest git tree.  You can also grab the resultant uImage from 
ftp://hilman.org/omap730/uImage-2.6.16-rc5-omap1 to test on your board.

You might try updating your u-boot.  The version on my board (rev4) is 1.1.4. 
There should be a newer u-boot available on linux.omap.com (which is currently 
down.)

Kevin

  reply	other threads:[~2006-04-21 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-20 14:42 Kernel Boot Problem - OMAP 730 P2 - v2.6.9-rc1-omap1 Chetan Kapoor
2006-04-20 18:17 ` Kevin Hilman
2006-04-21  7:25 ` Qi
2006-04-21  8:02   ` Chetan Kapoor
2006-04-21 16:32     ` Kevin Hilman [this message]
2006-04-23 11:52       ` Chetan Kapoor
2006-04-21 16:43     ` Qi
2006-04-21  9:42 ` dk_cheng79

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=4449091D.2030009@mvista.com \
    --to=khilman@mvista.com \
    --cc=chetan.kapoor@flextronicssoftware.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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