F5F Stay Refreshed Power Users Networks Using PTP over a network switch connects devices seamlessly.

Using PTP over a network switch connects devices seamlessly.

Using PTP over a network switch connects devices seamlessly.

P
pinkSparkle17
Member
Find
192
08-24-2023, 07:30 AM
#1
I'm attempting to synchronize three devices using a shared clock. The "grandmaster" runs on a Linux machine, while an L2 switch from Planet and an RFSoC also operate on Linux. I've used the standard IEEE 1588 PTP from here. What I've tried: linking the RFSoC directly to the master clock – it worked perfectly, timestamps matched. This leads me to suspect a possible blockage. I checked if the switch supported PTP and disabled IGMP snooping, as it might interfere. Configured the switch properly, set both Linux PTP instances to L2 transport with P2P delay, high priority values, and ensured the master clock gets top priority. When starting the master clock, it automatically selected itself as the master. The RFSoC Linux service reported seeing an "unidentified clock" and began listening. It seems there might be something preventing it from sending a signal back to the master to initiate sync. Maybe the priority needs adjustment for each device individually? Also, I've followed a configuration guide from Chapter 20 in Red Hat docs, which included a sample setup file (default.cfg) with custom options. The example shows how to tweak parameters like priority, delay mechanisms, and network transport settings.
Reply
Reply
P
pinkSparkle17
08-24-2023, 07:30 AM #1

I'm attempting to synchronize three devices using a shared clock. The "grandmaster" runs on a Linux machine, while an L2 switch from Planet and an RFSoC also operate on Linux. I've used the standard IEEE 1588 PTP from here. What I've tried: linking the RFSoC directly to the master clock – it worked perfectly, timestamps matched. This leads me to suspect a possible blockage. I checked if the switch supported PTP and disabled IGMP snooping, as it might interfere. Configured the switch properly, set both Linux PTP instances to L2 transport with P2P delay, high priority values, and ensured the master clock gets top priority. When starting the master clock, it automatically selected itself as the master. The RFSoC Linux service reported seeing an "unidentified clock" and began listening. It seems there might be something preventing it from sending a signal back to the master to initiate sync. Maybe the priority needs adjustment for each device individually? Also, I've followed a configuration guide from Chapter 20 in Red Hat docs, which included a sample setup file (default.cfg) with custom options. The example shows how to tweak parameters like priority, delay mechanisms, and network transport settings.

Reply
Reply