[ECOS] [Fwd: How to enable redboots CRC checking]

Mark Salter msalter@redhat.com
Wed May 26 13:00:00 GMT 2004


On Wed, 2004-05-26 at 06:15, Winkler Andreas wrote:

> What i get is
> 
> RedBoot> loa -r -b 0x01008000 jffs2k
> Using default protocol (TFTP)
> Raw file loaded 0x01008000-0x010c27c7, assumed entry at 0x01008000
> RedBoot> fi cr kernel
> ... Erase from 0x50040000-0x50100000: ......
> ... Program from 0x01008000-0x010c27c8 at 0x50040000: ......
> ... Unlock from 0x50fe0000-0x51000000: .
> ... Erase from 0x50fe0000-0x51000000: .
> ... Program from 0x0ffe0000-0x10000000 at 0x50fe0000: .
> ... Lock from 0x50fe0000-0x51000000: .
> RedBoot> fi wr -f 0x50060000 -b 0x1008000 -l 100
> * CAUTION * about to program FLASH
>             at 0x50060000..0x5007ffff from 0x01008000 - continue (y/n)? y
> ... Erase from 0x50060000-0x50080000: .
> ... Program from 0x01008000-0x01028000 at 0x50060000: .
> RedBoot> fi loa kernel
> RedBoot> e
> Using base address 0x01008000 and length 0x000ba7c8
> Uncompressing Linux...........
> 
> invalid compressed format (err=2)
> 
>  -- System halted
> 
> Any idea, what could be my fault?

Could you explain what you are trying to accomplish by the "fi wr"
command above? 

You download the kernel image and write it to flash from 0x50040000
to 0x500fa7c8. Then you write the first 100 bytes of the kernel
image to 0x50060000 which is in the middle of the kernel image you
wrote in the previous step. So of course the kernel decompresses
until it hits the area you corrupted, at which point it complains
about the invalid compressed image.

--Mark


-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss



More information about the Ecos-discuss mailing list