12 Batch Mode Execution

Overview

This chapter covers details of how to run Voltus-Fi-L in the batch mode including all the data requirements.

Migrating from Legacy (VPS-L) to Voltus-Fi-L in Batch Mode

The batch mode flow of Voltus-Fi-L supports both the configuration file, or the conf file used in Voltus-Fi-XL for IR/EM analysis, and the command file, cmd_file, used in the legacy (VPS-L) batch mode.

Support is provided to convert an existing legacy (VPS-L) command file to the Voltus-Fi-L configuration file using the command below:

vfibatch -convert <VPSL command file name> <new emir conf file name>

If the new emir configuration file name is not specified, then by default, the software will use the name, "ext_emir.conf".

It is recommended that after converting the command file to the configuration file, check the new emir.conf file and add any missing or additional information before running Voltus-Fi in the batch mode.

The details of the batch mode flow using the conf file and the cmd_file are provided in the following sections:

You can also use the emirreport command, from the simulation hierarchy, to generate textual and html reports for IR and EM analysis. For details, see “Generating EMIR Analysis Reports in Voltus-Fi-L” in the IR Drop Analysis Results chapter.

The Command File Support

The command file is used to load the IR drop and EM analysis results for the Voltus-Fi-L extracted view flow. The command file consists of the legacy (VPS-L) command file, Voltus-Fi commands, and values of the environment variables that are specified as commands. The commands that should be available in the command file are listed in the section below.

The following topics are covered in this section:

Supported Voltus-Fi Commands

The Voltus-Fi batch commands are specified in the command file for loading and viewing the results of different analyses types. These are specified in addition to the legacy (VPS-L) command file name. The following batch commands are available:

Batch Commands for IR Reports

You can load and print the results for IR drop analysis in the Voltus-Fi-L flow using the following commands:

load_ir_results_extview

load_ir_results_extview -i cmd_file

Loads the results of IR drop analysis in the Voltus-Fi-L flow.

Parameter

-i cmd_file

Specifies the name of the batch file used in the Voltus-Fi-L batch mode execution.

Example

The following command loads the results for IR drop analysis that are stored in the vsaIR.cmd file:
```
load_ir_results_extview -i vsaIR.cmd
```

print_ir_report

print_ir_report
-net {all_power | netname}
-type {ir |iv |rc |rcavg |rcrms} 
[-threshold threshold_value] 
-filename output_file_name

Prints the results of IR drop analysis in the Voltus-Fi-L flow. You can generate IR reports for all the power nets or for specific nets.

Before running this command, ensure that the IR drop results are loaded using the load_ir_results_extview command.

Parameters

-filename output_file_name

Specifies the name of the IR drop analysis report file. This is a required parameter.

-net {all_power | netname}

Specifies whether the IR drop analysis report is to be printed for all the power nets or for the specified net.

Select all_power to print the IR report for all the power nets. Select netname to print the IR report for the specified net.

This is a required parameter.

-threshold threshold_value

Specifies that resistors or nodes that have a threshold IR drop ratio value greater than the specified value will be reported. This is an optional parameter.

Default: The report prints results for all resistors or nodes.

-type {ir | rc |rcavg |rcrms}

Specifies the analysis type for which the report is being generated.

ir – specifies that the report is generated for IR drop analysis.

rc – specifies that the report is generated for the peak resistor Current Density analysis.

rcavg – specifies that the report is generated for the average resistor Current Density analysis.

rcrms – specifies that the report is generated for the RMS resistor Current Density analysis.

This is a required parameter.

Examples:

The following command prints the IR drop analysis report for all the nets for ir analysis in the all_ir.txt file:
```
print_ir_report \
```
```
-net all_power \
```
```
-type ir \
```
```
-filename all_ir.txt
```
The following command prints the IR drop analysis report for the VSS net for rc analysis in the vss_rc.txt file:
```
print_ir_report \
```
```
-net VSS \
```
```
-type rc \
```
```
-filename vss_rc.txt
```
The following command prints the IR drop analysis report for all the power nets for rcrms analysis in the all_power_rcRMS.txt file:
```
print_ir_report \
```
```
-net all_power \
```
```
-type rcrms \
```
```
-filename all_power_rcRMS.txt
```

print_rlrp_report

print_rlrp_report
-net netname
-filename output_file_name
-tap tapname

Prints the RLRP analysis report in the Voltus-Fi-L flow.

Before running this command, ensure that the IR drop results are loaded using the load_ir_results_extview command.

Parameters

-filename output_file_name

Specifies the name of the RLRP analysis report file. This is a required parameter.

-net netname

Specifies the name of the net for which the RLRP report is to be printed. This is a required parameter.

-tap tapname

Specifies the instances or tap-nodes of the specified net for which the LRP values are to be printed. You can specify multiple tap nodes for the specified net as shown in the example below. This is a required parameter.

Example:

Use the following commands to load the IR drop analysis results and print the RLRP analysis report for the tap nodes specified for the VDD net in the RLRP.rpt file:

load_ir_results_extview -i vsaIR
print_rlrp_report -net VDD -filename RLRP.rpt -tap MavD7_1_unmatched#d
print_rlrp_report -net VDD -filename RLRP.rpt -tap MavD7_2_unmatched#d

Batch Commands for EM Reports

You can load and print the results for EM analysis in Voltus-Fi-L using the following commands:

load_em_results_extview

load_em_results_extview -i cmd_file

Loads the results of EM analysis in the Voltus-Fi-L flow.

Parameters

-cmd_file

Specifies the name of the batch file used in the Voltus-Fi-L batch mode execution.

Example

The following command loads the results of EM analysis stored in the vsaEM file:
```
load_em_results_extview -i vsaEM
```

print_em_report

print_em_report
-net {all_power | all_signal | all_nets | netname}
-type {javg | jmax | jabsavg | jacpeak | jacrms | rc | rcavg | rcrms} 
[-threshold threshold_value] 
-filename output_file_name
[-rule custom_em_rule_name]

Prints the EM analysis reports in the Voltus-Fi-L flow.

Before running this command, ensure that the EM results are loaded using the load_em_results_extview command.

Parameters

`-filename` output_file_name	Specifies the name of the EM analysis report file. This is a required parameter.
`-net {all_power \| all_signal \| all_nets \|` netname`}`
	Specifies that the EM analysis report is to be generated for one of the following: `all_power`: prints the report for all power nets `all_signal`: prints the report for all signal nets `all nets`: prints the report for all nets netname: prints the report for the specified net This is a required parameter.
`-rule` custom_em_rule_name	Specifies the custom EM rule for which the report will be created. This is an optional parameter.
`-threshold` threshold_value	Specifies that resistors or nodes that have a threshold value of EM ratio above the specified value will be reported. This is an optional parameter. Default: The report prints the results for all resistors or nodes.
`-type {javg \|jmax \| jabsavg \| jacpeak \| jacrms \| rc \| rcavg \| rcrms}`
	Specifies the analysis type for which the report is being generated. `javg` – specifies that the report is generated for the average Current Density analysis data. `jmax` – specifies that the report is generated for the peak Current Density analysis data. `jabsavg` – specifies that the report is generated for the average absolute Current Density analysis data. `jacpeak` – specifies that the report is generated for the AC peak Current Density analysis data. `jacrms` – specifies that the report is generated for the RMS Current Density analysis data. `rc` – specifies that the report is generated for the peak resistor Current Density analysis data. `rcavg` – specifies that the report is generated for the average resistor Current Density analysis data. `rcrms` – specifies that the report is generated for the RMS resistor Current Density analysis data. This is a required parameter.

Examples:

The following command prints the EM analysis report for all the power nets for javg analysis in the all_power_javg.txt file:
```
print_em_report \
```
```
-net all_power \
```
```
-type javg \
```
```
-filename all_power_javg.txt
```
The following command prints the EM analysis report for all the signal nets for jmax analysis in the all_signal_jmax.txt file:
```
print_em_report \
```
```
-net all_signal \
```
```
-type jmax \
```
```
-filename all_signal_jmax.txt
```
The following command prints the EM drop analysis report for the VDD net for jabsavg analysis in the vdd_jabsavg.txt file:
```
print_em_report \
```
```
-net VDD \
```
```
-type jabsavg \
```
```
-filename vdd_jabsavg.txt
```
The following command prints the EM drop analysis report for the VDD net for tcrms analysis in the vdd_tcrms.txt file:
```
print_em_report \
```
```
-net VDD \
```
```
-type tcrms \
```
```
-filename vdd_tcrms.txt
```

Batch Command for RON Reports

You can report the on-resistance (RON) values of power devices in Voltus-Fi-L by using the following command:

report_vfi_L_ron

report_vfi_L_ron

report_vfi_L_ron
-pin_pair_file file_name
[-device_ron {true | false}
-param_list_file file_name
-output_file file_name

Generates the on-resistance (RON) report for IR drop and EM analysis for the specified pin-pairs. Layer-wise wire RON is reported by default. For reporting the device RON, specify the -device_ron parameter.

For details of the flow, see Reporting On-Resistance Values.

Parameters

-device_ron {true | false}

When set to true, the device RON is reported. This parameter is optional.

Default: false, which means the device RON is not reported.

-output_file file_name

Specifies the name of the output file to be created with the RON report.

This is a required parameter.

-param_list_file file_name

Specifies the parameters of the devices to be evaluated.

This is a required parameter.

-pin_pair_file file_name

Specifies the name of the pin-pair file that contains information about all the pin pairs for which the RON report is to be generated. The pins in each pair are separated by a space. Multiple pin-pairs can be specified in different lines.

The software reports the RON between each pin-pair listed in the file.

This is a required parameter.

Example

The following command creates a RON report in the output.rpt file for the pin-pairs specified in the pin_pair.txt file:

report_vfi_L_ron -pin_pair_file pin_pair.txt -output_file output.rpt

Batch Commands for Querying

You can query resistors and nodes in Voltus-Fi-L flow using batch commands. For this, first search for specific resistors and nodes, and then query specific information about these resistors and nodes using batch commands.

You can also specify these commands in a tcl file (conf.tcl) and specify the file in the EMIR control file by using the following emirutil command:

emirutil postTclCmdFile=[conf.tcl]

For details of the above variable, see EMIR Control File Options Supported in Voltus-Fi-L.

Listed below are the batch commands that can be specified for querying specific data. Links to the command descriptions in the “Batch Mode Execution” chapter of the Voltus-Fi Custom Power Integrity Solution XL User Guide are provided below.

Batch Commands for Viewing Results in vsaplot and vfiplot

The following commands are used to generate the VSA_RESULTS directory for IR drop and EM analysis in vsaplot for both Voltus-Fi-L and Voltus-Fi-XL. However, there are some parameters that are specific to either Voltus-Fi-L or Voltus-Fi-XL. The distinction is provided in the parameter descriptions.

The details of the commands are provided below.

write_ir_vsaplot_db

write_ir_vsaplot_db 
-libname library_name 
-cellname cell_name 
-viewname view_name 
-extractedlibname library_name
-extractedcellname cell_name
-extractedviewname view_name
-dfII_layermap_file dfII_layer_file
-qrc_run_directory run_dir
-qrc_run_name run_name
-input_type {psf | vavodb}
[-analysis_name analysis_name]
[-anaysis_type analysis_type]
[-vavodb_file file_name]
[-start_time start_time]
[-stop_time stop_time]
results_file_name

Generates the vsaplot database for the IR drop analysis results.

The parameters in “blue” in the above syntax are only applicable for Voltus-Fi-L.

Parameters

`-analysis_name` analysis_name
	Specifies the analysis name, which could be either DC operating-point (DCOP) analysis or transient analysis. This parameter is required to be specified when the `-input_type` is `psf`. This parameter is only applicable for Voltus-Fi-L.
`-analysis_type` analysis_type
	Specifies the type of analysis, `dc` for DCOP and `tran` for transient analysis. For transient analysis, you can specify separate start and stop times by using the `-start_time` and `-stop_time` parameters of this command. This parameter is mandatory when the `-input_type` is `psf`. This parameter is only applicable for Voltus-Fi-L.
`-cellname` cell_name	Specifies the schematic testbench cell name for the design in Voltus-Fi-L. Specifies the cell name for the design in Voltus-Fi-XL. This is a required parameter.
`-dfII_layermap_file dfII_layer_file`
	Specifies the name of the DFII layermap file that provides the mapping between the extracted view names and the DFII layer names in Voltus-Fi-L. Specifies the name of the DFII layermap file that provides the mapping between the xDSPF file layer names and the DFII layer names in Voltus-Fi-XL. This is a required parameter. The parameters, `-dfII_layermap_file` and `-qrc_run_dir` are mutually exclusive in Voltus-Fi-XL but they are both required in Voltus-Fi-L.
`-extractedcellname` cell_name	Specifies the extracted view cell name for the design. This is a required parameter. This parameter is only applicable for Voltus-Fi-L.
`-extractedlibname` lib_name
	Specifies the extracted view library name for the design. This is a required parameter. This parameter is only applicable for Voltus-Fi-L.
`-extractedviewname` view_name	Specifies the extracted view name for the design. This is a required parameter. This parameter is only applicable for Voltus-Fi-L.
`-input_type {psf \| vavodb}`	Specifies the type of data input. You can specify either the vavo database (`vavodb`) or the `psf` database. This is a required parameter. When `psf` data type is specified, the `-analysis_name` and `-analysis_type` parameters must be specified. This parameter is only applicable for Voltus-Fi-L.
`-libname` lib_name	Specifies the schematic testbench library name for the design in Voltus-Fi-L. Specifies the library name for the design in Voltus-Fi-XL. This is a required parameter.
`-qrc_run_directory run_dir`
	Specifies the name of the Quantus (QRC) run directory. This is a required parameter. The parameters, `-dfII_layermap_file` and -`qrc_run_dir` are mutually exclusive in Voltus-Fi-XL but they are both required in Voltus-Fi-L.
`-qrc_run_name` run_name
	Specifies the name of the Quantus (QRC) run name. This is a required parameter. This parameter is always specified with the `-qrc_run_directory` parameter.
results_file_name	Specifies the name of the simulation directory in Voltus-Fi-L. Specifies the name of the file that contains the EMIR simulation results data in Voltus-Fi-XL. This is a required parameter.
`-start_time` start_time
	Specifies the start time for the transient analysis. If not specified, the software analyzes the full duration of the simulation. This parameter is only specified when the `-input_type` selected is `psf` and the `-analysis_type` is `tran`. This parameter must be specified if the `-stop_time` parameter is specified. This parameter is only applicable for Voltus-Fi-L.
`-stop_time` stop_time	Specifies the stop time for the transient analysis. If not specified, the software analyzes the full duration of the simulation. This parameter is only specified when the `-input_type` selected is `psf` and the `-analysis_type` is `tran`. This parameter must be specified if the `-start_time` parameter is specified. This parameter is only applicable for Voltus-Fi-L.
`-vavodb_file` file_name
	Specifies the `vavo.db` database file required for the vavo_db flow. This parameter is mandatory if `vavodb` is specified as the `-input_type`. This parameter is only applicable for Voltus-Fi-L.
`-viewname` view_name	Specifies the schematic testbench view name for the design in voltus-Fi-L. Specifies the view name for the design in Voltus-Fi-XL. This is a required parameter.

Example:

The following example shows how to generates the vsaplot database for the IR drop analysis results for Voltus-Fi-L.

write_ir_vsaplot_db \

-libname amsPLL \

-cellname TB1_vco_single \

-viewname schematic \

-extractedlibname amsPLL \

-extractedcellname vco \

-extractedviewname av_extracted_vco_oa \

-dfII_layermap_file dfiilayer \

-qrc_run_directory vco_lvs_oa \

-qrc_run_name vco \

-input_type vavodb \

-vavodb_file tran_emir_vavo.db \

./simulation_flow/TB1_vco_single/spectre/schematic

The following example shows how to generates the vfiplot database for the IR drop analysis results for Voltus-Fi-XL.

write_ir_vsaplot_db \

-libname testlib \

-cellname testcell \

-viewname testview \

-dfII_layermap_file dfiilayer \

xps.emirtap.emir0_bin

write_em_vsaplot_db

write_em_vsaplot_db 
-libname library_name 
-cellname cell_name 
-viewname view_name 
-extractedlibname library_name
-extractedcellname cell_name
-extractedviewname view_name
-tech_file tech_file_name
[-layer_mapfile layer_map_filename] 
[-em_only_ict_file em_only_ict_file_name] 
-dfII_layermap_file dfII_layer_file
-qrc_run_directory run_dir
-qrc_run_name run_name 
-input_type {psf | vavodb} 
[-analysis_name analysis_name] 
[-analysis_type analysis_type] 
[-vavodb_file vavodb_file_name] 
[-start_time start_time] 
[-stop_time stop_time] 
-type {javg jmax jabsavg jacpeak jacrms}
results_file_name

Generates the vsaplot database for the EM analysis results.

The parameters in “blue” in the above syntax are only applicable for Voltus-Fi-L.

Parameters

`-analysis_name` analysis_name
	Specifies the analysis name, which could be either DC operating-point (DCOP) analysis or transient analysis. This parameter is required to be specified when the `-input_type` is `psf`. This parameter is only applicable for Voltus-Fi-L.
`-analysis_type` analysis_type
	Specifies the type of analysis, `dc` for DCOP and `tran` for transient analysis. For transient analysis, you can specify separate start and stop times by using the `-start_time` and `-stop_time` parameters of this command. This parameter is mandatory when the `-input_type` is `psf`. This parameter is only applicable for Voltus-Fi-L.
`-cellname` cell_name	Specifies the schematic testbench cell name for the design in Voltus-Fi-L. Specifies the cell name for the design in Voltus-Fi-XL. This is a required parameter.
`-dfII_layermap_file dfII_layer_file`
	Specifies the name of the DFII layermap file that provides the mapping between the extracted view names and the DFII layer names in Voltus-Fi-L. Specifies the name of the DFII layermap file that provides the mapping between the xDSPF file layer names and the DFII layer names in Voltus-Fi-XL. This is a required parameter. The parameters, `-dfII_layermap_file` and `-qrc_run_dir` are mutually exclusive in Voltus-Fi-XL but they are both required in Voltus-Fi-L.
`-em_only_ict_file` em_only_ict_file_name
	Specifies the name of the ICT file along with the process and EM model information that will be used for EM analysis. This is an optional parameter.
`-extractedcellname` cell_name
	Specifies the extracted view cell name for the design. This is a required parameter. This parameter is only applicable for Voltus-Fi-L.
`-extractedlibname` lib_name
	Specifies the extracted view library name for the design. This is a required parameter. This parameter is only applicable for Voltus-Fi-L.
`-extractedviewname` view_name
	Specifies the extracted view name for the design. This is a required parameter. This parameter is only applicable for Voltus-Fi-L.
`-input_type {psf \| vavodb}`	Specifies the type of data input. You can specify either the vavo database (`vavodb`) or the `psf` database. This is a required parameter. When `psf` data type is specified, the `-analysis_name` and `-analysis_type` parameters must be specified. This parameter is only applicable for Voltus-Fi-L.
`-layer_mapfile` layer_map_filename
	Specifies the name of the layer map file that provides the mapping between the layer names used in the technology file and the simulation database. This is an optional parameter. This parameter is only required if the layer names in the simulation database are different from the ones in the technology file.
`-libname` lib_name	Specifies the schematic testbench library name for the design in Voltus-Fi-L. Specifies the library name for the design in Voltus-Fi-XL. This is a required parameter.
`-qrc_run_directory run_dir`
	Specifies the name of the Quantus (QRC) run directory. The parameters, `-dfII_layermap_file` and `-qrc_run_dir` are mutually exclusive in Voltus-Fi-XL but they are both required in Voltus-Fi-L.
`-qrc_run_name` run_name	Specifies the name of the Quantus (QRC) run name. This parameter is always specified with the `-qrc_run_directory` parameter. This is a required parameter.
results_file_name	Specifies the name of the simulation directory in Voltus-Fi-L. Specifies the name of the file that contains the EMIR simulation results data in Voltus-Fi-XL. This is a required parameter.
`-start_time` start_time	Specifies the start time for the transient analysis. If not specified, the software analyzes the full duration of the simulation. This parameter is only specified when the `-input_type` selected is `psf` and the `-analysis_type` is `tran`. This parameter must be specified if the `-stop_time` parameter is specified. This parameter is only applicable for Voltus-Fi-L.
`-stop_time` stop_time	Specifies the stop time for the transient analysis. If not specified, the software analyzes the full duration of the simulation. This parameter is only specified when the `-input_type` selected is `psf` and the `-analysis_type` is `tran`. This parameter must be specified if the `-start_time` parameter is specified. This parameter is only applicable for Voltus-Fi-L.
`tech_file` tech_file_name	Specifies the name of the `qrcTechFile` or the `emDataFile` used for EM analysis. This is a required parameter.
`-type {javg jmax jabsavg jacpeak jacrms}`
	Specifies the type of analysis for which you want to view results in the vfiplot display window. `javg`: For viewing the results of average Current Density analysis data `jmax`: For viewing the results of peak Current Density data analysis `jabsavg`: For viewing the results of average absolute Current Density data analysis `jacpeak`: For viewing the results of AC peak Current Density data analysis `jacrms`: For viewing the results of RMS Current Density analysis data analysis This is a required parameter.
`-vavodb_file` file_name	Specifies the `vavo.db` database file required for the vavo_db flow. This parameter is mandatory if `vavodb` is specified as the `-input_type`. This parameter is only applicable for Voltus-Fi-L.
`-viewname` view_name	Specifies the schematic testbench view name for the design in Voltus-Fi-L. Specifies the view name for the design in Voltus-Fi-XL. This is a required parameter.

Example:

The following example shows how to generates the vsaplot database for the EM analysis results for Voltus-Fi-L.

write_em_vsaplot_db \

-libname amsPLL \

-cellname TB1_vco_single \

-viewname schematic \

-extractedlibname amsPLL \

-extractedcellname vco \

-extractedviewname av_extracted_vco_oa \

-tech_file qrcTechFile \

-layer_mapfile contactmapfile \

-dfII_layermap_file dfiilayer \

-qrc_run_directory vco_lvs_oa \

-qrc_run_name vco \

-input_type psf \

-analysis_name dcOp-dc \

-analysis_type dc \

-start_time 0 \

-stop_time 170 \

-type javg

./simulation_flow/TB1_vco_single/spectre/schematic

The following example shows how to generates the vfiplot database for the EM analysis results for Voltus-Fi-XL.

write_em_vsaplot_db \

-libname testlib \

-cellname testcell \

-viewname testview \

-tech_file qrcTechFile \

-layer_mapfile contactmapfile \

-dfII_layermap_file dfiilayer \

-type jacrms

xps.emirtap.emir0_bin

Supported VPSL Batch File Commands

Currently, only the commands listed below are supported in the Voltus-Fi-L extracted flow. If there are any additional commands in the specified legacy (VPS-L) cmd_file, they will be ignored.

The following commands are required to be in the specified batch file:

The following commands are optional:

The following hold true when using the above commands:

If the required commands are not present in the specified batch file, the job is aborted with the associated error message.
If the extracted view data cannot be loaded, or the appropriate dbFile/extview.tmp file is not located, the tool will throw an error before performing the analysis.
If there are any errors while reading the Voltus-Fi data, the tool will flag these errors.

The descriptions of the commands are provided below.

_vsa_extracted_lib_cell_view

_vsa_extracted_lib_cell_view "library" "cell" "view"

Specifies the RCX extracted view used as input for the analysis. This is a required command.

Parameters

`library`	Specifies the name of the library.
`cell`	Specifies the name of the cell within the library.
`view`	Specifies the name of the view within the cell.

Example

The following command specifies the RCX extracted view used as input for the analysis:

_vsa_extracted_lib_cell_view "amsPLL" "vco" "av_R"

_vsa_qrc_run_directory

_vsa_qrc_run_directory "run_dir_name"

Specifies the directory name of the Quantus QRC run. This is a required command.

Parameter

run_dir_name

Specifies the directory name of the Quantus QRC run.

Example

The following command specifies the directory name of the Quantus QRC run:

_vsa_qrc_run_directory "../custom/LVS"

_vsa_qrc_run_name

_vsa_qrc_run_name "run_name"

Specifies the Quantus QRC run name. This is a required command.

Example

_vsa_qrc_run_name "vco"

_vsa_simulation_directory

_vsa_simulation_directory "sim_dir_path"

Specifies the input simulation run. This is a required command.

Parameter

sim_dir_path

Specifies the path of the simulation directory.

Example

The following command specifies the path of the simulation directory:

_vsa_simulation_directory "/custom/simulation/TB1_vco_bak/spectre/schematic"

_vsa_em_tech_file

_vsa_em_tech_file "../path/fileName"

Specifies the path and filename of the technology file. This is required for EM analysis. If the technology file is not specified, the software gives an error. The following files are supported: The ICT file, the QRC tech file, and the emDataFile.

The _vsa_em_tech_file and the _vsa_em_data_file commands are only required in the EM analysis flow. One of these two commands must be specified.

Example

_vsa_em_tech_file "../amsPLL_oa_flow/qrcTechFile"

_vsa_em_data_file

_vsa_em_data_file "../path/fileName"

Specifies the path and file name of the emDataFile required for EM analysis. This is an optional command. If no other location is specified, the current working directory is used. If the emDataFile is not found, an error is returned.

The _vsa_em_tech_file and the _vsa_em_data_file commands are only required in the EM analysis flow. One of these two commands must be specified.

Parameter

../path/fileName

Specifies the path and name of the EM rule specification file.

Example

The following command specifies the path and filename of the emDataFile required for EM analysis:

_vsa_em_data_file "../custom/oa/gpdk/emDataFile.txt"

_vsa_analysis_data

_vsa_analysis_data "TRANSIENT" | "DCOP"

Specifies the type of analysis to perform.

For transient analysis, separate start and stop times can be specified for both IR Drop and EM analysis using the _vsa_analyze_ir and _vsa_analyze_em commands. If start and stop times are not specified, the default is the full duration of the simulation.

Default: “TRANSIENT”

Parameters

`TRANSIENT`	Specifies that transient analysis should be performed.
`DCOP`	Specifies that DC operating point analysis should be performed.

Examples

The following command specifies that transient analysis be performed for the full duration:
```
_vsa_analysis_data "TRANSIENT"
```
The following command specifies that DCOP analysis be performed:
```
_vsa_analysis_data "DCOP"
```

_vsa_vavo_db_file

_vsa_vavo_db_file "../path/FileName"

Specifies the vavo.db database file required for the vavo_db flow.

Example

_vsa_vavo_db_file "../amsPLL_oa_flow/vavo.db"

_vsa_testbench_lib_cell_view

_vsa_testbench_lib_cell_view "library" "cell" "view"

Specifies the schematic testbench. This is a required command.

Parameters

`library`	Specifies the name of the library.
`cell`	Specifies the name of the cell within the library.
`view`	Specifies the name of the view within the cell.

Example

The following command specifies the schematic testbench used as input for the analysis:

_vsa_testbench_lib_cell_view "amsPLL" "tb_vco_bak" "schematic"

_vsa_hierarchy

_vsa_hierarchy "hierarchy_name"

Specifies the hierarchy of the design. This is an optional command.

Parameter

hierarchy_name

Specifies the hierarchy name for the design.

Example

The following command specifies the hierarchy of the design:

_vsa_hierarchy "/X1"

_vsa_analyze_em

_vsa_analyze_em

Specifies the start and stop times for transient EM analysis. If the start and stop times are not specified, the full duration of the simulation is analyzed.

To specify DCOP analysis or to analyze the full duration of a transient analysis, use _vsa_analyze_em.

This command is only required in the EM analysis flow.

Parameters

`startTime`	Specifies the start time for the DCOP or transient analysis.
`stopTime`	Specifies the stop time for the DCOP or transient analysis.

Example

The following command is used to specify the start and stop times for transient EM analysis:

_vsa_analyze_em _vsa_analyze_em "0" "1n"

_vsa_analyze_ir

Specifies the start and stop times for transient IR drop analysis. If the start and stop times are not specified, the full duration of the simulation is analyzed.

To specify DCOP analysis or to analyze the full duration of a transient analysis, use _vsa_analyze_ir.

Parameters

`start_time`	Specifies the start time for the transient analysis.
`stop_time`	Specifies the stop time for the transient analysis.

Examples

The following command specifies the start and stop times for transient IR drop analysis:
```
_vsa_analyze_ir "0" "150n"
```
The following command is used for running DCOP analysis or full duration of transient IR analysis:
```
_vsa_analyze_ir
```

_vsa_pres_cellname

_vsa_pres_cellname "cellname"

Specifies the cell name of the parasitic resistor used by RCX that is added to the extracted view. This command is optional.

Default: “presistor”

Parameter

cellname

Specifies the cell name of the parasitic resistor within the cell.

Example

The following command specifies the name of the parasitic resistor used by RCX:

_vsa_pres_cellname "presistor"

_vsa_em_map_file

_vsa_em_map_file "../path/mapFileName"

Specifies the layermap file, which is the name of the mapping file to be used for EM analysis. It provides a mapping between the layer names in the simulation database and the layer names in the technology file specified using the _vsa_em_tech_file command.

This command is only required in the EM analysis flow.

Example

_vsa_em_map_file "../amsPLL_oa_flow/DFIIlayermap"

Sample Batch Mode Command File

A sample legacy (VPS-L) batch mode command file is provided below.

;vsa batch mode command file

;common commands for EM and IR

_vsa_extracted_lib_cell_view “amsPLL” “vco” “av_extracted_sol”

_vsa_testbench_lib_cell_view “amsPLL” “TB1_vco_single” “schematic”

_vsa_simulation_directory “/custom/TB1_vco_single/spectre/schematic/”

_vsa_pres_cellname “presistor”

_vsa_analysis_data “TRANSIENT”

; IR specific commands

;_vsa_analyze_IR “0” “170n”

_vsa_analyze_ir

;following command are for EM analysis

_vsa_qrc_run_directory  “/custom/WORK/AV/LVS_emir”

_vsa_em_data_file “emDataFile.txt”

;_vsa_analyze_em "0" "1n"

_vsa_analyze_em

exit

The Configuration File Support

Yo can use the configuration file to run Voltus-Fi-L in batch mode. The following command is used:

vfibatch -c <emir conf> -db <simulation directory path> -outdir <output directory>

The simulation directory path specified using the above command is the same as that specified in the VPS-L cmd_file.

Detailed information about the control file options that can be specified in the configuration file are provided in the subsequent section.

EMIR Control File Options Supported in Voltus-Fi-L

The following table summarizes the EMIR control file options supported in Voltus-Fi-L. These are specified in the configuration file using the emirutil command.

Table 12-1 Supported EMIR Control File Options

Keyword	Option Set	Explanation	Default Value
`emirutil`	`analysisName=”`analysis_name`”`	Specifies the analysis name for DCOP analysis and transient analysis.	`none`
	`analysisType=”dc \| tran”`	Specifies the type of analysis, `dc` for DCOP analysis and `tran` for transient analysis.	`none`
	`analysisStartTime="`value`"`	Specifies the start time for transient analysis. If not specified, the software analyzes the full duration of the simulation. For example, `emirutil analysisStartTime="0"`	`none`
	`analysisStopTime="`value`"`	Specifies the stop time for transient analysis. If not specified, the software analyzes the full duration of the simulation. For example, `emirutil analysisStopTime="170n"`	`none`
	`techfile="emDataFile"`	Specifies the EM rule file in the emdatafile, qrctechfile, or ictfile format. Case-insensitive layer names are supported allowing easier match between the extracted view and the technology files. Alternatively, you can use the `emdatafile="emDataFile"` option to specify the techfile in the emdata format, `qrctechfile="qrcTechFile"` to specify the Quantus QRC tech files, and `ictfile="ictfile"` to specify the file in ICT format. The `layermap` file provides the mapping between the extracted view layers and the layout database. It is applicable only for `qrcTechfile` and `ictfile`.	`none`
	`EMOnlyICTFile=”emOnlyICTFile”`	Specifies the process and EM models to be used for EM analysis. Note: This file can only be provided with the `qrcTechFile` flow.	`none`
	`postTclCmdFile=[conf.tcl]`	Specifies the tcl file that contains user-specified commands for querying specific resistor and node information and creating customized EM and IR drop analysis reports. For details about the commands that can be written in the file (`conf.tcl`), see Batch Command for RON Reports.	`none`
	`layermapfile=”mapfile”`	Specifies the layer map file that provides the mapping between the layer names in the simulation database to the layer names in the technology file.	`none`
	`report=[text \| html]`	Defines the type of report created by `emirutil`. `text` - produces only text report. `html` - creates the report in html format. Note: Multiple entries are supported.	`text`
	`notation=[s \| e]`	Notation for the text and html reports. `e` - engineering scale number (for example, 5.02m) `s` - scientific notation (for example, 5.02e-3)	`e`
	`sort_by_net=yes\|no`	Report IR and EM results per net, or all nets. `yes` - report EMIR results per net `no` - combine EMIR results of all nets into one report.
	`filter_ir_threshold=`value	Defines the IR voltage drop threshold for the node being reported. `filter_ir_threshold=0.01` reports all the nodes with IR drop above 0.01V.
	`filter_em_threshold=`value	Defines the EM analysis threshold value for the resistors being reported. The value for `filter_em_threshold` is the J/Jlimit value. `filter_em_threshold=1` reports only those resistors that have a J/Jlimit value above 1. Note: Specifying this option is equivalent to filtering all passed resistors.
	`enableDesignResistorPeakFactor= [true \| false]`	Specifies the addition of the factor, `1/(r)^1/2`, in the current limit calculation for the AC-Peak analysis of the design resistor. The software, by default, calculates the current limit for the AC-Peak analysis of the design resistor using the following equation: `I_{peak_ac(limit)}=I_{peak_dc(limit)}` To apply the factor, `1/(r)^1/2`, in your calculation, set this variable to `true`. The current limit will then be calculated in the following manner: `I_{peak_ac(limit)}=I_{peak_dc(limit)}/(r)^1/2`	`false`
	`enableDesignResistorScaling=[true \| false]`	Enables the scaling of the width and length values based on the `layout_scale` factor specified in the technology file before the EM rules are applied for EM analysis of design resistors. By default, the scaling of design resistors is enabled.	`true`
	`extendPWLMatch=[true \| false]`	When the EM rules are specified in terms of PWL and the width of metal or the area of via does not exactly match any width/area of the PWL, the EM limit will not be calculated for this metal resistor/via. When set to `true`, the software interpolates the limit value for the `resistor/via` from the selected rule PWL as follows: minimum of PWL `i^th` value * (metal's width or via's area) / (PWL `i^th` width or PWL `area`).	`false`
	`process_scale=`value	Specifies the value by which the width and length values will be multiplied before the EM rules are applied.	`1.0`
	`prioritizedPwlRulesLayers=[all \| none \|` list_layers`]`	Specifies the list of layers for which area-based PWL search is performed first. When no match is found, then non-PWL rules are used. The default value of this variable is `“all”`, which means that this behavior is enabled for all layers. To enable the behavior for specific layers, you can specify a list of layers. To disable this behavior for all layers, set the value of this variable to "`none`". In the GUI, you can set this variable in the Variables form. Example rules: `em_jmax_dc_avg 10 jmax_factor 90 2.384 95 2.078` - non-PWL baseline rule `em_jmax_dc_avg PWL 0.3582 0.001444 0.5694 0.003364 0.7164 0.0038 jmax_factor 90 2.384` - PWL rule When both the above rules are specified, the second rule is given priority over the first.	`all`
	`halfPeakAnalysis=[true\|false]`	Defines the time duration, `Td` as the duration for which the pulse current is greater than half the peak current (`I_peak`) value for dynamic AC peak analysis. By default, this parameter is set to `false`. For example, `emirutil halfPeakAnalysis=true`	`false`
	`pwc_threshold=1e-06`	Defines the current (`I`) threshold value for locating the start of the pulse to calculate the time duration, `T_d` for dynamic AC peak analysis. The default value is `1e-06(1uA)`. For example, `emirutil pwc_threshold=1e-06`	`1e-06`
	`idirn=[true\|false]`	Prints the current direction in the EM report (Current Direction column). For metal resistors, the current direction is printed. That is, W means that the current is flowing from east to west. For via resistors, the direction from/to layer is printed.	`false`
	`Tlife=hours \| years`	Specifies the lifetime for which the EM analysis will be performed. You can specify the value in either years or `hours`. For example: `emirutil Tlife=”20000hours”`	`years`
	`emLimitScale=`scale_factor_value \| “scale_factor_netfile”	Scales the EM limits of the parasitic resistors in the design before generating the EM reports. You can either apply the same scale factor to all the nets or specify different scale factors for different nets. To apply the same scale factor to the parasitic resistors of all the nets in the design, provide the value of the scale factor. `emirutil emLimitScale=`scale_factor_value For example, `emirutil emLimitScale=0.04` Note: This is applicable to `avg`, `avg abs`, and `rms` analyses. For the `avg` and `avg abs` analyses, the limit is directly multiplied by this factor. For rms analysis, the limit is multiplied by the root of this factor. To apply different scale factors to different nets in the design, provide the name of the file that contains information about the net names and the corresponding scale factors to be applied to these nets. `emirutil emLimitScale=”`scale_factor_netfile” For example, `emirutil emLimitScale=“scaleLimitFile”`	`none`
	`rmsMetalLineNumberSignal=`number	Specifies the value of the power on the metal lines for RMS EM analysis of signal nets. If this option is not specified, the default value of `0` is considered, which means the software uses the `em_ac_rms_metal_line_num` value specified in the ICT file. However, if this option is specified, it overrides the `em_ac_rms_metal_line_num` value specified in the ICT file.	`0`
	`recovery_factor`	Defines the recovery factor for iavg calculation with recovery factor. If specified, then `iavg=max(\|iavgpos\|,\|iavgneg\|)-recovery_factor*min(\|iavgpos\|,\|iavgneg\|)`. If not specified, then `iavg=iavgpos+iavgneg`
	`print_em_report`	Defines the EM analysis report file to be generated in the Voltus-Fi-L flow. `filename`: create a report with the specified filename `net`: create a report for the specified nets - all power nets (`all_power`), all signal nets (`all_signal`), all nets (`all nets`), or net (`netname`). `threshold` - create a report for resistors or nodes that have a threshold value of EM ratio above the specified value `type` - create a report for specified analysis type; `javg, jmax, jabsavg, jacpeak, jacrms, rc, rcavg, rcrms.` `rule` - specifies the custom EM rule for which the report should be generated
	`extendedreport=true`	Specifies that the following information should be included in the EM analysis report file: `Td`: time duration in micro second or total ‘On Time” period `dutyR`: duty ratio `I_limit`: current limit	`false`
	`reportUnmatchedRuleResistor=true \| false`	When set to `true`, specifies that while generating the EM analysis reports, the resistors that do not match any EM rule for the specified analysis in the ICT file should be reported in the `“#.rpt_unmatch”` file.	`true`
	`reportAllResistor=true \| false`	When set to `true`, reports all the resistors of the specified nets in the `“#.rpt_all”` file. If both, `reportUnmatchedRuleResistor` and `reportAllResistor`, are set to `true`, the `reportAllResistor` setting gets priority.	`false`
	`layer_filter=[layer1 layer2...]`	Specifies the layers that are to be filtered out from the EMIR analysis reports. For example, `emirutil layer_filter=[cont odcont]` If you have specified this option and also set the `reportAllResistor` option to `true`, the resistor information for the specified layers will be filtered out from the reports.	`none`
	`disableLayoutScale=true`	When set to `true`, disables the layout_scale factor defined in the ICT file for Voltus-Fi-L EM analysis. The layout_scale factor is the ratio of the scaled dimensions to the drawn dimensions. The ICT file is defined based on the scaled dimensions. Quantus applies the layout_scale factor to the input design during extraction so that the design dimensions and the ICT file dimensions are consistent.	`false`
	`simpleSingleViaDefinition=true \| false`	The keyword `single` is used to differentiate between a single square cut via and a square via array. It is applicable to a square via, with width equal to only '`vc_width`/`min_width`'. To support the `single` keyword for all via sizes, set the `simpleSingleViaDefinition` parameter to `true`.	`false`
	`hierarchy=”`hierarchy_name`”`	Specifies the hierarchy of the design. For example, `emirutil hierarchy=”/X1”`	`none`
	`presCellName=”`presistor_name`”`	Specifies the name of the parasitic resistor that is added to the extracted view.	`presistor`
	`view=[lib=<`lib`> cell=<`cell`> view=<`layout`>]`	Specifies the name of the extracted view in the library, cell, view format.	`none`
	`view_tb=[lib=<`lib`> cell=<`cell`> view=<`schematic`>]`	Specifies the name of the schematic testbench in the library, cell, view format.	`none`

For details of the emirutil commands that are the same as those used in Voltus-Fi-XL, see EMIR Control File Options Supported in Voltus-Fi-XL in the “Data Preparation” chapter of the Voltus-Fi Custom Power Integrity Solution XL User Guide.

Sample Configuration Files

The sample conf files for different analyses types are provided below.

DC Operating Point (DCOP) Analysis

===============================================

net name=[*] analysis=[iavg irms imax vavg vmax]

emirutil view=[lib=amsPLL cell=vco view=av_extracted_vco_oa]

emirutil view_tb=[lib=amsPLL cell=TB1_vco_single view=schematic]

emirutil analysisType="dc"

emirutil analysisName="dcOp-dc"

emirutil presCellName="presistor"

emirutil qrc_output=[runDir=vco_lvs_oa runName=vco]

emirutil hierarchy="/X1"

emirutil techfile="qrcTecFile"

Transient Analysis

================================================

net name=[*] analysis=[iavg irms imax vavg vmax]

emirutil view=[lib=amsPLL cell=vco view=av_extracted_vco_oa]

emirutil view_tb=[lib=amsPLL cell=TB1_vco_single view=schematic]

emirutil analysisType="tran"

emirutil analysisName="tran-tran"

emirutil presCellName="presistor"

emirutil qrc_output=[runDir=vco_lvs_oa runName=vco]

emirutil analysisStartTime="0"

emirutil analysisStopTime="170n"

emirutil hierarchy="/X1"

emirutil techfile="qrcTecFile"

Analysis using the vavo-db File

===============================================

net name=[*] analysis=[iavg irms imax vavg vmax]

emirutil view=[lib=amsPLL cell=vco view=av_extracted_vco_oa]

emirutil view_tb=[lib=amsPLL cell=TB1_vco_single view=schematic]

emirutil presCellName="presistor"

emirutil qrc_output=[runDir=vco_lvs_oa runName=vco]

emirutil hierarchy="/X1"

emirutil techfile="qrcTecFile"

emirutil vavoDBFile="tran_emir_vavo.db"

Return to top

Voltus-Fi Custom Power Integrity Solution L User GuideProduct Version IC23.1, August 2023

12

Batch Mode Execution

Overview

Migrating from Legacy (VPS-L) to Voltus-Fi-L in Batch Mode

The Command File Support

Supported Voltus-Fi Commands

Batch Commands for IR Reports

load_ir_results_extview

Parameter

Example

print_ir_report

Parameters

Examples:

print_rlrp_report

Parameters

Example:

Batch Commands for EM Reports

load_em_results_extview

Parameters

Example

print_em_report

Parameters

Examples:

Batch Command for RON Reports

report_vfi_L_ron

Parameters

Example

Batch Commands for Querying

Batch Commands for Viewing Results in vsaplot and vfiplot

write_ir_vsaplot_db

Parameters

write_em_vsaplot_db

Parameters

Supported VPSL Batch File Commands

_vsa_extracted_lib_cell_view

Parameters

Example

_vsa_qrc_run_directory

Parameter

Example

_vsa_qrc_run_name

_vsa_simulation_directory

Parameter

Example

_vsa_em_tech_file

_vsa_em_data_file

Parameter

Example

_vsa_analysis_data

Parameters

Examples

_vsa_vavo_db_file

_vsa_testbench_lib_cell_view

Parameters

Example

_vsa_hierarchy

Parameter

Example

_vsa_analyze_em

Parameters

Example

_vsa_analyze_ir

Parameters

Examples

_vsa_pres_cellname

Parameter

Example

_vsa_em_map_file

Sample Batch Mode Command File

The Configuration File Support

EMIR Control File Options Supported in Voltus-Fi-L

Table 12-1 Supported EMIR Control File Options

Sample Configuration Files

DC Operating Point (DCOP) Analysis

Transient Analysis

Analysis using the vavo-db File

Voltus-Fi Custom Power Integrity Solution L User Guide
Product Version IC23.1, August 2023