linuxptp-users — Open discussion on using the linuxptp software.

Re: [Linuxptp-users] Quarterly release schedule

[Bernie G. <be...@gm...>]

It would really be cool to read mode about your HIL setup. I would like to create a similar setup
regards,bernardo

Sent from fruit phone

> On Jun 9, 2023, at 8:42 AM, Richard Cochran <ric...@gm...> wrote:
> 
> Dear linuxptp users and developers,
> 
> Moving forward I am planning on making quarterly releases.  The next
> target dates are as follows.
> 
> September 5 2023
> December  5 2023
> March     5 2024
> June      5 2024
> 
> Inspired by Miroslav's wonderful linuxptp-testsuite, for yesterday's
> release I developed a hardware in the loop (HIL) test framework.
> Previously I had had a collection of smoke tests in the form of notes
> with hardware setup, command lines, and expected results, and running
> the tests was a major chore.
> 
> With the HIL framework in place, I am able run the smoke tests very
> easily, and that allows me to release the software with confidence.
> 
> I think the version numbering will continue with 4.1, 4.2, and so on.
> We can bump the major version to 5 when we get to 4.12.
> 
> Thanks,
> Richard
> 
> 
> 
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users

[Linuxptp-users] Quarterly release schedule

[Richard C. <ric...@gm...>]

Dear linuxptp users and developers,

Moving forward I am planning on making quarterly releases.  The next
target dates are as follows.

September 5 2023
December  5 2023
March     5 2024
June      5 2024

Inspired by Miroslav's wonderful linuxptp-testsuite, for yesterday's
release I developed a hardware in the loop (HIL) test framework.
Previously I had had a collection of smoke tests in the form of notes
with hardware setup, command lines, and expected results, and running
the tests was a major chore.

With the HIL framework in place, I am able run the smoke tests very
easily, and that allows me to release the software with confidence.

I think the version numbering will continue with 4.1, 4.2, and so on.
We can bump the major version to 5 when we get to 4.12.

Thanks,
Richard

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Richard C. <ric...@gm...>]

On Fri, Jun 09, 2023 at 12:28:29PM +0530, Tony Josi wrote:

> tony@tony-IdeaCenter:~$ sudo ethtool -T enx0c379
> Time stamping parameters for enx0c379:
> Cannot get device time stamping settings: No such device

You don't have a network interface of that name.

You can do

   cat /proc/net/dev

to see the interfaces that exist on your system.

Thanks,
Richard

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Tony J. <ton...@gm...>]

Thanks for the reply Richard,

This is the response for:     ethtool -T enox0c379

tony@tony-IdeaCenter:~$ sudo ethtool -T enx0c379
Time stamping parameters for enx0c379:
Cannot get device time stamping settings: No such device
tony@tony-IdeaCenter:~$

Regards,
*Tony*



On Fri, Jun 9, 2023 at 11:51 AM Richard Cochran <ric...@gm...>
wrote:

> On Thu, Jun 08, 2023 at 09:34:33PM +0530, Tony Josi wrote:
> > How can I specify the PTP device, Isnt it the network interface that I
> have
> > already specified?
>
> Yes, you did specify the interface/ptp device, and that should work.
>
> What does this show?
>
>    ethtool -T enox0c379
>
> Thanks,
> Richard
>

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Richard C. <ric...@gm...>]

On Thu, Jun 08, 2023 at 09:34:33PM +0530, Tony Josi wrote:
> How can I specify the PTP device, Isnt it the network interface that I have
> already specified?

Yes, you did specify the interface/ptp device, and that should work.

What does this show?

   ethtool -T enox0c379

Thanks,
Richard

[Linuxptp-users] [announce] version 4.0 released

[Richard C. <ric...@gm...>]

Dear linuxptp users and developers,

I am happy to announce the release of Version 4.0 of linuxptp, coming
almost three years since the previous release.  I pushed tag v4.0 to
the various git mirrors and uploaded a tar ball to SF.

The number of individual contributors has nearly doubled since the
last release.  Thank you to Alexander, Amar, Changqing, Christopher,
Cliff, David, Erez, Eyal, Grygorii, Hangbin, Heiko, Izunna, Jacob,
Juergen, Karthikkumar, Kosta, Lars, Luigi, Maciek, Magnus, Marcin,
Martin, Miroslav, Nikhil, Rahul, Sebastian, SyncMonk, Tan Tee,
Tomofumi, Vadim, Vincent, Vladimir, Wojtek, Wong Vee, and Yangbo.

The short log is appended, below.

Thanks,

Richard


Alexander Bulimov via Linuxptp-devel (3):
      Add PORT_SERVICE_STATS_NP management TLV
      Add UNICAST_MASTER_TABLE_NP management TLV
      Add new management TLVs to pmc.8

Amar Subramanyam (1):
      Added support for Standard Baudrates supported by GNSS receivers

Amar Subramanyam via Linuxptp-devel (2):
      Log optimization for ptp4l in jbod and client only mode (clientOnly=1 and boundary_clock_jbod=1)
      Log optimization for ptp4l in jbod and client only mode (clientOnly=1 and boundary_clock_jbod=1)

Changqing Li (1):
      makefile: use conditional assignment for KBUILD_OUTPUT

Christopher S M Hall (1):
      Set controlField to zero in message headers

Cliff Spradlin via Linuxptp-devel (2):
      port: Cache display name for logs.
      Improve port-related log messages.

Erez Geva (7):
      Ensure TLV_PORT_STATS_NP statistics uses little endian.
      Fix SLAVE_ONLY TLV
      Add master only management TLV
      TLV management messages need to be aligned to 16 bits.
      Add new managements TLVs get size.
      Fix management TLV print.
      Add new ptp capability.

Eyal Itkin via Linuxptp-devel (1):
      Avoid switching PHC when phc_index is negative

Grygorii Strashko (3):
      phc2sys: add dbg print for clock state change events
      phc2sys: fix BC sync fault when port in uncalibrated state
      util: add SIGHUP handling

Hangbin Liu (3):
      ptp4l: init iface->ts_label when interface created
      port: refactor port_link_status
      ptp4l: add VLAN over bond support

Heiko Thiery (1):
      missing.h: uclic-ng has clock_nanosleep support since v1.0.31

Izunna Otiji (1):
      ptp4l: Add profile_id configuration support for G.8275.1 and G.8275.2.

Jacob Keller (6):
      Increase the default tx_timestamp_timeout to 10
      phc2sys: move read_phc into clock_adj.c
      phc_ctl: replace calculate_offset with clockadj_compare
      port: don't clear fault if link is down
      config: allow fractional freq_est_interval
      servo: stop rounding initial frequency to nearest ppb

Juergen Werner (2):
      tlv: Fix byte reordering in ScaledNs
      Implement push notification for TIME_STATUS_NP

Karthikkumar V (1):
      Clock Class Threshold Feature addition for PTP4L

Karthikkumar V via Linuxptp-devel (1):
      Delay Response Timeout Feature addition for PTP4L

Kosta Demirev (1):
      Check 'print_log' before arguments are evaluated, not after.

Lars Munch (5):
      Set domainNumber for telecom examples
      ts2phc: Fix uninitialized variable in nmea_scan_rmc
      ts2phc: Close socket on peer shutdown
      ts2phc: Update leapfile documentation
      ts2phc: Add serial baudrate option

Luigi Mantellini (1):
      The PortId is defined as a couple of ClockId (an 8-bytes opaque) and the PortNumber (UInterger16).

Maciej Machnikowski (3):
      ts2phc: Rename pps_sink to tod_sink in main()
      ts2phc: Add option to specify the ToD source in the config file
      ts2phc: Use system time as the default ToD source

Maciek Machnikowski (12):
      phc2sys: Allow multiple sink clocks
      phc2sys: Add support for free-running mode
      phc2sys: Update TAI to UTC offset in manual
      ts2phc: Update default lstab expiry date
      lstab: Add LSTAB_EXPIRED result
      lstab: move update_leapsecond_table function to lstab
      ts2phc: Fix generic pps source when tai offset is not set in OS
      tz2alt: Add tz2alt to .gitignore
      ts2phc: Prevent reporting poll error when received termination signal
      ts2phc: Fix potential null-pointer dereference
      lstab: Update leapfile validity
      ntpshm: Invalidate SHM data before releasing the servo

Magnus Armholt (1):
      Strip Parallel Redundancy Protocol (PRP) trailer

Marcin Miklas (1):
      Fix --initial_delay for automotive profile

Martin Pecka (3):
      UDS: added option to set file mode for the created socket.
      UDS: allow specifying different file mode for the read-only socket.
      Fix detection of VLAN over bond support in case the driver does not support SIOCGHWTSTAMP ioctl.

Miroslav Lichvar (57):
      phc2sys: Remove superfluous code.
      phc2sys: Postpone adding of servo to clock.
      port: Don't assume transport from port number.
      port: Ignore non-management messages on UDS port.
      clock: Don't allow COMMAND action on non-UDS port.
      clock: Rename UDS variables to read-write.
      clock: Add read-only UDS port for monitoring.
      timemaster: Set uds_ro_address for ptp4l instances.
      sk: Don't return error for zero-length messages.
      Avoid unaligned pointers to packed members.
      pmc: Fix printed totalCorrectionField.
      Avoid undefined integer operations.
      Revert "phc2sys: Expand the validation of the PPS mode."
      tc: Fix length of follow-up message of one-step sync.
      clock: Reset state when switching port with same best clock.
      clock: Reset clock check on best clock/port change.
      port: Don't check timestamps from non-slave ports.
      port: Don't renew raw transport.
      clockcheck: Increase minimum interval.
      config: Add workaround for glibc getopt_long().
      Fix quoting in ptp4l man page.
      lstab: Close file after reading.
      clock: Accept new UTC offset after leap second.
      clock: Print info message when leap flags change.
      clock: Clear leap flags after leap second.
      clock: Notify servo about leap second on UTC hardware clock.
      clock: Split update of leap status from clock_time_properties().
      pmc: Initialize reserved field in management_tlv_datum.
      rtnl: Fix rtnl_rtattr_parse() to process max attribute.
      rtnl: Add function to detect virtual clocks.
      Add support for binding sockets to virtual clocks.
      config: Add port-specific phc_index option.
      port: Check for virtual clocks.
      tlv: Add PORT_HWCLOCK_NP.
      phc2sys: Use PHC index from PORT_HWCLOCK_NP.
      timemaster: Add support for virtual clocks.
      clockadj: Change clockadj_compare() to return errno.
      sysoff: Change sysoff_measure() to return errno.
      sysoff: Change log level of ioctl error messages.
      sysoff: Retry on EBUSY when probing supported ioctls.
      phc2sys: Don't exit when reading of PHC fails with EBUSY.
      port: Disable PHC switch with vclocks.
      sk: Handle EINTR when waiting for transmit timestamp.
      phc2sys: Add clocks after processing configuration.
      Drop support for old kernels returning zero frequency.
      Don't accept errors in clockadj_get_freq().
      Extend clockcheck to check for changes in frequency.
      config: Fix -Wformat-truncation warnings.
      port: Avoid faults with vclocks and PHC from command line.
      Remove obsolete statement in ptp4l man page.
      Add refclock_sock servo.
      timemaster: Replace shm_segment with refclock_id.
      timemaster: Use refclock_sock servo with chrony.
      unicast: Avoid undefined integer shifts.
      port: Don't switch to PHC with SW timestamping.
      Clear pending errors on sockets.
      clock: Fix summary interval in free-running mode.

Nikhil Gupta (1):
      lstab: Bring expiration up to date.

Rahul Rameshbabu via Linuxptp-devel (2):
      Improve efficiency of nullf servo synchronization
      Fix SERVO_JUMP docstring comment

Richard Cochran (78):
      Introduce the PMC agent module.
      pmc_agent: Rename pmc_node to something more descriptive.
      pmc_agent: Hide the implementation.
      Find a better home for the management TLV ID helper function.
      Find a better home for the management TLV data helper function.
      Clarify the documentation of the management TLV ID helper function.
      Introduce error codes for the run_pmc method.
      pmc_agent: Convert the subscribe method into the canonical form.
      pmc_agent: Simplify the update method.
      pmc_agent: Simplify logic in update method.
      pmc_agent: Remove bogus comparison between last update and now.
      pmc_agent: Perform time comparison using positive logic.
      pmc_agent: Rename the update method and attempt to document it.
      Avoid setting clock frequency when free running.
      Update the description of the time_stamping configuration option.
      rtnl: Fix trivial spelling error in the name of a helper function.
      phc2sys: Fix null pointer de-reference in manual mode.
      pmc_agent: Convert the method that queries TAI-UTC offset into the canonical form.
      pmc_agent: Convert the method that queries the port properties.
      pmc_agent: Generalize the method that queries the local clock identity.
      pmc_agent: Simplify the method that gets of the number of local ports.
      phc2sys: Don't duplicate the command line arguments.
      phc2sys: Rename PMC agent pointer from node to agent.
      phc2sys: Replace hard coded tests with a readable helper function.
      phc2sys: Validate the PPS mode right away.
      phc2sys: Expand the validation of the PPS mode.
      phc2sys: Replace magical test with a proper test.
      phc2sys: Replace yet another magical test with a proper test.
      phc2sys: Move static configuration to its own subroutine.
      pmc_agent: Let the update method poll for push events.
      phc2sys: Simplify the main loop.
      pmc_agent: Remove an obsolete method.
      phc2sys: Fix regression in the automatic mode.
      Update the unicast subscriptions when the GM changes.
      phc2sys: Ensure PHC source when using PPS mode.
      phc2sys: Update man page to reflect the new restriction on the PPS mode.
      phc2sys: Convert man page to source/sink terminology.
      phc2sys: Convert man page to client/server terminology.
      ptp4l: Convert man page to client/server terminology.
      ts2phc: Convert man page to source/sink terminology.
      phc2sys: Convert usage messages to time source/sink terminology.
      ptp4l: Convert usage messages to client/server terminology.
      ts2phc: Convert usage message to time source/sink terminology.
      Check for deprecated "long" options on the command line.
      Deprecate the slaveOnly option in favor of clientOnly.
      Convert the example configuration files over to the new clientOnly option.
      Update man pages to reflect the new clientOnly option.
      Deprecate the masterOnly option in favor of serverOnly.
      Convert the example configuration files over to the new serverOnly option.
      Update man page to reflect the new serverOnly option.
      Revert "phc2sys: Ensure PHC source when using PPS mode."
      tlv: Fix coding style.
      Prevent client ports getting stuck in the UNCALIBRATED state.
      Validate the messageLength field of incoming messages.
      Rename management ID macros.
      Maintain one Announce sequence counter per destination address.
      Maintain one Sync sequence counter per destination address.
      Fix up alphetical order in port_private header file.
      Alphabetize configuration options in the ptp4l man page.
      Remove stray copy/pasteo from the phc2sys man page.
      Alphabetize configuration options in the phc2sys man page.
      Alphabetize configuration options in the pmc man page.
      Alphabetize configuration options in the ts2phc man page.
      man pages: Bump date.
      Accept the full range for domainNumber.
      tlv: Encode and decode power profile TLVs.
      Introduce the power profile.
      Add a custom management message for power profile settings.
      tlv: Encode and decode alternate time offset indicator TLVs.
      Prepare clock based storage of up to four time zones.
      Add the ALTERNATE_TIME_OFFSET_PROPERTIES management message.
      Add the ALTERNATE_TIME_OFFSET_NAME management message.
      Implement the ALTERNATE_TIME_OFFSET_ENABLE management message.
      pmc: Convert internal helper function into global method.
      Introduce a time zone helper program.
      power profile: Fix regression in the default configuration file.
      ts2phc: Fix memory leak on initial error path.
      Version 4.0

Sebastian Andrzej Siewior (1):
      raw: Use BPF filter based on tcpdump syntax.

SyncMonk Technologies (5):
      G.8275.2 support for delay_mechanism NO_MECHANISM
      function to support get interface speed via ethtool
      adding speed field information for interface
      organization TLV support for interface rate
      adding delay asymmetry calculation

Tan Tee Min (1):
      msg: append TLV onto all PTP event messages

Vadim Fedorenko via Linuxptp-devel (3):
      unicast: Update announce timer when renew
      unciast_client: trigger BMCA upon CANCEL receive
      port: start sync rx timer on grant

Vincent Cheng (10):
      port: Fix link down/up to continue using phc_index set from command line -p option.
      clock: Introduce step_window to free run x Sync events after a clock step.
      unicast: Add support to check if message was received from an entry in the unicast master table.
      unicast: Add support to send CANCEL_UNICAST_TRANSMISSION TLVs.
      port: unicast client - do not add master to foreign master table if not in the unicast master table.
      port: cancel unicast transmission when closing port.
      unicast_client: stop sending abnormal contract cancel requests
      unicast_client: fix checkpatch ERROR: trailing whitespace
      unicast_client: cancel sync/delay_response on UC_EV_UNSELECTED event
      clock: Fix stale clock parent pid usage after best master change

Vladimir Oltean (20):
      phc2sys: break long lines in the PTP management message accessors
      phc2sys: extract PMC functionality into a smaller struct pmc_node
      phc2sys: make PMC functions non-static
      phc2sys: break out pmc code into pmc_common.c
      util: fix dangling file descriptors on the error path of posix_clock_open
      util: attempt to resolve symlinks to the PHC device in posix_clock_open
      pmc_agent: make pmc_agent_query_port_properties take an enum port_state argument
      ts2phc: rename source code files ("master" to "source", "slave" to "sink")
      ts2phc: rename "slave clocks" to "PPS sinks"
      ts2phc: rename "master" to "source"
      ts2phc: create a private data structure
      ts2phc: instantiate a full clock structure for every PPS sink
      ts2phc: instantiate a full clock structure for every PPS source of the PHC kind
      util: import port_state_normalize() logic from phc2sys
      ts2phc: instantiate a pmc agent
      ts2phc_slave: print offset to the source clock
      ts2phc: split PPS sink poll from servo loop
      ts2phc: reconfigure sync direction by subscribing to ptp4l port events
      ts2phc: allow PHC PPS sources to be synchronized
      ts2phc_phc_pps_source: make use of new kernel API for perout waveform

Wojtek Wasko via Linuxptp-devel (4):
      clockadj: return error if failed to adjust clock
      ptp4l: reset servo if failed to discipline clock
      phc2sys: reset servo if failed to discipline clock
      ts2phc: reset servo if failed to discipline clock

Wong Vee Khee (1):
      phc_ctl: Fix incorrect memset in do_cmp()

Yangbo Lu (2):
      Bump to IEEE 1588-2019 version
      lstab: update expiration to 28 December 2021

davidjm via Linuxptp-devel (1):
      Don't re-arm fault clearing timer on unrelated netlink events

yos...@fu... (1):
      Fix the descriptions of "G.8275.portDS.localPriority" and "G.8275.defaultDS.localPriority" in ptp4l man page.

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Elder C. <eld...@ti...>]

I suggest you try software timestamp (add -S switch). I have a panel PC at
the office where I installed Ubuntu and to my surprise there was no
hardware timestamp support (Intel CPU but Realtek Gbit/s
Ethernet controllers) whereas on another AMD based SBC with Intel Ethernet
controllers, hardware timestamp worked right away with Ubuntu unmodified
installation. Maybe your PC has one of these Realtek controllers as well
(from memory, when I researched on it, there were issues with Realtek
controllers and PHC support) or another controller not well supported.

HTH.





Em qui., 8 de jun. de 2023 às 13:06, Tony Josi <ton...@gm...>
escreveu:

> Hi,
>
> I'm trying to use PTP on my linux machine:
>
> *OS information:*
> Operating System: Ubuntu 20.04.5 LTS
> Kernel: Linux 5.15.0-71-generic
> Architecture: x86-64
>
> This is the default official Ubuntu version that I have installed from the
> .iso image available from the Ubuntu website. Not a custom built OS.
>
> I have installed *linuxptp *with the following command:
> sudo apt install linuxptp
>
> But when I try running ptp4l with the following command:
> sudo ptp4l -i enox0c379 -m -2 -P -l 6 -q -f $HOME/ptp_config.cfg
>
> I get the following error message:
>
> ptp4l[890.371]: ioctl SIOCETHTOOL failed: No such device
> ptp4l[890.371]: PTP device not specified and automatic determination is
> not supported. Please specify PTP device.
> failed to create a clock
>
> Here is the contents of $HOME/ptp_config.cfg:
>
> [global]
>     tx_timestamp_timeout    400
>     logMinPdelayReqInterval  3
>     logSyncInterval          -4
>     logAnnounceInterval      0
>
> How can I specify the PTP device, Isnt it the network interface that I
> have already specified?
>
> Thanks for your help
> Regards,
> Tony
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Tony J. <ton...@gm...>]

Thanks,

I will try that. Where can I update this configuration?

Also when I check if my network interface supports PTP I get the following
message. I think my NIC is not PTP capable?

tony@tony-IdeaCenter:~$ ifconfig -s
Iface MTU RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg
enp3s0 1500 449521 0 0 0 1398083 0 0 0 BMRU
enx0c379 1500 0 0 0 0 978 0 0 0 BMRU
lo 65536 11220 0 0 0 11220 0 0 0 LRU
tony@tony-IdeaCenter:~$ sudo ethtool -T enx0c379
Time stamping parameters for enx0c379:
Cannot get device time stamping settings: No such device
tony@tony-IdeaCenter:~$

Regards,
*Tony*




On Thu, Jun 8, 2023 at 10:19 PM Timothy Huang <tim...@ed...> wrote:

> Hi,
>
> I'm guessing your PTP module is not loaded in the kernel you are running?
> Have you tried manually loading the PTP module yet?
>
> To compile it as a built-in module, I think you need to enable these
> configs in the kernel.
>
> [image: image.png]
>
> Regards,
> Tim
>
> On Thu, Jun 8, 2023 at 9:43 AM Tony Josi <ton...@gm...> wrote:
>
>> Thanks Timothy for the reply,
>>
>> Unfortunately I can't find any PTP devices inside the /dev/ folder.
>>
>> Im trying the following demo:
>> https://dev.ti.com/tirex/explore/content/mcu_plus_sdk_am243x_08_06_00_43/docs/api_guide_am243x/EXAMPLES_ENET_LAYER2_MULTI_CHANNEL_PTP.html
>> Using the TI AM243x LP board.
>>
>> On the board side I'm getting the logs printed till above the line: Doing
>> first adjustment
>>
>> The board is connected directly to the Linux PC via a USB to Ethernet
>> adapter and LAN cable.
>>
>> I'm wondering if there is something that should be enabled in the Kernel
>> to get it recognised?
>>
>> Regards,
>> *Tony*
>>
>>
>>
>>
>> On Thu, Jun 8, 2023 at 9:54 PM Timothy Huang <tim...@ed...> wrote:
>>
>>> Hi Tony,
>>>
>>> I can reproduce your problem by manually bringing down the ethernet
>>> interface ptp4l is using. Did you check whether your ethernet interface is
>>> up or not? In addition to that, you should see the PTP device name by "ls
>>> /dev/ptp*" if your interface is up.
>>>
>>> Thanks,
>>> Tim
>>>
>>> On Thu, Jun 8, 2023 at 9:05 AM Tony Josi <ton...@gm...> wrote:
>>>
>>>> Hi,
>>>>
>>>> I'm trying to use PTP on my linux machine:
>>>>
>>>> *OS information:*
>>>> Operating System: Ubuntu 20.04.5 LTS
>>>> Kernel: Linux 5.15.0-71-generic
>>>> Architecture: x86-64
>>>>
>>>> This is the default official Ubuntu version that I have installed from
>>>> the .iso image available from the Ubuntu website. Not a custom built OS.
>>>>
>>>> I have installed *linuxptp *with the following command:
>>>> sudo apt install linuxptp
>>>>
>>>> But when I try running ptp4l with the following command:
>>>> sudo ptp4l -i enox0c379 -m -2 -P -l 6 -q -f $HOME/ptp_config.cfg
>>>>
>>>> I get the following error message:
>>>>
>>>> ptp4l[890.371]: ioctl SIOCETHTOOL failed: No such device
>>>> ptp4l[890.371]: PTP device not specified and automatic determination is
>>>> not supported. Please specify PTP device.
>>>> failed to create a clock
>>>>
>>>> Here is the contents of $HOME/ptp_config.cfg:
>>>>
>>>> [global]
>>>>     tx_timestamp_timeout    400
>>>>     logMinPdelayReqInterval  3
>>>>     logSyncInterval          -4
>>>>     logAnnounceInterval      0
>>>>
>>>> How can I specify the PTP device, Isnt it the network interface that I
>>>> have already specified?
>>>>
>>>> Thanks for your help
>>>> Regards,
>>>> Tony
>>>> _______________________________________________
>>>> Linuxptp-users mailing list
>>>> Lin...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>>>>
>>>

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Timothy H. <tim...@ed...>]

Hi Tony,

I can reproduce your problem by manually bringing down the ethernet
interface ptp4l is using. Did you check whether your ethernet interface is
up or not? In addition to that, you should see the PTP device name by "ls
/dev/ptp*" if your interface is up.

Thanks,
Tim

On Thu, Jun 8, 2023 at 9:05 AM Tony Josi <ton...@gm...> wrote:

> Hi,
>
> I'm trying to use PTP on my linux machine:
>
> *OS information:*
> Operating System: Ubuntu 20.04.5 LTS
> Kernel: Linux 5.15.0-71-generic
> Architecture: x86-64
>
> This is the default official Ubuntu version that I have installed from the
> .iso image available from the Ubuntu website. Not a custom built OS.
>
> I have installed *linuxptp *with the following command:
> sudo apt install linuxptp
>
> But when I try running ptp4l with the following command:
> sudo ptp4l -i enox0c379 -m -2 -P -l 6 -q -f $HOME/ptp_config.cfg
>
> I get the following error message:
>
> ptp4l[890.371]: ioctl SIOCETHTOOL failed: No such device
> ptp4l[890.371]: PTP device not specified and automatic determination is
> not supported. Please specify PTP device.
> failed to create a clock
>
> Here is the contents of $HOME/ptp_config.cfg:
>
> [global]
>     tx_timestamp_timeout    400
>     logMinPdelayReqInterval  3
>     logSyncInterval          -4
>     logAnnounceInterval      0
>
> How can I specify the PTP device, Isnt it the network interface that I
> have already specified?
>
> Thanks for your help
> Regards,
> Tony
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Timothy H. <tim...@ed...>]

Hi,

I'm guessing your PTP module is not loaded in the kernel you are running?
Have you tried manually loading the PTP module yet?

To compile it as a built-in module, I think you need to enable these
configs in the kernel.

[image: image.png]

Regards,
Tim

On Thu, Jun 8, 2023 at 9:43 AM Tony Josi <ton...@gm...> wrote:

> Thanks Timothy for the reply,
>
> Unfortunately I can't find any PTP devices inside the /dev/ folder.
>
> Im trying the following demo:
> https://dev.ti.com/tirex/explore/content/mcu_plus_sdk_am243x_08_06_00_43/docs/api_guide_am243x/EXAMPLES_ENET_LAYER2_MULTI_CHANNEL_PTP.html
> Using the TI AM243x LP board.
>
> On the board side I'm getting the logs printed till above the line: Doing
> first adjustment
>
> The board is connected directly to the Linux PC via a USB to Ethernet
> adapter and LAN cable.
>
> I'm wondering if there is something that should be enabled in the Kernel
> to get it recognised?
>
> Regards,
> *Tony*
>
>
>
>
> On Thu, Jun 8, 2023 at 9:54 PM Timothy Huang <tim...@ed...> wrote:
>
>> Hi Tony,
>>
>> I can reproduce your problem by manually bringing down the ethernet
>> interface ptp4l is using. Did you check whether your ethernet interface is
>> up or not? In addition to that, you should see the PTP device name by "ls
>> /dev/ptp*" if your interface is up.
>>
>> Thanks,
>> Tim
>>
>> On Thu, Jun 8, 2023 at 9:05 AM Tony Josi <ton...@gm...> wrote:
>>
>>> Hi,
>>>
>>> I'm trying to use PTP on my linux machine:
>>>
>>> *OS information:*
>>> Operating System: Ubuntu 20.04.5 LTS
>>> Kernel: Linux 5.15.0-71-generic
>>> Architecture: x86-64
>>>
>>> This is the default official Ubuntu version that I have installed from
>>> the .iso image available from the Ubuntu website. Not a custom built OS.
>>>
>>> I have installed *linuxptp *with the following command:
>>> sudo apt install linuxptp
>>>
>>> But when I try running ptp4l with the following command:
>>> sudo ptp4l -i enox0c379 -m -2 -P -l 6 -q -f $HOME/ptp_config.cfg
>>>
>>> I get the following error message:
>>>
>>> ptp4l[890.371]: ioctl SIOCETHTOOL failed: No such device
>>> ptp4l[890.371]: PTP device not specified and automatic determination is
>>> not supported. Please specify PTP device.
>>> failed to create a clock
>>>
>>> Here is the contents of $HOME/ptp_config.cfg:
>>>
>>> [global]
>>>     tx_timestamp_timeout    400
>>>     logMinPdelayReqInterval  3
>>>     logSyncInterval          -4
>>>     logAnnounceInterval      0
>>>
>>> How can I specify the PTP device, Isnt it the network interface that I
>>> have already specified?
>>>
>>> Thanks for your help
>>> Regards,
>>> Tony
>>> _______________________________________________
>>> Linuxptp-users mailing list
>>> Lin...@li...
>>> https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>>>
>>

Re: [Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Tony J. <ton...@gm...>]

Thanks Timothy for the reply,

Unfortunately I can't find any PTP devices inside the /dev/ folder.

Im trying the following demo:
https://dev.ti.com/tirex/explore/content/mcu_plus_sdk_am243x_08_06_00_43/docs/api_guide_am243x/EXAMPLES_ENET_LAYER2_MULTI_CHANNEL_PTP.html
Using the TI AM243x LP board.

On the board side I'm getting the logs printed till above the line: Doing
first adjustment

The board is connected directly to the Linux PC via a USB to Ethernet
adapter and LAN cable.

I'm wondering if there is something that should be enabled in the Kernel to
get it recognised?

Regards,
*Tony*




On Thu, Jun 8, 2023 at 9:54 PM Timothy Huang <tim...@ed...> wrote:

> Hi Tony,
>
> I can reproduce your problem by manually bringing down the ethernet
> interface ptp4l is using. Did you check whether your ethernet interface is
> up or not? In addition to that, you should see the PTP device name by "ls
> /dev/ptp*" if your interface is up.
>
> Thanks,
> Tim
>
> On Thu, Jun 8, 2023 at 9:05 AM Tony Josi <ton...@gm...> wrote:
>
>> Hi,
>>
>> I'm trying to use PTP on my linux machine:
>>
>> *OS information:*
>> Operating System: Ubuntu 20.04.5 LTS
>> Kernel: Linux 5.15.0-71-generic
>> Architecture: x86-64
>>
>> This is the default official Ubuntu version that I have installed from
>> the .iso image available from the Ubuntu website. Not a custom built OS.
>>
>> I have installed *linuxptp *with the following command:
>> sudo apt install linuxptp
>>
>> But when I try running ptp4l with the following command:
>> sudo ptp4l -i enox0c379 -m -2 -P -l 6 -q -f $HOME/ptp_config.cfg
>>
>> I get the following error message:
>>
>> ptp4l[890.371]: ioctl SIOCETHTOOL failed: No such device
>> ptp4l[890.371]: PTP device not specified and automatic determination is
>> not supported. Please specify PTP device.
>> failed to create a clock
>>
>> Here is the contents of $HOME/ptp_config.cfg:
>>
>> [global]
>>     tx_timestamp_timeout    400
>>     logMinPdelayReqInterval  3
>>     logSyncInterval          -4
>>     logAnnounceInterval      0
>>
>> How can I specify the PTP device, Isnt it the network interface that I
>> have already specified?
>>
>> Thanks for your help
>> Regards,
>> Tony
>> _______________________________________________
>> Linuxptp-users mailing list
>> Lin...@li...
>> https://lists.sourceforge.net/lists/listinfo/linuxptp-users
>>
>

[Linuxptp-users] ioctl SIOCETHTOOL failed: No such device

[Tony J. <ton...@gm...>]

Hi,

I'm trying to use PTP on my linux machine:

*OS information:*
Operating System: Ubuntu 20.04.5 LTS
Kernel: Linux 5.15.0-71-generic
Architecture: x86-64

This is the default official Ubuntu version that I have installed from the
.iso image available from the Ubuntu website. Not a custom built OS.

I have installed *linuxptp *with the following command:
sudo apt install linuxptp

But when I try running ptp4l with the following command:
sudo ptp4l -i enox0c379 -m -2 -P -l 6 -q -f $HOME/ptp_config.cfg

I get the following error message:

ptp4l[890.371]: ioctl SIOCETHTOOL failed: No such device
ptp4l[890.371]: PTP device not specified and automatic determination is not
supported. Please specify PTP device.
failed to create a clock

Here is the contents of $HOME/ptp_config.cfg:

[global]
    tx_timestamp_timeout    400
    logMinPdelayReqInterval  3
    logSyncInterval          -4
    logAnnounceInterval      0

How can I specify the PTP device, Isnt it the network interface that I have
already specified?

Thanks for your help
Regards,
Tony

Re: [Linuxptp-users] ptp4l passive phc synchronization with active phc in linux bonding

[Chris C. <ch...@ch...>]

> From: shashank varshney <sha...@gm...>

> As mentioned, PTP switchover from one NIC port to another is not seamless
> when ports belong to different NICs with different hardware clocks.

That seems like a good application for devices which can synchronize their
hardware clocks.

> I am looking to utilize PTP for very time sensitive use cases like 5G
> wireless, stock markets, etc. which desire High Availability and
> redundancy at NIC port level while utilizing PTP.

That is why 5G wireless and stock markets typically use hardware with
support for external clock input (e.g. Intel 10Gb or 25Gb cards with
external clock and PPS inputs), and/or custom FPGA based designs.

> This is going to be a significant use case if we would like to move to
> open sourced environment and LinuxPTP is going to have significant
> role to play to achieve this aspect.

I'm not sure who you are thinking is going "to move" to an open source
environment, but in my previous employment I worked on an early roll out
of 5G equipment from one of the largest telco operators in the US, and
that environment was using nothing but open source.
See for example
https://www.redhat.com/en/en/topics/5g-networks/what-is-open-ran
or any of the other articles on OpenRAN and vRAN which have been published
in the last several years.

> Can someone help me with getting this functionality of seamless switchover
> by synchronizing Active Port PHC with PTP GM and then synchronizing
> system clock and standby PHCs with active PHC?

If you are purchasing large quantities of hardware for 5G or financial
trading applications then I am sure your device or system vendor would be
willing to help you, or perhaps Red Hat, SuSE, etc. if you are purchasing
commercial support for your OS installation.

First you will need to define your synchronization requirements (if it is
truly a single PHP used between multiple ports that is not really a
concern, but if you have two separate PHP that are synchronized you will
need to define your acceptable timing budget.

You then need to define specifics about acceptable switchover behavior
(timing, which software entity makes the decision about if/when to switch
paths, etc.).

After you have those requirements defined, then you can begin to evaluate
different hardware architecture choices and see what can possibly meet
your requirements.

After you have hardware in hand which should be able to meet  your
requirements based on specifications, research, communication with the
vendors, etc. you can setup some proof-of-concept systems and start
working with the software to see if you can actually achieve in practice
what the specifications imply you should be able to.

By that point you may have some specific questions about ptp4l that you
have not been able to understand from reading the documentation and
looking at the source code.  Someone on the list can probably help answer
your specific questions.

The open ended nature of your question does not inspire a lot of
confidence that you have gone through the first steps outlined above yet.

-- 
Chris Caudle

Re: [Linuxptp-users] ptp4l passive phc synchronization with active phc in linux bonding

[Johannes Z. <j....@pe...>]

Hi Shashank,

On 6/6/23 08:51, shashank varshney wrote:
> Hi Richard/Miroslav,
> Hope you are doing good.
> 
> As mentioned, PTP switchover from one NIC port to another is not seamless when 
> ports belong to different NICs with different hardware clocks.


if the different ports of your endpoint are taking part in the same PTP domain 
and if they are synchronized there should be little or no offset. Why not using 
2 different NICs and having 2 daemons sync to the network? I don't quite get 
why you would even want to run PTP over LACP or something alike (using LACP in 
Realtime Network with tight timing budgets is asking for trouble anyway...).

Maybe I entirely miss your point, but from reading this thread, I'd recommend 
to review your system design.

> 
> I am looking to utilize PTP for very time sensitive use cases like 5G wireless, 
> stock markets, etc. which desire High Availability and redundancy at NIC port 
> level while utilizing PTP.

You probably want to look a bit closer on PCR/FRER for data transport, the 
different ports of your talker/listener devices can take part in a single 
(g)PTP domain.

> 
> This is going to be a significant use case if we would like to move to open 
> sourced environment and LinuxPTP is going to have significant role to play to 
> achieve this aspect.
> 
> Can someone help me with getting this functionality of seamless switchover by 
> synchronizing Active Port PHC with PTP GM and then synchronizing system clock 
> and standby PHCs with active PHC?
>
> PS: I am not from development background so it will be difficult to develop 
> this functionality from my end. So need community help to get this functionality.
>


This is not quite how the opensource community works - we can give you pointers 
and discuss the technical background, but you will probably not find anyone who 
does the implementation _for_ you, at least not for free.
You can either participate in the effort yourself or hire someone to do it, 
there is quite a lot of companies as well as well as freelance individual 
contributors with tons of expertise in PTP.

Best regards
Johannes

> 
> Thanks and regards
> Shashank Varshney
> 
> 
> On Sun, Apr 16, 2023 at 8:40 PM Richard Cochran <ric...@gm... 
> <mailto:ric...@gm...>> wrote:
> 
>     On Sun, Apr 16, 2023 at 01:54:20PM +0530, shashank varshney wrote:
> 
>      > *sfptpd supports PTP packets over bonded interfaces in an active/standby
>      > mode. In addition, sfptpd also supports bonding over LACP (802.3ad)
>      > bonding.*
> 
>     Looks like sfptpd is a hacked version of the old ptpd program.  If
>     that works for you, then great.
> 
>      >  *Is there any plan to include a similar kind of working mechanism for PTP
>      > over Linux Bonding for seamless switchover in case of failure of
>      > active-slave port to passive-slave port when both slaves are on different
>      > NICs with different PHCs?*
> 
>     I'm not aware of any plan for that.  If you feel like adding it, then
>     we'll look forward to your patches on the list...
> 
>     Thanks,
>     Richard
> 
> 
> 
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users

-- 
Pengutronix e.K.                | Johannes Zink                  |
Steuerwalder Str. 21            | https://www.pengutronix.de/    |
31137 Hildesheim, Germany       | Phone: +49-5121-206917-0       |
Amtsgericht Hildesheim, HRA 2686| Fax:   +49-5121-206917-5555    |

Re: [Linuxptp-users] ptp4l passive phc synchronization with active phc in linux bonding

[shashank v. <sha...@gm...>]

Hi Richard/Miroslav,
Hope you are doing good.

As mentioned, PTP switchover from one NIC port to another is not seamless
when ports belong to different NICs with different hardware clocks.

I am looking to utilize PTP for very time sensitive use cases like 5G
wireless, stock markets, etc. which desire High Availability and redundancy
at NIC port level while utilizing PTP.

This is going to be a significant use case if we would like to move to open
sourced environment and LinuxPTP is going to have significant role to play
to achieve this aspect.

Can someone help me with getting this functionality of seamless switchover
by synchronizing Active Port PHC with PTP GM and then synchronizing system
clock and standby PHCs with active PHC?

PS: I am not from development background so it will be difficult to develop
this functionality from my end. So need community help to get this
functionality.


Thanks and regards
Shashank Varshney


On Sun, Apr 16, 2023 at 8:40 PM Richard Cochran <ric...@gm...>
wrote:

> On Sun, Apr 16, 2023 at 01:54:20PM +0530, shashank varshney wrote:
>
> > *sfptpd supports PTP packets over bonded interfaces in an active/standby
> > mode. In addition, sfptpd also supports bonding over LACP (802.3ad)
> > bonding.*
>
> Looks like sfptpd is a hacked version of the old ptpd program.  If
> that works for you, then great.
>
> >  *Is there any plan to include a similar kind of working mechanism for
> PTP
> > over Linux Bonding for seamless switchover in case of failure of
> > active-slave port to passive-slave port when both slaves are on different
> > NICs with different PHCs?*
>
> I'm not aware of any plan for that.  If you feel like adding it, then
> we'll look forward to your patches on the list...
>
> Thanks,
> Richard
>

Re: [Linuxptp-users] [Linuxptp-devel] Can ptp4l specify master clock source by ip address?

[Maciek M. <ma...@ma...>]

On 6/2/2023 9:01 PM, Trey Harrison wrote:
> Subject kinda says it all.. We have previously been using chrony to
> synchronize systems on a network, and chrony allows slave devices to
> specify the ip address of their clock source.
> 
> It does not seem obvious after reviewing documentation here that this
> is possible:
> 
> https://manpages.ubuntu.com/manpages/bionic/man8/ptp4l.8.html
> 
To achieve this you need to deploy ptp in the unicast mode.

For details - please refer to UNICAST-MASTER.cfg and UNICAST-SLAVE.cfg
in the config subfolder.

And please post usecase-related questions to the linuxptp-users group.


> We generally deploy systems in groups where one is the master clock
> source and the others are started as "slaveOnly" devices. However, it
> is possible that we may have multiple groups like this deployed on the
> same network, where there may be a few sources competing to be the
> "master clock".. but it is important for slaves in one group always
> use their designated master clock, and not any other master clock that
> may also be present on the network.
> 
Do you assign different groups to different domainNumbers?

> We have considered redesigning our systems so that there is only ever
> a single master clock started on the network, with all other nodes
> starting as "slaveOnly".. but that would involve adding further
> configuration options to our software which would be one more thing
> for the system configurators to get wrong when deploying them.
> 
> TLDR; can a 'slaveOnly' ptp4l client specify the ip (ipv4) address of
> the master clock it wants to use?

TLDR; Yes - if you deploy it in unicast mode :)

Thanks,
Maciek

> 
> Thanks!
> 
> Trey
> 
> 
> _______________________________________________
> Linuxptp-devel mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Re: [Linuxptp-users] My linuxptp setup - overcomplicating?

[Elder C. <eld...@ti...>]

Someone?

>
> Sys clock (GM)
>      |
>      v
> phc2sys          phc2sys -> Sys clock SOM         Sys clock AM
>      |               ^             |                 ^
>      |               |          phc2sys              |
>      |               |             |                 |
>      v               |             v                 |
>    enp3s0        eth_head        eth_am            eth0 (SW ts)
>
> GM -----------------------> SOM <---------------------> AM
>    enp3s0        eth_head        eth_am            eth0
>
>    ptp4l(M)       ptp4l(S)       ptp4l(M)          ptp4l (S/SW)
>
>
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Re: [Linuxptp-users] Offset between TAI and PHC

[Elder C. <eld...@ti...>]

Hello Dennys, Miroslav.

I will try your suggestions. Thank you both for the help

BR.





Em qua., 24 de mai. de 2023 às 14:50, Dennis Hagarty (dehagart)
<deh...@ci...> escreveu:
>
> Hi,
>
> Yes, I think so.
>
> The GM will send those values in the Announce message and you pick it up with -w
> If it's not, you can configure the offset locally on the client end with -O
>
> Regards
> Dennis
>
> -----Original Message-----
> From: Miroslav Lichvar <mli...@re...>
> Sent: Wednesday, May 24, 2023 3:51 PM
> To: Elder Costa <eld...@ti...>
> Cc: lin...@li...
> Subject: Re: [Linuxptp-users] Offset between TAI and PHC
>
> On Wed, May 24, 2023 at 08:19:37AM -0300, Elder Costa wrote:
> > phc latency: 7472
> > phc-rt delta: 37000039320
> > phc-tai delta: 37000039035
> >
> > phc-tai delta is greater than 50 usec !
> > TAI offset set in kernel is not correct !
>
> I think you need to set currentUtcOffsetValid and timeTraceable on the
> GM with a pmc SET GRANDMASTER_SETTINGS_NP command for the client's
> phc2sys to actually set the TAI-UTC offset of the system clock.
>
> --
> Miroslav Lichvar
>
>
>
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users

[Linuxptp-users] My linuxptp setup - overcomplicating?

[Elder C. <eld...@ti...>]

I managed to assemble a test fixture similar to the embedded system
I am evaluating deploying linuxptp on, as shown on the diagram below.

System clocks of the three main components are working in synchrony
(apparently) and a change on the system clock of the GM is propagated
after a few seconds to the other two members of the gang.

Next step is checking how well synchronized they are and how well sync
is kept in the long run.

My question is about the configuration of the SOM component. I thought
of configuring the interfaces as a BC, but could not make it work. In
one of the runs that succeeded (i.e., produced no errors), ptp4l running
on the AM complained that Master clock quality received is greater
than configured, ignoring master!". I searched the mailing list about
boundary clock but I could not find information on how to use BC; I am
under the impression that BC depends on hardware support (a centralized
 clock the net interfaces use) for it to work.

So I ended up with the setup below, using one instance of ptp4l per
interface and four instances of phc2sys to synchronize system
clocks and interface.

My question is if I am overcomplicating it, IOW, if there is not a
simpler way to set the SOM, including using BC correctly, if
it is ever  possible with a X86 based architecture.

FWIW I tried using ts2phc to synchronize the eth_am interface with
eth_head, but I could not make it work, so I ended up using
the second instance of phc2sys instead.

Sys clock (GM)
     |
     v
phc2sys          phc2sys -> Sys clock SOM         Sys clock AM
     |               ^             |                 ^
     |               |          phc2sys              |
     |               |             |                 |
     v               |             v                 |
   enp3s0        eth_head        eth_am            eth0 (SW ts)

GM -----------------------> SOM <---------------------> AM
   enp3s0        eth_head        eth_am            eth0

   ptp4l(M)       ptp4l(S)       ptp4l(M)          ptp4l (S/SW)

Re: [Linuxptp-users] Offset between TAI and PHC

[Dennis H. (dehagart) <deh...@ci...>]

Hi,

Yes, I think so.

The GM will send those values in the Announce message and you pick it up with -w
If it's not, you can configure the offset locally on the client end with -O

Regards
Dennis

-----Original Message-----
From: Miroslav Lichvar <mli...@re...> 
Sent: Wednesday, May 24, 2023 3:51 PM
To: Elder Costa <eld...@ti...>
Cc: lin...@li...
Subject: Re: [Linuxptp-users] Offset between TAI and PHC

On Wed, May 24, 2023 at 08:19:37AM -0300, Elder Costa wrote:
> phc latency: 7472
> phc-rt delta: 37000039320
> phc-tai delta: 37000039035
> 
> phc-tai delta is greater than 50 usec !
> TAI offset set in kernel is not correct !

I think you need to set currentUtcOffsetValid and timeTraceable on the
GM with a pmc SET GRANDMASTER_SETTINGS_NP command for the client's
phc2sys to actually set the TAI-UTC offset of the system clock.

-- 
Miroslav Lichvar



_______________________________________________
Linuxptp-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Re: [Linuxptp-users] Offset between TAI and PHC

[Miroslav L. <mli...@re...>]

On Wed, May 24, 2023 at 08:19:37AM -0300, Elder Costa wrote:
> phc latency: 7472
> phc-rt delta: 37000039320
> phc-tai delta: 37000039035
> 
> phc-tai delta is greater than 50 usec !
> TAI offset set in kernel is not correct !

I think you need to set currentUtcOffsetValid and timeTraceable on the
GM with a pmc SET GRANDMASTER_SETTINGS_NP command for the client's
phc2sys to actually set the TAI-UTC offset of the system clock.

-- 
Miroslav Lichvar

Re: [Linuxptp-users] Offset between TAI and PHC

[Elder C. <eld...@ti...>]

Hello, Dennys, thank you for chiming in.

>From my understanding of the documentation, I assumed
the offset would be taken from ptp4l with the '-w' command
argument. Obviously I am missing some config or doing
something wrong I am not figuring out.
I tried some variations but either they desynchronized the
system clocks by the offset (37s) or changed the deltas
from positive to negative, still around 37 seconds.

Em qua., 24 de mai. de 2023 às 10:13, Dennis Hagarty (dehagart)
<deh...@ci...> escreveu:
>
> Hi,
>
> I'm not exactly sure what this tool is doing, but most likely explanation for the difference between those clocks is due to leap second offset (currently 37 seconds).
>
> I believe RT should be UTC, and the PHC should be TAI (37 seconds in front of TAI). phc2sys should add the offset (either from config or from the announce message).
>
> Have you configured that?
>
> Regards
> Dennis
>
> -----Original Message-----
> From: Elder Costa <eld...@ti...>
> Sent: Wednesday, May 24, 2023 1:20 PM
> To: lin...@li...
> Subject: [Linuxptp-users] Offset between TAI and PHC
>
> I am getting the result below with the check_clocks utility.
> downloaded from:
> https://tsn.readthedocs.io/timesync.html#checking-clocks-synchronization
>
> cve@cve-sbc-flt2:~/work$ sudo ./check_clocks -d enp3s0 -v
> Dumping timestamps and deltas
>
> rt tstamp: 1684764184805696608
> tai tstamp: 1684764184805696893
> phc tstamp: 1684764221805735928
> rt latency: 136
> tai latency: 120
> phc latency: 7472
> phc-rt delta: 37000039320
> phc-tai delta: 37000039035
>
> phc-tai delta is greater than 50 usec !
> TAI offset set in kernel is not correct !
> PTP peer port state and/or offset are messed up !
> Please verify ptp4l and phc config and restart them if necessary to
> synchronize the clocks !
>
>
> I am running ptp4l and phc2sys to keep the system clocks of the master and slave
> synchronized. Commands and configurations below.
>
> What am I missing?
>
>
> # Sincronize master's PTP with system clock (HW timestamp)
> sudo phc2sys -c enp3s0 -s CLOCK_REALTIME -q -m -w --step_threshold=0.001
>
> # Sincronize slave's system clock with PTP (HW timestamp)
> sudo phc2sys -s enp3s0 -c CLOCK_REALTIME -q -m -w --step_threshold=0.001
>
>
> # Test configuration of the Fitlet acting as a master
> [global]
> serverOnly              1
> BMCA                    noop
> use_syslog              0
> verbose                 1
>
> [enp3s0]
>
>
> # Test configuration of the Fitlet acting as a master
> [global]
> clientOnly              1
> BMCA                    noop
> step_threshold          0.001
> use_syslog              0
> verbose                 1
>
> [enp3s0]
>
>
> _______________________________________________
> Linuxptp-users mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Re: [Linuxptp-users] Offset between TAI and PHC

[Dennis H. (dehagart) <deh...@ci...>]

Hi,

I'm not exactly sure what this tool is doing, but most likely explanation for the difference between those clocks is due to leap second offset (currently 37 seconds).

I believe RT should be UTC, and the PHC should be TAI (37 seconds in front of TAI). phc2sys should add the offset (either from config or from the announce message).

Have you configured that?

Regards
Dennis

-----Original Message-----
From: Elder Costa <eld...@ti...> 
Sent: Wednesday, May 24, 2023 1:20 PM
To: lin...@li...
Subject: [Linuxptp-users] Offset between TAI and PHC

I am getting the result below with the check_clocks utility.
downloaded from:
https://tsn.readthedocs.io/timesync.html#checking-clocks-synchronization

cve@cve-sbc-flt2:~/work$ sudo ./check_clocks -d enp3s0 -v
Dumping timestamps and deltas

rt tstamp: 1684764184805696608
tai tstamp: 1684764184805696893
phc tstamp: 1684764221805735928
rt latency: 136
tai latency: 120
phc latency: 7472
phc-rt delta: 37000039320
phc-tai delta: 37000039035

phc-tai delta is greater than 50 usec !
TAI offset set in kernel is not correct !
PTP peer port state and/or offset are messed up !
Please verify ptp4l and phc config and restart them if necessary to
synchronize the clocks !


I am running ptp4l and phc2sys to keep the system clocks of the master and slave
synchronized. Commands and configurations below.

What am I missing?


# Sincronize master's PTP with system clock (HW timestamp)
sudo phc2sys -c enp3s0 -s CLOCK_REALTIME -q -m -w --step_threshold=0.001

# Sincronize slave's system clock with PTP (HW timestamp)
sudo phc2sys -s enp3s0 -c CLOCK_REALTIME -q -m -w --step_threshold=0.001


# Test configuration of the Fitlet acting as a master
[global]
serverOnly              1
BMCA                    noop
use_syslog              0
verbose                 1

[enp3s0]


# Test configuration of the Fitlet acting as a master
[global]
clientOnly              1
BMCA                    noop
step_threshold          0.001
use_syslog              0
verbose                 1

[enp3s0]


_______________________________________________
Linuxptp-users mailing list
Lin...@li...
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

[Linuxptp-users] Offset between TAI and PHC

[Elder C. <eld...@ti...>]

I am getting the result below with the check_clocks utility.
downloaded from:
https://tsn.readthedocs.io/timesync.html#checking-clocks-synchronization

cve@cve-sbc-flt2:~/work$ sudo ./check_clocks -d enp3s0 -v
Dumping timestamps and deltas

rt tstamp: 1684764184805696608
tai tstamp: 1684764184805696893
phc tstamp: 1684764221805735928
rt latency: 136
tai latency: 120
phc latency: 7472
phc-rt delta: 37000039320
phc-tai delta: 37000039035

phc-tai delta is greater than 50 usec !
TAI offset set in kernel is not correct !
PTP peer port state and/or offset are messed up !
Please verify ptp4l and phc config and restart them if necessary to
synchronize the clocks !


I am running ptp4l and phc2sys to keep the system clocks of the master and slave
synchronized. Commands and configurations below.

What am I missing?


# Sincronize master's PTP with system clock (HW timestamp)
sudo phc2sys -c enp3s0 -s CLOCK_REALTIME -q -m -w --step_threshold=0.001

# Sincronize slave's system clock with PTP (HW timestamp)
sudo phc2sys -s enp3s0 -c CLOCK_REALTIME -q -m -w --step_threshold=0.001


# Test configuration of the Fitlet acting as a master
[global]
serverOnly              1
BMCA                    noop
use_syslog              0
verbose                 1

[enp3s0]


# Test configuration of the Fitlet acting as a master
[global]
clientOnly              1
BMCA                    noop
step_threshold          0.001
use_syslog              0
verbose                 1

[enp3s0]

Re: [Linuxptp-users] Testing PTP synchronization

[Elder C. <eld...@ti...>]

Em dom., 21 de mai. de 2023 às 18:49, Vladimir Oltean
<ol...@gm...> escreveu:
>
> To prove PTP is working, typically you'd expect an oscilloscope with 2
> channels probing the PPS output signals from the end stations.
>

Maybe. I will take a look at it. It may be enough for my tests

> Something like this? https://github.com/vladimiroltean/isochron

Thank you for the heads up, I will also take a look at it if pps turns out not
to be sufficient.

BR.