AnsweredAssumed Answered


Question asked by samiksha on Nov 2, 2012
Latest reply on Nov 4, 2012 by Aaronwu


I am using cm-bf537e, kernel image and uboot from 2010 toolchain.

I noticed that in the printenv, there is


flashboot=flread 20040000 1000000 300000;bootm 0x1000000


Whereas earlier versions, there was:

flashboot=bootm 0x20040000


Why do we need the extra flread?

I am suspecting that my jffs2 file system is not able to mount because of this.

How can I boot from 0x20040000 directly. I am able to do that in cm-bf561

and that also mounts my file system. but on cm-bf537, if I try bootm 0x20040000,

then it gives the following error:


Hit any key to stop autoboot:  0

## Booting kernel from Legacy Image at 20040000 ...

   Image Name:   Linux Kernel and ext2

   Created:      2012-11-01  18:27:33 UTC

   Image Type:   Blackfin Linux Kernel Image (gzip compressed)

   Data Size:    3061652 Bytes = 2.9 MiB

   Load Address: 00100000

   Entry Point:  002bf670

   Verifying Checksum ... Bad Data CRC

ERROR: can't get kernel image!