[ELDK] reset command eventually produces "Bad Magic Number"

Snyder, James (jsnyde07) jsnyde07 at harris.com
Tue Nov 23 18:54:17 CET 2010

Thanks for the quick reply Stefano.

I actually came across the "iminfo" command and ran it against both
memory locations:

=> iminfo 0xFF000000

## Checking Image at ff000000 ...
   Image Name:   Linux-2.6.37-rc1-00171-gfd642d1-
   Created:      2010-11-24  12:16:54 UTC
   Image Type:   PowerPC Linux Kernel Image (gzip compressed)
   Data Size:    1544455 Bytes =  1.5 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
=> iminfo 0xFF2A0000

## Checking Image at ff2a0000 ...
   Bad Magic Number

Would this confirm your suspicion of the need to upgrade the u-boot?


-----Original Message-----
From: Stefano Babic [mailto:sbabic at denx.de] 
Sent: Tuesday, November 23, 2010 12:31 PM
To: Snyder, James (jsnyde07)
Cc: eldk at lists.denx.de
Subject: Re: [ELDK] reset command eventually produces "Bad Magic Number"

On 11/23/2010 05:36 PM, Snyder, James (jsnyde07) wrote:
> Hello,


> U-Boot 1.1.6 (Aug 25 2010 - 16:37:50)
> CPU:   AMCC PowerPC 440EPx Rev. A at 533.333 MHz (PLB=133, OPB=66,
> EBC=66 MHz)
>        Security/Kasumi support
>        I2C boot EEPROM enabled
>        Bootstrap Option G - Boot ROM Location I2C (Addr 0x54)
>        32 kB I-Cache 32 kB D-Cache

I am wondering if a so old u-boot is able to boot a kernel with the
device tree. I am unsure, but I think that FDT support was added in a
later version. You should update u-boot, or try generating cuImage.dtb
instead of uImage. Really it should be better to update U-Boot...

Best regards,
Stefano Babic

DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office at denx.de

More information about the eldk mailing list