We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 60733

OTN IP - signal clarifications


This Article contains information on the following:

  • tx_tpcsm_lane0_sync_err
  • rx_tpcsm_vlmarker
  • CAUI_In_Rep


tx_tpcsm_lane0_sync_err: How should this signal be used?

This is removed in the next version of the 100GE Mapper package. 

Tie off to ZERO in the interim.

rx_tpcsm_vlmarker: What are the requirements for this signal?

This input is unused in the mapper and is only there to match the output interface of the CAUI. 

It can either be connected to the CAUI rx_tpcsm_vlmarker output or tied off to ZERO.

CAUI_In_Rep: When will this signal will be driven? Is there any difference between it and rx_tpcsm_fault?

This input can be wired to a top-level CSR (reg) bit if needed to provide a software controlled replacement.

See the top right hand corner of (UG420) figure 2 for the internal block wiring.

rx_tpcsm_fault has the same effect and can be wired to not(stat_rx_status) from the CAUI providing an automatic replacement.
AR# 60733
Date Created 05/20/2014
Last Updated 03/09/2015
Status Active
Type General Article
  • Virtex-7
  • Vivado Design Suite - 2014.1