Hello, I have been playing with development version of Linuxptp connected to Microchip’s TP4100. It seems that commit (2a2532d) breaks compatibility with this particular GM. I am using G.8275.2 profile PTP configuration, i.e., unicast transmission. The signaling communication works fine, as well as Announce & Sync message reception. Delay_Resp message, however, never comes from GM.
It seems that the reason for that is that this particular GMs do not reply to Delay_Req messages with PTP minor version set to 1. Below find a fragment of the Delay_Req message from wireshark dump. As soon as I change the PTP minor version of the Delay_Req to 0, the Delay_Resp messages are transmitted by GM. I am not an expert on the 1588-2019 protocol, so not sure what should be the expected behavior of the GM. Any ideas what should be the expected behavior? Thank you and best regards Zdenek Chaloupka Frame 19: 86 bytes on wire (688 bits), 86 bytes captured (688 bits) on interface -, id 0 Ethernet II, Src: XXX, Dst: XXX Internet Protocol Version 4, Src: XXX, Dst: XXX User Datagram Protocol, Src Port: 319, Dst Port: 319 Precision Time Protocol (IEEE1588) 0000 .... = majorSdoId: Unknown (0x0) .... 0001 = messageType: Delay_Req Message (0x1) 0001 .... = minorVersionPTP: 1 .... 0010 = versionPTP: 2 messageLength: 44 domainNumber: 44 minorSdoId: 0 flags: 0x0400 correctionField: 0.000000 nanoseconds messageTypeSpecific: 0 ClockIdentity: XXX SourcePortID: 1 sequenceId: 0 controlField: Delay_Req Message (1) logMessagePeriod: 127 originTimestamp (seconds): 0 originTimestamp (nanoseconds): 0
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
