Re: [Linuxptp-users] linuxptp result doesn't match 1PPS measurement

On Fri, Sep 09, 2022 at 08:45:19AM +0800, Hamilton Alex wrote: > Hi, Richard: > I am not quite understand. I am using Calnex master-->board slave, if the > linuxptp print out is correct, that means local clock > has the same frequency and phase as master clock, then the 1PPS out should > near

Re: [Linuxptp-users] linuxptp result doesn't match 1PPS measurement

Hi, Richard: I am not quite understand. I am using Calnex master-->board slave, if the linuxptp print out is correct, that means local clock has the same frequency and phase as master clock, then the 1PPS out should near the reference 1PPS. why path asymmetry would affect the 1PPS out? Thanks

Re: [Linuxptp-users] [Linuxptp-devel] linuxptp result doesn't match 1PPS measurement

Hi, Miroslav: I am using calnex to test ptp. calnex can mimic the long path delay so it is reasonable. I am using switch chip, it has MAC timestamping and rx_delay, tx_delay are compensated. Thanks Alex Miroslav Lichvar 于2022年9月8日周四 21:26写道： > On Thu, Sep 08, 2022 at 07:41:53PM +0800, Hamilton

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

This is on a Kria K26 SOM, though granted, it's the development board KV260 version and not the production SOM. I can test on a production SOM if that's an issue. Here's the ptp4l entries in syslog: https://pastebin.com/54dqNgkB ntpd is stopped, chrony isn't installed. The output is the same

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

On Thu, Sep 08, 2022 at 10:21:09PM +, Brian Lilly wrote: > This is on a Kria K26 SOM, though granted, it's the development board KV260 > version and not the production SOM. I can test on a production SOM if that's > an issue. I would ask the vendor if/how they tested and validated the PTP

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

On Thu, Sep 08, 2022 at 02:39:13PM -0700, Jacob Keller wrote: > > > On 9/8/2022 7:14 AM, Brian Lilly wrote: > > I’m building a Petalinux image (Xilinx’ Yocto project based build system > > thing) that includes linuxPTP.  I have it starting as a service, and > > subsequently, I also have phc2sys

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

On Tue, Sep 06, 2022 at 08:20:48PM +, Brian Lilly wrote: > Some background: > > I'm building a Petalinux image (Xilinx' Yocto project based build system > thing) that includes linuxPTP. I have it starting as a service, and > subsequently, I also have phc2sys running to synchronize the

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

On 9/8/2022 7:14 AM, Brian Lilly wrote: > For reference, the output of phc2sys running for a good number of hours > with a 60 second report window: > > https://pastebin.com/YEra3LCK > >   > > *Brian Lilly / *Senior Firmware Engineer  > > Email:

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

For reference, the output of phc2sys running for a good number of hours with a 60 second report window: https://pastebin.com/YEra3LCK [cid:image001.png@01D8C352.92E38AF0] Brian Lilly / Senior Firmware Engineer Email: bri...@neuralynx.com From: Brian Lilly Sent: Tuesday, September 6, 2022 1:21

Re: [Linuxptp-users] Help with what is undoubtedly a problem with my configuration

Just throwing a ping out hoping that someone can shed a little light on this problem. Any takers? Get Outlook for Android From: Brian Lilly Sent: Tuesday, September 6, 2022 1:20:48 PM To: linuxptp-users@lists.sourceforge.net Subject:

Re: [Linuxptp-users] [Linuxptp-devel] linuxptp result doesn't match 1PPS measurement

On Thu, Sep 08, 2022 at 01:56:59PM +0200, Luigi 'Comio' Mantellini wrote: > - How is the 1PPS driven? Is there any reclocking logic? You need to ask > your FPGA-experts. +1 The circuit the produces the 1 PPS could well delay the signal by ten or more nanoseconds. Thanks, Richard

Re: [Linuxptp-users] linuxptp result doesn't match 1PPS measurement

On Thu, Sep 08, 2022 at 06:40:26AM -0700, Richard Cochran wrote: > On Thu, Sep 08, 2022 at 07:41:53PM +0800, Hamilton Alex wrote: > > > however, the 1pps time error is around 40 NS, which means my board is > > ahead of the reference for about 40NS, which doesn't match the result > > dumped by

Re: [Linuxptp-users] linuxptp result doesn't match 1PPS measurement

On Thu, Sep 08, 2022 at 07:41:53PM +0800, Hamilton Alex wrote: > however, the 1pps time error is around 40 NS, which means my board is > ahead of the reference for about 40NS, which doesn't match the result > dumped by ptp4l. > > anyone has met similar issue before? how to debug such issue?

Re: [Linuxptp-users] [Linuxptp-devel] linuxptp result doesn't match 1PPS measurement

On Thu, Sep 08, 2022 at 07:41:53PM +0800, Hamilton Alex wrote: > ptp4l[130171.662]: rms1 max2 freq-49 +/- 3 delay 9058 +/- 0 > my board has 1PPS output, I connect it to the master and compared with > reference PPS. > however, the 1pps time error is around 40 NS, which means my

Re: [Linuxptp-users] ts2phc error (ts2phc[20737.341]: PTP_EXTTS_REQUEST failed: Invalid argument

Dear Chris , We dont use external PPS, instead trying to get the local system clock's timestamp. *Setup:* master <--> eth0 (Device 1 -device acts as boundary clock) eth1 <---> etho(Device 2-slave) In this setup, eth0 is receiving timestamp from the master and updating local system clock on

Re: [Linuxptp-users] [Linuxptp-devel] linuxptp result doesn't match 1PPS measurement

Hi, Luigi: I am really thankful for your nice suggestions. 1. The delay for pps cable to calnex is already compensated in calnex configuration. 2. Yes, RX and TX path are asymmetry. the calnex can measure the T1, T4 and 2way time error, those time errors are only a few nano seconds, that means

[Linuxptp-users] linuxptp result doesn't match 1PPS measurement

Hi: I got an issue that linuxptp result doesn't match 1PPS measurement. my board is acting as a slave, the calnex is acting as a master with reference clock. after ptp4l runs, result is below, looks pretty good: ptp4l[130166.661]: rms1 max2 freq-50 +/- 4 delay 9059 +/- 0