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.
Apart from the fact that the formatting makes it very hard to read your code, what exactly is your problem? You have the code to show/hide the dummy (I assume that's what your code is doing), so what is the issue?
In reply to Andrew Beckett:
In reply to Weight66:
Which version are you using? If IC61, then Alt bindkeys can't be defined by default (because Alt is used for Menu accellerators), unless you use:
envSetVal("ui" "enableMenuShortcuts" 'boolean nil)
to turn that feature off. For the CtrlShift 0, I could define it using Ctrl<Key>) on my keyboard (I suggest using the bindkey editor, and then when you press the key combination it tells you the sequence).
Of course, I'm assuming that this is the problem and not to do with the actual code you're using. If course you can check that by just running the functions directly. If not, maybe you can state the version you're using too?
Sorry for late reply, It is IC615, I'm trying other keys,
but the function doesn't run properly,
yes, it runs, but doesn't do what I want, Thanks,
In that case you'll need to fix the code (or global variables that it uses) to make it work. You know what you want it to do, and you've not enlightened anyone on the forum, so I'm not really sure what you're expecting.
I went to the effort of tidying up the formatting of the code so I stood some chance of understanding it:
procedure(ST_Lyt_ShowHide_Layers(Command PressedKey ShowDummy) ;Available values for Command: >=1 to Add, <=1 to Remove and 0 to Hide all but selected one ;Available values for ShowDummy: t to show dummy types and nil to keep dummy layers hidden Lyt_Key_Layer_Assoc = '( ("0" 0) ("1" 1) ("2" 2) ("3" 3) ("4" 4) ("5" 5) ("6" 6) ("7" 7) ("8" 8) ("9" 9) ("`" 10) ("-" 11) ) Lyt_Sel_Layers = nth(nth(1 assoc(PressedKey Lyt_Key_Layer_Assoc)) Lyt_Layer_List) Lyt_Show_Layer = nil if((Command >= 0) then leSetEntryLayer(list(nth(0 Lyt_Sel_Layers) nth(0 Lyt_Layer_Purposes))) if((Command == 0) then leSetAllLayerVisible(nil) ) foreach(Lyt_SLayer Lyt_Default_Layers foreach(Lyt_SPurpose Lyt_Layer_Purposes LytShowLayer = t if((Lyt_SPurpose == Lyt_Dummy_Purpose_Name) then LytShowLayer = ShowDummy ) leSetLayerVisible(list(Lyt_SLayer Lyt_SPurpose) LytShowLayer) ) ) Lyt_Show_Layer = t ) if((Command >= -1) then leSetEntryLayer(list(nth(0 Lyt_Default_Layers) nth(0 Lyt_Layer_Purposes))) ) foreach(Lyt_SLayer Lyt_Sel_Layers foreach(Lyt_SPurpose Lyt_Layer_Purposes LytShowLayer = Lyt_Show_Layer if((rexMatchp(strcat(".*" Lyt_Dummy_Purpose_Name ".*") Lyt_SPurpose) == t) then LytShowLayer = (ShowDummy && LytShowLayer) ) leSetLayerVisible(list(Lyt_SLayer Lyt_SPurpose) LytShowLayer) ) ) hiRedraw())
And I can see from this that it uses four global variables. I tried setting these (based on some guess work) to match some settings in a gpdk technolog:
Lyt_Layer_List='(("Metal1" "drawing") ( "Metal2" "drawing") ( "Metal3" "drawing") ( "Metal4" "drawing"))Lyt_Layer_Purposes='("drawing" "slot" "label" "pin" "net")Lyt_Default_Layers='("Poly" "Oxide")Lyt_Dummy_Purpose_Name="slot"
But since I don't really understand what the code is trying to do (it seems rather strangely written, but maybe all would become clear if I knew what the global variables were supposed to look like), I couldn't really see what it was aiming at.
Please be aware that readers of the forum (including myself) cannot read your mind - so please, please, explain yourself clearly otherwise nobody is going to be able to help you. I've already spent quite a bit of my time (note, it's my own time as I do this as a volunteer not as part of my job with Cadence) trying to fathom out what you're actually asking...
Saying things like "it doesn't do what I want" doesn't really tell anyone what the problem is. In fact it doesn't even say that you want anything answered, so maybe you're happy already?
Here are global variables,
Lyt_Layer_List = list(
"NP" "PP" "PW" "NW" "DNW"
"VTH_P" "VTH_N" "UHVT_P" "UHVT_N"
"VTL_P" "VTL_N" "VTUL_P" "VTUL_N"
"OD_12" "OD_18" "OD_33")
list("drawing" "dummy" "odummy" "pin"
I set bind key to show dummy
"<Key>[" "ST_Lyt_ShowHide_Layers(0 \"1\" t)
ST_Lyt_ShowHide_Layers(-1 \".\" nil)")
to hide dummy
"<Key>]" "ST_Lyt_ShowHide_Layers(-1 \"1\" t)
ST_Lyt_ShowHide_Layers(1 \".\" nil)")
But it still doesn’t work, I
don’t know why,
Since you are in IC615, this is an opportunity to use the SKILL IDE to debug the problem.
Bring up the SKILL IDE from the CIW->Tools menu.
Open the file containing the code and load it through the IDE
Set a breakpoint on the function. When you execute the function, it will stop at the start.
As you step through the function you can follow the logic as it executes. You can query the variable values by turning on the tooltips.
Note thaqt you have a large number of non declared variables which become global variables when the function is evaluated. Run Lint on the file to clean those up before testing your code as it will eliminate many potential problems.
In reply to theopaone:
Also, look at the following line:
if((Lyt_SPurpose == Lyt_Dummy_Purpose_Name) then
You set Lyt_Dummy_Purpose_Name to be a list. This will always fail in your code.
I got the massage "no licence to run SKILL Develpoment", Thanks, Wei
Check with you CAD group to see if you have a license. You may have to check it out manually.
Otherwise, put printf statements in your code to check the values.
Is it OK to do
Lyt_Dummy_Purpose_Name = ("dummy" "odummy")
You will need either a single quote or the function "list" before the open parentesis otherwise you will get a syntax or run-time error:
'("dummy" "odummy") or list("dummy" "odummy")
In reply to skillUser:
It is OK to set the value as a list but your test is an equivalence test not a list member test. You should be testing for a member rather than ==
if( ( listp(Lyt_Dummy_Purpose_Name) and member( purpose Lyt_Dummy_Purpose_Name ) or purpose == Lyt_Dummy_Purpose_Name then