SLA Status	Assignee	Support Status
SLA Closed. Met after 7 hours	CatherineR Karl.O Hseth	Awaiting Customer Response

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

Katsu717 on Jun 4, 2026

Category: Software

Product Number: ADIN6310

Software Version: Version5.1.0

Hello！

Hello,

I am trying to synchronize time using IEEE 802.1AS-2020 with a Raspberry Pi CM5 as the Grandmaster(Time Transmitter) and an ADIN6310 as the TimeReceiver.

The Raspberry Pi CM5 is running LinuxPTP (ptp4l), and the ADIN6310 is configured for IEEE 802.1AS-2020 gPTP.

However, synchronization does not complete successfully.

Using Wireshark, I can confirm that the following gPTP messages are being exchanged correctly between the Raspberry Pi CM5 and the ADIN6310:

Announce
Sync
Follow_Up
Pdelay_Req
Pdelay_Resp
Pdelay_Resp_Follow_Up

Despite this, the ADIN6310 never calculates the Mean Link Delay. The Mean Link Delay remains 0 ns, and the device does not achieve synchronization.

One additional observation is that if I replace the Raspberry Pi CM5 eth0 interface with a USB Ethernet adapter, synchronization works correctly and the Mean Link Delay is calculated as expected. The problem only occurs when using the CM5 eth0 interface.

The Raspberry Pi CM5 is running ptp4l with hardware timestamping enabled.

Additional information:

Wireshark confirms that Pdelay_Resp and Pdelay_Resp_Follow_Up messages are exchanged.
On the ADIN6310 status page, the Pdelay timestamp fields (T1–T4) are populated.
However, Mean Link Delay remains 0 ns.
The Parent Dataset shows a Grandmaster Identity of 00-00-00-00-00-00-00-00.
Synchronization succeeds when using a USB Ethernet NIC on the Raspberry Pi, but fails when using the CM5 eth0 interface.

Could there be any known compatibility issues with the Raspberry Pi CM5 Ethernet MAC/PHY and the ADIN6310 gPTP implementation, or any additional settings required for IEEE 802.1AS-2020 interoperability?

Thank you for your help.

↑GUI Candidate screen

↑GUI Status screen

↑ptp4l-configure File

↑ptp4l Execution Results

CatherineR

on Jun 4, 2026 4:27 PM
0
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
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Katsu717 on Jun 5, 2026 12:08 AM in reply to CatherineR
0

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"
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Karl.O

on Jun 9, 2026 2:25 AM in reply to Katsu717
0
Hi,

I'm using ptp4l version 3.1.1 with a Raspberry Pi 5 board, and I'm seeing the Mean Link Delay in the web GUI.

Could you please confirm which version of ptp4l you are using?

Regards,

Karl
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Karl.O

on Jun 10, 2026 12:49 AM in reply to Karl.O
0
Hi,

Could you run the command below and share the results?

"ethtool -T eth0"

Could you also try running the same command, but replace eth0 with the interface name of the USB ethernet adapter?

Thanks,

Karl
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Katsu717 on Jun 10, 2026 3:15 AM in reply to Karl.O
0
Hi, Karl

Thank you for your responce.

I am using ptp4l version 4.0

I have also attached the output of ethtool -T for both the onboard Ethernet interface and the USB Ethernet adapter as requested.

After adding the following parameters to the ptp4l configuration on the Raspberry Pi CM5, the ADIN6310 was able to synchronize successfully and entered the Sync Locked state:

ingress_latency 98 egress_latency 250

I can now see the Mean Link Delay in the web GUI.

However, the reported Mean Link Delay is approximately 65 µs, which seems unexpectedly large for a direct Ethernet connection between the Raspberry Pi CM5 and the ADIN6310 evaluation board. Therefore, I suspect there may still be an issue with the timestamping or delay measurement.

If you have any suggestions on what else I could check or configure to obtain a more realistic Mean Link Delay value, I would greatly appreciate your advice.

Regards,

katsumata
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Karl.O

on Jun 10, 2026 7:09 AM in reply to Katsu717
0
Hi Katsumata,

What is the ptp4l command you used for the eth0 and the ethernet adapter?

You're right the 65 µs mean link delay is unexpectedly large.

I tried using the same version of the ptp4l, with the same ingress and egress latency.

I'm only getting around 200ns for the mean link delay using the Raspberry Pi 5.

Regards,

Karl
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Katsu717 on Jun 10, 2026 7:21 AM in reply to Karl.O
0
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
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Katsu717 on Jun 11, 2026 2:46 AM in reply to Katsu717
0

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
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Karl.O

on Jun 11, 2026 3:51 AM in reply to Katsu717
0
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
Cancel
Up 0 Down

Reply

Verify Answer

Cancel
Katsu717 on Jun 11, 2026 4:30 AM in reply to Karl.O
0

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
Cancel
Up 0 Down

Reply

Verify Answer

Cancel