2010-10-13 15:28:57 Bad data CRC/Can't get kernel image
T. Jump (UNITED STATES)
I've read several posts on this topic (as I am having this issue). I've reviewed TFTP server issues and checks but I'm not having success checking the file sizes with crc commands on my BF537 platform. Also I'm not having success running cksum or md5sum on the pc side as it just seems to process forever and never return any data.
I also saw a post on a patch (see here... blackfin.uclinux.org/gf/project/u-boot/scmsvn/?action=browse&path=/&view=rev) but I'm not sure whether this applies to my particular situation or if the u-boot.ldr I'm using already has the patch applied.
Here is the return I'm getting:
EEPROM @0x0 read: addr 01000000 off 30000 count 2097152 ... done
## Booting kernel from Legacy Image at 01000000 ...
Image Name: Linux-18.104.22.168-ADI-2009R1.1-svn
Created: 2010-10-09 15:31:21 UTC
Image Type: Blackfin Linux Kernel Image (gzip compressed)
Data Size: 2042983 Bytes = 1.9 MB
Load Address: 00400000
Entry Point: 005b71c0
Verifying Checksum ... Bad Data CRC
ERROR: can't get kernel image!
Help is appreciated.
2010-10-13 17:39:43 Re: Bad data CRC/Can't get kernel image
Mike Frysinger (UNITED STATES)
the eeprom code is long dead. we use the spi flash sub system now: