• Home
  • Help
  • Search
  • Login
  • Register
Pages: [1]
Author Topic: Bad Data CRC Problem with TFTP boot  (Read 4517 times)
star_trekguy
Newbie
*

Karma: 0
Posts: 10


View Profile
« on: June 07, 2009, 08:14:10 PM »

I just got the PlugPC a few days ago and have been playing around with it since. The first thing I did was to change the root password before updating the Ubuntu install, which I later found out is what you really shouldn't do. I locked myself out.

So now I am attempting to boot the the TFTP/NFS method. I am fairly new with Linux so I had to put a fresh install of Ubuntu on my laptop and install all the TFPT and NFS servers. Its been a rough process of slow trial and error but I have made some progress!

Now that the weekend is coming to an end I have hit another wall. When I boot the PlugPC, I get this error:

Code:
Marvell>> boot
Using egiga0 device
TFTP from server 192.168.1.102; our IP address is 192.168.1.104
Filename '/uImage.sheeva.20090319'.
Load address: 0x200000
Loading: #
done
## Booting image at 00200000 ...
   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

I am not sure if this is a problem with the TFTP and the uImage kernal or if it is with the NFS and the rootfs. I have been using all the stock files from the CD (the uImage, rootfs). I extracted the Linux Host Filesystem - rootfs.tar.bz2 into the /tftpboot folder and pointed the rootpath in u-boot to that folder.

Here are my u-boot variables. I just changed some to beable to easily switch between the nand and the NFS.

Code:
baudrate=115200
loads_echo=0
CASset=min
MALLOC_len=1
ethprime=egiga0
ethmtu=1500
usb0Mode=host
nandEcc=1bit
ethact=egiga0
cesvcid=ULULULULULULPPULULULULULDA
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
autoload=no
run_diag=no
ethaddr=00:50:43:01:C8:49
bootargs_root=root=/dev/nfs rw
image_name=/uImage.sheeva.20090319
bootfile=/uImage.sheeva.20090319
dnsip=68.105.28.11
console=console=ttyS0,115200 mtdparts=nand_flash:0x100000@0x000000(u-boot),0x400000@0x100000(uImage),0x1f800000@0x500000(rootfs)rw
bootargs_end=:::DB88FXX81:eth0:none
loadaddr=0x200000
boottftp=tftpboot $(loadaddr) $(image_name)
bootnand=nand read.e $(loadaddr) 0x00100000 0x00500000
bootargs_nand=root=/dev/mtdblock2 rw
bootargs_tftp=root=/dev/nfs rw nfsroot=$(serverip):$(rootpath)
bootcmd_nand=run bootnand;setenv bootargs $(console) $(bootargs_nand) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm $(loadaddr)
bootcmd_tftp=run boottftp;setenv bootargs $(console) $(bootargs_nfs) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm $(loadaddr)
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=no
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
bootcmd=run boottftp;setenv bootargs $(console) $(bootargs_tftp) ip=$(ipaddr):$(serverip)$(bootargs_end);bootm $(loadaddr)
rootpath=/tftpboot/rootfsv1.0
netmask=255.255.0.0
ipaddr=192.168.1.104
serverip=192.168.1.102
bootargs=console=ttyS0,115200 mtdparts=nand_flash:0x100000@0x000000(u-boot),0x400000@0x100000(uImage),0x1f800000@0x500000(rootfs)rw root=/dev/nfs rw nfsroot=$(serverip):$(rootpath) ip=192.168.1.104:192.168.1.102:::DB88FXX81:eth0:none

Environment size: 2036/131068 bytes

Any help would be appreciated and thank you.
Logged

star_trekguy
Newbie
*

Karma: 0
Posts: 10


View Profile
« Reply #1 on: June 10, 2009, 03:37:31 PM »

I've seen a few other posts around here with this load screen and it seems like there is normally more # after the loading. Does this mean it is not loading the whole image or something?
Logged

prafulla
Global Moderator
Newbie
*****

Karma: 0
Posts: 21


View Profile
« Reply #2 on: June 11, 2009, 12:56:38 AM »

Hi,
in you tftp log you mentioned file name as "/uImage....." do you need "/" there or it is typo mistake?
Secondly the tftp download log just below it indicates it has not downloaded complete ketnel file (just on #) this indicates either the file you are refering is invalid or "/" createing some problem...

Last but not least, tftp download address in the log is 0x200000, this is u-boot code base address,  please use it always greated than 0x400000, ex: tftp 0x6400000 <uImage...>

thats what I can smell from the log.
Hope it will help you.

Regards..
Prafulla . .
Logged

star_trekguy
Newbie
*

Karma: 0
Posts: 10


View Profile
« Reply #3 on: June 14, 2009, 03:21:25 PM »

I figured out the problem I was having! It was a problem with my tftp server. It was looking to a folder /var/lib/tftpboot which had a uImage file, but no meat to it (0 kb). now the kernel is booting.

To answer some of your comments, I guess the "/uImage" doesn't really matter if the / is there or not. Also, I guess the console variable set the memory spaces up so that 0x200000 is the uImage space and the u-boot space is from 0x000000 - 0x100000.

I might have another problem with the NFS server now, but I'll start another thread for that.

Thanks for your help!!
Logged

Pages: [1]
Print
Jump to: