• Locked Locked
  • Replies 8 replies
  • Subscribers 120 subscribers
  • Views 18348 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?
  • Note: This was originally posted on 6th May 2011 at http://forums.arm.com

    i think my network cable is not cross over because the color is not arranged opposite way... I'm not connect to hub.. I connect modem directly to PC.
  • Note: This was originally posted on 7th May 2011 at http://forums.arm.com

    I'm connecting the cross cable u shown in the link directly to PC. And i tried both IP address but it still show not alive.

    The U-boot terminal testing result:
    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       
    dnsip=202.188.1.5             
    ethaddr=00:25:11:03:47:10                     
    netmask=255.255.255.0                 
    gatewayip=192.168.1.1                 
    ipaddr=169.254.168.124                     
    serverip=169.254.168.124                       
    stdin=serial           
    stdout=serial         
    stderr=serial         
    ver=U-Boot 2009.11 (May 03 2010 - 15:38:40)                                       

    Environment size: 458/65532 bytes                             
    U-Boot > ping 169.254.168.124                         
    Using  device           
    ping failed; host 169.254.168.124 is not alive
    U-Boot > setenv ipaddr 192.168.1.100                 
    U-Boot > setenv serverip 192.168.1.100  
    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
    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)
    ipaddr=192.168.1.100
    serverip=192.168.1.100

    Environment size: 454/65532 bytes                               
    U-Boot > ping 192.168.1.100                       
    Using  device         
    ping failed; host 192.168.1.100 is not alive
  • Note: This was originally posted on 16th May 2011 at http://forums.arm.com

    So, i assign the serverip to my pc IP and then ipaddr as board ip...

    so is like :
    serverip = 192.168.1.100
    ipaddr = 192.168.1.1

    then i tried ping 192.168.1.1 and ping 192.168.1.100. But both also ping not alive.

    I was connect the board only check ipconfig /all . Then it display DNS servers as 202.188.1.5.
    My board ethernet port has LED flashing green / yellow when i turn on my board.

    I also attached a picture from the user manual i had. It show using device is normal. If you want the whole pdf here then i will post later.
  • Note: This was originally posted on 21st May 2011 at http://forums.arm.com

    Anyone know the reason? or anyone has guild pdf for downloading kernel. i had a u-boot guild pdf.
  • Note: This was originally posted on 5th May 2011 at http://forums.arm.com

    From the .png it looks like your host has chosen IP=169.254.168.124 (in the mDNS/Zeroconf range).  Have you tried pinging that?

    Are you connecting both devices to a hub or directly to each other?  If they are connected directly to each other you may need a cross-over Ethernet cable http://en.wikipedia....crossover_cable (depending on whether either device support automatic cable detection).
  • 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?

  • Hi, anyone had success using ping to test a connection of juno to PC?

  • in reply to fsck

    marchese

    Please create a new discussion, rather than commenting on something which is probably unrelated - helps keeps the discussions on-topic and searchable.

    Cheers,

    Pete