QRC + command file

I haven't used command line QRC, but have you tried running QRC from Virtuoso Layout XL, filling in the desired fields in the GUI, running QRC extraction and seeing what the command line arguments are in the log file? That may give you some idea about what you're doing incorrectly.

Hi Slawa

You can resolve the problem as follows:

a. Create a file named "qrc_tech.lib" in the working directory. It should contain this line:
DEFINE LALA /your-path/yourTechgenDirectory

b. In your QRC cmd file, you should have lines similar:

process_technology \
   -technology_library_file "qrc_tech.lib"
   -technology_name "LALA"
...


QRC will first look for the library definition file "qrc_tech.lib". If found, it will search for a library definition named "LALA". This should point to a directory which contains the file named "qrcTechFile". The library definition file does not really have to be named as "qrc_tech.lib". It can be any other filename.

Best regards
Quek

 With it like clear. Did similarly. I can not understand whence to take "LALA". I so understand that QRC will search for this most "LALA" in qrcTechFile located on the address specified in "qrc_tech.lib" a file defined through "DEFINE". And as qrcTechFile it is received directly from ICT, accordingly "LALA" this name of technology specified in ICT a file? Or what?

Best regards

Beginner engineer from Russia 

Hi Slawa

The name usually follows the contents of the qrc technology directory. E.g. it can be "tsmc035", "umc90n", etc. It can be anything as long as the path is correct. It can be any "ABC" or "XYZ". It does not matter to qrc. The name is given according to the preference of the user.

Best regards
Quek

 Thanks for the help. I did all correctly but a problem it has appeared in other. As well as cds.lib the file qrc_tech.lib has similar syntax and consequently problems with them identical. In this case after "DEFINE lala/path/lala"
The cursor has not been rearranged for other line and QRC did not understand the termination of the given way. It is insulting that any more once came across on it with cds.lib at its clearing of remote libraries and has got again but already with QRC :)

Best regards

Beginner engineer from Russia 

 Good afternoon dear colleagues. Allow to set to you some more questions on command_file for QRC.
Now I study start QRC with Calibre input. Questions the following:
1)-layer_map_file - maps the layers in the AGDS file to layers found in the Calibre
LVS rules file. What its syntax? And if it is possible with an example.
2) - library_cell_list_file, hierarchy_delimiter and design_cell_name....... Whether Is these parametres obligatory or they can be ignored?
3) whether Prompt it is correctly made command_file for start with Calibre input and if there is no that that in it incorrectly? process_technology \
-technology_library_file "qrc_tech.lib" \
-technology_name "LALA"

 output_setup \
-net_name_space layout \
-directory_name /Any directory for storage of the output data 

 extraction_setup \
-technology_layer_map \
M1 M1 \
M2 M2 \
M3 M3 \
M4 M4 \
M5 M5 \
V1 V1 \
V2 V2 \
V3 V3 \
V4 V4 \
V5 V5 \
GP GP \
PolyCont CON \
-max_fracture_length 50

 input_db -type calibre \
-directory_name /path to a directory with the target data calibre query

-run_name Design \

-layer_map_file /path to a map_file.txt \
-device_property_value 7 \
-instance_property_value 6 \
-net_property_value 5

 -design_cell_name AA01D1 layout LOGIC      ??? Whether it is necessary? And if yes that leaves that given library Cadence should be in the same folder whence all start QRC is made?

output_db \
-type spef \
-subtype standard

 extract \
-selection all \
-type rc_decoupled

graybox \
-type none

log_file \
-file_name qrc.log \
-dump_options true

filter_coupling_cap \
-coupling_cap_threshold_relative 0.05

metal_fill \



-type floating

Best regards

Beginner engineer from Russia 

Hi Slawa

The gds layer map file should be automatically generated during the Calibre query step and not manually created. The actual Calibre lvs database cannot be used directly by QRC. An additional "query" step has to be performed. Here is an example of its contents:

Gds_Map 1000
Layers:
0 0 31 Oct  1 14:24:51 2007
DNW 1 0
nw_dnw 2 0
...

The "library_cell_list_file" is needed when you are generated dspf or spef output. Otherwise, it is not required. "design_cell_name" is only needed if you are generated extracted view output. Otherwise, it is not needed. It is also not required to specify the hierarchy delimiter is the default value of "/" is fine.

You do not to have "technology_layer_map" section if you are using Calibre input. It is only for LEF/DEF inputs.

Best regards
Quek

 Many thanks for fast and the main thing the intelligible answer. Then we will return to "library_cell_list_file". What its syntax? And if I will tell I have project PROJECT containing LOGIC1 LOGIC2 IP1 IP2 PAD1 PAD2 that "library_cell_list_file" should contain them? Or this parametre concerns what that still? And with what the similar error can be connected?

WARNING (RCXSPIC-28051): Substrate stamping disabled for X-DSPF/SPEF.
WARNING (RCXSPIC-28131): The SPEF language as per IEEE 1481-1999 does not have a
 syntax for printing parasitic resistor or capacitor model names
ERROR (LBMISC-215480): at "RCXspice": LVS connectivity file  is missing .2.
ERROR (LBRCXM-633): Bad return status from RCX script generator. Status 512
INFO (LBRCXM-709): *****  QRC terminated abnormally  *****

Best regards

Beginner engineer from Russia 

Hi Slawa

The format for "library_cell_list_file" is as follows:

DEFINE myLib1 /abc1/xyz1/myLib1
DEFINE myLib2 /abc2/xyz2/myLib2

Do you mean that you have a project directory that contains the libraries "LOGIC1", "LOGIC2", etc? If the cells in these libraries are used in the design, then you have to declare them in the library definitions file.

Would you please start a new thread for the qrc error so that we don't mixed up the question on ccl cmd file and qrc errors?

Thanks
Quek