• 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. SOC Encounter :: Layout Routing Issues

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 92
  • Views 14898
  • 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

SOC Encounter :: Layout Routing Issues

Sohaib Qazi
Sohaib Qazi over 13 years ago

Hi

I am facing a problem with the layout generated by Encounter. I am unable to route the design properly. After setting up the Floorplan of the design when I place the Standard Cells, it also routes the metals and the metals are overlapped. Also it doesn't use the standard rules like using M1 Horizontal and M2 Vertical. I am not sure why it does so and how could I overcome this issue.

I am attaching a pic of the layout as well.

SOC Encounter Layout Issue

  • Cancel
Parents
  • Sohaib Qazi
    Sohaib Qazi over 13 years ago

     

     I am unable tofigure out the problem. When I run the nanoRoute then I get an error and I am unable to get through this also 

     I get some Warnings and Errors,

    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M1 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M1 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M2 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M2 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M3 is ignored
    #WARNING (EMS-27) Message (NRDB-318) has exceeded the current message display limit of 20.
    #To increase the message display limit, refer to the product command reference manual.
    #WARNING (NRDB-2005) SPECIAL_NET vdd has special wires but no definition for instance-pin connection. This will cause routability problems later.
    #WARNING (NRDB-2005) SPECIAL_NET gnd has special wires but no definition for instance-pin connection. This will cause routability problems later.
    #NanoRoute Version v10.10-p002 NR101202-1141/USR66-UB
    #WARNING (NREX-28) The height of the first routing layer M1 is 0.000000. It should be larger than 0.000000
    #WARNING (NREX-29) The metal thickness of routing layer M1 is 0.000000. It should be larger than 0.0. Add this to the technology information for better accuracy.
    #WARNING (NREX-30) Please also check the height and metal thickness values for the routing layers heigher than routing layer M1
    #WARNING (NREX-4) No Extended Cap Table was imported. Not enough process information was provided either and default Extended Cap Table database will be used.
    #WARNING (NRDB-2040) Rule LEF_DEFAULT doesn't specify any vias that satisfy a minimum area rule on M2 M3 M4 M5 M6 M7
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M1 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M2 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M3 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M4 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (EMS-27) Message (NRDB-778) has exceeded the current message display limit of 20.
    #To increase the message display limit, refer to the product command reference manual.
    #WARNING (NRDB-2040) Rule virtuosoDefaultSetup doesn't specify any vias that satisfy a minimum area rule on M2 M3 M4 M6
    # M1           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.180
    # M2           V   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M3           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M4           V   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M5           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M6           V   Track-Pitch = 10.000    Line-2-Via Pitch = 0.800
    # M7           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.800
    # AP           V   Track-Pitch = 10.000    Line-2-Via Pitch = 5.000
    #ERROR (NRDB-158) There is no default via from LAYER M1 to LAYER M2 in RULE LEF_DEFAULT.
    #Cpu time = 00:00:01
    #Elapsed time = 00:00:01
    #Increased memory = 1.00 (Mb)
    #Total memory = 308.00 (Mb)
    #Peak memory = 342.00 (Mb)
    #WARNING (NRIF-19) Fail to complete globalDetailRoute on Tue Feb 14 14:30:07 2012

    How can I resolve this issue ????

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

     

     I am unable tofigure out the problem. When I run the nanoRoute then I get an error and I am unable to get through this also 

     I get some Warnings and Errors,

    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M1 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M1 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M2 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M2 is ignored
    #WARNING (NRDB-318) MINIMUMCUT rule specifying 1 (<= 1) cuts for LAYER M3 is ignored
    #WARNING (EMS-27) Message (NRDB-318) has exceeded the current message display limit of 20.
    #To increase the message display limit, refer to the product command reference manual.
    #WARNING (NRDB-2005) SPECIAL_NET vdd has special wires but no definition for instance-pin connection. This will cause routability problems later.
    #WARNING (NRDB-2005) SPECIAL_NET gnd has special wires but no definition for instance-pin connection. This will cause routability problems later.
    #NanoRoute Version v10.10-p002 NR101202-1141/USR66-UB
    #WARNING (NREX-28) The height of the first routing layer M1 is 0.000000. It should be larger than 0.000000
    #WARNING (NREX-29) The metal thickness of routing layer M1 is 0.000000. It should be larger than 0.0. Add this to the technology information for better accuracy.
    #WARNING (NREX-30) Please also check the height and metal thickness values for the routing layers heigher than routing layer M1
    #WARNING (NREX-4) No Extended Cap Table was imported. Not enough process information was provided either and default Extended Cap Table database will be used.
    #WARNING (NRDB-2040) Rule LEF_DEFAULT doesn't specify any vias that satisfy a minimum area rule on M2 M3 M4 M5 M6 M7
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M1 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M2 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M3 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (NRDB-778) No multicut vias are defined for LAYER M4 in RULE LEF_DEFAULT. When a LEF MINIMUMCUT rule is defined for a layer, you must define multicut vias for the layer in the LEF file. Edit your LEF file and read it in again.
    #WARNING (EMS-27) Message (NRDB-778) has exceeded the current message display limit of 20.
    #To increase the message display limit, refer to the product command reference manual.
    #WARNING (NRDB-2040) Rule virtuosoDefaultSetup doesn't specify any vias that satisfy a minimum area rule on M2 M3 M4 M6
    # M1           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.180
    # M2           V   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M3           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M4           V   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M5           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.200
    # M6           V   Track-Pitch = 10.000    Line-2-Via Pitch = 0.800
    # M7           H   Track-Pitch = 10.000    Line-2-Via Pitch = 0.800
    # AP           V   Track-Pitch = 10.000    Line-2-Via Pitch = 5.000
    #ERROR (NRDB-158) There is no default via from LAYER M1 to LAYER M2 in RULE LEF_DEFAULT.
    #Cpu time = 00:00:01
    #Elapsed time = 00:00:01
    #Increased memory = 1.00 (Mb)
    #Total memory = 308.00 (Mb)
    #Peak memory = 342.00 (Mb)
    #WARNING (NRIF-19) Fail to complete globalDetailRoute on Tue Feb 14 14:30:07 2012

    How can I resolve this issue ????

    • 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