AR# 35055

描述

解决方案

Macro Description

Starting in ISE Design Suite 12.1, MAP inserts a macro that instantiates each transceiver that is not already being used by the design. This macro protects from the Delay Aligner performance degradation causing RXRECCLK Static Operating Behavior. The macro only instantiates unused GTX Transceivers and does not use any additional logic or routing.

Known Issues

• Additional power usage: Those GTX Transceivers instantiated by the macro use additional power to what would otherwise be consumed by an unused transceiver. These numbers are included in the PA power estimation tool in 12.1, and will be added to the XPE power estimation spreadsheets.
  

  	Typical	Maximum
  MGTAVCC	30.5 mA	41.9 mA
  MGTAVTT	25.7 mA	26.9 mA

• Netgen Discrepancies: Netgen removes the inserted macro from the design for post-MAP/PAR timing simulations. This does not impact the results of the simulation and allows simulations to run faster. (Xilinx Answer 35514) discusses this issue in greater depth.

Disabling Macro Insertion

If the Delay Aligner is not used (*), it is possible to disable the MAP feature which inserts the macro. There are two different methods available, depending on the version of tool being used. In 12.1, the user can create the following environment variable which disables any macro insertion:

XIL_MAP_NO_INSERT_GTXE1_PWRUP = 1

This work-around is only valid for ISE Design Suite 12.1. In 12.2, more granular disabling is possible via the PROHIBIT UCF constraint. Using the prohibit constraint on a specific GTX location keeps MAP from inserting the macro on that specific GTX.

For example:
CONFIG PROHIBIT = GTXE1_X0Y5;
See (Xilinx Answer 38933).

Note that 12.2 only supports the PROHIBIT constraint for disabling macro insertion. TheXIL_MAP_NO_INSERT_GTXE1_PWRUP environment variable is not supported for 12.2.

(*) Note

As per Errata EN142, the Delay Aligner is no longer supported. For this reason the DA protecting macro is no longer required.