On Wed, Feb 4, 2009 at 1:37 PM, mak visp
<mak.visp@xxxxxxxxx> wrote:
Hello,
I have successfully ported petalinux for my custom board. I am facing
some issues related to network.
====> Also I am not able to access the board from remote system once
the board is up. I need to do some activity on network from board side
(I do ping from board). After this everything works fine. Is there any
issue with the ARP? How can I find out.
===> The ping does not work under u-boot which comes along with
PetaLogix. Are there some extra settings required to use network under
uboot. Also I could not download the image using tftp and nfs (I have
done correct settings on the host as I could access those from another
machine on the network).
U-Boot> printenv
baudrate=115200
filesize=5DF
autoload=no
ethaddr=00:0a:35:00:22:01
ipaddr=10.111.10.136
serverip=10.111.10.129
netkargs=macaddr=00:0a:35:00:22:01
mtdparts=physmap-flash.0:256K(boot),256K(bootenv),256K(config),30M(image),10M(jffs2),10M(backup),13M(spare)
mtdkargs=mtdparts=physmap-flash.0:256K(boot),256K(bootenv),256K(config),30M(image),10M(jffs2),10M(backup),13M(spare)
clobstart=0x40000000
bootsize=0x40000
bootstart=0x8c000000
bootenvsize=0x40000
bootenvstart=0x8c040000
eraseenv=protect off $(bootenvstart) +$(bootenvsize); erase
$(bootenvstart) +$(bootenvsize)
kernsize=0x1E00000
kernstart=0x8c0c0000
bootargs=mtdparts=physmap-flash.0:256K(boot),256K(bootenv),256K(config),30M(image),10M(jffs2),10M(backup),13M(spare)
macaddr=00:0a:35:00:22:01
bootcmd=bootm 0x8c0c0000
bootdelay=4
load_kernel=tftp $(clobstart) image.ub
install_kernel=protect off $(kernstart) +$(kernsize);erase
$(kernstart) +$(kernsize); cp.b $(fileaddr) $(kernstart) $(filesize)
update_kernel=run load_kernel install_kernel
load_uboot=tftp $(clobstart) u-boot-s.bin
install_uboot=protect off $(bootstart) +$(bootsize);erase $(bootstart)
+$(bootsize);cp.b $(clobstart) $(bootstart) $(filesize)
update_uboot=run load_uboot install_uboot
Environment size: 1209/262140 bytes
U-Boot> bdinfo
boot_params = 0x7FF4FFD0
memstart = 0x40000000
memsize = 0x40000000
flashstart = 0x8C000000
flashsize = 0x04000000
flashoffset = 0x00000000
ethaddr = 00:0A:35:00:22:01
ip_addr = 10.111.10.136
baudrate = 115200 bps
U-Boot> ping 10.111.10.129
ping failed; host 10.111.10.129 is not alive
====> Ping works fine when used under Linux. But for some packet sizes
the response time is too large. It works fine up to packet size 1472.
Then from 1473 to up to 1580 the response time is too large. After
that up to 1972 (this is what the maximum packet size allowed) it is
again acceptable. Please see the logs:
# ping 10.111.10.129 -s 1472
PING 10.111.10.129 (10.111.10.129): 1472 data bytes
1480 bytes from 10.111.10.129: icmp_seq=0 ttl=64 time=2.1 ms
1480 bytes from 10.111.10.129: icmp_seq=1 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=2 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=3 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=4 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=5 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=6 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=7 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=8 ttl=64 time=1.8 ms
1480 bytes from 10.111.10.129: icmp_seq=9 ttl=64 time=1.8 ms
--- 10.111.10.129 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 1.8/1.8/2.1 ms
# ping 10.111.10.129 -s 1500
PING 10.111.10.129 (10.111.10.129): 1500 data bytes
1508 bytes from 10.111.10.129: icmp_seq=0 ttl=64 time=1011.4 ms
1508 bytes from 10.111.10.129: icmp_seq=1 ttl=64 time=366.7 ms
1508 bytes from 10.111.10.129: icmp_seq=2 ttl=64 time=535.7 ms
1508 bytes from 10.111.10.129: icmp_seq=3 ttl=64 time=262.3 ms
1508 bytes from 10.111.10.129: icmp_seq=4 ttl=64 time=2.4 ms
1508 bytes from 10.111.10.129: icmp_seq=5 ttl=64 time=39.2 ms
1508 bytes from 10.111.10.129: icmp_seq=6 ttl=64 time=29.3 ms
1508 bytes from 10.111.10.129: icmp_seq=7 ttl=64 time=328.3 ms
1508 bytes from 10.111.10.129: icmp_seq=8 ttl=64 time=200.3 ms
1508 bytes from 10.111.10.129: icmp_seq=9 ttl=64 time=391.1 ms
1508 bytes from 10.111.10.129: icmp_seq=10 ttl=64 time=298.6 ms
1508 bytes from 10.111.10.129: icmp_seq=11 ttl=64 time=288.5 ms
1508 bytes from 10.111.10.129: icmp_seq=12 ttl=64 time=43.2 ms
1508 bytes from 10.111.10.129: icmp_seq=13 ttl=64 time=362.3 ms
1508 bytes from 10.111.10.129: icmp_seq=14 ttl=64 time=1012.1 ms
1508 bytes from 10.111.10.129: icmp_seq=15 ttl=64 time=41.1 ms
1508 bytes from 10.111.10.129: icmp_seq=16 ttl=64 time=30.4 ms
1508 bytes from 10.111.10.129: icmp_seq=17 ttl=64 time=20.5 ms
1508 bytes from 10.111.10.129: icmp_seq=18 ttl=64 time=174.9 ms
--- 10.111.10.129 ping statistics ---
20 packets transmitted, 19 packets received, 5% packet loss
round-trip min/avg/max = 2.4/286.2/1012.1 ms
# ping 10.111.10.129 -s 1972
PING 10.111.10.129 (10.111.10.129): 1972 data bytes
1980 bytes from 10.111.10.129: icmp_seq=0 ttl=64 time=3.0 ms
1980 bytes from 10.111.10.129: icmp_seq=1 ttl=64 time=2.5 ms
1980 bytes from 10.111.10.129: icmp_seq=2 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=3 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=4 ttl=64 time=2.5 ms
1980 bytes from 10.111.10.129: icmp_seq=5 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=6 ttl=64 time=2.5 ms
1980 bytes from 10.111.10.129: icmp_seq=7 ttl=64 time=2.5 ms
1980 bytes from 10.111.10.129: icmp_seq=8 ttl=64 time=2.5 ms
1980 bytes from 10.111.10.129: icmp_seq=9 ttl=64 time=2.5 ms
1980 bytes from 10.111.10.129: icmp_seq=10 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=11 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=12 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=13 ttl=64 time=2.4 ms
1980 bytes from 10.111.10.129: icmp_seq=14 ttl=64 time=2.4 ms
--- 10.111.10.129 ping statistics ---
15 packets transmitted, 15 packets received, 0% packet loss
round-trip min/avg/max = 2.4/2.4/3.0 ms
Since the packet will be fragmented in last both the case how can be
such huge time difference.
Any hint is appreciated.
--
Thanks
Mak
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/