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.
The encounter users guide says:
"Manually move the power domains into the core area."
This lacks a little clarity about what commands I use to do this. I have guessed it might be createFence but have no way to be sure.
It seems to work but check place isn't very happy.
encounter 30> checkplace
**WARN: (SOCSP-364): Placer could not determine rows for 'SRC'. Will use stdCellHgt for flooded rows.
**ERROR: (SOCSP-357): Could not init legalization data for powerDomain 'SRC'.
**ERROR: (SOCSP-358): PowerDomain box is not valid
Searching sourcelink for SOCSP yield nothing.
Hello,The errors here indicate setup issues.I suggest you run "verifyPowerDomain" after commitCPF and make sure there are no errors before continuing in the flow. Based on the errors it sounds like the power domains were not moved into the core area. You should not need to use createFence as this will be taking care of via CPF commit. Drag the power domain into the core area and resize as needed. The error "...Could not init legalization data for powerDomain" makes me think the power domain has not been dragged into the core area.....Here is the flow:loadConfigloadCPFcommitCPF Note: You should see the power domains to the left of the designverifyPowerDomainfloorPlan -site ... Note: This is the manual part, move/resize/reshape by clicking on the power domain and move it into the core area Note: You can also accomplish this via TCL using the "setObjFPlanBox Group x,y coords"modifyPowerDomainAttr -minGaps -rsExts Note: The POWER DOMAIN name above should match the name in the CPFAt this point the basic LP infrastructure is created. You should be able to do a saveDesign (saveDesign floorplan.enc) and use this as your starting point going forward.Let me know if you have any follow-up questions.Regards,Elvis
The answer turned out to be place the domain using:modifyPowerDomainAttr pdName [-box llx lly urx ury]