This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DRA62x CPTS 1588 Annex D打时标不成功问题

我们在DRA624上调试cpts,发现cpu向外发送的annex D peer delay req报文无法打上时标

根据1588协议,Peer delay Request报文的目的地址是224.0.0.107,但CPTS手册里关于tx数据包打时标的过滤条件有目的ip范围在224.0.1.129~132,与协议要求的不一致。

我在e2e上看到有同样的问题,但原厂没有回复

请问这是一个CPU的bug么?

The Technical Reference Manual for the AM335X states that the 3PSW ethernet subsystem supports
IEEE 1588v2 Clock Synchronization (2008 Annex D and Annex F).

In a custom board with the AM3356 microprocessor is running the linuxptp stack and I have
found that UDP (Annex D - Transport of PTP over User Datagram Protocol over Internet Protocol) with peer 
delay mechanism doesn´t work (the peer delay messages are not timestamped).

With the annex F (Transport of PTP over IEEE 802.3 /Ethernet) configuration and Peer delay
mechanism the PTP synchronization works properly.

The Technical Reference Manual (SPRUH73N October 2011–Revised June 2016), 
chapter 14.3.2.2.2.2 Annex D (IEEE 1588v2 Transmit Packet Operation), indicates that
a packet is determined to be a transmit event packet if the following is met:

...

6. Byte 30 contains decimal 224 (0xe0)
7. Byte 31 contains 0x00
8. Byte 32 contains 0x01
9. Byte 33 contains one of the following:
• Decimal 129 and the pX_ts_129 bit in the switch Px_Control register is set
• Decimal 130 and the pX_ts_130 bit in the switch Px_Control register is set
• Decimal 131 and the pX_ts_131 bit in the switch Px_Control register is set
• Decimal 132 and the pX_ts_132 bit in the switch Px_Control register is set

These values correspond to the multicast addresses 224.0.1.129 - 224.0.1.132,

but what about the multicast address 224.0.0.107 used by the Peer delay mechanism messages?

Could this be the reason that these messages are not timestamped?