SPRUII0F May 2019 – June 2024 TMS320F28384D , TMS320F28384D-Q1 , TMS320F28384S , TMS320F28384S-Q1 , TMS320F28386D , TMS320F28386D-Q1 , TMS320F28386S , TMS320F28386S-Q1 , TMS320F28388D , TMS320F28388S
Table 43-13 shows the common message header for the PTP messages. This format is taken from the IEEE 1588-2008.
Bits | |||||||||
---|---|---|---|---|---|---|---|---|---|
7 | 6 | 5 | 4 | 3 | 2 | 1 | 0 | Octet | Offset |
transportSpecific | messageType(1) | 1 | 0 | ||||||
Reserved | versionPTP | 1 | 1 | ||||||
messageLength | 2 | 2 | |||||||
domainNumber | 1 | 4 | |||||||
Reserved | 1 | 5 | |||||||
flagField | 2 | 6 | |||||||
correctionField | 8 | 8 | |||||||
Reserved | 4 | 16 | |||||||
sourcePortIdentity | 10 | 20 | |||||||
sequenceId | 2 | 30 | |||||||
controlField(1) | 1 | 32 | |||||||
logMessageInterval | 1 | 33 |
There are some fields in the Ethernet payload that you can use to detect the PTP packet type and control the snapshot to be taken. These fields are different for the following PTP packets: