Stats

Locked Locked
Replies 4
Subscribers 143
Views 1621
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

vmsUpdateCellViews - Limit extracts to single view within cell

When running vmsUpdateCellViews() with something like:

vmsUpdateCellViews(?lib "myLib" ?cell "myCell" ?view "systemVerilog_progXX")

If multiple views exist within this cell, all views are extracted. We have a setup where we have 10 different testprograms written in this format, and having to extract all 10, each time we make changes to one is combersome.

Can vmsUpdateCellViews() be forced to only extract the single view that we changed?

Br,

Christian

Andrew Beckett over 3 years ago

Hi Christian,

I don't see that behaviour - for me, specifying ?view means that only that view will be checked/updated.

Which IC sub-version are you using? Type getVersion(t) in the CIW and it will tell you the full sub-version number/

Thanks,

Andrew
Cancel
Vote Up 0 Vote Down

Cancel
jehh over 3 years ago in reply to Andrew Beckett

Hi Andrew,

I've tested both isr 16 and isr 18, both seem to extract all views within the cell pointed to.
But I also just tested whether it would be the same with a veriloga view - and there it doesn't. Only for the systemVerilog views.

The system verilog views contain includes to some basic files needed - could this trigger something?

BR,

Christian
Cancel
Vote Up 0 Vote Down

Cancel
Andrew Beckett over 3 years ago in reply to jehh

Hi Christian,

I just did some checks and I see that it is invoking the parser for all the views if you're using systemVerilog, but it only actually updates the views you ask for.

If you look at How to disable cross view check during vmsUpdateCellViews() or during schInstallHDL and set vmsCrossViewCheck=nil it turns off the cross-view check and avoids it analysing all the other systemVerilog views - this is because of the "shadow-free" use model much of the time, it doesn't know for certain whether the views are consistent unless it re-analyzes the files.

There is this envSetVal( "schematic" "vicCheckPinOrder" 'boolean nil) setting which disables portOrder checks, but it still analyses the views (see How to disable port order checking for text view vs symbol view?) so I suspect the vmsCrossViewCheck=nil is the trick for you?

Andrew
Cancel
Vote Up 0 Vote Down

Cancel
jehh over 3 years ago in reply to Andrew Beckett

Exactly, yes! vmsCrossViewCheck=nil did the trick.

Thanks Andrew.

BR.
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.