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.

[FAQ] AM625: AM625x EtherPHY RGMII synchronous clock

Expert 2901 points
Part Number: AM625
Other Parts Discussed in Thread: SK-AM62B-P1

Tool/software:

Hello,

May I have question about SoC clock?

Q1

In this document,

https://www.ti.com/lit/an/sprad21e/sprad21e.pdf

It says EPHY need match clock to SoC.

Is the mean of "match" same frequency and constant multipled frequency , or synchronous clock?

Q2

In 7.3.1.4.3 Processor Clock Output (CLKOUT0),

It says RGMII PHY require NOT-synchronous clock to other signals.

I think "signals" is including SoC clock, other PHYs clock.

However, SK-AM62B-P1 EVM use one OSC to two EtherPHYs and SoC clock.

This schematic provide synchronous clock to EtherPHYs and SoC.

It should use another OSC to PHYs and SoC.

Why is this?

Or it allow syncronous(same) clock to PHYs and SoC?

Thanks,

GR

  • This clocking topology was introduced on the AM64x EVM to satisfy an industrial application that uses Time Sensitive Networking (TSN). The clocking topology has been carried over to newer EVMs. The person that included the comments in the schematic check list may not have fully understood the reason this was done. I will try to get this clarified in the next revision.

    Most applications do not require the SoC and Ethernet PHY to operate from the same clock source.  This is only a requirement for a few industrial applications using Time Sensitive Networking (TSN). The TSN application doesn’t require phase aligned clocks, but it does require all of the devices to be operating at the same frequency. This clocking topology was used to ensuring each device on the AM64x EVM is operating at the same frequency, without the small PPM error that would be introduced from multiple clock sources.  

    In some cases, a customer may want to use a single 25MHz clock source for multiple devices and their application doesn't require a specific clock relationship across the devices. They may be buying a single LVCMOS clock source and using it for multiple devices because it offers a lower cost solution then buying multiple LVCMOS oscillators or crystals. In this case they should use a 1-input to n-output buffer to ensure appropriate signal quality on each clock signal. Branching a clock signal without buffers on each signal path is problematic because the clock signal will be distorted, and the distortion could create glitches on the internal clock tree of the attached devices.

    You will need to determine the best clocking solution for your specific system. Assuming your system is using separate clock sources for each device, you just need to make sure the clock source selected for each device is operating within the limits defined for that device. For example, the AM62x device requires a 25MHz reference clock with a maximum frequency error of 50PPM when using RMII or RGMII. The 50PPM error must be the combination of the initial frequency error and the frequency error introduced by temperature variation and aging of the clock source across the system's entire operating range.

    Regards,
    Paul

  • Hello Paul,

    Thanks for your information.

    This clocking topology was introduced on the AM64x EVM to satisfy an industrial application that uses Time Sensitive Networking (TSN). The clocking topology has been carried over to newer EVMs. The person that included the comments in the schematic check list may not have fully understood the reason this was done. I will try to get this clarified in the next revision.

    I understand the EVM schematic means.

    And I want to check once.

    You mean
    "RGMII EPHYs require a 25 MHz clock input that is not synchronous to any other signals." is uncorrect?

    Or simplly mean 25MHz clock should not provide to more than one devices such as PHY and another module? (should use clock buffer)

    Best regards,

    GR

  • The 25MHz reference clocks required for the AM62x device and Ethernet PHY does not need to be synchronous because Ethernet data is transferred between the MAC and PHY using the source synchronous clocks that are part of RGMII. Each device has a maximum frequency error that is allowed for their reference clock to ensure data flowing from one device to the other never over-runs an elastic buffer that spans the two clock domains.

    Connecting multiple loads to a single clock output is a bad design practice because this creates signal distortion that can be problematic on clock signals.

    Regards,
    Paul

  • Hi Paul,

    Thanks for your information.

    I understand.

    Best regards,

    GR