by There are some basic setups before running synthesis. By setting “search_path”, designers do not need to specify the absolute paths of files; Designers needs to specify the target technology library as well as the link library to resolve all instances inside the design.
|
1 2 3 4 5 6 7 |
# no longer need to specify the absolute path of the files # directory “libs” may contain the target library as well as any IP library cell/macros used in the design set_app_var search_path “$search_path rtl constraints libs" # set target technology library set_app_var target_library 16nm_wc.db # set link library to resolve all instances instantiated in the design set_app_var link_library “* $target_library” |
To run Topographical synthesis / production synthesis, physical data is required. The following example shows how to setup milkyway design library for DC-Topographical.
|
1 2 3 4 |
# specify reference libraries set_app_var mw_reference_library “./mw_libs/sc ./mw_libs/macros” # specify the name of the Milkyway library set_app_var mw_design_library ./design_lib |
If this is the first time for loading physical technology data, user must create a Milkyway design library as a “container”. This is used to package up the reference libraries, the technology file and TLU-plus models for use by DC-topographical
|
1 2 3 4 |
# create milkyway library create_mw_lib -technology ./mw_libs/tech/16nm.tf \ -mw_reference_library $mw_reference_library \ $mw_design_library |
The next step is to load an already existing design library:
|
1 2 3 4 5 6 7 |
# The following needs to be done all the time. This is for reloading an existing design library open_mw_lib $mw_design_library # make sure there is no error with the design library check_library set_tlu_plus_files -max_tluplus ./mw_libs/tlup/16nm_max.tluplus -tech2itf_map ./mw_libs/tlup/16nm.map # make sure there is no error with the TLUPlus file check_tlu_plus_files |
This concludes the basic setups before running synthesis. In next post, we will cover the DC synthesis flow.
2 Comments