John Efstathiades
|
ptpd very long synchronisation time
|
John Efstathiades
08/21/2019 12:30 PM
post119817
|
ptpd very long synchronisation time
Hello,
I am running ptpd with an Intel i210 to synchronise a PTP slave. The e1000 driver is started with the ptp flag so the
hardware timestamp support in the i210 is enabled.
I'm starting ptpd in foreground to see the statistics on the console as follows:
# ptpd -C -g -L -b wm0
The ptpd takes a very long time to synchronise the slave PTP time to the master - anything from several minutes to more
than 10 minutes. The time required to converge the clocks appears to be dependent on the initial clock offset. For
example, If the offset is tens or hundreds of milliseconds the convergence is linear until the offset less than one
millisecond at which point it takes a non-linear path, still slowly.
By comparison, Linux ptp4l takes about 30 seconds to synchronise the clocks regardless of the initial clock offset.
The PTP master in my configuration is another QNX system with an i210 interface with hardware timestamps enabled. The
same behaviour is seen if the master is a Linux machine running ptp4l.
I've tried E2E and P2P - behaviour is the same.
ptpd-avb appears to be broken - the slave does not syncrhonise at all.
I am using the generic x86_64 BSP on a Skylake target board. My ptpd is from package com.qnx.sdp.target.net.ptp/7.0.1031
.S201810151344
I have also tried teh new SDP 7.0.4 release (com.qnx.sdp.target.net.ptp/7.0.4247.S201906281113) but the behaviour is the
same.
Is the behaviour I am seeing normal for QNX ptpd?
If not, what is the expected QNX ptpd slave convergence time? 10 minutes is way too long to be useful.
Thanks,
John
|
|
|