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.

RTOS/TDA2PXEVM: Supporting marvel ethernet on TDA2PX custom board

Part Number: TDA2PXEVM
Other Parts Discussed in Thread: SYSBIOS, DP83867IR

Tool/software: TI-RTOS

Hello All

As per client application requirement we intend to bring two Ethernet interface on custom board with TDA2px.
Configuration is as below.
1)      RGMII0 interface shall use PHY DP838867 . This port to be used as debug port . ( support is available on TDa2x –EVM )
2)      RGMII1 interface shall use PHY Marval 88Q2110. This port to be used for connectivity with vehicle network.

As per   , on TDA2PX sysbios only one ethernet device is supported while on VSDK linux support to both phy devices is possible simultaneously.

We currently need to support Marvel ethernet only in VSDKNSP_GMACSW_Framework_Understanding.doc8424.NSP_GMACSW_Framework_Understanding.doc sysbios configuration. Please find attached document capturing our understanding and queries related to it .

Please let us know if our understanding is correct and feedback regarding querries

regards

Hrishikesh

  • Hello Hrishikesh,

    My replies inline.

    Hrishikesh Rajurkar said:

    1. We think that to add the support for Marvell 88Q2110 Ethernet device  instead of default DP83867IR device changes are needed only in mdio_.h file.  This file includes definitons for PHY register addresses and Hardware register fields. Below table lists the identified registers to be changed for Marvell device support.

    2. Rest of the procedure will remain same.

    3. We would like to know how to calculate the hardware register field value such as  MII_PHY_RESET , MII_PHY_LOOP, MII_AUTO_NEGOTIATE_EN ..etc.  Are these values provided by device manufacturer?

    Please let us know if our understanding is correct and feedback regarding querries

    Nothing needs to be changed in the mdio_.h file as the registers mentioned in the this file and used in the mdio.c are standard IEEE  registers and ar supported on all PHYs. 

    NSP only configures standard registers so if any other configuration is needed you need to get it from Marvel and add it into mdio.c and call from mdio_init by commenting other code.

    Experience from other customer when bringing this PHY with NSP, you need to get phy library functions from Marvell. Have you got them?

    Also there was known issue in this PHY about link status not shared with MAC, please confirm that too.

  • Hi Hrishikesh,

    I haven’t heard back from you, I’m assuming you were able to resolve your issue. If not, just post a reply below (or create a new thread if the thread has locked due to time-out)
  • Hi Prasad
    We have raised the queries to Marvel and awaiting their replies.
    regards
    Hrishikesh
  • Hi Prasad,
    We have few queries on this till we receive feedback from Marvel.
    In our custom board , PHY DP838867 and Marvel PHY 88Q2110 are present. From the query e2e.ti.com/.../2555079 , in sysbios configuration only one PHY is supported at one instance. Will you please let us know how to disable PHY DP838867 . So that we confirm if Marvel device is detected .
    regards
    Hrishikesh
  • Hello Hrishikesh,

    You can disable PHY in the NSP package by not giving PHY address for first MAC port in GMACSW_getConfig function.

    Also if you dont connect LAN cable on that port (where DP83867 is present), NSP will only check for links of Marvel PHY port.