Transmit 1588 Insertion and Timestamp Function - 3.1 English - PG203

UltraScale+ Devices Integrated 100G Ethernet Subsystem LogiCORE IP Product Guide (PG203)

Document ID
PG203
Release Date
2024-07-17
Version
3.1 English

The egress logic uses an operation/command bus to identify frames that require time stamping returned to the user, or frames for which a timestamp should be inserted. See Table 13 for a description of the command fields.

Transmit timestamping is illustrated in the following figure.

Figure 1. TX Timestamping
UltraScale Architecture Integrated Block for 100G Ethernet (CMAC) Page-1 Sheet.1 10(4) 10(4) Sheet.2 Standard Arrow.483 Sheet.4 Sheet.5 2-step Logic 2-stepLogic Standard Arrow.483 Sheet.7 ctl_tx_systemtimerin[80-1:0] tx_ptp_1588op_in[1:0] tx_ptp_tag... ctl_tx_systemtimerin[80-1:0]tx_ptp_1588op_in[1:0]tx_ptp_tag_field_in[15:0]tx_ptp_upd_cksum_intx_ptp_chksum_offset_in[15:0]tx_ptp_tstamp_offset_in[15:0]ctl_tx_ptp_1step_enablectl_tx_ptp_transpclk_modectl_tx_ptp_vlane_adjustctl_tx_ptp_latency_adjust[10:0] Sheet.8 Sheet.9 Core Logic CoreLogic Standard Arrow.10 Sheet.11 1-step Logic Including UDP Checksum Update 1-step Logic Including UDP Checksum Update Standard Arrow.12 Sheet.13 TX LBUS Adapter TX LBUS Adapter Standard Arrow.14 Sheet.15 TX LBUS TX LBUS Arrow Standard Right.16 Sheet.17 stat_tx_ptp_fifo_write_error stat_tx_ptp_fifo_read_error tx_p... stat_tx_ptp_fifo_write_errorstat_tx_ptp_fifo_read_errortx_ptp_tstamp_valid_outtx_ptp_pcslane_out[5-1:0]tx_ptp_tstamp_tag_out[15:0]tx_ptp_tstamp_out[79:0] Standard Arrow.16 Standard Arrow.20 Sheet.20 SerDes SerDes Sheet.21 10(4) 10(4) Sheet.22 Standard Arrow.483 Sheet.24 Sheet.25 PCS Lane MUX PCS Lane MUX Sheet.26 20 20 Sheet.27 Standard Arrow.483 Sheet.29 Sheet.30 Gearbox Gearbox Bracket.284 Bracket.32 Arrow Standard Right.33 Sheet.34 Sheet.35 Standard Arrow.484 Sheet.37 Sheet.38 seq seq Sheet.39 Sheet.40 TS2 TS2 Sheet.41 TS1 TS1 Standard Arrow.41 Sheet.43 Sheet.44 Sheet.45 Rounded rectangle.487 Lane Logic Lane Logic Sheet.47 Note: Some core logic and lane logic blocks are not shown for... Note: Some core logic and lane logic blocks are not shown for clarity. Sheet.48 Sheet.49 X14344 X14344 Sheet.50 TS2' TS2' Sheet.51 seq seq Standard Arrow.52 Standard Arrow.53

As seen on the diagram, timestamping logic exists in two locations depending on whether 1-step or 2-step operation is desired. 1-step operation requires UDP checksum and FCS updates and therefore the FCS core logic is re-used.

The TS references are defined as follows:

  • TS1: The output timestamp signal when a 1-step operation is selected.
  • TS2: The output timestamp signal when a 2-step operation is selected.
  • TS2': The plane to which both timestamps are corrected.

TS2 always has a correction applied so that it is referenced to the TS2' plane. TS1 might or might not have the TS2' correction applied, depending on the value of the signal ctl_tx_ptp_latency_adjust[7:0] . The default value of this signal is 90 (decimal).

On the transmit side, a control input is provided by the client to the subsystem in parallel with the frame sent for transmission. This indicates, on a frame-by-frame basis, the 1588 function to perform (either no-operation, 1-step, or 2-step) and also indicates, for 1-step frames, whether there is a UDP checksum field to update.

  • If using the Ordinary Clock mode, then for both 1-step and 2-step operations, the full captured 80-bit ToD timestamp is returned to the client logic using the additional ports defined in Table 13 and Table 14.
  • If using the Transparent clock mode, then for both 1-step and 2-step operations, the full captured 64-bit timestamp is returned to the client logic using the additional ports defined in Table 13 and Table 14 (with the upper bits of data set to zero as defined in the table).
  • If using the Ordinary Clock mode, then for a 1-step operation, the full captured 80-bit ToD timestamp is inserted into the frame. If using the Transparent clock mode, then for 1-step operation, the captured 64-bit timestamp is summed with the existing Correction Field contained within the frame and the summed result is overwritten into the original Correction Field of the frame. Supported frame types for 1-step timestamping are:
  • Raw Ethernet
  • UDP/IPv4
  • UDP/IPv6

For 1-step UDP frame types, the UDP checksum is updated in accordance with IETF RFC 1624. For all 1-step frames, the Ethernet Frame Check Sequence (FCS) field is calculated after all frame modifications have been completed. For 2-step transmit operation, all Precision Time Protocol (PTP) frame types are supported.