• 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. Logic Design
  3. starting RTL compiler and Encounter

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 62
  • Views 14309
  • 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

starting RTL compiler and Encounter

jun1119
jun1119 over 13 years ago

Hi all

I am totally new to encounter. I have written a VHDL code and intended to implement it using XFAB xh035 technology. I have read some tutorials online and the manual and found out that to use RC, I have to have a source script (.tcl file) and some library files. Where can I get the .tcl file and library file? I can find some .tcl and .lib files from the XFAB design kit but they do not seem to be appropriate. I have also tried loading my vhdl file without any source script with the command read_hdl -vhdl myvhdl.vhd but nothing happened. When I load it for the second time, I will get this message:

 entity Digital_controller is
|
Warning : Replacing existing design unit. [VHDLPT-800]
        : Unit 'default:Digital_controller' in file '/home/chew/rc_digital_ctrl/VHDL/Digital_controller.vhd' on line 11, column 1.
        : A previously analyzed unit is being replaced.
Warning : Marking out-of-date unit as invalid. [VHDLPT-801]
        : Unit 'default:digital_controller-rtl' depends on overwritten unit 'default:digital_controller'.
        : A unit is considered out-of-date when a unit that it depends on is re-analyzed.
Warning : Replacing previously read Verilog module or VHDL entity. [HPT-76]
        : Replacing VHDL entity 'Digital_controller' in library 'default' with newly read VHDL entity 'Digital_controller' in the same library in file '/home/chew/rc_digital_ctrl/VHDL/Digital_controller.vhd' on line 11.
        : A newly read VHDL entity replaces any previously read Verilog module or VHDL entity in the same library if its name matches (case-insensitively) the existing module or entity.
    For instance:
        VHDL 'foo'                  replaces  VHDL {'FOO' or 'foo' or 'Foo' or ...} in the same library
        VHDL 'foo' (in any library) replaces  Verilog {'FOO' or 'foo' or 'Foo' or ...} in the same library
 
A newly read Verilog module replaces any previously read Verilog module if its name matches (case-sensitively) that module.  Further, it replaces any previously read VHDL entity in the same library if its name matches (case -insensitively) that entity.
    For instance:
        Verilog 'foo' replaces    VHDL {'FOO' or 'foo' or 'Foo' or ...} in the same library
        Verilog 'foo' replaces    Verilog 'foo' only
    In addition:
        Verilog 'foo' does not replace Verilog 'FOO' and the two remain as distinct modules.

 How can I start RC? Also, for encounter, are the .lef, tlf, I/O files provided by the foundry as well?

 

Thank you

  • Cancel
  • grasshopper
    grasshopper over 13 years ago
    Hi jun1119, write_template -help would probably provide you a good starting point. I think the message is pretty clear in your previous post. You read twice therefore a number of things are being overwritten. Maybe you though it did not do anything but the messages seem to indicate otherwise. If you read the documentation, you will remember that the design needs to be elaborated after reading so read_hdl -vdhl elab and you should have the design in RC vdir infrastructure good luck, gh-
    • 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