文件列表:

PT (0, 2013-06-09)
PT\PT-RMsettings.txt (934, 2010-05-19)
PT\Release_Notes.PT-RM.txt (13412, 2010-05-19)
PT\rm_pt_scripts (0, 2013-06-09)
PT\rm_pt_scripts\pt.tcl (5974, 2010-05-19)
PT\rm_setup (0, 2013-06-09)
PT\rm_setup\common_setup.tcl (4889, 2010-05-19)
PT\rm_setup\pt_setup.tcl (2727, 2010-05-19)

#################################################################################### # PrimeTime Reference Methodology # Version: D-2009.12-SP2 (March 29, 2010) # Copyright (C) 2009-2010 Synopsys All rights reserved. #################################################################################### The reference methodology provides users with a set of reference scripts that serve as a good starting point for running each tool. These scripts are not designed to run in their current form. They should be used as a reference and adapted for use in your design environment. The PrimeTime Reference Methodology includes options for running PrimeTime, PrimeTime SI, and PrimeTime VX. Note that an additional license is required when running PrimeTime SI and PrimeTime VX. The PrimeTime Reference Methodology also includes options for running multivoltage scaling libraries and UPF mode, options for running power analysis, and a link to TetraMAX. Note that IEEE 1801 (TM) is also known as the Unified Power Format (UPF). The PrimeTime Reference Methodology includes the following scripts ================================================================== PT-RMsettings.txt - Reference methodology option settings that were selected when the scripts were generated README.PT-RM.txt - Information and instructions for setting up and running the PrimeTime Reference Methodology scripts Release_Notes.PT-RM.txt - Release notes for the PrimeTime Reference Methodology scripts listing the incremental changes in each new version of the scripts common_setup.tcl - Common design setup variables for all reference methodologies, including those for Design Compiler, IC Compiler, and TetraMAX pt_setup.tcl - Library and variable setup for PrimeTime Reference Methodology rm_pt_scripts/pt.tcl - PrimeTime Reference Methodology generic run script for PrimeTime rm_pt_scripts/dmsa.tcl - PrimeTime Reference Methodology DMSA run script for PrimeTime rm_pt_scripts/dmsa_mc.tcl - PrimeTime Reference Methodology DMSA scenario script for PrimeTime rm_pt_scripts/dmsa_analysis.tcl - PrimeTime Reference Methodology DMSA analysis script for PrimeTime rm_pt_scripts/ptvx.tcl - PrimeTime Reference Methodology PrimeTime VX run script for PrimeTime rm_pt_scripts/ptvx_varlib.tcl - PrimeTime Reference Methodology PrimeTime VX library script for PrimeTime rm_pt_scripts/ptvx_dmsa_comb.tcl - PrimeTime Reference Methodology PrimeTime VX with DMSA run script for PrimeTime rm_pt_scripts/ptvx_dmsa_comb_mc.tcl - PrimeTime Reference Methodology PrimeTime VX with DMSA scenario script for PrimeTime rm_pt_scripts/ptvx_dmsa_comb_analysis.tcl - PrimeTime Reference Methodology PrimeTime VX with DMSA analysis script for PrimeTime Instructions for using the PrimeTime Reference Methodology ========================================================== 1. Copy the reference methodology files to a new location. 2. Edit the common_setup.tcl file to set the design name, search path, and library information for your design. 3. Edit the pt_setup.tcl file to further customize your PrimeTime setup. This file is designed to work automatically with the values provided in the common_setup.tcl file. 4. Edit the pt_scripts/pt.tcl file to customize the steps that you want to perform in your static timing analysis. Read the script carefully, note the comments, and choose which steps you want to include in your analysis. You might also want to change the file names to support your design environment. This is a reference example and it requires modification to work with your design. 5. Run your static timing analysis by using the appropriate run script based on the flow you selected. For the standard reference methodology flow, run the tool from the directory above the rm_setup directory. For the Lynx-compatible reference methodology flow, run the tool from a directory tree that is parallel to the working directory. The working directory name should be $rm_root/rm_pt/tmp, and the directory $rm_root/rm_pt/logs should also exist before you run the tool. To run the generic flow, enter one of the following commands: o For the standard reference methodology flow, enter % pt_shell -f rm_pt_scripts/pt.tcl | tee ptlog o For the Lynx-compatible reference methodology flow, enter % pt_shell -f ../../scripts_block/rm_pt_scripts/pt.tcl | tee ../logs/ptlog To run the DMSA flow, enter one of the following commands: o For the standard reference methodology flow, enter % pt_shell -multi -f rm_pt_scripts/dmsa.tcl | tee dmsalog o For the Lynx-compatible reference methodology flow, enter % pt_shell -multi \ -f ../../scripts_block/rm_pt_scripts/dmsa.tcl | tee ../logs/dmsalog To run the PrimeTime VX flow, enter one of the following commands: o For the standard reference methodology flow, enter % pt_shell -f rm_pt_scripts/ptvx.tcl | tee ptvxlog o For the Lynx-compatible reference methodology flow, enter % pt_shell \ -f ../../scripts_block/rm_pt_scripts/ptvx.tcl | tee ../logs/ptvxlog To run the PrimeTime VX with DMSA flow, enter one of the following commands: o For the standard reference methodology flow, enter % pt_shell -multi -f rm_pt_scripts/ptvx_dmsa_comb.tcl | tee ptvxdmsalog o For the Lynx Compatible reference methodology flow, enter % pt_shell -multi \ -f ../../scripts_block/rm_pt_scripts/ptvx_dmsa_comb.tcl \ | tee ../logs/ptvxdmsalog Input files for PrimeTime Reference Methodology =============================================== Note: Not all of these files are required. You can change these default names. ================ Flow Independent ================ ${NETLIST_FILES} (list of Verilog netlist files defined in pt_setup.tcl) ============ Generic Flow ============ ${libraries} (Library files) ${mv1_scaling_library} (Multivoltage scaling library (1) file) ${mv2_scaling_library} (Multivoltage scaling library (2) file) ${UPF_FILE} (UPF setup file) ${SDF_PATHS} (Standard Delay Format (SDF) path for SDF file, if SDF back annotation flow is used) ${SDF_FILES} (SDF file, if SDF back annotation flow is used) ${PARASITIC_PATHS} (Path to parasitics file if either a Synopsys Binary Parasitic Format (SBPF) file or a Standard Parasitic Exchange Format (SPEF) file is used) ${PARASITIC_FILES} (Parasitic file, either SBPF or SPEF file can be used) ${CONSTRAINT_FILES} (Timing constraint files for the design) ${AOCVM_FILES} (Advanced OCV mode derate file) ${ACTIVITY_FILE} (Switching activity file for power analysis) ${STRIP_PATH} (Provides strip path setting for the switching activity file) ${NAME_MAP_FILE} (Name mapping file for power analysis) ${TMAX2PT_OUTPUT_FILE} (TetraMAX generated files) ${PT2TMAX_SCRIPT_FILE} (pt2tmax tool command language (Tcl) script file) ========= DMSA Flow ========= Libraries, UPF, SDF, AOCVM, and parasitic files are corner based: ${dmsa_corner_library_files($corner)} (Library files) ${dmsa_mv1_scaling_library($corner)} (Multivoltage scaling library (1) file) ${dmsa_mv2_scaling_library($corner)} (Multivoltage scaling library (2) file) ${dmsa_UPF_FILE} (Unified Power Format setup file) ${SDF_PATHS($corner)} (Path to SDF file, if SDF back annotation flow is used) ${SDF_FILES($corner)} (SDF file, if SDF back annotation flow is used) ${PARASITIC_PATHS($corner)} (Path to parasitics file, if either SBPF or SPEF file is used) ${PARASITIC_FILES($corner)} (Parasitic file, if either SBPF or SPEF file is used) ${AOCVM_FILES($corner)} (Advanced OCV mode file for each corner) ${ACTIVITY_FILE} (Switching activity file for power analysis) ${STRIP_PATH} (Provides strip path setting for the switching activity file) ${NAME_MAP_FILE} (Name mapping file for power analysis) Constraints Are Mode Based: ${dmsa_mode_constraint_files($mode)} (Mode-dependent timing constraints for the design) ${TMAX2PT_OUTPUT_FILE($mode)} (Mode-dependent TetraMAX generated files) ================= PrimeTime VX Flow ================= ${ptvx_unified_libraries} (PrimeTime VX unified library file) ${ptvx_nominal_libraries} (PrimeTime VX nominal library files) ${UPF_FILE} (UPF setup file) ${SDF_PATHS} (Path to SDF file, if SDF back annotation flow is used) ${SDF_FILES} (SDF file, if SDF back annotation flow is used) ${PARASITIC_PATHS} (Path to parasitics file, if either SBPF or SPEF file is used) ${PARASITIC_FILES} (Parasitic file, if either SBPF or SPEF file is used) ${CONSTRAINT_FILES} (Timing constraint files for the design) =========================== PrimeTime VX with DMSA Flow =========================== Libraries, UPF, SDF, and parasitic files are corner based: ${ptvx_unified_libraries($corner)} (Library file) ${ptvx_nominal_libraries($corner)} (PrimeTime VX multivoltage scaling library files) ${dmsa_UPF_FILE} (UPF setup file) ${SDF_PATHS($corner)} (Path to SDF file, if SDF back annotation flow is used) ${SDF_FILES($corner)} (SDF file, if SDF back annotation flow is used) ${PARASITIC_PATHS($corner)} (Path to parasitics file, if either SBPF or SPEF file is used) ${PARASITIC_FILES($corner)} (Parasitic file, if either SBPF or SPEF file is used) Constraints Are Mode Based: ${dmsa_mode_constraint_files($mode)} (Mode-dependent timing constraints for the design) Output files from PrimeTime Reference Methodology ================================================= For all the flows--generic, DMSA, PrimeTime VX, and PrimeTime VX with DMSA: ${REPORTS} directory defined in pt_setup.tcl contains reports from the static timing analysis run. For the DMSA and PrimeTime VX with DMSA flows, you should inspect the following subdirectory: Each mode or corner (scenario) of a DMSA run has a log file located at: /work/scenario/out.log You should analyze the output files generated by the PrimeTime Reference Methodology scripts to resolve issues with the setup (check_timing -verbose and report_clock) and timing violations (report_timing and report_constraints).

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：