SNLA431 January   2024 DP83TC812R-Q1 , DP83TC812S-Q1

 

  1.   1
  2.   Trademarks
  3. 1Preface
  4.   Notational Conventions
  5. 2Related Documentation
  6. 3Support Resources
  7. 4Troubleshooting the PHY Application
    1. 4.1  Schematic and Layout Checklist
    2. 4.2  Verify Successful Power-up of PHY
    3. 4.3  Peripheral Pin Checks
      1. 4.3.1 Probe the RESET_N pin
      2. 4.3.2 Probe the INH pin
      3. 4.3.3 Probe the CLKOUT pin
      4. 4.3.4 Probe the Serial Management Interface (MDC, MDIO) Pins
    4. 4.4  Register Dump Comparison
    5. 4.5  Verifying Strap Configurations
    6. 4.6  Check the MDI Signal
    7. 4.7  Link Up Failed Common Issues
    8. 4.8  Signal Quality Check
    9. 4.9  Power Up Timing
    10. 4.10 Loopback Testing
    11. 4.11 Debugging the MAC Interface
    12. 4.12 Verify Open Alliance PMA Compliance
    13. 4.13 Tools and References
      1. 4.13.1 DP83TC812 Register Access
      2. 4.13.2 DP83TC812 USB2MDIO Scripts
      3. 4.13.3 Extended Register Access
      4. 4.13.4 Software and Driver Debug on Linux
        1. 4.13.4.1 Commonly Seen Linux Terminal Outputs
  8. 5Conclusion

Loopback Testing

When packets are not able to be received between nodes or bit errors are appearing in the stream, an integrated debugging tool called loopbacks can be used to narrow down the source of the problem. Loopback allows the PHY to transmit received data and isolate different parts of the data path to see where the problem resolves. In a connection between two nodes, a problem can lie on the MAC interface of PHY1, MAC interface of PHY2, or MDI connection between PHYs. Loopbacks can isolate which one of the three is the problem.

Two different kinds of loopback exist on the DP83TC812 PHY: MAC side (digital loopback) and cable side (reverse loopback). These can be used together to check each segment of the data path. Most MACs have packet generating and checking capabilities. A packet can be transmitted, looped back, and received by the MAC and compared to the original value. If the packet is not received or packet errors occur when a segment has been isolated from the data path, we know that to be the problem segment. Below shows the two tests required to isolate such a problem.

First, a MAC side loopback (digital loopback) is enabled on PHY 1 (by writing 0x16 = 0x0104). Packets are then generated and checked by MAC1. If errors are present, the problem is located on the xMII interface between MAC1 and PHY1. If not, the problem is elsewhere.

GUID-20240106-SS0I-J0GT-18QS-0HPP16FHWRQF-low.png Figure 4-7 Utilizing Digital Loopback to Check Packets

Next, a cable side loopback is enabled on PHY2 (by writing 0x16 = 0x0110), and packets are once again generated and checked by MAC1. If the issue persists here but not in the previous step, the problem is located on the MDI interface between the two PHYs. If packet errors are still not present, the problem must be located on the xMII interface between PHY2 and MAC2.

GUID-20240106-SS0I-SWTF-VCDR-MTDDBVDQ6J8B-low.png Figure 4-8 Utilizing Reverse Loopback to Check Packets

Now that we know where the problem lies, targeted investigation can be had at this location. For problems with the MDI, see Section 4.7. For problems with the xMII, see Section 4.11.