• 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. relative placement with macros

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 15029
  • 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

relative placement with macros

kasyab
kasyab over 12 years ago

Hi,

  I am trying to place a design with some macros and I use relative placement for these. Since the design is fairly large and only one (shared) 4 core machine is available I try not to use the GUI to do this. In my script file to carry out the relative placement I perform the following steps:

1) Adjust the floorplan with the floorPlan command. I use a relative floorplan with an aspect ratio of 1.1 and 50% density.

2) Read the co-ordinates of the new floorplan using the dbGet commands.

3) Relatively place the macros using " relativeFPlan --place <instance> <reference_coordinates> <offset_coordinates> <orientation> "

4) Create obstructions using "createObstruct -name <NAME> -box <coordinates>" after calculating the required coordinates.

5)  Select the placed macros and use cutRow -selected -halo <spacing>.

6) Place other instances in the design hierarchy using createRegion and createGuide.

After each of the numbered steps I run deselectAll followed by redraw to ensure that none of the previously selected instances foul up following calculations. 

Here's my problem: the first time I run this script (with or without the GUI) the obstructions are not created correctly and a number of these warnings are issued:

" **WARN: (ENCSYC-6130):    Warning: The X coordinate of lower left corner is greater than upper right. We will exchange them."

When I run the script a second time (after deleting the obstructions), the run complains about HInst constraints being outside the die (fair enough, since I don't actually delete the relativeFPlan) and then warnings about HInsts having constraints on them already and overriding them (again, fair enough). But this time I get the floorplan I want.

Am I missing something in my script? Why do I have to run the script twice to get the floorplan I want?

I am not able to attach pictures which would give you a better idea of what I am trying to get at.

Any help is appreciated.

 

Kasyab

  • 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