• 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. Recommend steps using First Encounter

Stats

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

Recommend steps using First Encounter

archive
archive over 18 years ago

Hello.
I'm in the process of verifying what are the necessary steps to achieve fully placed & routed design using First Encounter - I've read few tutorials and assembled the following steps:

* Design import (sythesized verilog file, SDC etc.)
* Floorplanning
* Power planning (power rings,power stripes and routing)
* Placement
* Pre-CTS timing optimization
* Clock tree synthesis (creating specification, specifying it and the actual clock tree synthesis)
* Post-CTS timing optimization
* Routing using NanoRoute
* Post-routing timing optimization
* Filling (fillers,metal fills)
* Verifying
* Exporting results

Your input on the validity of those steps and ideas for possible needed changes would be much appreciated.

Thank You,
Adi. 


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

    Hello Adi,

    I think you have the major steps outlined.

    Depending on the size of your design you may spend time in the prototyping / floorplanning step. In my experience the more time you spend in this part of the flow the more push-button the rest of the flow is.

    The macro placer is very useful for macro placement, estimating module and partition placement as well as congestion analysis and IR Drop analysis. You can generate multiple floorplans and rank them based on user criteria. There are additional options for controlling the placement of the memories.

    This feature (command is planDesign) will automatically create a power structure if desired based on your design power requirements, next run a quick placement (cluster place) and finally run global routing.

    The flow is as follows:

    setPlanDesignMode -autoPowerPlan 100 -congAware
    planDesign

    The "100" specified above in setPlanDesignMode is an estimate power requirement of 100mW. You can also add -powerAware option to have the tool perform an IR Drop analysis if used planDesign will automatically overlay the floorplan placement with an IR drop map.

    Regards,

    Elvis

    Originally posted in cdnusers.org by elvis
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    How do you do your floorplanning? Directly within Encounter or do you do it in Virtuoso and then somehow export it?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 14 years ago

     Floorplanning is done in Encounter.

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

    For a mixed-signal design where a schematic rather than a Verilog netlist is the starting point, Virtuoso-XL can be used to convert the schematic view to a layout view using a flow involving the V-XL command:  Generate Physical Hierarchy.

    After floorplanning in V-XL, output a DEF file which captures your floorplan.    The LEF views of your IPs along with this DEF file can be imported to First Encounter where you continue in the recommended FE flow.

    HTH ...

    • 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