• 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. Slotting problems

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 91
  • Views 14838
  • 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

Slotting problems

BraveHeart
BraveHeart over 13 years ago

 Hi,

1. I was interested in knowing how can we slot wide metal connects in our automated flow of encounter, I have found an option in place and route, its a guide file which is a text file but that is an  option which is not viable.

2. How can I increase the width of the routing metals.

Thanks in advance

Aj

  • Cancel
Parents
  • wally1
    wally1 over 13 years ago

    The flow for inserting multi-cut vias for signal routes using NanoRoute is described in this solution article:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11652470

    For #2, can you clarify what you mean by "without physically connecting it to anything". Have you run SRoute to connect blocks, standard cells, IOs? addRing and addStripe are used to create the power mesh structure and SRoute is used to make the remaining connections. If you go through the tutorial below it demonstrates the flow:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:DocumentViewer;src=wp;q=Training/Digital_IC_Design/EDI11_Tutorial.html

    Lastly, if their is a rule in your DRC deck not defined in the LEF you will need to define that rule in the LEF file. The LEF/DEF Reference Manual can be found in cdnshelp or on Cadence Online Support here:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:DocumentViewer;src=pubs;q=lefdefref/lefdefref5.7/lefdefrefTOC.html

    You might check with your foundry to see if they have a technology LEF available to use.

    Regards,

    Brian

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • wally1
    wally1 over 13 years ago

    The flow for inserting multi-cut vias for signal routes using NanoRoute is described in this solution article:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:ViewSolution;solutionNumber=11652470

    For #2, can you clarify what you mean by "without physically connecting it to anything". Have you run SRoute to connect blocks, standard cells, IOs? addRing and addStripe are used to create the power mesh structure and SRoute is used to make the remaining connections. If you go through the tutorial below it demonstrates the flow:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:DocumentViewer;src=wp;q=Training/Digital_IC_Design/EDI11_Tutorial.html

    Lastly, if their is a rule in your DRC deck not defined in the LEF you will need to define that rule in the LEF file. The LEF/DEF Reference Manual can be found in cdnshelp or on Cadence Online Support here:

    http://support.cadence.com/wps/mypoc/cos?uri=deeplinkmin:DocumentViewer;src=pubs;q=lefdefref/lefdefref5.7/lefdefrefTOC.html

    You might check with your foundry to see if they have a technology LEF available to use.

    Regards,

    Brian

    • 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