• 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. Is it necessary to have set_load and set_drive in SDC file...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 91
  • Views 3182
  • 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

Is it necessary to have set_load and set_drive in SDC file, when IO libary is used for P&R

Greatrebel
Greatrebel over 15 years ago

I am designing P&R for a project using Encounter.I modified the netlist of the design, created a top dummy module which contains both the core design and IO cells. After I input the design, I got a lot of errors like the ones below.

**ERROR: (TCLCMD-917):    Cannot find 'ports' that match 'clk' (File results/matrix.sdc, Line 15).

The reason I got those errors is because I have some set_drive and set_load commands in the SDC file and there is no ports for the top dummy module in the netlist. I am wondering whether set_load and set_drive are still needed in SDC file, if IO cell library is included as Encounter P&R design input. Or I need to add a port list for the dummy top module.

 

Thanks in advance

 

  • Cancel
  • BobD
    BobD over 15 years ago

    Now that you have the IO cells in the design, the loads and drive strengths should be characterized by the .lib models for the IO cells.  The timing constraints previously used to model these things can be safely removed.

    Hope this helps,
    Bob

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Greatrebel
    Greatrebel over 15 years ago
    Thank you very much for your help, Bob
    • 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