• 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. WIDE METAL ROUTES

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 13126
  • 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

WIDE METAL ROUTES

tiEngr
tiEngr over 14 years ago

Hi All,

I want to change M3 to a wide metal. Dont want to use NON-DEFAULT RULES because I want to have all M3 3.3um wide. I tried and it leaves some M3 as DEFAULT where ever there is congestion.

Only info I have is that M3 WIDTH=3.3 and MIN SPACING = 3.3 , INTRA SPACING = 3.3

What will be the correct number to define PITCH, OFFSET and  SPACING RANGE. So that I will  no warings for trial route and identify congestion before detail route. 

 LAYER METAL3
  TYPE ROUTING ;
  DIRECTION HORIZONTAL ;
  PITCH   X ;
  OFFSET  X ;
  WIDTH   3.3 ;
  SPACING 3.3 ;
  SPACING X RANGE 15 10000 ;
  AREA X ;
  ANTENNAAREARATIO 100 ;
  ANTENNADIFFAREARATIO PWL ( ( 1 100 ) ( 10 1000 ) ( 100 10000 ) ) ;
END METAL3

 

Thanks,

Irfan

 

  • Cancel
Parents
  • Kari
    Kari over 14 years ago

     This is not something that's typically done, but you'll have to check your process Design Rule Manual for the spacing range details. For the PITCH and OFFSET, you'll have to make sure that these allow your new M3 to line up properly with the other layer pitches and do not lead to DRC violations.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 14 years ago

     This is not something that's typically done, but you'll have to check your process Design Rule Manual for the spacing range details. For the PITCH and OFFSET, you'll have to make sure that these allow your new M3 to line up properly with the other layer pitches and do not lead to DRC violations.

    • 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