• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Subscribers 102 subscribers
  • Views 1747 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

66AK2H12 GbE can not respond ping from PC

RY9983
Guru 10570 points
Other Parts Discussed in Thread: 66AK2H12

Hello,

One of my customer have encountered trouble who can not succeed ping in their custom 66AK2H12 board.

- Could you let me know what you noticed or what it is wrong?
- And, give us any advice to debug? we will check it.

Trivial informations would be appreciate.

If you need more information, please let me know.

Best regards, RY

  • 0
    TI__Mastermind 20790 points

    RY,

    The custom board having different phy compared with EVM. I hope, the below E2E post will helpful to find the solution. At the same time the reference posts are related with keystone-I device.

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/367396.aspx

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/366058/1286228.aspx#1286228

  • 0 in reply to Pubesh
    TI__Guru 50170 points

    Hi, RY,

    I am confused with your description. Was the ping done on TI EVM and PC not getting responses from TI EVM? If that was the case, what are the IP addresses for eth0 and eth1? If they are on the same subnet, both can not be connected at the same time. We have tried on K2H and both eth0 and eth1 works without any issue.

    Rex

  • 0 in reply to Rex Chang
    Guru 10570 points

    Pubesh-san, Rex-san,

    Thank you so much for your advise!

    Pubesh-san,
      I will check the url and get back to you. Thanks!

    Rex-san,
      First, our K2HEVM network configuration is following :
      a) PC1 .. ipaddr 192.168.11.1, netmask 255.255.255.0
      b) K2HEVM port1(SGMII0) .. ipaddr 192.168.11.2, netmask 255.255.255.0
      c) K2HEVM port2(SGMII1) .. ipaddr 192.168.4.35, netmask 255.255.255.0
      d) PC2 .. ipaddr 192.168.4.34, netmask 255.255.255.0

    H/W connection
      PC1 <---> K2HEVM port1(SGMII0)
      PC2 <---> K2HEVM port2(SGMII1)

    In this condition, both ping from a) to b) and ping from c) to d) succeed.

    Are there any misunderstanding?
    And, I am checking about customer's ipaddr and netmask.

    Best regards, RY

  • 0 in reply to RY9983
    TI__Guru 50170 points

    Hi, RY,

    Marvell 88E15xx does not power up ready for use like older PHY. MDIO control is needed to get it going. K2E uses 88E1512/14. Your customer may want to refer to the latest code to see how it is done.

    Rex

  • 0 in reply to Rex Chang
    Guru 10570 points

    Rex-san,

    Great thanks for your information.
    I will check it. 

    Best regards, RY

  • 0
    Guru 10570 points


    Hello,

    We have been checking target board. But, we can not cleared it.
    Instead, we found that MACSTATUS->IDLE field is different between K2HEVM and our target board.

    K2HEVM
    Before link-up .. MACSTATUS->IDLE = 1
    After link-up .. MACSTATUS->IDLE = 1

    Our target board
    Before link-up .. MACSTATUS->IDLE = 1
    After link-up .. MACSTATUS->IDLE = 0

    And, I found below link, it can be seen as same issue.
    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/439/t/52539.aspx

    Question)
    Can you tell me about condition to be cleared IDLE bit in EMAC?
    If link-up is failed, is it cleared?

    I would like to clarify if it is PHY side trouble or EMAC side trouble.

    Best regards, RY

  • 0 in reply to RY9983
    Guru 10570 points

    We could succeed ping by 66AK2H12 + 88E1512.

    I modified configuration:
      66AK2H12:
        SGMII_CONTROL->MASTER = 0x21 // master mode, auto-negotiation enable
        MR_ADV_ABILITY = 0x9801 // Full duplex, Speed Gig
      88E1512:
        Configured as Slave

    On my exam,
      When SGMII is slave mode (PHY is master), ping was failed.
      When SGMII is master mode (PHY is slave), ping was succeed.

    The default MCSDK for K2HEVM configures SGMII as slave mode. (using 88E1111)
    And, KeyStone Gigabit Ethernet UG describes that SGMII module needs to be configured in slave mode to connect with an external PHY.

    Question)
      - To decide master/slave mode, are there any rules?
        (Because, UG describes that SGMII needs to be slave.)
      - EVMK2E has 88E1514. Is the SGMII module configured in slave mode?

    Best regards, RY

  • 0 in reply to RY9983
    TI__Guru 50170 points

    Hi, RY,

    Defining the SGMII port to be master, it might be taking advantage of some arbitrary power-on state which makes it working, but the stability of this solution is questionable. SGMII is a MAC-to-PHY link as defined by the IEEE.  In an implementation of a K2H connected to an Ethernet PHY, this is the defined use case.  IEEE defines the PHY as the master of the SGMII link and the MAC as the slave on an SGMII link.  This allows the PHY to negotiate the PHY-to-PHY link over the cable and then to present these capabilities to the MAC.  If the MAC is defined as the SGMII master, this end-to-end link functionality is broken. 88E1512 can be used like the K2E EVM but will need MDIO support to get the PHY to link up.

    Rex