• 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. Functional Verification
  3. Gate Level Sim - SDF annotation debug

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 66
  • Views 6584
  • 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

Gate Level Sim - SDF annotation debug

andymont
andymont over 12 years ago

Hi, 

I am trying to annotate an SDF to my gate level synthesis netlist and I am seeing some strange behaviour.

When I annotate using just the netlist, cell_lib and sdf , everything works fine. However, when I try to annotate using the testbench and providing the full scope to the netlist within the verification environment (SCOPE=test_env.<scopetodigtop>.udig_top), I see thousands of 

SDFNEP, SDFNET errors. The paths and timing checks which ncelab is complaining about definitely do exist in the cell_lib verilog, and the scope is definitely correct. I have tried modifying the scope just to make sure that it was correct and with anything apart from these settings the annotator complains that the scope is incorrect and refuses to proceed.

What am I missing and what is the best way to debug this ?

I have tried versions incisiv/11.10.011, incisiv/12.10.011 and incisiv/12.20.008 

thanks

Andy 

  • Cancel
Parents
  • andymont
    andymont over 12 years ago
    Found the issue. My run script had inherited a '-delay_mode unit' switch which for some reason meant that Incisiv knew nothing about the timing checks. The warnings make sense when you know the solution but they're not very helpful during debug. Problem solved! Andy
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • andymont
    andymont over 12 years ago
    Found the issue. My run script had inherited a '-delay_mode unit' switch which for some reason meant that Incisiv knew nothing about the timing checks. The warnings make sense when you know the solution but they're not very helpful during debug. Problem solved! Andy
    • 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