Quantus QRC Extraction Plug-n-Play

Quantus 20.1
March 2021
Copyright Statement

© 2018 Cadence Design Systems, Inc. All rights reserved

worldwide. Cadence and the Cadence logo are registered
trademarks of Cadence Design Systems, Inc. All others are
the property of their respective holders.

2 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Purpose

• Several foundries provide Quantus QRC techfiles and LVS

rules in separate packages. These Quantus QRC techfiles
need to be recompiled by end users with files (compilation
command file, layer_setup and lvsfile) from LVS packages.

• Quantus QRC Extraction Plug-n-Play provides capability to

support direct-from-foundry QRC techdir files in Quantus
QRC, with “on-the-fly compilation” use model.

• CCL’s options and UI options have been added since 17.12

for Quantus QRC to support on-the-fly compilation use
model.

3 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Overview

Technology directory
from Foundry
(No lvsfile required) Add CCL or UI process commands for
1 -technology_command_file,
layer_setup
-technology_layer_setup_file
compilation.cmd to point to the
qrcTechFile compilation.cmd and layer_setup files

compilation.cmd executed 2 Run Quantus to

at Quantus runtime extract parasitic elements
generates the lvsfile used
for compilation in the
Quantus –
temporary_directory
Replaces Techgen -lvs lvsfile option
Techgen –compilation
-lvs_query_directory
The lvsfile can be generated using Techgen from the
../query_output existing QCI or PVS svdb directory.
-lvs_run_name Design …
This is optional for the QCI and PVS/QRC flows: lvsfile
can now be generated at Quantus QRC runtime.

4 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Overview

• With Quantus Plug-N-Play, the DK can have the

following files in separate locations:
– The simulated-only qrcTechFile
– The layer_setup and compilation.cmd files
• Standalone Techgen -compilation in the QRC techdir is
no longer required:
– Plug-n-Play feature is available in both PVS-QRC and QCI flows
– Techgen compilation is done at runtime using layer_setup and
compilation command file, as well as generated lvsfile
– lvsfile is prepared at Quantus runtime from data in the LVS output
directory:
With PVS-QRC flow, the lvsfile is generated in svdb dir by PVS.
With QCI flow, the lvsfile can also be generated at runtime by
adding -lvs_query_directory and -lvs_run_name in
compilation.cmd, from files in the query_output directory
(see the next slide).
5 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Quantus QRC runtime requirements from CCL

• Two CCL’s options must be used together or Quantus

will report an error and terminate:
process_technology
-technology_command_file
-technology_layer_setup_file

• Technology layer_setup file:

– This file is provided by foundry.
– This is the layer mapping file between LVS interconnect layers and
QRC techfile.
• Technology command file:
– This file is also provided by foundry.
– This is a compilation file, which QRC will use to compile QRC
techfile at runtime, with layer_setup file and lvsfile generated from
LVS.

6 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Quantus QRC runtime requirements in GUI

• The two CCL’s options are also available in GUI:

process_technology
-technology_command_file
-technology_layer_setup_file

7 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Compilation command file requirements

• Supports the simulated-only qrcTechFile:

Techgen –compilation is not needed
• PVS-QRC flow:
– lvsfile is generated by PVS in svdb dir: svdb/{runname}.lvsfile
– No option is needed in the compilation command file.
• QCI flow:
– lvsfile is generated by QRC at runtime from the query_output
directory (using Design.lvs_settings, Design.devtab and
Design.ports files). query_output needs to be generated with:
”lvs settings report write query_output/Design.lvs_settings”
See: $QRC_HOME/share/extraction/examples/query_cmd
– Two compilation options are needed in compilation command file:
-lvs_query_directory and -lvs_run_name

lvs_query_directory and -lvs_run_name are placeholders for QRC to generate lvsfile,

and do not need to exist (use dummy name).

8 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
DK Setup – other options

• Optional DK setup with Quantus Plug-N-Play

– Add in QRC techdir qrcInclude.ccl with:
process_technology
-technology_command_file "$env(LVSsetupdir)/compilation.cmd“
-technology_layer_setup_file "$env(LVSsetupdir)/layer_setup"
– In techRuleSets:
ruleSet( “typical“
(RcxSetupDir "$QRCtechdir/typical")
(RcxInclude "$LVSsetupdir/qrcInclude.ccl") )
– The qrcInclude.ccl file will automatically be used by Quantus at
runtime with no CCL change, or need for GUI input.
• lvsfile can also be generated standalone using Techgen
– It supports both Calibre query directory and PVS svdb directory
Techgen -compilation -lvs_query_directory {query_dir} -lvs_run_name {runname}
– qrcTechFile can be compiled with the same options, as replacement
to the -lvsfile option:
Techgen -compilation -lvs_query_directory {query_dir} -lvs_run_name {runname}
-layer_setup layer_setup –cmd compilation.cmd
9 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Summary

• QRC techfiles can be delivered separately from the LVS

package, and do not need to be compiled / recompiled
anymore.
– Compilation will be done by Quantus QRC at runtime.
– Files for on-the-fly compilation (layer_setup and compilation
command file) still need to be provided, but can be located in a
separate package, and this can be set up transparently for the end
user in qrcInclude.ccl.
• This flow also provides alternative to calibre2qrc for the QCI
flow, as lvsfile can now be generated directly from the
query_output directory.
– calibre2qrc cannot be used on the encrypted LVS rules
– lvsfile does not need to be generated in QRC techdir if the
compilation command file given at runtime to QRC has -
lvs_query_directory and -lvs_run_name
10 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com
Support & Feedback

• Support
Cadence Support Portal provides access to support
resources, including an extensive knowledge base, access
to software updates for Cadence products, and the ability to
interact with Cadence Customer Support. Visit
https://support.cadence.com.
• Feedback
Email comments, questions, and suggestions to
content_feedback@cadence.com.

11 © 2018 Cadence Design Systems, Inc. All rights reserved. Learn more at Cadence Support Portal - https://support.cadence.com