Re: [Linuxptp-users] sawtooth from linux timestamp?

2023-07-25 Thread jmfriedt
I have just realized that the freq field in the /var/log/messages log file of phc2sys is representative of the CPU (system clock) and should provide the information needed for synthonization. (and I now realize the 37 s from my previous post is UTC-TAI) Thanks, Jean-Michel -- JM Friedt, FEMTO-S

Re: [Linuxptp-users] sawtooth from linux timestamp?

2023-07-24 Thread jmfriedt
> So I would now like to try and synchonize the CPU clock on the PHC sorry for the typo, that should read "and synthonize the CPU clock", Jean-Michel ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lis

Re: [Linuxptp-users] sawtooth from linux timestamp?

2023-07-24 Thread jmfriedt
On Mon, 24 Jul 2023 09:17:10 +0200 Miroslav Lichvar wrote: > On Sat, Jul 22, 2023 at 04:12:32PM +0200, jmfriedt wrote: > > To do this I am connecting an Ettus Research X310 software defined > > radio to the CM4 and configuring to start collecting data upon > > detection

[Linuxptp-users] sawtooth from linux timestamp?

2023-07-22 Thread jmfriedt
Thanks to the help I received earlier I am now able to control the Compute Module 4 (CM4) on (White Rabbit) PTP, NTP or GPS. I am trying to understand the meaning of the 9 digits Linux is providing when reading an inode state with "stat -c %y" and how many decimals are actually relevant. To do thi

Re: [Linuxptp-users] 3.1.1 -> 4.0 evolution?

2023-07-10 Thread jmfriedt
> > I think that means the hardware cannot timestamp PTPv2.1 packets, > > only PTPv2.0 packets. > Something fixable by the white rabbit projet as it is a full fpga > implementation. Is it the WRS that needs to be updated? their web page says "Technically, the White Rabbit Network is a Bridged L

Re: [Linuxptp-users] 3.1.1 -> 4.0 evolution?

2023-07-10 Thread jmfriedt
... and I can confirm that the correction proposed at https://github.com/richardcochran/linuxptp/commit/2a2532d66121d0060b042c5bd6020a62153f1e0a namely setting the PTP_MINOR_VERSION from 1 to 0 in msg.h returns proper operation of the PTP client on the current git version of linuxptp. Thanks, Jean

[Linuxptp-users] 3.1.1 -> 4.0 evolution?

2023-07-10 Thread jmfriedt
I actually see a comment about this patch at https://github.com/richardcochran/linuxptp/commit/2a2532d66121d0060b042c5bd6020a62153f1e0a stating that "it seems that this commit breaks compatibility with some GMs, e.g., Microchip's TP4100. Tested with G.8275.2 profile. The reason being that this par

[Linuxptp-users] 3.1.1 -> 4.0 evolution?

2023-07-10 Thread jmfriedt
"don't you use automotive profile or 802.1 AS profiles?": I am not (yet) familiar enough with linuxptp to comment. I did not change anything to the settings, using the default configuration, whatever that is. I git bisected and the faulty commit is 2a2532d66121d0060b042c5bd6020a62153f1e0a is the

[Linuxptp-users] 3.1.1 -> 4.0 evolution?

2023-07-10 Thread jmfriedt
I have a Compute Module4 single board computer controlled using linuxptp to a White Rabbit switch as grand master. The client is controlled by the server with linuxptp 3.1.1 ptp4l[8729.388]: selected /dev/ptp0 as PTP clock ptp4l[8729.432]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE ptp4l[8