2010-08-25 22:42:18     BF548 NFS Loading

Document created by Aaronwu Employee on Sep 25, 2013
Version 1Show Document
  • View in full screen mode

2010-08-25 22:42:18     BF548 NFS Loading

Simon Brewer (AUSTRALIA)

Message: 92772   

 

I am using the BF548 Ezkit and have loaded a uBoot image into parallel flash.  That is working fine, but when I try using nfs it does not work correctly.

 

I am using the latest uboot snapshot. (22 August)

 

bfin> nfs 10.122.9.114:/home/sbrewer/Blackfin/uboot/u-boot-bf548-ezkit-2010R1-pre.elf

smc911x: detected LAN9218 controller

smc911x: phy initialized

smc911x: MAC 00:e0:22:fe:bb:d8

Using smc911x-0 device

File transfer via NFS from server 10.122.9.114; our IP address is 10.122.9.159; sending through gateway 192.168.0.1

Filename '/home/sbrewer/Blackfin/uboot/u-boot-bf548-ezkit-2010R1-pre.elf'.

Load address: 0x1000000

Loading: T T *** ERROR: Cannot mount

T T T *** ERROR: Cannot umount

 

 

Running tcpdump on the host side, I am seeing the following.  The host is reporting a bad UDP checksum.

 

    10.122.9.114.111 > 10.122.9.159.1000: [bad udp cksum 8e5!] UDP, length 28

12:30:34.766655 IP (tos 0x0, ttl 255, id 7, offset 0, flags [DF], proto UDP (17), length 84)

    10.122.9.159.1000 > 10.122.9.114.111: [no cksum] UDP, length 56

12:30:34.766761 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 56)

    10.122.9.114.111 > 10.122.9.159.1000: [bad udp cksum 7a3!] UDP, length 28

12:30:34.766869 IP (tos 0x0, ttl 255, id 8, offset 0, flags [DF], proto UDP (17), length 120)

    10.122.9.159.1000 > 10.122.9.114.50688: [no cksum] UDP, length 92

12:30:36.766529 IP (tos 0x0, ttl 255, id 9, offset 0, flags [DF], proto UDP (17), length 120)

 

 

Any ideas on how to make nfs work?

QuoteReplyEditDelete

 

 

2010-08-25 23:07:02     Re: BF548 NFS Loading

Mike Frysinger (UNITED STATES)

Message: 92776   

 

that "sending through gateway 192.168.0.1" shouldnt really be there.  what is your netmask set to ?

 

seems to work on my bf548-ezkit OK:

gatewayip=192.168.0.1

netmask=255.255.255.0

ipaddr=192.168.1.15

serverip=192.168.1.2

 

bfin> nfs 192.168.1.2:/tftpboot/u-boot.bin

smc911x: detected LAN9218 controller

smc911x: phy initialized

smc911x: MAC 00:e0:22:fe:e1:01

Using smc911x-0 device

File transfer via NFS from server 192.168.1.2; our IP address is 192.168.1.15

Filename '/tftpboot/u-boot.bin'.

Load address: 0x1000000

Loading: ########################################################

done

Bytes transferred = 283068 (451bc hex)

bfin>

 

also, you've made sure that that NFS path is accessible from another Linux machine right ?

 

usually people load new images via tftp since it is a lot simpler to setup & maintain than nfs.  plus, why are you loading the u-boot ELF ?  that isnt meant for usage on the board since it contains a lot of extraneous cruft.  the board generally uses a bin or ldr.

QuoteReplyEditDelete

 

 

2010-08-26 00:21:06     Re: BF548 NFS Loading

Simon Brewer (AUSTRALIA)

Message: 92778   

 

I found the problem.  It was a nfs issue as you guessed.  I was sure I had tested nfs, but I had played with some settings and had broken it in the mean time.

 

I was loading the ELF image just as a test to get nfs working.  I prefer NFS because I share my whole development tree.

 

Thanks for the suggestions.

Attachments

    Outcomes