• 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. Custom IC SKILL
  3. vmsUpdateCellViews disable automatic symbol creation

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 1659
  • 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 disable automatic symbol creation

SimhanAnalog
SimhanAnalog 6 months ago

vmsUpdateCellViews for a systemverilog view compiles the view and shows warnings/errors and also checks other views like symbol, schematic if the ports match. If symbol is not present it shows a popup asking for symbol view creation. In order to disable all these popups I set
vmsCrossViewCheck = nil
vmsRunningInUI = nil

So that it doesnt show popup if there are any cross view mismatches and if there are any parser warnings.

But when I run for a view that doesn't have symbol it silently creates symbol

vmsUpdateCellViews(?lib lib_name_d, ?cell module_name, ?view "systemVerilog", ?viewt "systemVerilogText")

 I was thinking if I disable popup and crossviewcheck it shouldn't create symbol if it doesn't exist. Is there some option to disable symbol creation?

  • Cancel
  • Andrew Beckett
    Andrew Beckett 6 months ago

    Use vmsUpdateSymbolAfterEdit = nil

    See: How can I perform a check and save of a functional view using a SKILL command without opening the functional view from GUI?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • SimhanAnalog
    SimhanAnalog 6 months ago in reply to Andrew Beckett

    Thanks Andrew. This helped.
    I guess you have been the only constant in this changing world for the past 15+ yrs(maybe more. I have interacted for this time).

    • 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