DP83TD510E-EVM: DP83TD510E media converter using DP83825I

Part Number: DP83TD510E-EVM
Other Parts Discussed in Thread: DP83825I, DP83TD510E

Hello,

First we have made Media converter board based on ADIN1101 / DP83825I, where both PHYs were setup as RMII Slaves, and 50MHz Clock was sourced to both in the same time. That board works fine.

Next we've made another Media converter board where DP83TD510E was used instead of ADIN1101. The DP83TD510E is setup differently as RMII Master sourcing the clock, while DP83825I is the same as RMII Slave but its clock being sourced from DP83TD510E. On this board data is not going through, although both T1L and Ethernet link on it are up. The test setup is:

Raspberry PI – Media Converter (DP83825I, ADIN1101) – (DP83TD510E, DP83825I) Media Converter – Laptop. 

I would need an email address to provide accordingly schematic and register readings from both PHYs (DP83TD510E and DP83825I). 

Regards,
MTD

  • Hi, 

    You can email me at v-jaiswal@ti.com 

    First, let's try to narrow down the area responsible for this packet loss. You mentioned that the Ethernet link status on both T1L devices (510 and 1101) is reading as up (Register 0x0010 Bit 0), and the link status on both 825 devices is also reading as up (Register 0x0001 Bit 2). Assuming that all links described above are up, we can try setting up some loopbacks on the devices to check which part of the datapath is responsible for the packet loss.

    We can set up a Reverse Loopback on the 510 by writing register 0x0016 to 0x0110. This would send the data received by the 510 MDI interface back to the MDI. Through this, you could send a ping packet or something similar from the Raspberry Pi to the Laptop, which should be looped back and sent back to the Raspberry Pi. This would ensure that the datapath up until the 510 device, including the 825 x 1101 is good. You can check for the reception of this packet by using packet sniffer tools such as wireshark. 

    Similarly, we could set up MII Loopback by setting Register 0x0000 bit 14. This would send the data received from the 825 side over RMII back to the 825. This would help us see if the packet loss is because of the RMII interface between 825 and 510.

    Kindly also provide the schematic over email. I can go over it to make sure that nothing on the hardware level may be the root cause of this packet loss.

    Best,

    Vivaan

  • Hello Vivaan,

    Thank you for the prompt response.
    I have send you an email, along with the information for the progress made.

    Regards, 
    MTD

  • Let's continue the conversation over email. I will be closing this thread for now.