• 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. A warning when doing timing-driven NanoRoute, Urgent!

Stats

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

A warning when doing timing-driven NanoRoute, Urgent!

archive
archive over 17 years ago

#Total number of DRC violations = 2
#Total number of violations on LAYER M1 = 2
#Total number of violations on LAYER M2 = 0
#Total number of violations on LAYER M3 = 0
#Total number of violations on LAYER M4 = 0
#Total number of violations on LAYER M5 = 0
#Total number of violations on LAYER M6 = 0
#Total number of violations on LAYER M7 = 0
#Total number of violations on LAYER M8 = 0
#option droute_honor_min_feature is default to true
#    because min feature/manufacturing grid is defined in the library
#Analyzing pin access.
#Done analyzing pin access.
#WARNING (NR) No sdc file was imported, Timing Analyzer is not called.
#WARNING (NR) Total 176 pins do not have the noise margin specified, in which 176 pins are IO pins. Default rise/fall noise margins 0.400000/0.500000 have been used.
#    48 out of 48 nets are selected for further SI-fixing!

Above is an excerpt from nanoroute log file, the red characters means SDC file is not imported? But I never see setNanoRouteMode can set which SDC file to use. How can I make this WARNING disappear? Need help

BRs


Originally posted in cdnusers.org by eminemshow
  • Cancel
Parents
  • archive
    archive over 17 years ago

    I would think nano would grab the SDC file already loaded in the FE session. Did you by chance load the design without the SDC file? Also, have you compared results of timingDriven nano to non-timingDriven? We usually turn on SI prevention, but leave timingDriven off.

    - Kari


    Originally posted in cdnusers.org by Kari
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 17 years ago

    I would think nano would grab the SDC file already loaded in the FE session. Did you by chance load the design without the SDC file? Also, have you compared results of timingDriven nano to non-timingDriven? We usually turn on SI prevention, but leave timingDriven off.

    - Kari


    Originally posted in cdnusers.org by Kari
    • 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