Jump to content

Problem : I'm trying to get three devices to share a common clock. I have a linux machine acting as the "grandmaster clock", an L2 enabled network switch from Planet, and an RFSoC (also running a linux OS). I'm using the default IEEE 1588 Linux PTP from here Welcome to The Linux PTP Project

What I've Tried : Directly connecting the RFSoC to the "grandmaster clock". This worked great. Well synced timestamps. This makes me think the switch is blocking somehow.

  • made sure network switch could do PTP and had 2 Layer timing protocol
  • disabled IGMP snooping since it can interfere with PTP
  • ensured switch config, and two linuxptp configs are set to the same standards (i.e. network_transport = L2, delay_mechanism = P2P, priority set to high values)
  • grandmaster clock has the highest priority value

Current State When I start up the grandmaster clock, it sets itself to the "master clock". I start up the RFSoC linuxptp service and it states it can see an "unidentified clock" and starts listening. That's it.

 

Is there anything else that I'm missing that isn't in the configuration photos I've attached? It feels like there is something happening that is not allowing the RFSoC to send a signal back to the grandmaster clock letting it know to start syncing up timestamps. Perhaps the priority needs to be configured specifically for each of the three devices, but I'm not sure to what.

 

Also : I've been using this as one resource Chapter 20. Configuring PTP Using ptp4l | Red Hat Product Documentation but we've also copied the configuration setup from another group that has the same hardware as us and successfully has PTP working.

 

Example Configuration File

# 802.1AS example configuration containing those attributes which
# differ from the defaults. See the file, default.cfg, for the
# complete list of available options.
# [global] 
gmCapable 1
priority1 248
priority2 248
logAnnounceInterval 0
logSyncInterval -3
syncReceiptTimeout 3
neighborPropDelayThresh 800
min_neighbor_prop_delay -20000000
assume_two_step 1
path_trace_enabled 1
follow_up_info 0
transportSpecific 0x1
network_transport L2
delay_mechanism P2P

 

Screenshotfrom2025-04-1016-14-08.thumb.png.a4355734b4aa2599a4bef733d1cc3c7e.png

 

 

Screenshot from 2025-04-10 16-13-56.png

Link to comment
https://linustechtips.com/topic/1609621-ptp-through-network-switch/
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×