From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] cuImage doesn't boot with u-boot 2009.11 version
Date: Thu, 6 Sep 2012 18:03:42 -0500 [thread overview]
Message-ID: <50492BCE.4070807@freescale.com> (raw)
In-Reply-To: <CAP-kDZU+SU035yNpJR8btjb1cj657Aq_zUPN3Z68Y+pWOduJXA@mail.gmail.com>
On 09/03/2012 01:08 PM, narayanasami vijayaraghavan wrote:
> Hello uboot experts,
> ( I am new to board level debugging. So, please excuse if I am asking any
> basic question).
>
> Is cuImage format supported with u-boot-2009.11 version?
>
> I am running linux 2.6.32 with powerpc P1020 (freescale) board. The board
> has u-boot version 2009.11.
> When I build the uImage and device tree blob separately, it is booting from
> u-boot.
> But, if I build cuImage format, it doesn't boot, and stops at
> "Uncompressing Kernel Image ... OK":
Why are you using cuImage with P1020? cuImage is for old boards with
old U-Boots that don't support device trees.
-Scott
next prev parent reply other threads:[~2012-09-06 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 18:08 [U-Boot] cuImage doesn't boot with u-boot 2009.11 version narayanasami vijayaraghavan
2012-09-06 23:03 ` Scott Wood [this message]
2012-09-07 16:07 ` narayanasami vijayaraghavan
2012-09-07 16:18 ` Scott Wood
2012-09-07 17:32 ` narayanasami vijayaraghavan
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=50492BCE.4070807@freescale.com \
--to=scottwood@freescale.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