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

R

Chapter 11

XST Naming Conventions

This chapter (XST Naming Conventions) describes XST Naming Conventions. This chapter includes:

“XST Net Naming Conventions”

“XST Instance Naming Conventions”

“XST Name Generation Control”

XST Net Naming Conventions

This section discusses XST Net Naming Conventions. These rules are listed in order of naming priority:

1.Maintain external pin names.

2.Keep hierarchy in signal names, using forward slashes (/) or underscores (_) as hierarchy designators.

3.Maintain output signal names of registers, including state bits. Use the hierarchical name from the level where the register was inferred.

4.Ensure that output signals of clock buffers get _clockbuffertype (such as _BUFGP or _IBUFG) follow the clock signal name.

5.Maintain input nets to registers and tristates names.

6.Maintain names of signals connected to primitives and black boxes.

7.Name output net names of IBUFs using the form net_name_IBUF. For example, for an IBUF with an output net name of DIN, the output IBUF net name is DIN_IBUF.

8.Name input net names to OBUFs using the form net_name_OBUF. For example, for an OBUF with an input net name of DOUT, the input OBUF net name is DOUT_OBUF.

9.Base names for internal (combinatorial) nets on user HDL signal names where possible.

XST Instance Naming Conventions

This section discusses XST Instance Naming Conventions. These rules are listed in order of naming priority:

1.Keep hierarchy in instance names, using forward slashes (/) or underscores (_) as hierarchy designators.

When instance names are generated from VHDL or Verilog generate statements, labels from generate statements are used in composition of instance names.

XST User Guide

www.xilinx.com

585

10.1

Chapter 11: XST Naming Conventions

R

For example, for the following VHDL generate statement:

i1_loop: for i in 1 to 10 generate inst_lut: LUT2 generic map (INIT => "00")

XST generates the following instance names for LUT2:

i1_loop[1].inst_lut

i1_loop[2].inst_lut

i1_loop[9].inst_lut

...

i1_loop[10].inst_lut

2.Name register instances, including state bits, for the output signal.

3.Name clock buffer instances _clockbuffertype (such as _BUFGP or _IBUFG) after the output signal.

4.Maintain instantiation instance names of black boxes.

5.Maintain instantiation instance names of library primitives.

6.Name input and output buffers using the form _IBUF or _OBUF after the pad name.

7.Name Output instance names of IBUFs using the form instance_name_IBUF.

8.Name input instance names to OBUFs using the form instance_name_OBUF.

Xilinx highly recommends these instance naming conventions. To use instance naming conventions from previous releases of ISE™, insert the following command line option in the XST command line:

-old_instance_names 1

XST Name Generation Control

Use the following properties to control aspects of the manner in which names are written. Apply these properties using Project Navigator > Synthesis Properties, or the appropriate command line options. For more information, see “XST Design Constraints.”

“Hierarchy Separator (–hierarchy_separator)”

“Bus Delimiter (–bus_delimiter)”

“Case (–case)”

“Duplication Suffix (–duplication_suffix)”

586

www.xilinx.com

XST User Guide

 

 

10.1

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