• 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. trialRoute runtime even if routing only two nets

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 91
  • Views 12652
  • 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

trialRoute runtime even if routing only two nets

Nishant
Nishant over 13 years ago

hi,

We have a very weired shape block with below design info

** info: there are 24727 modules.
** info: there are 624875 stdCell insts.
** info: there are 52 Pad insts.
** info: there are 1026 macros.
** info: there are 7190 multi-height stdCell insts (2 stdCells)

the congestion number from the previous step run
Overflow: 259143 = 144067 (0.70% H) + 115077 (0.48% V) 

because trialRoute takes time and I wanted to try out insertBuffer only on two nets, I set all other nets as skipRouting but those two but still trialRoute is running since 17hrs. Below is what I'm doing and the log output from trailRoute. The encounter version is v10.12-s181_1 (64bit) 

velocity 26> set allNets [dbGet top.nets] 
velocity 26> dbSet $allNets.skipRouting true
velocity 27> dbset [dbGet -p top.nets.name TP_JtScanClk2].skipRouting false
velocity 28>  dbset [dbGet -p top.nets.name BP_TCK].skipRouting false
velocity 29> insertRepeater -rule data/repeaterStitch.rule -selNet data/stich_nets.names -outfile data/repeaterInsertion.violations -keepPort 

#################################################################################
# Design Stage: PreRoute
# Design Mode: 90nm
# Analysis Mode: non-MMMC non-OCV
# Extraction Mode: default
# Delay Calculation Options: engine=default signOff=true SIAware=false(opt)
# Switching Delay Calculation Engine to feDC
#################################################################################
*** Starting trialRoute (mem=3386.1M) ***

 

 

**WARN: (ENCDB-2078):   Output pin VDD18_TMON_S of instance PA/TMONW0_S is connected to power net PA_VDD18_TMON0_S.  This can create a short circuit if the output is 0.  Check the connectivity in the netlist.

**WARN: (ENCDB-2078):   Output pin VDD18_TMON_S of instance PA/TMONW0_P is connected to power net PA_VDD18_TMON0_S.  This can create a short circuit if the output is 0.  Check the connectivity in the netlist.

There are 0 pin guide points passed to trialRoute.

Options:  -noPinGuide

 

Nr of prerouted/Fixed nets = 648912
routingBox: (-20202000 -20652000) (20201840 20651200)
coreBox:    (-20200000 -20650000) (20199840 20649200)

 

 Thanks,

Nishant 

  • 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