Knowledge Base Article

Why Does a 528-bit PCS66 Phase Shift Occur with 400GZR/ZR+ Coherent Optical Modules on F-Tile Ethernet Hard IP?

Description

In the Quartus® Prime Pro Edition software version 26.3 and earlier, raw receive PCS66 parallel data might appear phase-shifted by 528 bits when a 400G-8 F-Tile Ethernet Hard IP design without the Media Access Control (MAC) block is connected to a 400GZR or ZR+ coherent optical module.

The shift equals eight 66-bit Physical Coding Sublayer (PCS) blocks, or half of the 1056-bit parallel word.
The 66-bit symbols can remain intact, and rx_block_lock andrx_am_lock can remain asserted.

This behavior can occur when the receive path selects the alternate 1:2 demultiplexer phase. The PCS does not provide parallel-data phase alignment relative to the original transmit AM and data relationship.

The behavior was observed in the raw Media Independent Interface (MII) PCS66 path. MAC and MAC Segment modes successfully transferred packets.
Electrical loopback, digital-to-analog converter loopback, internal serial loopback, and 400GE-8 short-reach optical paths did not show the same behavior.

Resolution

No Quartus Prime Pro Edition software fix is identified for this behavior at this time.
To work around this problem, use a packet-oriented higher layer where possible.
For designs that consume raw PCS66 data, follow these steps:

  1. Capture rx_pcs66_d and any available AM location or indication, rx_block_lock , and rx_am_lockas signals.
  2. Transmit a deterministic PCS66 block sequence that includes a unique known block pattern around the transmit AM location.
  3. Compare the received block sequence with the expected sequence to determine whether the received data
    is at offset 0 or offset 8 PCS66 blocks, which is a 528-bit offset.
  4. Implement protocol-specific realignment in the higher-level logic based on the detected offset.
  5. Do not use rx_am_lockas the sole phase detector. It indicates AM lock,
    but it does not identify which 1:2 demultiplexer phase is selected.

A generalized phase-correction method or dedicated status bit/register has not been identified.
The required realignment depends on the protocol consuming the raw PCS66 stream.

Additional Information

The current explanation is based on available data. It is generalized to all ZR/ZR+ module (subject to data availability). Customer-specific protocol details are required to define a complete phase-correction implementation or to suggest workarounds.

Updated 6 days ago
Version 3.0
No CommentsBe the first to comment