• Locked Locked
  • Replies 8 replies
  • Subscribers 120 subscribers
  • Views 18561 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ping failed; host 192.168.1.100 is not alive

murnesty lm
Note: This was originally posted on 5th May 2011 at http://forums.arm.com

My hyper terminal display:
Booting with TI UBL            
Device OPP (300MHz, 1.2V)                  

U-Boot 2009.11 (May 03 2010 - 15:38:40)                                

I2C:   ready        
DRAM:  64 MB        
In: serial      
Out:   serial      
Err:   serial      
ARM Clock : 300000            
DDR Clock : 132000000 Hz                    
Net:   Ethernet PHY: GENERIC @ 0x00                            

Hit any key to stop autoboot:  0                            
U-Boot > print
bootargs=mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p1 rw rootwait ip=off
bootcmd=sf probe 0;sf read 0xc0700000 0x80000 0x220000;bootm 0xc0700000
baudrate=115200
bootfile="uImage"
dlbuff=0xc0400000
kerneladdr=0x00080000
bootdelay=6
ipaddr=192.168.1.100
serverip=192.168.1.100
dnsip=202.188.1.5
ethaddr=00:25:11:03:47:10
netmask=255.255.255.0
gatewayip=192.168.1.1
stdin=serial
stdout=serial
stderr=serial
ver=U-Boot 2009.11 (May 03 2010 - 15:38:40)

Environment size: 454/65532 bytes
U-Boot > ping 192.168.1.100
Using  device
ping failed; host 192.168.1.100 is not alive
U-Boot >

I connected my serial port and network cable. It did not show any error or warning... but yet cant connect.. anyone can tell me the reason?
Parents
  • Note: This was originally posted on 9th May 2011 at http://forums.arm.com

    Your most recent info make it look like both the host and target are using address '192.168.1.100' -- that won't work well (although I'd kinda expect self-pings to work).

    I'm also suprised that it looks like the host has been given the '192.168.1.100' address by a DHCP server -- if the host is directly connected to the target, I would not expect there to be a DHCP server found.

    Try with the host and target having different addresses on the same subnet, e.g. '192.168.1.100' and '192.168.1.1'.

    Also the U-Boot output says "Using  device" which looks like the device name is missing, but maybe that's normal.

    Do either of you Ethernet sockets have link LEDs?  Are they lighting?  flashing?
Reply
  • Note: This was originally posted on 9th May 2011 at http://forums.arm.com

    Your most recent info make it look like both the host and target are using address '192.168.1.100' -- that won't work well (although I'd kinda expect self-pings to work).

    I'm also suprised that it looks like the host has been given the '192.168.1.100' address by a DHCP server -- if the host is directly connected to the target, I would not expect there to be a DHCP server found.

    Try with the host and target having different addresses on the same subnet, e.g. '192.168.1.100' and '192.168.1.1'.

    Also the U-Boot output says "Using  device" which looks like the device name is missing, but maybe that's normal.

    Do either of you Ethernet sockets have link LEDs?  Are they lighting?  flashing?
Children
No data