add readme for architecture file naming
This commit is contained in:
parent
1015880d0e
commit
20cf4acda0
|
@ -0,0 +1,17 @@
|
|||
# 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.
|
||||
- frac: If fracturable LUT is used or not.
|
||||
- N<le\_size>: Number of logic elements for a CLB. If you have multiple CLB architectures, this should be largest number.
|
||||
- tileable: If the routing architecture is tileable or not.
|
||||
- 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
|
||||
- <wide>\_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
|
||||
- <feature_size>: The technology node which the delay numbers are extracted from.
|
||||
|
||||
Other features are used in naming should be listed here.
|
Loading…
Reference in New Issue