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.
The Cadence Academic Network helps build strong relationships between academia and industry, and promotes the proliferation of leading-edge technologies and methodologies at universities renowned for their engineering and design excellence.
Participate in CDNLive
A huge knowledge exchange platform for academia to network with industry. We are looking for academic speakers to talk about their research to the industry attendees at the Academic Track at CDNLive EMEA and Silicon Valley.
Come & Meet Us @ Events
A huge knowledge exchange platform for academia. We are looking for academic speakers to talk about their research to industry attendees.
Americas University Software Program
Join the 250+ qualified Americas member universities who have already incorporated Cadence EDA software into their classrooms and academic research projects.
EMEA University Software Program
In EMEA, Cadence works with EUROPRACTICE to ensure cost-effective availability of our extensive electronic design automation (EDA) tools for non-commercial activities.
Apply Now For Jobs
If you are a recent college graduate or a student looking for internship. Visit our exclusive job search page for interns and recent college graduate jobs.
Cadence is a Great Place to do great work
Learn more about our internship program and visit our careers page to do meaningful work and make a great impact.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
Overview All Courses Asia Pacific EMEANorth America
Instructor-led training [ILT] are live classes that are offered in our state-of-the-art classrooms at our worldwide training centers, at your site, or as a Virtual classroom.
Online Training is delivered over the web to let you proceed at your own pace, anytime and anywhere.
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.
With this code inside a pcell and myFunction used from within that pcell, no errors arise so is this a good practice?
I'm wondering if this might cause some errors down the line when a tool is reading the cadence database.
if(!procedurep(getd(stringToSymbol("myFunction"))) then procedure( myFunction(name) println(name stdout) ))
I don't think that it is good practice to print (to stdout) from within a PCell. I think that I've seen fprintf to stderr for debugging purposes. Are you intending to keep this print statement in the code? What happens when you Stream Out (pipo / strmout) ? I've got a feeling that this may look okay in DFII, but programs like Stream Out would choke.
BTW, why do you have "stringToSymbol("myFunction")"
rather than 'myFunction ?
Oh, I think I missed the point, sorry.
You are asking if it is okay to define a procedure within a PCell? If the procedure is going to be called outside the scope of the PCell then I would think it is a really bad idea - how do you know if the PCell that defines the procedure is going to run before the code that uses the procedure? However, if the procedure is used only within the scope of the PCell code, then I would think it should be safe.
In reply to skillUser:
You could use:
The main issue with having all the functions defined this way within the pcell code is that the code vector could get too large, and you might hit the limit of code size.
The usual way to define auxilliary functions used within pcell code is to put them in (or load them from) the libInit.il of the library containing the pcell.
In reply to Andrew Beckett:
I am going to HAVE to agree with Lawrence and Andrew, defining procedures within a pcell is not a good idea. I would define them either before the pcDefinePcell or in a separate file and use libInit.il to load that procedure. Your implementation is very hard to debug.
Inside a pcell, println causes an error. poport, the output port for println, is not available in the pcell interpreter. stdout and stderr are available so you should use fprintf:
fprintf( stdout "%s => %L\n" pcCellView~>cellName outputValue )
In reply to Austin CAD Guy:
You might also want to define such a function outside your pcell, and of course you must follow the advices of previous posts telling you to use libInit.il to load it so it's defined when your pcell code is run.
;; Custom print function for debugging(defun print_debug (var) (if (boundp 'pcCellView) (fprintf stdout "%s => %L\n" pcCellView~>cellName var ) (fprintf stdout "Top Level => %L\n" var )))