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,
> 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
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 of the WR 1PPS rising
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 of the WR 1PPS rising edge. The SDR input is connected to the
> 1PPS to assess that the record
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
