• 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. Custom IC Design
  3. RULE LEF_DEFAULT definition for Abstract Generator/Encounter...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 127
  • Views 2956
  • 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

RULE LEF_DEFAULT definition for Abstract Generator/Encounter/NanoRoute

eklikeroomys
eklikeroomys over 14 years ago
I am using Cadence Abstract Generator to create abstract cell views for a standard cell library. In the Verify Step, I keep getting the following error: Encounter: (NRDB-158) There is no default via from LAYER MET1 to LAYER MET2 in RULE LEF_DEFAULT. I do not know how or where to define this RULE LEF_DEFAULT, please help.
  • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    I cant find this RULE LEF_DEFAULT in the technology file
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Hello,

     Please look at the LEFDefaultRouteSpec constraint group in you technology file (that you could dump with the technology toolbox).

    All custom vias which are part of the validVia list of the LEFDefaultRouteSpec constraint group will be considered as DEFAULT.

    Thanks,

    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago

     Halo alex,

    This is an old post which has been solved already, I dont know how to remove it,

    thank you

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Sohaib Qazi
    Sohaib Qazi over 13 years ago

    Hi eklikeroomys,

     I you have resolved this issue, can you please tell me how can I resolve it as I am stuck in same error i.e. There is no default via from LAYER MET1  to LAYER MET2.

    Thanks,

    Qazi

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • stevemc
    stevemc over 13 years ago

    Alex Soyer said:
    All custom vias which are part of the validVia list of the LEFDefaultRouteSpec constraint group will be considered as DEFAULT.

     

     

    I'm not finding this to be the case. My techfile has 

       ( "LEFDefaultRouteSpec" nil "LEFDefaultRouteSpec"
        interconnect(
            ( validLayers
                ( M1 M2 M3 M4 M5 M6 M7 )
            )
            ( validVias
                ( M2_M1 M3_M2 M4_M3 M5_M4 M6_M5 M7_M6 )
            )
        ) ;interconnect

     

    and I'm still getting the error during globalDetailRoute

     #ERROR (NRDB-158) There is no default via from LAYER M1 to LAYER M2 in RULE LEF_DEFAULT.

    btw, I'm running Encounter 11.10

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RobB47
    RobB47 over 7 years ago in reply to stevemc

    I'm having a similar issue when using nanoRoute.

    When I dump my technology file, the via definitions appear to be there.  Additionally, when I place the design I can see that the tool is able to drop in the correct vias.

    I've tried creating a non default route spec, but even if I assign all nets to that NDR the tool still fails on error NRDB-158 during routing.

    Ideas on how to fix this?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to RobB47

    The Forum Guidelines ask you not to post questions in old threads - and in this case it may be better answered elsewhere. So I'd suggest you ask the question in the Digital Implementation forum, which would be more suited for NanoRoute and Innovus questions.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RobB47
    RobB47 over 7 years ago in reply to Andrew Beckett

    Thank you Andrew, I will repost as a new question.

    • Cancel
    • Vote Up 0 Vote Down
    • 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