[U-Boot-Users] Re: u-boot error message

[Detlev Zundel]

Hi Bruce,

>     Hello Detlev Zundel ,
>
>
>     I used u-boot-1.1.1 to boot linux.My target board is ALTERA DK1C20 and cpu
>     is nios.I used tools/mkimage to encapsulate a linux kernel image with
>     header information.But it display some error messages,it like that:

First off - I am not the best person to answer these questions, as I
have never used a NIOS system.  So please try to get help on the
mailing list that I cc'ed my last reply to.  Someone there should be
able to have better answers to your questions.

One more thing though - from your description I am not sure what
version of U-Boot you are using and whether you were able _at all_ to
boot Linux on your system.  The error messages below strongly leave me
to not believe this.

>     Index: tools/mkimage.c
>
>     ===================================================================
>
>     RCS file: /cvsroot/u-boot/u-boot/tools/mkimage.c,v
>
>     retrieving revision 1.13
>
>     diff -p -u -r1.13 mkimage.c
>
>     --- tools/mkimage.c    10 Jul 2004 22:36:01 -0000     1.13
>
>     +++ tools/mkimage.c    29 Oct 2004 00:01:12 -0000
>
>     @@ -86,6 +86,8 @@ table_entry_t arch_name[] = {
>
>          {  IH_CPU_MICROBLAZE,     "microblaze",  "MicroBlaze",  },
>
>          {  IH_CPU_MIPS,           "mips",        "MIPS",        },
>
>          {  IH_CPU_MIPS64,         "mips64",      "MIPS 64 Bit", },
>
>     +    {   IH_CPU_NIOS,            "nios",         "NIOS",         },
>
>          {  IH_CPU_PPC,            "ppc",         "PowerPC",     },
>
>          {  IH_CPU_S390,           "s390",        "IBM S390",    },
>
>          {  IH_CPU_SH,      "sh",       "SuperH",   },

Why did you remove the other line from my patch?  Obviously this is
the patch I suggested and the second line was in there because I have
seen that there is still another CPU type not implemented yet in
mkimage so one should try to fix this in one go.  It does _not make
sense_ to throw out such things after the work it has taken to put
them in.

>     When I boot linux image to my target board, it have error messages.
>
>     Like that:
>
>      
>
>     DK1C20 > imi 200000
>
>      
>
>     ## Checking Image at 00200000 ...
>
>        Image Name:   linux kernel
>
>        Image Type:   Unknown Architecture Linux Kernel Image (uncompressed)
>
>        Data Size:    1015552 Bytes = 991.8 kB
>
>        Load Address: 01010000
>
>        Entry Point:  01010000
>
>        Verifying Checksum ... OK
>

As you know from studying cmd_bootm.c the imi command _does not_ check
the compression type.  The image type shows uncompressed so mkimage
should have put a 0 in the compression type field.

>     DK1C20 > bootm 200000
>
>     ## Booting image at 00200000 ...
>
>        Image Name:   linux kernel
>
>        Image Type:   Unknown Architecture Linux Kernel Image (uncompressed)
>
>        Data Size:    1015552 Bytes = 991.8 kB
>
>        Load Address: 01010000
>
>        Entry Point:  01010000
>
>        Verifying Checksum ... OK
>
>     Unimplemented compression type 39
>
>     DK1C20 >

Yep, there are compression type 0, 1 and 2 but nothing else.
According to what I wrote above the compression field is boguos.  Of
course you noticed reading the source for mkimage that it should have
put a 0 in it and now theres a 39 in there.  It looks like the image
is corrupt for whatever reason - try using the debugger and a hexdump
program to find out at what stage this goes wrong.

And of course use U-Boot from CVS and _not_ U-Boot 1.1.1

Cheers
  Detlev

PS: Mail f'up-to set _again_ to u-boot-users at lists.sourceforge.net.
    You know of course from the netiquette, that it is considered rude
    behaviour to ignore such hints repeatedly, don't you?

-- 
(define Y (lambda (f)
	    ((lambda (g) (f (lambda (x) ((g g) x))))
	     (lambda (g) (f (lambda (x) ((g g) x)))))))