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.

DP83TG720S-Q1: DP83TG720S-Q1 Timing Clarification

Part Number: DP83TG720S-Q1

Dear Team,

We are considering TI's DP83TG720S-Q1 part for 1000 base T1 functionality in our product. We shall be interfacing with NVIDIA's Orin AGX SOM via RGMII interface. 

The design guide for the Orin AGX doesn't contain any timing-related specifications (such as setup time, output skew etc). However, NVIDIA states that the Orin SoC complies with RGMII 2.0 standard. Furthermore, the SOM does not support the RGMII-ID feature and delay must be added externally by PHY or PCB. Orin_RGMII.pdf

Based on this data, we are considering the following approach.

Orin Tx out to PHY Tx inConsidering +/-500ps output skew as per the RGMII standard and minimum 1ns setup/hold time mandated by PHY chip, the required clock to data delay shall be greater than 1.5ns and less than 2.5ns (for 4ns ton). To meet this requirement, DLL DLL_TX_DELAY_CTRL_SL=8 or DLL DLL_TX_DELAY_CTRL_SL=9 shall be considered.

PHY Rx out to Orin Rx in

The Orin mandates a clock-to-data skew of greater than 1.5ns and less than 2ns to ensure proper sampling. The in-built delay values for Rx don't seem to meet this criterion. Having said that, we may have to add an external delay in the form PCB delay or clock buffer (on top of the PHY internal delay if used). 

Can the TI team let us know if the above approach could be considered to satisfy RGMII timing at both ends? 

Also, to meet RX timings, does adding a clock buffer for additional delay make sense? if so, can TI suggest a buffer part for the same?

  • Hi Balaji,

    The Orin mandates a clock-to-data skew of greater than 1.5ns and less than 2ns to ensure proper sampling

    The above statement means that Orin is asking for a setup time of 1.5ns and hold time 2ns, which is a violation of RGMII specification.
    Any device which is RGMII compliant can ask only for 1ns setup time and 1ns hold time.

    Can you please check if Orin is RGMII compliant?

    --
    Regards,
    Gokul.

  • Dear Gokul.

    I confirmed it from the NVIDIA forum and they state that it's RGMII 2.0 compliant. Even the datasheet of Orin AGX states the same (mentioned below).

    For clarity, this is what the design guide states on the clock-to-data skew requirement for RX signals

  • Hi Balaji,

    Can you please check with the Orin team about the delay 1.5ns to 2ns? Is this a typical number?
    Since they claim that the PHY is RGMII compliant, it seems that they are talking about typical delay.

    If the boards traces of RX_CLK and RX_D are matched, and since Orin is RGMII compliant, it will be okay to use the default RX Delay code to meet the timing.

    --
    Regards,
    Gokul.