• 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. placeDesign uses trialRoute

Stats

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

placeDesign uses trialRoute

Johann Glaser
Johann Glaser over 14 years ago

Hi!

 

I'm using the Foundation Flows of Encounter v08.10 for a flat design. I found that running the step "place" uses the command "placeDesign". When run interactively, this command uses trial route before doing the placement, while when run from the script, it doesn't. No wires are routed because no cells are placed, but it still does something.

To find the reason I compared the settings in both cases with getUsefulSkewMode, getAnalysisMode, getExtractRCMode, getOptMode, getScanReorderMode, and getTrialRouteMode. After setting the very same options in the interactive run, it still used to run trial route before the placement.

Could you please give me a hint what options case the usage of trial route before the placement? And what are the pros and cons for it?

Additinally I found quite large differences in the placement for my test design (a simple 16 bit up/down counter). When doing placement by the script, Encounter puts all D-FF at the two bottom rows of the core and all combinational gates in the rows above. When doing the placement in the interactive run (with identical options of the above modes) the D-FF are spread across the whole core area. Could this be caused by the preceding trial route? Or what else could cause this?

Thanks

  Johann Glaser

  • 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