• 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. How to specify the distance between 2 macros (top,left,bottom...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 90
  • Views 1136
  • 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

How to specify the distance between 2 macros (top,left,bottom,right) in the multiple row in FP

archive
archive over 18 years ago

Hi,

In the Floorplaning we will place macros manually according to logiacal connectivity. If we have suppose 24 macros and i have placed these macros in the four (4) rows an 6 colums.

1. How to specify the distance between 2 macros for all sides(top,left,bottom,right) and what r parameters to be comsidered?

2. Any good document which specifies the designing the power structure or how to design the power structure? what are facors or parameters are rquired to design power structure(designing power strap widths, number fo power straps)?

3. In IR drop analysis, how switching factor, probability and toggle rate works (means how it works in the process or IR drop implimentation)?

Please suggest me

Thanks & Regards,
Prashant


Originally posted in cdnusers.org by kulprashant05
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hi Prashant,

    For spacing/aligning your macros, check out the floorplanning options:

    Floorplan->Edit Floorplan->Align Instances, Shift Instances, Space Instances

    The power question is a bit more difficult to answer. Coming up with a power grid can be challenging. You want to have a grid that supplies enough power to all your components without going below an IR-drop limit that you have decided on. Most folks pick 5% of the supply (that means a 2.5% drop for VDD and a 2.5% bounce for VSS).

    Then you need to decide which layers to use for the grid and the widths. Most people do back-of-the-envelope calculations or use a spreadsheet which calculates the IR-drop based on total power consumption, supply voltage, resistance of the metal layers, and widths/pitches of the metal layers. You can plug different widths and pitches for the layers into the spreadsheet until you get an acceptable IR-drop number. This can work well for wirebond designs, but becomes much more complicated for flip-chip designs. (But flip chips will need less of a grid, since power is coming into the design at regular intervals and not just from the chip boundary.)

    You will also want to center your power stripes on the routing grids so that you don't use up signal routing tracks unnecessarily. We have also found that more stripes of narrower width are better than fewer stripes of wider width for routability. But you don't want the power stripes to be too narrow (too much resistance).

    It's a good idea to do IR-drop analysis as early as possible in the flow to vet your power structure. When using a toggle rate for IR-drop analysis, a typical number is 20%. Some folks think this is a bit high, but others will say it's a bit low. It really depends on the chip and how it operates. For example, in test mode, you may be toggling everything more than you would in functional mode, and may want to use a higher toggle rate. But in general, the clocks use the most power and they are always toggling 100% (except for gated clocks).

    I probably didn't completely answer your power questions, but as you can see, there is a lot involved.

    I hope this helps out at least a little bit.

    - Kari


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

    Hi Prashant,

    For spacing/aligning your macros, check out the floorplanning options:

    Floorplan->Edit Floorplan->Align Instances, Shift Instances, Space Instances

    The power question is a bit more difficult to answer. Coming up with a power grid can be challenging. You want to have a grid that supplies enough power to all your components without going below an IR-drop limit that you have decided on. Most folks pick 5% of the supply (that means a 2.5% drop for VDD and a 2.5% bounce for VSS).

    Then you need to decide which layers to use for the grid and the widths. Most people do back-of-the-envelope calculations or use a spreadsheet which calculates the IR-drop based on total power consumption, supply voltage, resistance of the metal layers, and widths/pitches of the metal layers. You can plug different widths and pitches for the layers into the spreadsheet until you get an acceptable IR-drop number. This can work well for wirebond designs, but becomes much more complicated for flip-chip designs. (But flip chips will need less of a grid, since power is coming into the design at regular intervals and not just from the chip boundary.)

    You will also want to center your power stripes on the routing grids so that you don't use up signal routing tracks unnecessarily. We have also found that more stripes of narrower width are better than fewer stripes of wider width for routability. But you don't want the power stripes to be too narrow (too much resistance).

    It's a good idea to do IR-drop analysis as early as possible in the flow to vet your power structure. When using a toggle rate for IR-drop analysis, a typical number is 20%. Some folks think this is a bit high, but others will say it's a bit low. It really depends on the chip and how it operates. For example, in test mode, you may be toggling everything more than you would in functional mode, and may want to use a higher toggle rate. But in general, the clocks use the most power and they are always toggling 100% (except for gated clocks).

    I probably didn't completely answer your power questions, but as you can see, there is a lot involved.

    I hope this helps out at least a little bit.

    - Kari


    Originally posted in cdnusers.org by Kari
    • 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