Stats

Locked Locked
Replies 3
Subscribers 143
Views 1783
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

Using SKILL to auto-update VerilogA & Symbol views

I am trying to use SKILL to take a Verilog-A text file and:

Check and save, generating additional Cadence files and updating CDF parameters
Regenerate symbol from updated view list

After scouring the forums and the web, I found the vmsUpdateCellViews( <lib> <cell> <view> ), which will achieve (1), sort of. If I use this command on a single file, this works well, since I will often get UI prompts to update the CDF and/or symbol. Unfortunately, if I try to do this on multiple files, the function doesn't wait for the UI prompts to be closed before moving to the next line in the SKILL script. The UI interfaces then become unresponsive as the script to continues to execute.

I have also tried to use schViewToView() function, but I can't find a built in "fromFunction" for Verilog-A (schVerilogToPinList() does not seem to work for Verilog-A). The schHiViewToView sort of works, but requires a lot of manual inputs. Is there a simple way to do this for a standard Verilog-A text file?

Regards,

Azar

AzarK over 8 years ago

I realized after reading an unrelated post that putting UI calls inside of a let( ) block functions differently than just putting lines in a .il file and loading. If I nest the vmsUpdateCellViews() calls inside a let() block, then each call waits for resolution of any prompts before moving to the rest of the script. This solution is good enough. Thanks,
Cancel
Vote Up 0 Vote Down

Cancel
Andrew Beckett over 8 years ago

This solution on the support site also gives some info about how to turn off the popups altogether.

Regards,

Andrew.
Cancel
Vote Up 0 Vote Down

Cancel
AzarK over 8 years ago

Thanks Andrew. The linked article was very helpful, and I have everything I need now.

Regards,
Azar
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.