10.12.2012 Views

Quartus II Settings File Reference Manual - Altera

Quartus II Settings File Reference Manual - Altera

Quartus II Settings File Reference Manual - Altera

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.

6–92 Chapter 6: Fitter Assignments<br />

DUAL_PURPOSE_CLOCK_PIN_DELAY<br />

DUAL_PURPOSE_CLOCK_PIN_DELAY<br />

Type<br />

Specifies the propagation delay from a dual-purpose clock pin to its fan-out<br />

destinations that are routed on the global clock network. Legal integer values range<br />

from 0 through 63 for Cyclone and Cyclone <strong>II</strong> device families and from 0 through 11<br />

for Cyclone <strong>II</strong>I, where 0 is the setting with the least delay and 63 is the setting with the<br />

most delay. This is an advanced option that should be used only after you have<br />

compiled a project, checked the I/O timing, and determined that the timing is<br />

unsatisfactory. For detailed information on how to use this option, refer to the data<br />

sheet for the device family. This option is ignored if it is applied to anything other<br />

than an input or bidirectional pin, or if the pin is user assigned to a non-dual-purpose<br />

clock pin location.<br />

Integer<br />

Device Support<br />

This setting can be used in projects targeting the following device families:<br />

■ Cyclone<br />

■ Cyclone <strong>II</strong><br />

■ Cyclone <strong>II</strong>I<br />

■ Cyclone <strong>II</strong>I LS<br />

■ Cyclone IV E<br />

■ Cyclone IV GX<br />

Notes<br />

This assignment supports wildcards.<br />

Syntax<br />

set_instance_assignment -name DUAL_PURPOSE_CLOCK_PIN_DELAY -to -<br />

entity <br />

<strong>Quartus</strong> <strong>Settings</strong> <strong>File</strong> June 2012 <strong>Altera</strong> Corporation<br />

<strong>Reference</strong> <strong>Manual</strong>

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

Saved successfully!

Ooh no, something went wrong!