Bad Data CRC on booting from SD or NAND

[oliphaunt]

Hello,

I recently bought two SheevaPlugs from Globalscale.  After bad luck on the first plug with debian installer (8 attempts without success so far) and SheevaPlug Installer (it segfaulted on me), I decided to give that plug a break and start from scratch with the new one.

The SheevaPlug installer had caused the first plug to be unbootable, so I decided to follow the procedure at http://www.openplug.org/plugwiki/index.php/SD_Card_As_Root_File_System.  It all went very smoothly and I managed to boot from the SD card.  But then, upon reboot, I got an error:

Code:

NAND read: device 0 offset 0x100000, size 0x400000

Reading data from 0x4ff800 -- 100% complete.
 4194304 bytes read: OK
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.22.18
   Created:      2009-03-19   9:18:16 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2106696 Bytes =  2 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

Never mind, I thought, I'll just fall back to the NAND and boot from that. But that gives literally the same error.

So now, unfortunately, I have two plugs that for the moment I can't do anything with.  I could try and update the uboot on this second plug, because I've left it at the original version: U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16
But I can't understand why I couldn't fall back to the NAND.  Any explanations?  Suggestions?

Thanks!

[dtk]

Hey there,

I could try and update the uboot on this second plug, because I've left it at the original version: U-Boot 1.1.4 (Mar 19 2009 - 16:06:59) Marvell version: 3.4.16

Actually, I got the same error (except that my size is 0x200000) _after_ updating u-boot to 'U-Boot 3.4.27+pingtoo binary'. Downgraded to 3.4.19, didn't help, though.

Did you make any progress on this issue?

tia
dtk

[oliphaunt]

Hi, thanks for replying.  No, no progress on this issue.  I decided to give it a rest (I had no idea what to do anyway) and follow the Debian Lenny tarball approach.  That worked pretty smoothly and I soon wound up with a working Debian system on SD.

However I then quickly ran into problems where the process mmcqd would eat up neary 100% of processor capacity, which has also been described on this forum.  I'm hoping that installing flashybrid will cure that.  It seems at least that running from SD is not as robust as it is from NAND or an external HD.