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.

PTPD2 Driver for dp83630

Other Parts Discussed in Thread: AM1808, DP83630

Hi,

   I am working on a AM1808 platform running Linux and want to use dp83630 to implement PHY time stamping. 

We are able to get the software version of PTPD 2 working, but we can't get it to use the hardware time stamp in the DP83630 PHYTER part.  We are trying to implement a layer4 UDP solution but have been unsuccessful so far.  We have been through over half a dozen repositories and no one has posted something that works.  I was hoping we could get a contact person at TI who knows this stuff in and out to fast track us to finding the problem.

Also, I cannot find any documentation indicating whether TI (or a third party) has a Linux driver that supports PTPD2 PHY time stamping. Please let me know if TI has such a driver.

In advance, thank you.

TG

  • Hi,

    While there is not a specific PTPd v2 driver for timestamping with the DP83630, there is some supporting collateral for the device.  Based on that collateral and what you have been able to accomplish with PTPd v2 at the software level, we can hopefully get you pointed in the right direction.

    In addition to the datasheet (http://www.ti.com/litv/pdf/snls335a), the best starting point would be the Software Development Guide (SDG) and the EPL C code reference library.  The SDG provides detailed information on our IEEE 1588 implementation.  The SDG and the EPL are available on the web at:

    http://www.ti.com/litv/zip/snlc036

    The EPL C code reference library includes functions that should help you understand the device functionality and should help in developing a driver.

    Could you give me some indication of what you have accomplished so far?  For example, what level of synchronization have you been able to achieve between a PTP Master and PTP Slave?  What Sync rate are you using?  Are you implementing a one-step clock or a two-step clock?

    Patrick