• 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. Fixing Process Antenna Violations using Nanoroute

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 92
  • Views 16764
  • 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

Fixing Process Antenna Violations using Nanoroute

Utkarsh03
Utkarsh03 over 5 years ago

Hi,

I am getting 47 Process Antenna Violations after routing my design, all these violations are on intermediate layers. When I try to run Nanoroute(modes mentioned below), it does not adds any antenna diode to fix the violations, please suggest how to clean these violations using Nanoroute. 

-dbAdjustAutoViaWeight true # bool, default=true
-dbAllowInstanceOverlaps false # bool, default=false
-dbIgnoreFollowPinShape false # bool, default=false
-dbProcessNode {} # string, default=""
-dbRcExtractionCorner {} # string, default=""
-dbSkipAnalog false # bool, default=false
-dbViaWeight {} # string, default=""
-drouteAntennaEcoListFile {} # string, default=""
-drouteAutoStop true # bool, default=true
-drouteEndIteration 0 # int, default=0
-drouteFixAntenna true # bool, default=true, user setting
-drouteFixViaDensityViolationAfterViaSwap false
# bool, default=false
-drouteMaskOnlyOnLayer false # string, default=false
-drouteMinLengthForWireSpreading 0 # string, default=0
-drouteMinLengthForWireWidening 1 # float, default=1
-drouteMinSlackForWireOptimization 0 # float, default=0
-drouteNoTaperInLayers {} # string, default=""
-drouteNoTaperOnOutputPin false # ternary, default=false
-drouteOnGridOnly none # string, default=none
-droutePostRouteLithoRepair false # bool, default=false
-droutePostRouteSpreadWire 1 # string, default=auto, user setting
-droutePostRouteSwapVia false # string, default=false
-droutePostRouteSwapViaPriority auto # string, default=auto
-droutePostRouteWidenWire none # string, default=none
-droutePostRouteWidenWireRule {} # string, default=""
-drouteSearchAndRepair true # bool, default=true
-drouteSignOffEffort high # string, default=high
-drouteStartIteration 0 # int, default=0, user setting, obsoleteWarn
-drouteUseMultiCutViaEffort low # string, default=low
-envNumberFailLimit 0 # int, default=0
-envNumberProcessor 1 # int, default=1
-envNumberWarningLimit 0 # int, default=0
-envThirdPartyData false # bool, default=false
-hfrouteConstraintFile {} # string, default=""
-hfrouteConstraintGroups {} # string, default=""
-hfrouteMatchReportFile {} # string, default=""
-hfrouteNumReserveLayers 1 # int, default=1
-hfrouteRemoveFloatingShield false # bool, default=false
-hfrouteSearchRepair false # string, default=false
-hfrouteShieldTrimLength 0 # float, default=0
-routeAllowPinAsFeedthrough true # string, default=true
-routeAntennaCellName ANTENNA_T3_12T_DG24RVT
# string, default="", user setting
-routeAntennaPinLimit 1000 # int, default=1000
-routeBottomRoutingLayer 0 # int, default=0
-routeConcurrentMinimizeViaCountEffort medium
# string, default=medium
-routeConnectToBump false # bool, default=false
-routeDesignFixClockNets false # bool, default=false
-routeDesignRouteClockNetsFirst true # bool, default=true
-routeEnableNdrSiLimitLength false # string, default=false

-routeEnforceNdrOnSpecialNetWire false # string, default=false
-routeExtraViaEnclosure 0 # float, default=0
-routeFixTopLayerAntenna true # bool, default=true
-routeHonorPowerDomain false # bool, default=false
-routeIgnoreAntennaTopCellPin true # bool, default=true
-routeInsertAntennaDiode true # bool, default=false, user setting
-routeInsertDiodeForClockNets false # bool, default=false
-routeRelaxedNdrSpacingToPGNets none # string, default=none
-routeReserveSpaceForMultiCut false # bool, default=false
-routeReverseDirection {} # string, default=""
-routeSelectedNetOnly false # bool, default=false
-routeShieldCrosstieOffset {} # string, default=""
-routeStrictlyHonorNonDefaultRule false # string, default=false
-routeStripeLayerRange {} # string, default=""
-routeTieNetToShape auto # string, default=auto
-routeTopRoutingLayer 0 # int, default=0
-routeTrimPullBackDistanceFromBoundary {}
# string, default=""
-routeTrunkWithClusterTargetSize 1 # int, default=1
-routeUnconnectedPorts false # bool, default=false
-routeWithEco true # bool, default=false, user setting
-routeWithLithoDriven false # bool, default=false
-routeWithSiDriven false # bool, default=false, user setting
-routeWithSiPostRouteFix false # bool, default=false, user setting, private
-routeWithTimingDriven false # bool, default=false, user setting
-routeWithViaInPin false # string, default=false
-routeWithViaInPinSingleMask false # bool, default=false
-routeWithViaOnlyForMacroCellPin false # string, default=false
-routeWithViaOnlyForStandardCellPin false
# string, default=false
-timingEngine CTE # string, default=CTE, user setting, private

Thanks

Utkarsh

  • Cancel
Parents
  • Chaitu88
    Chaitu88 over 5 years ago

    Hi Utkarsh, were you able to find resolution for these violations?

    If so, can you share across?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Utkarsh03
    Utkarsh03 over 5 years ago in reply to Chaitu88

    Hi

    I raised this concern to the Cadence Support. There we figured out that the techlef & lef that I was using was having incorrect ANTENNA definitions.

    Thanks

    Utkarsh

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Utkarsh03
    Utkarsh03 over 5 years ago in reply to Chaitu88

    Hi

    I raised this concern to the Cadence Support. There we figured out that the techlef & lef that I was using was having incorrect ANTENNA definitions.

    Thanks

    Utkarsh

    • 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