• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. QRC + command file

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 126
  • Views 18457
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

QRC + command file

Slawa
Slawa over 15 years ago

Good afternoon dear colleagues.
I had a following problem.
I have started to master QRC but I can not adjust command file in any way. In particular I can not understand with -technology_library_file and -technology_name. Constantly writes "Could not map technology name "LALA" to a path using "/./XXX"Check spelling to insure the name is correct."   I have created a separate folder "techgen" in which have made simulation Techgen -si and Techgen -compilation. In it has put ict, proc, p2lvs, lvsrule, and qrcTechFile. And here to start QRC does not leave. What it is necessary to enter in a  -technology_name and -technology_library_file ? Very much I count on your help.

Best regards

Beginner engineer from Russia

  • Cancel
Parents
  • Slawa
    Slawa over 15 years ago

     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 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Slawa
    Slawa over 15 years ago

     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 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information