we use dp83640 for ptp, most of time it works well.
but sometimes the clock change to abnormal random value. I use PTPClockRead to get the phy clock(sec. nanosec.).
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.
we use dp83640 for ptp, most of time it works well.
but sometimes the clock change to abnormal random value. I use PTPClockRead to get the phy clock(sec. nanosec.).
Hi weiping,
If possible, may I ask what parentage is the board working well?
When you mention "abnormal random value", may I ask what is the abnormal value of the clock signal?
If possible, could you share the scope capture waveform for both working case and non working case?
--
Regards,
Hillman Lin
Hi Hillman,
we design this board for ptp whose phy is dp83640.
the network works well all the time. But the timestamp in phy is not stable. Sometime the value which is read by PTPClockRead function, change to 0, 533 or 23643 and so on, a random value. the normal value is like 1715140871(sec) and 238474893(nsec).
At this time the network works well. So the timestamp in the udp packet of ptp is changed to a random value, while the time of slave boards is changed to a wrong time.
HI weiping,
I will discuss with the team and provide you a feedback later this week.
--
Regards,
Hillman Lin
Hi Weiping,
I discuss with the team. Here are some of the documents and debug approach:
--
Regards,
Hillman Lin