3.4. DRC/LVS with IC Validator
IC Validator is very command-line driven. Here are some usage notes:
Many PDK decks will use variables to control switches. These are defined on command line with
-Dand can be defined in Hammer config using the
<drc/lvs>.icv.defineskey (type: List[Dict[str, str]]).
Any deck directories that need to be included are defined on command line with
-Iand can be defined in Hammer config using the
<drc/lvs>.icv.include_dirskey (type: List[str]).
Extensibility is enabled by passing a file to the icv command with
-clf. This file contains additional command line arguments, and is generated in the
generate_<drc/lvs>_args_filestep (can be overridden).
Decks are included using the
generate_<drc/lvs>_run_filestep (can be overridden with additional ICV method calls).
Results/violations are generated in a format readable by VUE (interactive violation browser) using the
Layout is viewed using IC Validator Workbench (ICVBV). It can communicate with VUE to generate violation markers by opening up a socket to ICV. The socket number can range between 1000 and 65535 (selectable by
<drc/lvs>.icv.icvwb_port. Running the
generated_scripts/view_<drc/lvs>script will handle this automatically, by starting ICVWB, opening the port, waiting for it to be listening, and then starting VUE.
ICVWB layer mapping can be specified in