01.07.2013 Views

Xilinx Constraints Guide

Xilinx Constraints Guide

Xilinx Constraints Guide

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

INREG (Input Registers)<br />

Architecture Support<br />

Applicable Elements<br />

Propagation Rules<br />

Chapter 4: <strong>Xilinx</strong> <strong>Constraints</strong><br />

INREG (Input Registers) applies to register and latch instances with their D-inputs<br />

driven by input pads, or to the Q-output nets of such registers and latches. By default,<br />

registers and latches for CoolRunner XPLA3 and CoolRunner-II designs that have<br />

their D-inputs driven by input pads are automatically implemented using the device’s<br />

Fast Input path, where possible. If you disable the ISE® Design Suite property Use Fast<br />

Input for INREG for the Fit (Implement Design) process, then only register and latches<br />

with the INREG attribute are considered for Fast Input optimization.<br />

Applies to CoolRunner XPLA3 and CoolRunner-II devices only.<br />

Applies to register and latch instances with their D-inputs driven by input pads or to the<br />

Q-output nets of such registers or latches.<br />

Applies to register or latch to which it is attached or to the Q-output nets of such<br />

registers or latches<br />

Syntax Excamples<br />

The following examples show how to use this constraint with particular tools or<br />

methods. If a tool or method is not listed, you cannot use this constraint with it.<br />

Schematic Syntax<br />

• Attach to a register, latch, or net<br />

• Attribute Name<br />

INREG<br />

• Attribute Values<br />

None (TRUE by default)<br />

UCF Syntax<br />

NET “signal_name” INREG;<br />

INST “register_name” INREG;<br />

<strong>Constraints</strong> <strong>Guide</strong><br />

UG625 (v. 13.2) July 6, 2011 www.xilinx.com 139

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!