• 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. Eco help

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 14665
  • 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

Eco help

rdohanyos
rdohanyos over 15 years ago

I have the original database (enc.dat) file and the verilog file. When I restore it I get all the routing back, but the cells aren't placed where they were previously.  They are just placed off to the side in big blocks.

**ERROR: (SOCSP-503):   Design must be placed before running "ecoDesign -postMask -modifyOnlyLayers M1:M2 ************_enc.dat cellname_here ************_p2.v".

Basically I don't have any spare cells defined we are just making a change to how a few gates are wired.

Is there a way to accomplish this?

Thanks

Robert 

  • Cancel
  • Kari
    Kari over 15 years ago

     Your command looks correct. Make sure that the ecoDesign command is the FIRST thing you do when encounter comes up. Don't have a database already loaded. Another thing to try is just to restore your enc.dat design and make sure the placement looks ok. Maybe there is a problem with the starting database.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • TomBelpasso
    TomBelpasso over 15 years ago

     In order for the ECO flow to work in Encounter, the names of the modules and instances must be maintained between the two versions of the netlist. Look at the log or eco report and verify that only the number of changes you expected were actually made.  Based on your description it sounds like it didn't find any of the original cells and considered all the cells of the design as unplaced.

    How were the changes made to create the new Verilog?  Did you do manually edit theVerilog file or regenerate from another tool?

    If the netlist was generated by a synthesis tool, then you can use Conformal ECO to have it compare the netlists and update the new one to use the original names.  You will need Conformal ECO license if you need to do this.

    To debug the problem I would recommend just restoring the original design. If the original design was from an older version of FE then you are currently using, save it using the following command, to a new database name, so you don't clobber your original data:

    Verify that all the cells are placed correctly.  

     enc> saveDesign <newName.enc>  -def

    The -def option will force FE to also write a <design>.def file into the .dat directory.  When the design is restored, the DEF file will also be read, so only use this option at the end of your flow, when you are going to achive your design.  The DEF file will contain both the placement and routing in a text format, so it is more portable between different tools and versions.  I also recommend using the -def option, when saving blocks, if you are going to assemble a hierarchical design.

    Exit FE and try the ecoDesign command again, again check the log and report files to verify that only the number of changes you expect are being detected.

     Good luck,

    - Tom Belpasso

    Integrated Vision

     

     

     

     

     

    • 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