• 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. Why LVS Errors by SOC Encounter ?

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13458
  • 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

Why LVS Errors by SOC Encounter ?

IEEE Chairman
IEEE Chairman over 14 years ago

 When I used the command "v2lvs" to transfer a netlist from SOC Encounter to a spice file, there were warnings :

"Warning: Duplicate port/net name "...." found in module "......" while doing case-insensitive lookup ."

 

I just ignored it , and did a LVS check . But the final result is :

Error:    Different numbers of nets.
Error:    Connectivity errors.
Warning:  Ambiguity points were found and resolved arbitrarily. 

...

INITIAL NUMBERS OF OBJECTS
--------------------------

                Layout    Source         Component Type
                ------    ------         --------------
 Ports:             10        12    *

 Nets:             140       131    *

...

NUMBERS OF OBJECTS AFTER TRANSFORMATION
---------------------------------------

                Layout    Source         Component Type
                ------    ------         --------------
 Ports:             10        10

 Nets:             140       129    *

...

It passed  a DRC check , but failed in a LVS check. I don't know if the failure reason is previous warnings . I have no idea why a netlist from SOCE couldn't pass a LVS check . After all the LVS check just check the design in different forms ,a netlist & a gds ,from the same SOCE design.

However my  same flow is OK for other designs.

Could anyone help me?

Thanks  

 

  • Cancel
  • IEEE Chairman
    IEEE Chairman over 14 years ago

     I found that it was because some tiehi pins didn't connect to VDD.

    • 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