Stats

  • Locked Locked
  • Replies 2
  • Subscribers 61
  • Views 2430
  • 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

Exclude Paramter name/value during module generation in LEC

Rafeeq2129

Hi,

     I'm using Conformal LEC to match RTL vs Netlist (synopsys's DC generated).

    Our requirement is just to use Uniquification numbers for same modules, and do not require tool to append parameter names/values for the generated modules. The generated netlist has been generated as expected.

   But , Is there a way in Conformal LEC to exclude Paramters(name&value) while generating module name ?

 

regards,

rafeeq

 

  •  View solution "20092848" on support.cadence.com for information on how to handle this.

     To summarize, this is what you need to do:

     However if the default naming convention for module names is changed during synthesis with DC/RC, then the above commands would not match module names in LEC. To resolve this, you need run uniquification in LEC to match the module names. This command is given after reading the library and design files.
    SETUP> uniquify -all -nolib

     

    Basically, the uniquify command will match module names between golden and revised.  Do this before running "write hier dofile".

     

  •  Hi Miller,

                    I'm using the "uniquify -all -nolib" command", which isn't helping me in removing mismatches. 

                Does uniquify Identifies any paramterized module pattern of Synthesized netlist ? How does uniquify help in matching different naming style modules ?

              I would like to know if there is any command in LEC-XL which can generate paramterized modules only with <module_Name>_<uniquification no.>  . 

              My DC netlist is generated with no Paramter name/value appended to module name . Can i get the similar result with LEC on RTL ?

     

    regards,

    rafeeq

     

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.