• 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. SDF Errors

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 94
  • Views 17525
  • 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

SDF Errors

tswong
tswong over 14 years ago

We are performing postlayout simulation for a digital design which adopts TSMC 65nm standard cell library. During SDF back annotation by Verilog-XL 8.2, there are many SDFA errors, "Failed to find SETUP timingcheck" and "Failed to find HOLD timingcheck". But the simulation is still passed. Is it caused by mismatch Verilog model of the standard cells? or by improper EDA tools? Is it important?

Thanks!

  • Cancel
Parents
  • Scrivner
    Scrivner over 14 years ago

    The verilog models are not generated by synthesis or modified by the router. I think you might be referring to instantiations of gates in a netlist (which are synthesized and affected by the router). 

    The verilog models I was referring to are the verilog library of the standard cells. These define the funtions and behaviors of the gates instantiated in the netlist. They are used by ncverilog to simulate the instances in the netlist.

    What you need to do is look at the timingcheck section for a flop in the SDF file and compare it to the timingcheck section in the verilog model of the same cell. For each timing check in the SDF, there should be a matching timing check in the verilog model. This matching timing check in the verilog model is what the SDF back-annotates to. When there is a timing check in the SDF that does not have a matching timing check in the verilog model, there is nothing for that SDF timing check to back-annotate to. That is when you get an error or warning like the ones you are seeing.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Scrivner
    Scrivner over 14 years ago

    The verilog models are not generated by synthesis or modified by the router. I think you might be referring to instantiations of gates in a netlist (which are synthesized and affected by the router). 

    The verilog models I was referring to are the verilog library of the standard cells. These define the funtions and behaviors of the gates instantiated in the netlist. They are used by ncverilog to simulate the instances in the netlist.

    What you need to do is look at the timingcheck section for a flop in the SDF file and compare it to the timingcheck section in the verilog model of the same cell. For each timing check in the SDF, there should be a matching timing check in the verilog model. This matching timing check in the verilog model is what the SDF back-annotates to. When there is a timing check in the SDF that does not have a matching timing check in the verilog model, there is nothing for that SDF timing check to back-annotate to. That is when you get an error or warning like the ones you are seeing.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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