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.
When I generate a pcell, it includes a marker error.
If I look up the explanation, it says:
location: ("testLib" "pcTest" "layout")reason: Generating Pcell for 'pcTest layout'.
Any idea what this means? If this is'nt enough, I can always post the PCell code.
Do you by any chance have a printf() statement in your pcell code?
If not, perhaps you can post the code?
In reply to Andrew Beckett:
I have indeed a sprintf statement, what's wrong with that?
In reply to RVERP:
Nothing wrong with an sprintf - it's printf that I was asking about. Within pcell evaluation, anything printed to standard output is converted to be a marker on the pcell - this is a convenience to allow markers to be generated.
So an sprintf should not cause this problem...
Maybe you should just post your code?
procedure( icsMatchedCrossQuad(arrayLibName arrayCellName mosType l w labelList) eval(`pcDefinePCell( list(ddGetObj(,arrayLibName) ,arrayCellName "layout") ; PCell Parameters ; ---------------- ( (l float float(l)) (w float float(w)) (mosType string mosType) (labelList ILList labelList) ) ; PCell skill code ; ---------------- let((pathPitch unitName) pathWidth = 2*cadr(icsInit->metalConstraints->metalViaEnclosure) + cadr(icsInit->viaConstraints->viaWidth) pathPitch = pathWidth + cadr(icsInit->metalConstraints->metalSpace) ; Generate unit ; ------------- unitName = sprintf(nil "%s_unit" ,arrayCellName) icsMatchedCrossQuadUnit(,arrayLibName unitName mosType float(l) float(w) labelList) ; Place in cross quad ; ------------------- let((xPos yPos pcMaster) yPos = icsInit->mosConstraints->mosGOffset + pathPitch*2 xPos = 4*l + 6*icsInit->mosConstraints->mosSDOffset pcMaster = dbOpenCellViewByType(,arrayLibName unitName "layout" "maskLayout") dbCreateParamInst( pcCellView pcMaster nil (0:yPos) "R0" 1 list( list("l" "float" l) list("w" "float" w) list("mosType" "string" mosType) list("labelList" "ILList" labelList) ) ) dbCreateParamInst( pcCellView pcMaster nil (xPos:-yPos) "R180" 1 list( list("l" "float" l) list("w" "float" w) list("mosType" "string" mosType) list("labelList" "ILList" labelList) ) ) ) ;End of let ) ;End of let ) ;End of pcDefinePCell ) ;End of eval) ;End of procedure
My guess (I can't run your code because it is not complete) is that this is caused by the call to icsMatchedCrossQuadUnit() in your code. I'm guessing that this function also generates a pcell - and so it will output a message telling you that it is building a new pcell - and that output (because it's on stdout) will appear as a marker.
In general I really would not create a new pcell within a pcell evaluation. Fine to instantiate another pcell, but building it doesn't make so much sense to me. It's not obvious why you would want to do that, rather than creating the pcell up front (outside of the pcDefinePCell).
Ok, I moved the creation of the second Pcell out of the "Master" Pcell,and the marker is gone.