I'm using a board with an AM3356 microprocessor and I have found that PTP Peer delay messages over
UDP seem not to be timestamped by the 3PSW Ethernet subsystem (the CPTS does not push onto the
event FIFO this kind of messages).
The Technical Reference Manual (SPRUH73N October 2011–Revised June 2016), for the 3PSW Ethernet subsystem,
in chapter "IEEE 1588v2 Receive Packet Operation" (14.3.2.2.1.2 Annex D) states that a packet is determined
to be a receive event packet under the following conditions:
...
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 129 and the pX_ts_132 bit in the switch Px_Control register is set
For "IEEE 1588v2 Transmit Packet Operation" (14.3.2.2.2.2 Annex D) states 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 IPv4 multicast addresses 224.0.1.129 - 224.0.1.132, but
the multicast address 224.0.0.107 used by the Peer delay mechanism messages is not considered.
Could this be the reason that these messages are not timestamped?
