Stats

  • Locked Locked
  • Replies 3
  • Subscribers 145
  • Views 17651
  • 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

Schematic versus schematic by using SKILL .

marbs

 Hi All,

I need your help once more . 

How can I make a SKILL program to compare two schematic from two 

different library ? I want to display the differences of the two schematic 

in a text file . I am using icfb version 5.1

 

Thanks in advance ,

Marbs

 

 

 

 

 

 

 

 

Parents

  • Hi Marbs,

    I agree with Quek that the best tools for SVS are often those traditionally also used for LVS (Diva, Dracula, Assura, PVS etc.)

    If you wanted to compare two schematics, what do you wish to compare?  The graphics? Or just the connectivity and parameter values? Just one schematic, or the hierarchy?  The answer to these questions would help determine the best method.  If it is the devices and their parameters, it is not too difficult to write a simple "netlister" that outputs the devices, their parameters and the connectivity, but how would you compare the two netlists?  This would not be trivial to write, hence the suggestion of using an SVS capable tool.

    Regards,

    Lawrence.

Reply

  • Hi Marbs,

    I agree with Quek that the best tools for SVS are often those traditionally also used for LVS (Diva, Dracula, Assura, PVS etc.)

    If you wanted to compare two schematics, what do you wish to compare?  The graphics? Or just the connectivity and parameter values? Just one schematic, or the hierarchy?  The answer to these questions would help determine the best method.  If it is the devices and their parameters, it is not too difficult to write a simple "netlister" that outputs the devices, their parameters and the connectivity, but how would you compare the two netlists?  This would not be trivial to write, hence the suggestion of using an SVS capable tool.

    Regards,

    Lawrence.

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.