Thank you Phil and Chris,
I followed your suggestions to do the test. First I changed INTERFACES="eth1"
in
/etc/default/dhcp3-server
Then, I linked the ethernet cable from my board to LAN 1 port on router box,
and RS232 cable with my laptop. Before power up the board I tested the
local NFS as the first step
mkdir /mnt/nfsmount -t nfs 192.168.1.207:/home/zyang1/workdir/filesys /mnt/nfs
I can see the subdirs and files in the originally empty /mnt/nfs subdir. It
seems the
NFS is locally working
I then power up the board and try the second step
After break into the board command line EVM #, I entered,
DM355 EVM # setenv nfshost 192.168.1.207
DM355 EVM # setenv rootpath /home/zyang1/workdir/filesys
DM355 EVM # setenv bootargs console=ttyS0,115200n8 noinitrd rw
ip=192.168.1.199:192.168.1\.207:192.168.1.1:255.255.255.0:::off root=/dev/nfs
nfsroot=192.168.1.207:/home/zyang1/workdir\/filesys,nolock mem=116M
Here I try to set a static IP address 192.168.1.199 to the board. I use two
line wraps at the end of two lines and the next character starts at the
beginning of the next line.
I then typed bdinfo to check, and find,
DM355 EVM # bdinfo
arch_number = 0x00000565
env_t = 0x00000000
boot_params = 0x80000100
DRAM bank = 0x00000000
-> start = 0x80000000
-> size = 0x08000000
ethaddr = 00:0E:99:02:C2:1A
ip_addr = 0.0.0.0
baudrate = 115200 bps
So the board does not get an IP address as expected. I boot it with boot
command, get,
DM355 EVM # boot
Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
Image Name: Linux-2.6.10_mvl401
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1585240 Bytes = 1.5 MB
Load Address: 80008000
Entry Point: 80008000
Same as before. Then I find that /dev does not have a subdir of nfs, so I
created one, and do
mount -t nfs 192.168.1.207:/home/zyang1/workdir/filesys /dev/nfs
Now the /dev/nfs has the shared subdir and files.
I repeated the whole process but still got the same result. Any more
suggestions?
Thanks.
Michael
Subject: RE: problems on testing the shared file system
Date: Mon, 28 Apr 2008 08:56:38 +0100
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]; [email protected]
Hi,
your INTERFACES=eth0 should be
INTERFACES=eth1
The laptop has associated with the router via eth1,
hence the IP address of eth1 is in the range you are trying to set up DHCP for.
Your eth0 interface has no IP address.
You will need to plug the DM355 into the router and not
eth0. If you want to use eth0 for the DM355 you will need a switch, using cross
over cables can cause problems with the link coming up at all. Then you will
have to set the address on eth0 manually.
(Mmm - just a thought - if you did plug the DM355 into
the router, won't it get an IP address from there.)
I would try to fix this in 2
stages...
First: test your NFS server by mounting the exported
filesystem locally....
As root (changing IP address to suit yours) - note your
IP address is NOT 77.97.207.254 (I assume this is the public IP address of your
router - I am not sure why you thought we neded to know this). It needs to be
the IP address of one of the interfaces on your laptop, preferably the eth1 as
this seems to be your LAN address.
mkdir /mnt/nfs
mount -t nfs 172.18.1.49:/share/path
/mnt/nfs
This must work before it will ever work to a remote
board. You should then be able to see files under /mnt/nfs, the usual 'bin boot
dev etc home...'
Second: On the DM355 end, try setting the ip
address statically, instead of ip=dhcp in the 'bootargs' variable
something like...
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
Example:
ip=172.18.1.222:172.18.1.49:172.18.0.254:255.255.0.0:::off
This will force the IP address so you won't need DHCP
at all. You need to turn off the 'autoconf' variable - hence the final 'off'.
If
you don't it will still try to DHCP. The hostname & device sections are not
required but must be specified (as NULL, hence the ':::').
Then try booting the board...post the console output if
it fails.
Regards
Phil Q
Phil Quiney, Senior Software
Engineer
Trinity Convergence
Cambridge Business Park
Cowley Road
Cambridge CB4 0WZ, UK
T:
+44(0)1223-435536
F: +44(0)1223-435560
www.trinityconvergence.com
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
YangZhijun
Sent: 27 April 2008 22:28
To:
[email protected]
Subject: problems on
testing the shared file system
Hi Folks,
I still have some problems on testing my shared file
system in my laptop with the DVEVM355 board. I think Spectrum's getting started
guide for DM355 DVEVM is insufficient for a newbie to get start, especially in
a
different linux distribution like my case of Ubuntu. Now I list all the
procedure I used from the very start, and hope you can help.
I first
installed NSF in my laptop as follows,
sudo apt-get install
nfs-kernel-server nfs-common portmap
Then I followed the getting started
guide 4.3.4 to export a shared file system for target access.
After
installing NFS, and before I tried to set up DHCP server in my laptop, I use
/sbin/ifconfig,
--------------------------------------------------------------------------------------
[EMAIL PROTECTED]:~$
/sbin/ifconfig
eth0 Link encap:Ethernet
HWaddr 00:1C:23:3C:75:E4
UP BROADCAST!
MULTICAST MTU:1500
Metric:1
RX packets:0
errors:0 dropped:0 overruns:0
frame:0
TX packets:0
errors:0 dropped:0 overruns:0
carrier:0
collisions:0
txqueuelen:1000
RX
bytes:0 (0.0 b) TX bytes:0 (0.0
b)
Interrupt:18
eth1 Link encap:Ethernet HWaddr
00:1F:3C:13:88:D6
inet
addr:192.168.1.207 Bcast:192.168.1.255
Mask:255.255.255.0
inet6 addr: fe80::21f:3cff:fe13:88d6/64
Scope:Link
UP
BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
&!
nbsp; RX packets:53423 errors:26
dropped:401 overruns:0
frame:0
TX
packets:39067 errors:0 dropped:0 overruns:0
carrier:0
collisions:0
txqueuelen:1000
RX
bytes:49489243 (47.1 MiB) TX bytes:5500038 (5.2
MiB)
Interrupt:17 Base
address:0x8000 Memory:efdff000-efdfffff
eth0:avah Link
encap:Ethernet HWaddr 00:1C:23:3C:75:E4
inet
addr:169.254.7.95 Bcast:169.254.255.255
Mask:255.255.0.0
UP
BROADCAST MULTICAST MTU:1500
Metric:1
Interrupt:18
lo Link encap:Local
Loopback
! ;
inet addr:127.0.0.1
Mask:255.0.0.0
inet6
addr: ::1/128
Scope:Host
UP LOOPBACK
RUNNING MTU:16436
Metric:1
RX packets:93
errors:0 dropped:0 overruns:0
frame:0
TX packets:93
errors:0 dropped:0 overruns:0
carrier:0
collisions:0
txqueuelen:0
RX
bytes:7156 (6.9 KiB) TX bytes:7156 (6.9
KiB)
-----------------------------------------------------------------------------------------------
I
can see that eth0 is the interface for network card and eth1 my wireless. I
then
use,
sudo apt-get install dhcp3-server
I get the following lines,
---------------------------!
--------------------------
[EMAIL PROTECTED]:~$ sudo apt-get install dhc
p3-server
Password:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed
dhcp3-server
0 upgraded, 1 newly installed, 0 to remove and 196 not upgraded.
Need to get 302kB of archives.
After unpacking 856kB of additional disk space will be used.
Get: 1 http://gb.archive.ubuntu.com feisty/main dhcp3-server 3.0.4-12ubuntu4
[302kB]
Fetched 302kB in 8s (37.2kB/s)
Preconfiguring packages ...
Selecting previously deselected package dhcp3-server.
(Reading database ... 88186 files an!
d directories currently installed.)
Unpacking dhcp3-server (from .../dhcp3-server_3.0.4-12ubuntu4_i386.deb) ...
Setting up dhcp3-server (3.0.4-12ubuntu4) ...
Generating /etc/default/dhcp3-server...
* Starting DHCP server dhcpd3 [fail]
invoke-rc.d: initscript dhcp3-server, action "start" failed.
-----------------------------------------------------------------
I then do,
sudo gedit /etc/default/dhcp3-server
I find INTERFACES="", and replace it with INTERFACES="eth0"
Then,
sudo gedit /etc/dhcp3/dhcpd.conf
In which I comment out the following,
----------------------------------------------------------------
option domain-name "example.or!
g";
option domain-name-servers ns1.example.org, ns2.example.org;
default-lease-time 600;
max-lease-time 7200;
-----------------------------------------------------------------
and find this section,
----------------------------------------------------------
...
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
...
-----------------------------------------------------------
Replace it with,
-----------------------------------------------------------------
# A slightly different configuration for an internal subnet.
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.100 192.168.1.200;
option domain-name-servers 194.168.4.33, 194.168.4.237;
# opti!
on domain-name "internal.example.org";
option routers 192.168.1.1;
option broadcast-address 192.168.1.255;
default-lease-time 600;
max-lease-time 7200;
}
-----------------------------------------------------------------
Then I use,
sudo /etc/init.d/dhcp3-server restart
But I get,
-------------------------------------------------------------------------------
* Stopping DHCP server dhcpd3 [fail]
* Starting DHCP server dhcpd3 [fail]
-------------------------------------------------------------------------------
Obviously the DHCP server in my laptop is not successfully installed. I am a
former blueyonder.co.uk, now the virginmedia broadband user. My wireless router
is 3COM OfficeConnect wireless 11g cable/DSL router (I think the wireless
router box is also my real DHCP server). I also find, through google,!
that my ip address is 77.97.207.254, the virgin media domain name
server is
ns4.virginmedia.net, ns2.virginmedia.net, then by ping them I got their IP
addresses and use them in the subnet block above. I comment out the
domain-name as I do not know it for my home network.
I do not know if the above confiuration is right as it try to use WAN, and
I think to simply share my laptop file system with the board, a simple LAN
configuration should be okay (if so, how to configure given my information
above?)
Despite the above problem, I carried on to test the shared file system. I
use gtkterm to connect to the EVM board via RS232. After power on the board,
I got,
--------------------------------------------------
this is MT29F16G08FAA device
UBL: detected valid U-Boot magic number
UBL: booting to U-Boot
U-Boot 1.2.0 (Oct 17 2007 - 15:38:02)
DRAM: 128 MB
NAND: NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V
8-bit)
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
nand_read_bbt: Bad block at 0x09280000
nand_read_bbt: Bad block at 0x14380000
nand_read_bbt: Bad block at 0x2f860000
nand_read_bbt: Bad block at 0x3e260000
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xd3 (Micron NAND 1GiB 3,3V 8-bit)
Bad block table found at page 524224, version 0x01
Bad block table found at page 524160, version 0x01
nand_read_bbt: Bad block at 0x035e0000
nand_read_bbt: Bad block at 0x08c20000
nand_read_bbt: Bad block at 0x0a4a0000
nand_read_bbt: Bad block at 0x0e6a0000
nand_read_bbt: Bad block at 0x10840000
nand_read_bbt: Bad block at 0x1d080000
nand_read_bbt: Bad block at 0x1ea00000
nand_read_bbt: Bad block at 0x263e0000
nand_read_bbt: Bad block at 0x2c0e0000
nand_read_bbt: Bad block at 0x30020000
nand_read_bbt: Bad block at 0x30060000
nand_read_bbt: Bad block at 0x300a0000
nand_read_bbt: Bad block at 0x300e0000
nand_read_bbt: Bad block at 0x30120000
nand_read_bbt: Bad block at 0x30160000
nand_read_bbt: Bad block at 0x301a0000
nand_read_bbt: Bad block at 0x301e0000
nand_read_bbt: Bad block at 0x30220000
nand_read_bbt: Bad block at 0x30260000
nand_read_bbt: Bad block at 0x302a0000
nand_read_bbt: Bad block at 0x302e0000
nand_read_bbt: Bad block at 0x30320000
nand_read_bbt: Bad block at 0x30360000
nand_read_bbt: Bad block at 0x303a0000
nand_read_bbt: Bad block at 0x303e0000
nand_read_bbt: Bad block at 0x30420000
nand_read_bbt: Bad block at 0x30460000
nand_read_bbt: Bad block at 0x304a0000
nand_read_bbt: Bad block at 0x304e0000
nand_read_bbt: Bad bl!
ock at 0x30520000
nand_read_bbt: Bad block at 0x30560000
nand_read_bbt: Bad block at 0x305a0000
nand_read_bbt: Bad block at 0x305e0000
nand_read_bbt: Bad block at 0x30620000
nand_read_bbt: Bad block at 0x30660000
nand_read_bbt: Bad block at 0x306a0000
nand_read_bbt: Bad block at 0x306e0000
nand_read_bbt: Bad block at 0x30720000
nand_read_bbt: Bad block at 0x30760000
nand_read_bbt: Bad block at 0x307a0000
nand_read_bbt: Bad block at 0x307e0000
nand_read_bbt: Bad block at 0x30820000
nand_read_bbt: Bad block at 0x30860000
nand_read_bbt: Bad block at 0x308a0000
nand_read_bbt: Bad block at 0x308e0000
nand_read_bbt: Bad block at 0x30920000
nand_read_bbt: Bad block at 0x30960000
nand_read_bbt: Bad block at 0x309a0000
nand_read_bbt: Bad block at 0x309e0000
nand_read_bbt: Bad block at 0x30a20000
nand_read_bbt: Bad block at 0x30a60000
nand_read_bbt: Bad block at 0x30aa0000
nand_read_bbt: Bad blo!
ck at 0x30ae0000
nand_read_bbt: Bad block at 0x30b20000
nand_read_bbt: Bad block at 0x30b60000
nand_read_bbt: Bad block at 0x30ba0000
nand_read_bbt: Bad block at 0x30be0000
nand_read_bbt: Bad block at 0x33ac0000
2048 MiB
In: serial
Out: serial
Err: serial
ARM Clock :- 216MHz
DDR Clock :- 171MHz
Hit any key to stop autoboot: 1
DM355 EVM #
--------------------------------------------------------
The above EVM # command prompt is shown after I hit a key. Then I enter,
---------------------------------------------------------
DM355 EVM # setenv nfshost 192.168.1.207
DM355 EVM # setenv rootpath /home/zyang1/workdir/filesys
DM355 EVM # setenv bootargs console=ttyS0,115200n8 noinitrd rw ip=dhcp
root=/dev/nfs nfsroo\
t=192.168.1.207:/home/zyang1/workdir/filesys,nolock mem=116M
DM355 EVM # boot
Loading from NAND 1GiB 3,3V 8-bit, offset 0x400000
Image Name: Linux-2.6.10_mvl401
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1585240 Bytes = 1.5 MB
Load Address: 80008000
Entry Point: 80008000
DM355 EVM #
---------------------------------------------------------
It is imaginable the file system in rootpath is now shared, since I got the
same results after I typed boot directly without using three setenvs.
Even though, I don't know what should be used as my nfshost - is it
192.168.1.207 or 169.254.7.95 (as shown for eth0:avah in ifconfig) or something
else?
The final thing, I used bdinfo in the EVM # command prompt, and got,
-------------------------------------
DM355 EVM # bdinfo
arch_number = 0x00000565
env_t = 0x00000000
boot_params = 0x80000100
DRAM bank = 0x00000000
-> start = 0x80000!
000
-> size = 0x08000000
ethaddr = 00:0E:99:02:C2:1A
ip_addr = 0.0.0.0
baudrate = 115200 bps
--------------------------------------
where the ethaddr (my board MAC code) is set by me at start. I noticed that
no IP address is assigned for the board, which I suppose is wrong. How can I
assign an address to the client board?
I think this whole procedure might be a common question for a DVEVM board
newbie,
I would be grateful if anybody can give me a detailed solution to this problem.
Thanks a lot.
Michael
使用新一代 Windows Live Messenger 轻松交流和共享！ 立即体验！
_________________________________________________________________
多个邮箱同步管理，live mail客户端万人抢用中
http://get.live.cn/product/mail.html_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
