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.

AM335x EVM SK Network issue, please help!!!

Hi All

In AM335x_SK, i enable eth0/eth1 and ping them both.

But when i use ifconfig to link down eth1, eth0 also lost ping after several pings.

Even if i enable eth1 again, i can not ping eth0 or eth1 anymore.

I must link down eth1 and eth0 both, then link up eth1 and eth0.

Is this a bug? Which driver version can fix it?

Please help, thanks

Kiros

  • What software/version are you using?
  • Hi Biser

    I use linux-3.2.0-psp04.06.00.08

    Thanks

    Kiros

  • Hi Biser

    Thanks for your help.

    I see the CPSW Driver's Guide, but i still have no idea.

    Because I use default firmware ( kernel and drvier ) without modify.

    I think the default firmware in AM335x EVM SK will work perfectly.

    Do i need to modify some kernel feature or get some patches to fix this issue?

    Thanks

    Kiros

  • Hi Kiros,
     
    Can you look towards the end of the wiki page: http://processors.wiki.ti.com/index.php/AM335x_CPSW_(Ethernet)_Driver's_Guide#Dual_Standalone_EMAC_mode. I think that what you see is a configuration issue which will be resolved if the CPSW is configured in dual standalone EMAC mode.
  • Hi Biser

    The default firmware is already configured in dual standalone EMAC mode.

    So i can see the eth0 and eth1.

    But the issue is still exist. :(

    Thanks

    Kiros

  • OK Kiros, I will ask our networking experts to help on this.
  • Hi,

    could you please post your /etc/network/interfaces

    I know it is a very stupid thing but maybe starting from the bottom could help :-)

    In my SK I don't have this problem

  • Hi,

    /etc/network/interface ( I didn't modify anything )

    # /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)

    # The loopback interface

    auto lo

    iface lo inet loopback

    # Wireless interfaces

    #

    # Example of an unencrypted (no WEP or WPA) wireless connection

    # that connects to any available access point:

    #

    iface wlan0 inet dhcp

            wireless_mode managed

            wireless_essid any

    iface tiwlan0 inet dhcp

            wireless_mode managed

            wireless_essid any

    #

    #

    # Same as above but locked to a specific access point:

    #

    #iface wlan0 inet dhcp

    #       wireless_mode managed

    #       wireless-essid some-essid

    #

    # A WEP encrypted connection locked to a specific access point:

    #

    #iface wlan0 inet dhcp

    #       wireless-essid some-essid

    #       wireless-key s:My-PlainText-Password

    #       wireless-mode managed

    #

    # A WPA1 or WPA2 encrypted connection locked to a specific access point.

    # This is the best option for non-roaming, single-network usage.

    # Note that your card may require a firmware update to use WPA.

    # Some distributions install a temporary volatile firmware update on ifup.

    #

    #iface wlan0 inet dhcp

    #       wpa-essid some-essid

    #       wpa-psk My-PlainText-Password

    #

    # A WPA1 or WPA2 encrypted connection using an external configuration file

    # for wpa-supplicant. This is the way to go if you need to configure multiple

    # networks with different keys and / or WPA settings and roaming support.

    #

    # iface wlan0 inet dhcp

    #    wpa-conf /etc/wpa_supplicant.conf

    #    wpa-driver hostap

    iface atml0 inet dhcp

    # Wired or wireless interfaces

    auto eth0

    iface eth0 inet dhcp

            pre-up /bin/grep -v -e "ip=[0-9]\+\.[0-9]\+\.[0-9]\+\.[0-9]\+" /proc/cmdline > /dev/null

    iface eth1 inet dhcp

    # Ethernet/RNDIS gadget (g_ether)

    # ... or on host side, usbnet and random hwaddr

    iface usb0 inet dhcp

    # Zaurus 2.4 Lineo net_fd; obsolete

    iface usbd0 inet static

            address 192.168.129.201

            netmask 255.255.255.0

            network 192.168.129.0

            gateway 192.168.129.200

    # iPAQ 2.4 mach-sa1100/usb-eth

    # (192.168.0.202 is the iPAQ's IP, 192.168.0.200 is the host's IP)

    iface usbf inet static

            address 192.168.0.202

            netmask 255.255.255.0

            network 192.168.0.0

            gateway 192.168.0.200

    # Bluetooth networking

    iface bnep0 inet dhcp

    ----------------------------------------------------------------------------------------------------------------------

    Thanks

    Kiros

  • try to add

    auto eth1

    just before

    iface eth1 inet dhcp

  • Hi 

    I think add auto eth1 just enable eth1 at startup.

    i try to add and still have the same problem.

    Here is the interface configuration

    PHY: 0:00 - Link is Up - 100/Full

    eth0    Link encap:Ethernet HWaddr D4:94:A1:89:36:D1

                inet addr:192.168.10.100 Bcast:192.168.10.255 Mask:255.255.255.0

    PHY: 0:01 - Link is Up - 100/Full

    eth1    Link encap:Ethernet HWaddr D4:94:A1:89:36:D2
                inet addr:192.168.20.151 Bcast:192.168.20.255 Mask:255.255.255.0

    At first, i ping( fping can duplicate the issue fast) two interface and it's ok.

    And then i ifconfig eth0 down, and i see eth1 also lost ping after several pings.

    And i ifconfig eth0 up, they still lost ping. 

    So i ifconfig eth0/eth1 down both. And ifconfig eth0/eth1 up again.

    They work again.

    What is your kernel psp version? 

    Thanks

    Kiros

  • I'm using the last realeas of psp:

    linux-3.2.0-psp04.06.00.11

    I'm sorry I  have no other ideas for now.

    I think that if you don't use all the devices listed in your /etc/network/interfaces you can delete some of them and keep only eth0 and eth1 (copy that file before). I know they are very elementary  steps, but I know how it feels when something don't work :-)

  • Hi Giuseppe

    Thanks for your information.

    Try to keep only eth0 and eth1 in /etc/network/interfaces is not work.

    I guess there is something wrong with cpsw driver.

    Because i try to re-initialize some settings on cpsw_ndo_open when eth0 up again.

    And ping will not be lost !!!

    But there are still bugs on these settings, it will cause driver crash. 

    So I still keep debugging.

    And I will try to update the driver code with last kernel psp.

    Thanks

    Kiros