From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anatolij Gustschin <agust@denx.de>
Date: Wed, 7 Dec 2011 20:58:57 +0100
Subject: [U-Boot] How to test a new u-boot image over network?
In-Reply-To: <629D989C137DD040A0A994BD21888F1E75E81D17@MX29A.corp.emc.com>
References: <629D989C137DD040A0A994BD21888F1E75E81D17@MX29A.corp.emc.com>
Message-ID: <20111207205857.786ffaca@wker>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi,

On Wed, 7 Dec 2011 12:41:38 -0500
<vikas.sontakke@emc.com> wrote:
...
> 
> uboot-sources-EMC/u-boot-2009.01> file u-boot.bin
> u-boot.bin: u-boot/PPCBoot image
> 
> uboot-sources-EMC/u-boot-2009.01> mkimage -d u-boot.bin u-boot.bin.load
> Image Name:
> Created:      Wed Dec  7 12:08:45 2011
> Image Type:   PowerPC Linux Kernel Image (gzip compressed)
> Data Size:    393216 Bytes = 384.00 kB = 0.38 MB
> Load Address: 0x00000000
> Entry Point:  0x00000000
> uboot-sources-EMC/u-boot-2009.01>
> 
> 
> I then tftp the image "u-boot.bin.load" and bootm it but I am getting following error.
> Error: Bad gzipped data
> GUNZIP: uncompress or overwrite error - must RESET board to recover

Did you read the documentation? Why are you trying to
boot U-Boot image using 'bootm' command? 'bootm' command is
used for booting operating system images.

If you want to update U-Boot on the board, you need to write
it into the flash memory used for booting. Do you have a
JTAG debugger for the case updating U-Boot image goes wrong
for some reason?

> I have tried many different load addresses such as 0x40.0000,
> 0x400.0000, 0x800.0000, 0x1000.0000.  with exactly the same
> behaviour.  What am I missing?

Please read U-Boot documentation [1] to understand which
command is used for which purpose. Updating U-Boot is
also described in the U-Boot documentation.

HTH,
Anatolij

[1] http://www.denx.de/wiki/view/DULG/UBoot