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.
Hi Jeff,
Option 1 :
not recommended since RX_CLK is a remote node recovered clock, and TX_CLK is the PHY (TLK) Free-Running Clock.
due to PPM differences between remote node clock and TLK clock ( CLKOUT25 is also based on free- running clock), this scheme will not work.
I can offer new scheme, using RMII Interface ( support by TLK110) so you can connect two PHY sharing the same XI and connect TXD to RXD and RX_DV to TX_EN between them.
In RMII PPM difference between remote node and local node XI clock is compensated internally using a Async_fifo.
Option 2:
It seem like very good and creative idea, using far end loop for each direction will cancel the need to use MII Interface ( you can left the RX and TX unconnected
And avoid using the CLOCKS since it is an internal loop back).
Beside of carful routing of the PHYs TD and RD pairs ( Node1 is transmitting to PHY1, PHY1 receives and looping it out to its TD pair that should be connected to
Node2 RD pair and vice versa) a MDIO support is needed, since you have no other option to put TLK in loop mode.
- Setting the device into FORCE_10_FD is possible using Strap pins.
- Changing the pin3 voltage is not recommended. TLK should support 200 meters by default.
Best Regards,
Yaniv