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.

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

FROM-THRU-TO (From Thru To)<br />

Architecture Support<br />

Applicable Elements<br />

Propagation Rules<br />

The FROM-THRU-TO constraint:<br />

• Is an advanced timing constraint,<br />

• Is associated with the Period constraint of the high or low time.<br />

From synchronous paths, a FROM-TO-THRU constraint controls only the setup path,<br />

not the hold path. This constraint applies to a specific path that begins at a source<br />

group, passes through intermediate points, and ends at a destination group. The source<br />

and destination groups can be either user or predefined groups. You must define an<br />

intermediate path using TPTHRU before using THRU.<br />

Applies to FPGA devices. Does not apply to CPLD devices.<br />

Predefined and user-defined groups<br />

Applies to the specified FROM-THRU-TO path only.<br />

Syntax Examples<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 />

UCF and NCF Syntax<br />

TIMESPEC “TSidentifier”=FROM “source_group” THRU “thru_pt1”...[THRU “thru_pt2”<br />

...] TO “destination_group” value [Units] [DATAPATHONLY];<br />

where<br />

• identifier can consist of characters or underbars<br />

• source_group and destination_group are user-defined or predefined groups<br />

• thru_pt1 and thru_pt2 are intermediate points to define specific paths for timing<br />

analysis<br />

• value is the delay time<br />

• units can be ps, ms, ns, or micro<br />

The DATAPATHONLY keyword indicates that the FROM-TO constraint does not take<br />

clock skew or phase information into consideration. This keyword results in only the<br />

data path between the groups being constrained and analyzed.<br />

TIMESPEC TS_MY_PathB = FROM “my_src_grp” THRU “my_thru_pt” TO “my_dst_grp” 13.5 ns DATAPATHONLY;<br />

FROM or TO is optional. You can have just a FROM or just a TO.<br />

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

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

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

Saved successfully!

Ooh no, something went wrong!