OpenFPGA/openfpga_flow/vpr_arch

Naming convention for VPR architecture files

Please reveal the following architecture features in the names to help quickly spot architecture files.

• k<lut_size>_: Look-Up Table (LUT) size of FPGA. If you have fracturable LUTs or multiple LUT circuits, this should be largest input size.
  • The keyword 'frac' is to specify if fracturable LUT is used or not.
  • The keyword 'Native' is to specify if fracturable LUT design is a native one (without mode switch) or a standard one (with mode switch).
• N<le_size>: Number of logic elements for a CLB. If you have multiple CLB architectures, this should be largest number.
• tileable<IO|ConcatWire>: If the routing architecture is tileable or not.
  • The keyword 'IO' specifies if the I/O tile is tileable or not
  • The keyword 'ConcatWire' specifies if the routing wires can be continued in the same direction or not. For example, L4 -> L1
• fracff<2edge>: Use multi-mode flip-flop model, where reset/set polarity is configurable. When 2edge is specified, clock polarity can be switched between postive edge triggered and negative edge triggered
• adder_chain: If hard adder/carry chain is used inside CLBs
• register_chain: If shift register chain is used inside CLBs
• scan_chain: If scan chain testing infrastructure is used inside CLBs
• __mem<mem_size>: If block RAM (BRAM) is used or not. If used, the memory size should be clarified here. The keyword 'wide' is to specify if the BRAM spans more than 1 column. The keyword 'frac' is to specify if the BRAM is fracturable to operate in different modes.
• __dsp<dsp_size>reg: If Digital Signal Processor (DSP) is used or not. If used, the input size should be clarified here.
  • The keyword 'wide' is to specify if the DSP spans more than 1 column.
  • The keyword 'frac' is to specify if the DSP is fracturable to operate in different modes.
  • The keyword 'reg' is to specify if the DSP has input and output registers. If only input or output registers are used, the keyword will be 'regin' or 'regout' respectively.
• mem<mem_size>: If block RAM (BRAM) is used or not. If used, the memory size should be clarified here. The keyword wide is to specify if the BRAM spanns more than 1 column.
• aib: If the Advanced Interface Bus (AIB) is used in place of some I/Os.
• multi_io_capacity: If I/O capacity is different on each side of FPGAs.
• reduced_io: If I/Os only appear a certain or multiple sides of FPGAs
• registerable_io: If I/Os are registerable (can be either combinational or sequential)
• IoSubtile: If I/O block contains sub tiles (more compact with a higher density of I/Os)
• CustomIoLoc: Use OpenFPGA's extended custom I/O location syntax
• rstOnLut: The reset signal of CLB can feed LUT inputs through a local routing architecture
• localClkGen: The clock signal of CLB can be generated by internal programmable resources
• localRstGen: The reset signal of CLB can be generated by internal programmable resources
• <feature_size>: The technology node which the delay numbers are extracted from.
• TileOrgz: How tile is organized.
  • Top-left (Tl): the pins of a tile are placed on the top side and left side only
  • Top-right (Tr): the pins of a tile are placed on the top side and right side only
  • Bottom-right (Br): the pins of a tile are placed on the bottom side and right side only
• GlobalTileClk: How many clocks are defined through global ports from physical tiles. is the number of clocks

Other features are used in naming should be listed here.

Update architecture files in batch

From v1.1 to v1.2

make v1p1_to_v1p2