• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Sheevaplug: Verifying Checksum ... Bad Data CRC  (Read 6963 times)
MattB
Newbie
*

Karma: 0
Posts: 10


View Profile
« on: October 14, 2009, 04:53:01 AM »

Hi Everyone,

Just to warn everyone, having only been introduced to Linux within the last 2 years, and coming to the plug from the NSLU2, which (at least at the moment) seems a bit simpler, I am very much a beginner with this type of thing, so please be patient!

I bought a Sheevaplug from New IT off eBay the other day, and it arrived yesterday. My NSLU2 has been overloaded beyond belief and it is just too slow, so I was looking for something with a bit more grunt to act as a home server running things like CUPS, Transmission, Samba, Apache and maybe a webcam.

I was worried about the relatively small amount of space on the plug when it arrived. I decided to move the root file system to an SD card I had (Sandisk 4Gb card) so I followed the guide on the wiki here.

When I got to the part to do with UBoot, as per the guide, I changed the bootargs using the command (I did check that my bootargs were initially set the same as those in the guide, and they were, so I thought it would be fine):

Code:
setenv bootargs console=ttyS0,115200 root=/dev/mmcblk0p1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none
And then checked it using printenv bootargs. All looked well, so I typed 'boot' and the plug booted. I watched it boot, and a couple of [failed] notices came up, but Debian (mine has Debian on it as standard? I am not sure) booted, I logged ina dn all was fine. I also SSHd in to prove to myself that it wasn't broken. All worked well.

I then repeated the process (shut down, got into UBoot, setenv bootargs etc) and included saveenv at the end, as I figured the changes I made were good.

That seemed to go well. Then I typed 'boot'. I got this:

Code:
Marvell>> boot
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

This seems to happen without fail every time I turn it on. I tried setting the bootargs back to what I had originally, with this line:

Code:
setenv bootargs console=ttyS0,115200 mtdparts=nand_mtd:0x400000@0x100000(uImage),0x1fb00000@0x500000(rootfs) rw root=/dev/mtdblock1 rw ip=10.4.50.4:10.4.50.5:10.4.50.5:255.255.255.0:DB88FXX81:eth0:none

But it still does the same thing upon boot.

So I have a couple of questions - first of all - did I go wrong anywhere obvious? I would love to fully understand what caused this, as well as how to fix it.

Second - how can I fix it? I have found a couple of other threads which sound similar, and they suggested restoring via USB - so this would mean following these instructions?

I would be grateful for any help anyone can offer - as I say, I am a bit of a newbie, but eager to learn from my mistakes!

Thanks,

Matt
« Last Edit: October 14, 2009, 04:55:10 AM by MattB » Logged

MattB
Newbie
*

Karma: 0
Posts: 10


View Profile
« Reply #1 on: October 14, 2009, 02:32:26 PM »

OK! So thanks to the instructions on the wiki and in the README, I have managed to reflash the plug with Sheevaplug Installer 1.0. I had quite a lot of hurdles to jump while I was trying to get it to work, but I think a lot of it stemmed from my inexperience with almost all aspects of the process.

In case it helps anyone else, I bought my Sheevaplug from New IT in the UK, and I did not need to change the vid and pid in the conf file (in fact, as it mentioned 'newer plugs', I changed them and it didn't work, so i had to change them back) to run the installer. I tried it on my girlfriends Vista laptop, but it was much easier to do everything on my Ubuntu box. I (stupidly) kept trying to connect to ttyUSB0 to see the console, then realised the port I wanted was ttyUSB1. Once I realised all the mistakes I was making, it went great!

But all good news - it works again. I will no doubt try and move the rootfs to the sd card again sometime, but for the moment I'll stick with 512Mb and see what I can do.
Logged

birdman
Sr. Member
****

Karma: 4
Posts: 429


View Profile WWW
« Reply #2 on: October 14, 2009, 03:16:10 PM »

But all good news - it works again. I will no doubt try and move the rootfs to the sd card again sometime, but for the moment I'll stick with 512Mb and see what I can do.
When you do switch to moving the rootfs to SD you'll need to have an mmcinit command in you boot command (it's absent from what you posted above).
I've set mine to boot from SD too.  The SD card has /boot (first partition, small). / (second partition - 4GB), swap (500MB) and /local (~11GB - where all of my stuff goes).  The advantage of this is that kernel updates (which get posted here) just involve:
  • unpack the modules to get /lib/modules/2.6.xx.x
  • copy the sheeva-2.6.xx.x-uImage to /boot and hard-link it to uImage (what my boot command expects)
  • reboot
No flashing required.
Logged

MattB
Newbie
*

Karma: 0
Posts: 10


View Profile
« Reply #3 on: October 15, 2009, 01:04:44 AM »

Hi birdman,

Thank you for the advice. Actually, just after I posted that reply, I read this.

So I changed my bootargs_root to match that, and now it boots from the SD card no worries. Good times! Funny how some nights I can get anything to work for the life of me, and then other nights I'm on a roll.

Thanks,

Matt
Logged

Caesar
Newbie
*

Karma: 0
Posts: 4


View Profile
« Reply #4 on: January 30, 2010, 03:22:05 AM »

Hi MattB,

I read your last post very carefully, read also the topic: 'Boot from SDcard with Alpha 6' and the HowTo: 'SD Card As Root File System', but my trys always fails....

My SheevaPlug has now UBOOT version 3.4.24 but every SD Card I used for debian installation via tar ball or debian installer stopps in reading uImage from SD Card.

output:
         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: SHEEVA PLUG LE

U-Boot 1.1.4 (Nov 10 2009 - 11:35:01) Marvell version: 3.4.24

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
SDHC found. Card desciption is:
Manufacturer:       0x03, OEM "\x83h"
Product name:       "  \x00\x00\x00", revision 8.5
Serial number:      618
Manufacturing date: 4/2009
CRC:                0x00, b0 = 0

2729104 bytes read

1811960 bytes read
## Booting image at 00400000 ...
   Image Name:   Debian kernel
   Created:      2010-01-29  23:47:11 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1811896 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC
Marvell>>


The same installation procedure works fine with USB memory, but I want to use SD Card to have USB free to connect HDs.

My question: What might be wrong? I followed Martin Michlmayrs HowTos and did'nt wrote the command manually - I copied to avoid big-finger-errors - but I have'nt  success.

I hope anyone read this old thread....

Thanks,

Caesar
Logged

Caesar
Newbie
*

Karma: 0
Posts: 4


View Profile
« Reply #5 on: January 30, 2010, 04:28:57 AM »

I did it!

The only working advise was http://plugcomputer.org/plugforum/index.php?topic=968.0!

@Martin Michlmayr: Please correct your link to the uboot version 3.4.23 on http://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade.html - yesterday there was version 3.4.24 in http://plugcomputer.org/plugforum/index.php?action=dlattach;topic=921.0;attach=153 - this uboot versio don't works with SD Card

Thanks all readers!

Caesar
Logged

tbm
Full Member
***

Karma: 7
Posts: 121



View Profile WWW
« Reply #6 on: January 31, 2010, 02:00:47 AM »

Fixed, thanks.
Logged

Tamadite
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #7 on: May 01, 2010, 04:45:11 PM »

I'm guess I'm missing something somewhere, but I can't get it... I'm also getting "Bad Data CRC" message when booting from USB.

I have tried uboot versions 19, 23 and 24 but does not help.

Code:
U-Boot 1.1.4 (Nov  4 2009 - 12:58:36) Marvell version: 3.4.23

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6281 A0 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM CS[1] base 0x10000000   size 256MB
DRAM Total size 512MB  16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:512 MB
Flash:  0 kB

CPU : Marvell Feroceon (Rev 1)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
.
.........................
........[...]...
.

4480111 bytes read
.
.........................
.........................
.........................
.........................
.........................
.........................
......................

1820384 bytes read
## Booting image at 00800000 ...
   Image Name:   Debian kernel
   Created:      2009-11-23  17:25:02 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1820320 Bytes =  1.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... Bad Data CRC

Variables:
Code:
Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
run_diag=yes
console=a0000
e=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x1ff00000@0x100000(root)
CASset=min
MALLOC_len=1
ethprime=egiga0
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
ethaddr=00:50:43:00:27:02
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
nandEcc=1bit
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
ethact=egiga0
bootargs_console=console=ttyS0,115200
bootcmd_usb=usb start; ext2load usb 0:1 0x01100000 /uInitrd; ext2load usb 0:1 0x00800000 /uImage
bootcmd=setenv bootargs $(bootargs_console) $(bootargs_root); run bootcmd_usb; bootm 0x00800000 0x01100000
arcNumber=2097
bootargs_root=root=/dev/sda2 rootdelay=10
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=a0000
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
bootdelay=3
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
bootargs=console=ttyS0,115200 root=/dev/sda2 rootdelay=10
filesize=1BC6E0

Environment size: 1446/131068 bytes

Any idea?
Logged

Tamadite
Newbie
*

Karma: 0
Posts: 6


View Profile
« Reply #8 on: May 02, 2010, 02:21:24 AM »

SOLVED!

It seems files uImage and uInitrd included in base.tar.bz2 I downloaded from http://www.cyrius.com/debian/kirkwood/sheevaplug/unpack.html have wrong md5.

Fix found in http://plugcomputer.org/plugforum/index.php?topic=1505.msg9287#msg9287
Logged

Pages: [1]
Print
Jump to: