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.

DP83867E: driver for linux3.18 kernel version

Part Number: DP83867E


1. DP83867 Troubleshooting Guide (Rev. A) shows Near-End Loopback Example with RGMII. My customer is using SGMII interface. They'd like to know what register configurations needed to meet Near-End Loopback Example.

Further more, how to check loopback data rate, Packet Loss Rate etc. and how to verify if communication between MAC & PHY SGMII ok?  

 

2. My customer tested eye diagram of SGMII and confirmed that the signal quality of SGMII  basically meets the requirements. Therefore, it hopes to verify the MDI interface through the Far-End Loopback test. If Link Partner a tool for issuing packages running on a PC? and is it recommended for PC?

 

3. Does it need to reset all registers before writing the following two registers? In this Far-End Loopback test, can the computer network port obtain an IP address? Thanks.

a. Write register 0x0016 to 0x0020 to enable reverse loopback.

b. Write register 0x001F to 0x4000 to apply a software restart.



  • Hello,

    To answer your questions: 

    1. Please refer to Table 4 in the datasheet to confirm which loopback modes are available with SGMII. Please refer to section 8.4.4 in the datasheet for information on each loopback mode. Register 0x16 will be used to configure the PHY into different loopback modes. In the case of near-end loopback, the MAC will be responsible for generating and checking data packets.

    2. Any link partner with the ability to generate packets can be used as the link partner for Far-End loopback. 

    3. As long as the device is already correctly set to communicate with the link partner, a hard reset is not required before setting the Far-End loopback test.

    Thank you,

    Nikhil