05.07.2013 Views

Xilinx Synthesis Technology User Guide

Xilinx Synthesis Technology User Guide

Xilinx Synthesis Technology User 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.

XST <strong>User</strong> <strong>Guide</strong><br />

• Full Case (Verilog)<br />

The FULL_CASE directive is used to indicate that all possible<br />

selector values have been expressed in a case, casex, or casez<br />

statement. The directive prevents XST from creating additional<br />

hardware for those conditions not expressed. See the<br />

“Multiplexers” section of the “HDL Coding Techniques” chapter<br />

of this manual, and the “FULL_CASE” section in the Constraints<br />

<strong>Guide</strong> for details.<br />

• Generate RTL Schematic<br />

The Generate RTL Schematic (RTLVIEW) command line option<br />

enables XST to generate a netlist file, representing the RTL<br />

structure of the design. Note that this netlist generation is not<br />

available when Incremental <strong>Synthesis</strong> Flow is enabled. It can be<br />

specified by selecting the Generate RTL Schematic option under<br />

the <strong>Synthesis</strong> Options tab in the Process Properties dialog box<br />

within the Project Navigator, or with the -rtlview command line<br />

option. See the “RTLVIEW” section in the Constraints <strong>Guide</strong> for<br />

details.<br />

• Hierarchy Separator<br />

The Hierarchy Separator (HIERARCHY_SEPARATOR)<br />

command line option defines the hierarchy separator character<br />

that will be used in name generation when the design hierarchy<br />

is flattened. It can be specified by selecting the Hierarchy<br />

Separator option under the <strong>Synthesis</strong> Options tab in the Process<br />

Properties dialog box within the Project Navigator, or with the<br />

-hierarchy_separator command line option. See the<br />

“HIERARCHY_SEPARATOR” section in the Constraints <strong>Guide</strong> for<br />

details.<br />

• Iostandard<br />

Use the IOSTANDARD constraint to assign an I/O standard to<br />

an I/O primitive. See the “IOSTANDARD” section in the<br />

Constraints <strong>Guide</strong> for details.<br />

• Keep<br />

The KEEP constraint is an advanced mapping constraint. When a<br />

design is mapped, some nets may be absorbed into logic blocks.<br />

When a net is absorbed into a block, it can no longer be seen in<br />

the physical design database. This may happen, for example, if<br />

5-16 <strong>Xilinx</strong> Development System

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

Saved successfully!

Ooh no, something went wrong!