• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Setting power domain locations with CPF flow

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 90
  • Views 16286
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Setting power domain locations with CPF flow

archive
archive over 17 years ago

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. Any suggestions?


Originally posted in cdnusers.org by sreeb
  • Cancel
Parents
  • archive
    archive over 17 years ago

    The answer turned out to be place the domain using:

    modifyPowerDomainAttr pdName [-box llx lly urx ury]




    Originally posted in cdnusers.org by sreeb
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    The answer turned out to be place the domain using:

    modifyPowerDomainAttr pdName [-box llx lly urx ury]




    Originally posted in cdnusers.org by sreeb
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. 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. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information