The ASSIGN_PIN_DELAYS MACRO tells dal constraints to add pin_delay information from a spreadsheet type file for a list of Reference Designators in your design
PIN_DELAY FILE
The PIN_DELAY_FILE is expected to be a list of comma separated rows where the pin delay for each pin is specified.
The FILE_HDR_ROWS and FILE_CONTENT_FMT attributes allow the user to tell dal_constraints how the pin-delayt data is actually formatted in the file.
Note that any row starting with a '#' in the pin_delay_file witll
REF_DES
The REF_DES Attribute is a comma separated List of patterns used to identify the target of the ASSIGN_PIN_DELAYS MACRO
Syntax:
REF_DES=>REF_DES_1,REF_DES_N...,REF_DES_N
dalTools will assign pinDelay data it extracts from the FILE attribute to every REF_DES in the List
Example:
REF_DES=>U1,U2,U3,U83
Here dal constraints will add the data from the specified FILE to any part in the design whose Reference designator (or LOCATION) property= U1 or U2 or U2 or U83
Future: PART_NUMBER
This would be a more portable way to define pin_delays since the PartNumber would be consistent across designs while the REF_DES would probably be different
The PART_NUMBER Attribute is a comma separated List of PART_NUMBERS used to identify the target of the ASSIGN_PIN_DELAYS MACRO
This would work well if the organization adds a unique PART_NUMBER to each device in their library.
Syntax:
PART_NUMBER=>PART_NUMBER_1,PART_NUMBER_2...,PART_NUMBER_N
dalTools will assign pinDelay data it extracts from the FILE attribute to every part in the design whose partNumber poperty matches one of the PART_NUMBERS in the list
Example:
PART_NUMBER=>1005_0004_001
Here dal constraints will add the data from the specified FILE to any part in the design whose PART_NUMBER property=1005_0004_001
if U1,U2,U3 and U83 were the same part with PartNumber=1005_0004_001 then this would be equivalent to the REF_DES attribute above (and would also be portable to another design that uses PN:1005_0004_001
To implement this properly, dal constraints might need a configuration setting to define which device property actually maps to the PART_NUMBER property,
as some organizations may use a different name for the PART_NUMBER property
FILE
The FILE Attribute points to the PIN_DELAY_FILE which contains all the available pin-delay data for a device.
Syntax:
FILE=>FILE_NAME or FILE=>FULL_PATH_TO_FILE_NAME
The FILE attribute that dal constraints will read to extract pin-delay data for each PIN_NAME or PIN_NUM (depending on the MAP_DLY_USING attribute)
The file may be specified as a relative path or with a fully qualified path.
Example:
FILE=>PinDelayInfo/HC1B_MC_SGD_FPGA_dly.csv
in this case the file assignment is a relative path, so there must be a PinDelayInfo directory in the same directory as the .brd file containing the HC1B_MC_SGD_FPGA_dly.csv file.
FILE_HDR_ROWS
The FILE_HDR_ROWS Attribute tells dal constraints which rows to skip when reading the PIN_DELAY_FILE
Syntax:
FILE_HDR_ROWS=>NONE
or
FILE_HDR_ROWS=>ROW_NUM_1,ROW_NUM_2...ROW_NUM_N
The user can specify that the FILE contains no HEADER rows using NONE
or they can provide a comma separated list of Rows to skip when reading the pin_delay file
Example:
FILE=>PinDelayInfo/HC1B_MC_SGD_FPGA_dly.csv
in this case the file assignment is a relative path, so there must be a PinDelayInfo directory in the same directory as the .brd file containing the HC1B_MC_SGD_FPGA_dly.csv file.
0 Comments