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

#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
Parents

  • Posted By Kari on 6/20/2008 2:29 PM
    What version do you see this in? It appears to be a bug in older versions, where this message was printed, but the SDC is in fact read in and timing-driven routing is still performed. In the rest of the route log, do you see timing numbers?

    - Kari

    I am now using SOC-E 52 update 5. This version of Encounter also will issue a warning if I didn't give it the '.timing.tif' file, that why I use the 'writeDesignTiming' command 1st to generate a timing file. By the way, I didn't see any timing numbers after NanoRoute, just see a WNS at the very beginning of the globalDetailRoute phase, I think this is the result NanoRoute parsed from the '.timing.tif' file.

    BRs


    Originally posted in cdnusers.org by eminemshow
Reply

  • Posted By Kari on 6/20/2008 2:29 PM
    What version do you see this in? It appears to be a bug in older versions, where this message was printed, but the SDC is in fact read in and timing-driven routing is still performed. In the rest of the route log, do you see timing numbers?

    - Kari

    I am now using SOC-E 52 update 5. This version of Encounter also will issue a warning if I didn't give it the '.timing.tif' file, that why I use the 'writeDesignTiming' command 1st to generate a timing file. By the way, I didn't see any timing numbers after NanoRoute, just see a WNS at the very beginning of the globalDetailRoute phase, I think this is the result NanoRoute parsed from the '.timing.tif' file.

    BRs


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