ADIN6310 Fails to Calculate Mean Link Delay When Synchronizing with Raspberry Pi CM5 eth0

Hi Katsumata-san,

Thanks for your message, sorry to hear you are having issue with this setup. 

Can you share the packet capture when connected to eth0?

We will review in more detail. 

best regards,

Catherine

Hello CatherineR

Thank you for your response.

I have attached the packet capture collected while using the Raspberry Pi CM5  eth0 interface, as well as screenshots from the ADIN6310 web GUI.

Please let me know if any additional information would be helpful.

Best regards,

Katsumata

↑web GUI screenshot

"No.","Time","Source","Destination","Protocol","Length","Info"
"1","0.000000000","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"2","0.003306482","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"3","0.009818945","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","74","Signalling Message"
"4","0.009956722","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"5","0.010003296","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"6","0.013080370","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"7","0.125027704","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"8","0.127985056","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"9","0.230140296","192.168.0.1","192.168.0.255","NBNS","110","Registration NB <01><02>__MSBROWSE__<02><01>"
"10","0.250179870","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"11","0.253207241","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"12","0.375204352","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"13","0.378167778","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"14","0.500402185","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"15","0.503409389","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"16","0.503465296","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"17","0.503765907","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"18","0.503888518","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"19","0.557492703","7a:c6:bb:11:11:13","Spanning-tree-(for-bridges)_00","STP","119","MST. Root = 32768/0/7a:c6:bb:11:11:11 Cost = 0 Port = 0x8002"
"20","0.625446018","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"21","0.628425185","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"22","0.628458537","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Announce Message"
"23","0.750502185","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"24","0.753490574","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"25","0.875558740","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"26","0.878526685","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"27","0.995661537","192.168.0.1","192.168.0.255","NBNS","110","Registration NB <01><02>__MSBROWSE__<02><01>"
"28","1.000620148","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"29","1.003585462","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"30","1.009815907","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","74","Signalling Message"
"31","1.009956574","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"32","1.010004425","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"33","1.012921370","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"34","1.125679703","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"35","1.128612555","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"36","1.250749444","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"37","1.253847277","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"38","1.375822129","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"39","1.378788777","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"40","1.500881518","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"41","1.503849129","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"42","1.503878184","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"43","1.504195444","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"44","1.504321870","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"45","1.625935795","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"46","1.628881721","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"47","1.628909944","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Announce Message"
"48","1.751028314","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"49","1.754046573","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"50","1.760272758","192.168.0.1","192.168.0.255","NBNS","110","Registration NB <01><02>__MSBROWSE__<02><01>"
"51","1.876076925","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"52","1.879057110","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"53","2.001156314","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"54","2.004321351","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"55","2.009806703","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","74","Signalling Message"
"56","2.009953591","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"57","2.009989943","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"58","2.012962962","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"59","2.126199295","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"60","2.129181332","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"61","2.251258721","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"62","2.254227591","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"63","2.376321332","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"64","2.379280610","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"65","2.501377406","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"66","2.504326350","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"67","2.504354573","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"68","2.504670795","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"69","2.504799239","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"70","2.511942406","192.168.0.1","192.168.0.255","NBNS","110","Registration NB <01><02>__MSBROWSE__<02><01>"
"71","2.557498591","7a:c6:bb:11:11:13","Spanning-tree-(for-bridges)_00","STP","119","MST. Root = 32768/0/7a:c6:bb:11:11:11 Cost = 0 Port = 0x8002"
"72","2.626436276","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"73","2.629349517","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"74","2.629380795","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Announce Message"
"75","2.751471573","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"76","2.754425702","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"77","2.876544406","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"78","2.879508869","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"79","2.997102517","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"80","2.997268906","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"81","2.997354313","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"82","2.997433758","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"83","2.999535535","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"84","2.999612461","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"85","2.999727183","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"86","2.999832758","192.168.0.10","192.168.0.255","UDP","74","63267 > 22936 Len=32"
"87","3.001596221","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"88","3.004556813","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"89","3.009799165","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","74","Signalling Message"
"90","3.009949091","7a:c6:bb:11:11:13","LLDP_Multicast","PTPv2","68","Peer_Delay_Req Message"
"91","3.009984221","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp Message"
"92","3.012923146","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","68","Peer_Delay_Resp_Follow_Up Message"
"93","3.126668554","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"94","3.129628609","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"95","3.251693461","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"
"96","3.254637702","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","90","Follow_Up Message"
"97","3.274667387","192.168.0.1","192.168.0.255","BROWSER","228","Request Announcement DESKTOP-UFUQ2QF"
"98","3.274807313","192.168.0.1","192.168.0.255","BROWSER","228","Request Announcement DESKTOP-UFUQ2QF"
"99","3.275324757","192.168.0.1","192.168.0.255","BROWSER","258","Domain/Workgroup Announcement WORKGROUP, NT Workstation, Domain Enum"
"100","3.376770535","88:a2:9e:29:be:52","LLDP_Multicast","PTPv2","58","Sync Message"

Hi Karl

Thank you for checking this on your side.

I am using a Raspberry Pi Compute Module 5 (CM5) rather than a standard Raspberry Pi 5 board.

For the onboard Ethernet interface, I used:

"sudo ptp4l -i eth0 -f /etc/linuxptp/gptp.cfg -m -H"

If the ADIN6310 GUI is reporting a mean link delay of approximately 200 ns, that seems much more reasonable for a direct connection.

If you notice any differences in the configuration or setup between your environment and mine, I would appreciate it if you could let me know.

Regard，

Katsumata

Hi Karl

Would it be possible for you to share the exact ptp4l command line and configuration file that you used to obtain the 200 ns mean link delay? I would like to compare them with my setup.

Regard,

katsumata

Hi Katsumata,

I'm using the command below:

"sudo ./ptp4l -i eth0 -f /home/kobias/Downloads/PTP/linuxptp-4.0/configs/gPTP.cfg -m"

With the default gPTP.cfg file, I'm seeing a mean link delay of around 233+.

Here is the cfg file for reference:

 gPTP.zip

I've also attached the output of the ethtool -T command for eth0 interface.

Regards,

Karl

Hi, Karl

Thank you for providing your environment information.

I performed another test by swapping the TimeTrasnmitter and TimeReceiver roles. In this setup, ptp4l reported a delay of approximately 40 ns, which seems reasonable for a direct connection.

However, the ADIN6310 GUI previously reported a Mean Link Delay of approximately 58 µs for the same connection. This difference seems quite large.

Have you observed the same behavior in your setup, where the delay reported by ptp4l differs significantly from the Mean Link Delay shown in the ADIN6310 GUI?

Would it be correct to assume that the value reported by ptp4l (approximately 40 ns) is the more accurate representation of the actual link delay?

Regards,

Katsumata

Hi Katsumata,

I'm still investigating the large difference between what is reported by the ADIN6310 GUI and ptp4l.

Have you made any changes to the Mean Link Delay Threshold in the ADIN6310 GUI or in the ptp4l configuration file?

The default mean link delay is 800ns, which may explain why the device is not achieving time synchronization with the egress and ingress latency adjustments.

Could you increase the Mean Link Delay Thresh (ns) in the ADIN6310 GUI to 100,000 and set the neighborPropDelayThresh in the ptp4l configuration file to 100,000 as well?

Also, please remove the ingress and egress latency. and then check whether the mean link delay values reported by the ADIN6310 GUI and ptp4l are similar?

Regards,

Karl

Hi Karl

Sorry for the delayed response.

I tested the configuration as you suggested:

• Mean Link Delay Thresh = 100,000 ns in the ADIN6310 GUI
• neighborPropDelayThresh = 100,000 in ptp4l
• ingress and egress latency removed

However, in this configuration, the measured propagation delay becomes 0 and the devices do not synchronize.

The reason I originally added the ingress and egress latency values was to make the propagation delay measurable. During my investigation, I observed that the T2 and T3 timestamps were sometimes exactly the same. I suspected that this might be the reason why the propagation delay was not being measured correctly.

After adding the ingress and egress latency values, the synchronization was successfully established, which is why I continued using those settings.

Do you think the identical T2 and T3 timestamps could indicate an issue with the timestamp measurement process on the CM5 side?


↑ WebGUI screenshot

Regards,

Katsumata

Hi Katsumata,

Similar values for T2 and T3 shouldn't be cause the propagation delay to become 0.

Based on the T1, T2, T3, and T4 timestamps, the mean link delay should still be within the threshold.

Additionally, how did you identify the ingress/egress latency values, 98/250?

Regards,

Karl

Hi Karl

Thank you for your reply.

Theoretically, I agree that similar T2 and T3 values should not cause the propagation delay to become zero.

However, when I checked the captured packets in Wireshark, the T2 and T3 timestamps in the Pdelay_Resp and Pdelay_Resp_Follow_Up messages are different, while the ADIN6310 reports them as identical. This suggests that some kind of correction or processing is being applied internally by the ADIN6310. Therefore, I suspected that this internal processing might also be affecting the propagation delay calculation and causing it to become zero.

Regarding the ingress/egress latency values (98 ns / 250 ns), I simply used the values provided in the ADIN6310 documentation for 100 Mbps time synchronization. My intention was not to determine the exact latency values but rather to verify whether enabling the ingress/egress latency compensation would affect the synchronization behavior. In fact, I believe that even values such as 1 ns would have produced the same effect, since the important point was enabling the latency compensation itself.

If there are recommended ingress and egress latency values specifically for the Raspberry Pi CM5 Ethernet interface, I would greatly appreciate it if you could let me know.

Regards,

Katsumata

Hi Katsumata,

I tried running ptp4l on a CM5 setup, and I'm observing a similar behavior.

I'm still checking whether the T2 and T3 values reported by the ADIN6310 correspond directly to the timestamps seen in the Wireshark capture, or if there is any internal timestamp correction or processing involved.

Regarding the ingress/egress latency values, could you please confirm whether the ADIN6310 port is configured for 100 Mbps in your setup?

I'm also checking whether any additional CM5 configuration is required to get linuxptp working correctly with this setup.

I'll update you once I have more information.

Regards,

Karl

Hi Katsumata,

I tried running ptp4l on a CM5 setup, and I'm observing a similar behavior.

I'm still checking whether the T2 and T3 values reported by the ADIN6310 correspond directly to the timestamps seen in the Wireshark capture, or if there is any internal timestamp correction or processing involved.

Regarding the ingress/egress latency values, could you please confirm whether the ADIN6310 port is configured for 100 Mbps in your setup?

I'm also checking whether any additional CM5 configuration is required to get linuxptp working correctly with this setup.

I'll update you once I have more information.

Regards,

Karl