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 SKILL script that runs out of memory and terminates Cadence when running on a medium-sized MMIC. I will try assigning intermediate variables to nil after they are used but is there anything I can do either to increase memory or in general to redue its use?
Difficult to guess without having a pice of code.
Anyhow there are few hints:
- if possible, switch to a 64bit cadence version, probable yours is a 32bit
- could be a OS limitation of memory/process
- you may need to change your data structures, from what I've noticed creating a lot of lists will exhaust the memory. Also, the extensive usage of hashes/associative_arrays makeTable(...) may create memory problems.
In reply to marcelpreda:
Thanks for the inputs.
The version of Cadence is dictated by the foundry so the first option is out
I will look into the second possibility on the OS
I do have a number of lists and am now assigning them to nil when not in use - hopefully that will correct the issue.
In reply to thomas1000:
Do you have a Skill development license? If so, you can profile the performance and memory usage of your program:
CIW->Tools->Skill Development Click on Skill ProfilerFrom the profile menu, you can choose "Start Profiling Time" or "Start Profiling Memory". After the profiler has started, run your program. Since it is currently crashing Cadence, you'll want to run a smaller data set, or even ctrl-c to cancel the command before you crash. When your run has finished, press the "Stop" button on the profiler form (the square) and you'll see some information about the top memory users or time users. Press the Browse button (looks like a tree) and it will build a tree of your code to help you see your memory usage in your code hierarchy.Then examine the profile results to help pin point your memory hog. If you are able to get this far and isolate the problem code, then post it and we can help you improve it.
If you don't have the profiler, you might want to post a sample of your code.
In reply to dmay:
Thanks. That was helpful. I was able to find the memory problem and solve it. I had not needed to use the profiler much before but in this case it was helpful.