• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 99 subscribers
  • Views 415 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.

TDA4VM: No ETH1 interface on A72

Yuri Lyudkevich
Intellectual 470 points
Part Number: TDA4VM


Hello.

I am trying to bring up TDA4VM + GESI setup. But unfortunatelly I have no ETH1 interface on A72 running linux. Only eth0 (which is cpsw2g as I understand).

I have SD card prepared as per this guide, I can send traffic over GESI 1G ports, but I have no ETH1 interface on the linux side, thus I can't send traffic from A72 linux to devices connected to GESI ports.

It seems like linux device-tree issue, but I can't figure out that is wrong.

Any help/suggestions/advices would be appreciated.

  • 0
    Intellectual 470 points

    UPD:
    I have ETH1 interface working now, but I cant send traffic from device connected to GESI 1G port to device connected to 100M port on TDA4EVM board.

    I have checked ip forwarding:

    root@j7-evm:~# sysctl net.ipv4.ip_forward
    net.ipv4.ip_forward = 1

    it's already enabled.

    Meanwhile I can ping both devices from A72 linux console:

    100M port:

    root@j7-evm:~# ping 192.168.5.5
    PING 192.168.5.5 (192.168.5.5): 56 data bytes
    64 bytes from 192.168.5.5: seq=1 ttl=255 time=4.585 ms
    64 bytes from 192.168.5.5: seq=2 ttl=255 time=4.904 ms

    GESI port:

    root@j7-evm:~# ping 192.168.6.6
    PING 192.168.6.6 (192.168.6.6): 56 data bytes
    64 bytes from 192.168.6.6: seq=0 ttl=255 time=5.129 ms
    64 bytes from 192.168.6.6: seq=1 ttl=255 time=5.015 ms
    64 bytes from 192.168.6.6: seq=2 ttl=255 time=11.616 ms

    My network configuration:

    eth0      Link encap:Ethernet  HWaddr 50:51:A9:FC:B2:77  
              inet addr:192.168.5.1  Bcast:192.168.5.255  Mask:255.255.255.0
              inet6 addr: fe80::5251:a9ff:fefc:b277/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:8287256 errors:0 dropped:0 overruns:0 frame:0
              TX packets:88 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:502476826 (479.1 MiB)  TX bytes:15378 (15.0 KiB)

    eth1      Link encap:Ethernet  HWaddr 70:FF:76:1D:92:C1  
              inet addr:192.168.6.1  Bcast:192.168.6.255  Mask:255.255.255.0
              inet6 addr: fe80::72ff:76ff:fe1d:92c1/64 Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:21 errors:0 dropped:0 overruns:0 frame:0
              TX packets:97 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:1982 (1.9 KiB)  TX bytes:18340 (17.9 KiB)

  • 0 in reply to Yuri Lyudkevich
    TI__Genius 14680 points

    Yuri,

    Can you share your routing table -- "route -n" ? This will show if the gateway is set correctly so that packets are forwarded to right port.

    Best regards,

    Dave

  • 0 in reply to Dave Bell
    Intellectual 470 points

    Hello Dave,

    Here it is:

    root@j7-evm:~# route -n
    Kernel IP routing table
    Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
    192.168.5.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
    192.168.6.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1

    Also I see this everytime I trying to configure eth1 interface:

    j721e-cpsw-virt-mac main_r5fss_cpsw9g_virt_mac0: register_ipv4 rpmsg - fail -5

    Is this normal?