• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 4130 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

OMAP-L137 ping failed, Ethernet doesn't work

Ming Tang
Intellectual 320 points
Other Parts Discussed in Thread: OMAP-L137

Hi everyone.

I'm using ubuntu on vmware workstation and using hyperterminal. My board is OMAP-L137 revision I.

Net setting of vmware is bridge, on Ubuntu is manual, on u-boot is static ip. I don't have a router, so I use a Ethernet cable to connect the PC and EVM directly.

The cable is not crossover. I also have atftp, tftp-hpa on my Ubuntu and they are runing, all firewalls are shut down.

My Ubuntu host IP (using ifconig) is 192.168.91.10 and Win 7 IP is 192.168.91.1

but when I enter "ping 192.168.91.10" in u-boot, it shows:

ping failed; host 192.168.91.10 is not alive. Even ping 127.0.0.1 or "setenv" a ipaddr and ping it also show the same.

When try tftp, it just keep loadding:"T T T T T..." and retry. VMWare and Win 7 command prompt can ping themselves.

I searched some similar threads, but couldn't find the solution. It seems most cases working with dhcp are fine.

Please help me with it, thank you!

Ming

  • 0
    TI__Guru* 81335 points

    Hi Ming,

    Thanks for the post.

    What is the Ethernet link status (Ethernet LED's are glowing)?

    Set the Target IP Configurations from u-boot as follows:
    u-boot> setenv ipaddr 192.168.91.11
    u-boot> setenv serverip 192.168.91.10
    u-boot> setenv gatewayip 192.168.91.1
    u-boot> setenv netmask 255.255.255.0

    Ensure to have the same value for gatewayip and netmask as configured in the Host machine (VMWare and Win 7).

    Please try "ping" the serverip from u-boot prompt.

    u-boot> ping $serverip

    Thanks.

  • 0 in reply to Raja
    TI__Mastermind 20790 points

    Ming,

    Please kindly see the below wiki pages for setting up of OMAPL137 filesystem.
    http://processors.wiki.ti.com/index.php/Setting_up_OMAP-L137_Target_File_System
    http://processors.wiki.ti.com/index.php/Booting_Linux_kernel_using_U-Boot

    Note that bootargs in these examples sets ip=dhcp.
    If your EVM is not connected to a network with a DHCP server, you will want to set ip=off. For booting with NFS as root file system, having a valid IP address is a must.

  • 0
    Intellectual 320 points

    Thank you guys, I somehow get the Ethernet working. Just post my configuration here:

    Using crossover Ethernet cable(may not necessary) to connect EVM and PC directly. 

    VMware:

    Network adapter settings: Bridged: Connected directly to the physical network

    Virtual network editor: VMnet0: Bridged: Bridge to: Automatic. VMnet1 and VMnet8, leave them default.

    Ubuntu:

    IPv4: Method: manual

    Address 192.18.71.3 Netmask 255.255.255.0 Gateway 192.168.71.1

    Win7:

    Control panel: Network and Internet: Network Connections:

    Local Area Connection:

    Details: DHCP Enable: No

    IPv4 Address: 192.168.71.5

    IPv4 Subnet Mask: 255.255.255.0

    Properties: IPv6 unchecked(may not necessary)

    u-boot:

    ipaddr=192.168.71.4

    serverip=192.168.71.5

    netmask=255.255.255.0

    gatewayip=192.168.71.1

    Ubuntu terminal and Win7 cmd prompt can ping each others.

    Under u-boot, ping above both shows "alive"

    When in tftp transmission, Both terminal and cmd prompt can ping EVM.

    Thank you guys, and hope everyone works well:)

  • 0 in reply to Ming Tang
    TI__Guru* 81335 points

    Hi Ming Tang,

    I thought the information on u-boot commands will help you to solve the Ethernet issue.  

    Thanks for the update. The information provided will be helpful to others.

  • 0 in reply to Raja
    Intellectual 320 points

    Thank you Rajasekaran, My u-boot environment settings and other configurations were just like you told me when I gave the first try. I guess there were something else I missed. So I started over and reconfigured everything I could think of. It works now, but I don't pretty sure where it went wrong. So I just post as much as I know.