• State TI Thinks Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 877 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 using the second ethernet use

Jone Joniee
Intellectual 470 points

Other Parts Discussed in Thread: OMAP-L137

Dear Sir/Madam,

I have OMAP-L137 EVM. It have two Ethernet interfaces. I want to use the first one to boot the linux Os and the second Ethernet interface to send/receive data between PC and the board. How can I do this work? How can I activate the second interface? 

Jone,

  • 0
    TI__Mastermind 43955 points
    Hi Jone,
    I think, you can use both ports.
    In OMAPL137 EVM, MICREL switch is is used to have two ethernet ports (RGMII)

    Please refer to the EVM reference guide.
    support.spectrumdigital.com/.../EVMOMAPL137_TechRef_revg.pdf

    Try to up the second port like below.
    ifconfig eth1 10.100.1.63 up
  • 0 in reply to Shankari G
    Intellectual 470 points
    Hi Shankari,
    "ifconfig eth1 10.100.1.63 up" does not work. "ifconfig -a" returns

    eth0 Link encap:Ethernet HWaddr 00:0E:99:03:1A:4A
    inet addr:172.16.3.109 Bcast:172.16.3.255 Mask:255.255.255.0
    inet6 addr: fe80::20e:99ff:fe03:1a4a/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:10406 errors:1 dropped:0 overruns:0 frame:0
    TX packets:6080 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:9810832 (9.3 MiB) TX bytes:1048816 (1.0 MiB)
    Interrupt:33 Base address:0x3000

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:16436 Metric:1
    RX packets:8 errors:0 dropped:0 overruns:0 frame:0
    TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:560 (560.0 b) TX bytes:560 (560.0 b)

    sit0 Link encap:IPv6-in-IPv4
    NOARP MTU:1480 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

    tunl0 Link encap:IPIP Tunnel HWaddr
    NOARP MTU:1480 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:0
    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

    I think other action should be done to see eth1 on the above list. What is your opinion?

    Jone,