Stats

  • Locked Locked
  • Replies 3
  • Subscribers 61
  • Views 14544
  • 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

on Encounter RTL compiler

archive

I have a few questions regarding using Encounter RTL compiler. First, is RTL compiler an equivalent of the Synopsys Desing Complier tool? Both Synthesize the RTL verilog code to a gate-level netlist? Second, as an user in academic institutions, we have downloaded technology packages from MOSIS and the one we are currently using ARM/Artisan library for IBM 0.13um technology. However, I am having trouble with RTL compiler with this library? Should I set "lib_search_path" to the directory where the standard cells are located? Also, I could not find a .lbr or .lib file from the ARM/Artisan library, so I do not know how to set "library"? Do I have to create that file myself? Does anyone have used MOSIS ARM/Artisan before? Your help is highly appreciated.


Originally posted in cdnusers.org by cdnhua
Parents

  •  The .lib describe timing, power and funtionnality of standard cells, it's a mandatory file for synthesis. ARM give it, you can't generate it (although you want to characterize all cells :-))...

     

    In unix shell type this find . -name "*.lib" , if you have no result, call ARM.

    ConcerningRTL compiler, you have to set library path, and hdl path before, you can find it in cadence documentation (preparing the design section, i think).

     

     

Reply

  •  The .lib describe timing, power and funtionnality of standard cells, it's a mandatory file for synthesis. ARM give it, you can't generate it (although you want to characterize all cells :-))...

     

    In unix shell type this find . -name "*.lib" , if you have no result, call ARM.

    ConcerningRTL compiler, you have to set library path, and hdl path before, you can find it in cadence documentation (preparing the design section, i think).

     

     

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.