Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
xst.pdf
Скачиваний:
141
Добавлен:
11.06.2015
Размер:
5.64 Mб
Скачать

Chapter 5: XST Design Constraints

R

The following constraints use a different syntax:

“Parallel Case (PARALLEL_CASE)”

“Full Case (FULL_CASE)”

“Translate Off (TRANSLATE_OFF) and Translate On (TRANSLATE_ON)”

For more information, see “Verilog Attributes and Meta Comments.”

XST Constraint File (XCF)

This section discusses the XST Constraint File (XCF), and includes:

“Specifying the XST Constraint File (XCF)”

“XCF Syntax and Utilization”

“Native and Non-Native User Constraint File (UCF) Constraints Syntax”

“XCF Syntax Limitations”

Specifying the XST Constraint File (XCF)

XST constraints can be specified in the Xilinx Constraint File (XCF). The XCF has an extension of .xcf. For information on specifying the XCF in ISE, see the ISE Help.

To specify the XCF in command line mode, use “Synthesis Constraint File (–uc)” with the run command. For more information about the run command and running XST from the command line, see “XST Command Line Mode.”

XCF Syntax and Utilization

The XST Constraint File (XCF) syntax enables you to specify a specific constraint for:

The entire device (globally), or

Specific modules

The XCF syntax is basically the same as the User Constraint File (UCF) syntax for applying constraints to nets or instances, but with an extension to the syntax to allow constraints to be applied to specific levels of hierarchy. Use the keyword MODEL to define the entity or module to which the constraint is applied. If a constraint is applied to an entity or module, the constraint is applied to each instance of the entity or module.

Define constraints in Project Navigator > Process Properties, or the XST run script, if running on the command line. Specify exceptions in the XCF file. The constraints specified in the XCF file are applied ONLY to the module listed, and not to any submodules below it.

To apply a constraint to the entire entity or module use the following syntax:

MODEL entityname constraintname = constraintvalue;

Examples

MODEL top mux_extract = false;

MODEL my_design max_fanout = 256;

If the entity my_design is instantiated several times in the design, the max_fanout=256 constraint is applied to each instance of my_design.

316

www.xilinx.com

XST User Guide

 

 

10.1

R

XST Constraint File (XCF)

To apply constraints to specific instances or signals within an entity or module, use the INST or NET keywords. XST does not support constraints that are applied to VHDL variables.

BEGIN MODEL entityname

INST instancename constraintname = constraintvalue ;

NET signalname constraintname = constraintvalue ;

END;

Examples

BEGIN MODEL crc32

INST stopwatch opt_mode = area ;

INST U2 ram_style = block ;

NET myclock clock_buffer = true ;

NET data_in iob = true ;

END;

For a complete list of XST synthesis constraints, see “XST-Specific Non-Timing Options.”

Native and Non-Native User Constraint File (UCF) Constraints Syntax

All constraints supported by XST can be divided into two groups:

“Native User Constraint File (UCF) Constraints”

“Non-Native User Constraint File (UCF) Constraints”

Native User Constraint File (UCF) Constraints

Only Timing and Area Group constraints use native User Constraint File (UCF) syntax.

Use native UCF syntax, including wildcards and hierarchical names, for native UCF constraints such as:

“Period (PERIOD)”

“Offset (OFFSET)”

“Timing Name on a Net (TNM_NET)”

“Timegroup (TIMEGRP)”

“Timing Ignore (TIG)”

“From-To (FROM-TO)”

Do not use these constraints inside the BEGIN MODEL... END construct. If you do, XST issues an error.

Non-Native User Constraint File (UCF) Constraints

For all non-native User Constraint File (UCF) constraints, use the MODEL or BEGIN

MODEL... END; constructs. This includes:

Pure XST constraints such as:

“Automatic FSM Extraction (FSM_EXTRACT)”

“RAM Style (RAM_STYLE)”

XST User Guide

www.xilinx.com

317

10.1

Соседние файлы в предмете [НЕСОРТИРОВАННОЕ]