Are you able to text one of the floating outputs in the layout, and add a top level name on the same net in the source to match?
Another idea is to use LVS CPOINT. You may need to use hierarchical LVS for that experiment though, so you can use hierarchical pathnames to get down to those floating output nets.
Are there just a few spare logic gates, or many? Using a higher LVS PROPERTY RESOLUTION MAXIMUM may help if there are lots of spare logic gates.
The idea was to leave the outputs floating, unconnected, and not mark them as ports. This solution would help Calibre to identify them based on ports name but would require to name the outputs individually and carry the text to top level.
The hierarhical LVS is not applicable, we don't have a license for that, only flat.
BUT solution no3 worked thank you !!!
I highly appreciate you help. Thanks again. First time I bump into this problem, probably until now I had fewer than 32 spare logic gates.
That's a nice way to start the morning! Thanks for sharing the good news.
Now i see the warning in the previous LVS report, it says clearly Warning: LVS property resolution maximum exceeded... didn't noticed it before
And I didn't think to ask about that warning either. Thanks for taking the time to add that observation.
As more and more Calibre users find out about this community and add their questions and comments it should become more and more valuable.
Just for grins I went to google.com and searched for this:
calibre lvs spare logic gates errors
And your thread came up as the top result. I think that's neat... anyone around the world can use google to search for a Calibre problem or question and they might find threads that you or I were discussing publicly. I know it's not a substitute for SupportNet or official documentation but as an extra thing that is available to everyone that wants to help each other I think it's pretty cool.
Glad I can help ...and receive.
Anyway i didn't expect to receive an answer so soon, but after spending almost a day to debug this i gave up and called upon other users knowledge... glad i did.
Thanks for the solution.
I was also facing the same issue, where can i specify this particular switch?
Currently i am using LVS PROPERTY RESOLUTION MAXIMUM ALL(in calibre rule file), still i am getting the the issue.
I think you can check first, in the report at "LVS Parameters", if the command was applied correctly, check the number for "LVS PROPERTY RESOLUTION MAXIMUM". And check for any other warnings also.
If you still have the problem it could be another cause.
As a note from SVRF Manual :
Note that there is a potential performance penalty for specifying large property resolution
maximum values. In particular, the ALL keyword should be avoided.
Thanks for that quick reply, let me check it.