• 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. Power domains or not?

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 91
  • Views 15523
  • 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

Power domains or not?

schnufff
schnufff over 12 years ago

Hi all,

I have to setup a chip with 5 completely separated cores. Each core has its own vcc_core/io and vdd_core/io ind i/o pins.

But the actual voltage of all cores is 1.8V. For testing only one core should be active at a time.

Can I do this just with connectGlobalNet or is this more like a multi supply voltage flow with a single volate?

 

If there is some documentation about this topic, please give me a hint. The UserGuide didn't cover this topic.

  • Cancel
  • Kari
    Kari over 12 years ago

    It almost sounds like you can just use globalNetConnect, but when you say that only one core should be active at a time, that implies domains controlled by power-switch cells, which is more complicated. There is a Low Power Design chapter in the EDI user guide, have you reviewed that? If you need further info, search for Low Power on support.cadence.com. There will be some other documentation there.

    - Kari 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • schnufff
    schnufff over 12 years ago

     Hi Kari, thanks for the reply

    To make it clearer: We are only powering one core via external vcc at a time. There is no need for power switches. The used lib even does not have and power awareness. My problem in the moment is, that the power supply lines of the standard cell rows are always connected to the last used vcc_core$. 

     

    what I have is one toplevel module which instanciates the 5 cores. than i create a fence for each core, create the powerrings around the fence and connect the pin vdd_core (only under module core1) to global net vdd_core1. the same for cores 2 to 5.

     

    how can i restrict sroute to only route the standard cell vdd lanes inside the area of the module fences? outside the fences there will be no logic at all, only wires.

     

    Thanks

    Stefan

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 12 years ago

    Ok, this should be pretty easy then. You might want to look at globalNetConnect -module to assign the different sources to the different core hierarchies.

    For sroute, try putting placement blockages between the core fences. That should stop the followpin generation from happening between fences. If I've misunderstood, please post a picture - I'm sure we can get the tools to do what you want here.

    - Kari 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • schnufff
    schnufff over 12 years ago

     Hi Kari,

     

    sorry for the late reply. I was busy with paperwork. I managed to connect the global nets correctly and also constrainted the follow pins as you suggested. Now the next problem: When I add TieHiLow cells or do CTS, how can I control to which vcc_core_x (x in 1 to 5) the by Encounter added cells will be connected.

    All cores are surrounded by a placement blockage as you suggested. All buffer/inverters added by CTS and the TieHighLow cells should be placed inside the corresponing fence andconnect the the vdd,vcc already routed there.

    Thanks in advance

    Stefan

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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