Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I have a script (http://www.cadence.com/Community/forums/p/24288/1317148.aspx#1317148) that will save the design tree file to a shell to run a shell script on, working in Virtuoso v5, but is breaking in Virtuoso v6 on the command hiSaveAsViewFile.
The Save File As form looks quite different in v6, but I cannot figure out Cadence's documentation to search for (anything..) something like this.
In v5 I use:
hiSaveAsViewfile->file->value-> = Newfilename
However, in v6, I get the error message " eval: unbound variable - hiSaveAsViewfile".
Since testing with print statements is able to show me that the variable Newfilename is properly defined, and the command hiSaveAsViewfile() works in v6, I can only guess that the form itself is different in v6, and the format hiSaveAsViewfile->file->value is not the same.
2 Questions -
1. how can I test for the version of Virtuoso as an environment variable so I can handle this save function accordingly?
2. what is the v6 format for hiSaveAsViewfile->file->value??
many thanks in advance!
The form looks like it is probably a QT form and won't have the Skill hooks to it. However, you can simply save it to a file like this:
hiSaveAsViewfile( [w_windowId] [t_fileName] )
In 6.1: dbGetDatabaseType() -> "OpenAccess"
In 5.1: dbGetDatabaseType() -> "CDBA"
In reply to dmay:
I have the file saved out successfully now and will try this same code in v5.
I get an error when I try to test the environment for version using your suggested code however.
In reply to jaleco:
What error do you get in your CIW, and what exactly did you try for your Skill code? The command is just: dbGetDatabaseType()
Don't add the "->" stuff, I was just trying to show you the output of the command. If you are running a really old version of Cadence 5, the command might not be available, in which case you might need to do something like this:
procedure(myCheckIsOA() if(getd('dbGetDatabaseType) && dbGetDatabaseType() == "OpenAccess" t nil )) ;proc
Hello Derek, or others who may see this thread,
I am running the script below to operate on the Design Tree saved out to the shell as an ascii file, but the hiSaveAsViewFile() cmd does not overwrite an existing file.
Is there a way to force hiSaveAsViewFile() to overwrite an existing file?
If not, I can always do it with a shell script, but using SKILL would be simpler.
Any help with this would be much appreciated!!!
procedure( TreeInvList() 9 printf(">>>>>>>> Creating a tree inventory from current level to bottom. <<<<<<<\n") 10 printf("***************** Note: *************\n") 11 printf("This will strip out all symbolic links in the tree, most of which are contact or via cells created by the \"Create Contact\" function.\n") 12 printf("An inventory is a unique list of layout files in the tree, including standard cells.\n") 13 hiGetCurrentWindow()->stopLevel = dbGetMaxHierDepth() 14 CellName = geGetEditCellView()->cellName 15 printf("Cell name is %s.\n" CellName) 16 printf("Tree File is %s_tree.\n" CellName) 17 printf("Inventory file is %s_tree_inv.\n" CellName) 18 WritePath = geGetEditCellView()->cell->writePath 19 printf("Write path where files will be created is:\n") 20 printf("%s\n" WritePath) 21 TreeFile = strcat(WritePath "/" CellName "_tree") 22 printf("TreeFile full path is %s\n" TreeFile) 23 InvFile = strcat(TreeFile "_inv") 24 printf("InvFile full path is %s\n" InvFile) 25 printf("Wait for results....................................\n") 26 printf("File is being created...............................\n") 27 leHiTree() 28 hiFormDone(leTreeForm) 29 ; hiSaveAsViewfile->file->value = TreeFile ; version 5 input form code 30 hiSaveAsViewfile(hiGetCurrentWindow() TreeFile) ; version independent code 31 ; hiFormDone(hiSaveAsViewfileForm) ; version 5 code 32 hiFormDone(leTreeForm) 33 ipcWait(ipcBeginProcess(strcat("./scripts/treeinv " TreeFile))) 34 view(InvFile) ; view prior to response from BeginProcess displays blank window 35 ) ; proc
Use the hiSaveViewfile() function instead, it has a third optional argument g_donotOverwrite that you can set to nil in this case. This function appears to exist in both IC5141 and IC61x versions.
In reply to skillUser: