• 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. Digital Implementation
  3. RTL compiler - elaborate problem.

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 92
  • Views 5277
  • 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

RTL compiler - elaborate problem.

sandeepsuhas
sandeepsuhas over 15 years ago
Hi All, When I run rtl compiler I am facing the following error: Error : Invalid operating_conditions name. [LBR-32] [elaborate] : Library has no operating conditions named 'tt_1p2v_25c'. : Use ls to see the valid operating_conditions in the libraries. Error : Error when processing libraries loaded into domain. Cannot continue unless all domains' libraries are OK. [LBR-115] [elaborate] : Error when processing domain: /libraries/library_domains/_default_ Failed on elaborate -libpath /home/ssriram/project -libext .lib mult.v But the above said operating condition is present in the library. Any help would be appreciated. Regards Sandeep.
  • Cancel
  • diablo
    diablo over 15 years ago

    The first I would check whether operating condition is defined in your tt_1p2v_25c.lib file as below


      operating_conditions(tt_1p2v_25c) {
        process    : 1;
        temperature    : 25;
        voltage    : 1.2;
        tree_type    : balanced_tree
      }

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sandeepsuhas
    sandeepsuhas over 15 years ago
    Hi , Thanks for the reply. but i have it in my .lib file. Here is the print: operating_conditions(tt_1p2v_25c) { process : 1; temperature : 25; voltage : 1.2; tree_type : balanced_tree; power_rail (VDD, 1.2); power_rail (VSS, 0.0); }
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sandeepsuhas
    sandeepsuhas over 15 years ago
    How should I go now.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • diablo
    diablo over 15 years ago

    The first thing this question will be relevant in logic design forum instead of digital implementation forum .

     Looking at your error, elaborate -libpath /home/ssriram/project -libext .lib mult.v, is confusing.

    Usually we have 

    set_attribute lib_search_path home/ssriram/project/

    set_attribute library tt_1p2v_25c

    read_hdl *.v

    elaborate $design

    I am not sure what are your commands . It will help if you run each command in your script line by line in RC prompt and see which command is giving you error. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sandeepsuhas
    sandeepsuhas over 15 years ago
    Hi Diablo, Here are the commands which I used for elabortion. set_attribute lib_search_path { /home/ssriram/project } set_attribute script_search_path { /home/ssriram/project } set_attribute hdl_search_path { /home/ssriram/project } set_attribute path /home/ssriram/project # target libraries #create_library_domain {nor} set_attribute library scmetro_cms9flp-rvt_tt_1p2v_25c.lib ./ # Reads the rtl files and syntax xhecks set file_list mult.v read_hdl $file_list elaborate -libpath /home/ssriram/project -libext .lib mult.v Regards Sandeep.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • diablo
    diablo over 15 years ago

    Did you try running each command in a RC instead of running whole script? Is it the "elaborate -libpath /home/ssriram/project -libext .lib mult.v" that's giving you error? what happends if you just do "elaborate <top level of your design>"  ?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sandeepsuhas
    sandeepsuhas over 15 years ago
    Hi Diablo, As you mentioned I ran individual commands, the problem is in elaborate command which is not able to take the operating_condition attribute. Regards Sandeep.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • grasshopper
    grasshopper over 15 years ago

    Hi sandeepsuhas,

    I believe you are using the commands incorrectly

     rc:/> elab -h
      elaborate: elaborates previously read HDL files and creates corresponding design and subdesigns

    Usage: elaborate [-parameters <string>] [-libpath <string>]+ [-libext <string>]+ [<string>+]

        [-parameters <string>]:
            specifies a list of parameter/value pairs for top-level Verilog module or VHDL entity
        [-libpath <string>]:
            defines Verilog library search path
        [-libext <string>]:
            defines Verilog library file extension
        [<string>+]:
            the top-level Verilog modules or VHDL architectures to elaborate

     

    You can see in the usage that -libpath refers to the Verilog library search path and not the Technology libraries hence your -libext should certainly not have .lib in it.

     I normally set libraries using 

     set_attribute library <library file list>  /

     Also, RC questions are probably better suited for the logic design forum I think.

    good luck,

    gh-

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • sandeepsuhas
    sandeepsuhas over 15 years ago
    Thanks for the mail, I tried the above combination it is not taking the operating condition correctly. As per your comments I will post the query in logic design
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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