Home > Community > Forums > Digital Implementation > Segmentation fault in SoC Encounter 4.1 with Nanoroute

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Segmentation fault in SoC Encounter 4.1 with Nanoroute 

Last post Sat, Jul 22 2006 6:18 AM by archive. 4 replies.
Started by archive 22 Jul 2006 06:18 AM. Topic has 4 replies and 2085 views
Page 1 of 1 (7 items)
Sort Posts:
  • Sat, Jul 22 2006 6:18 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    Hi,
    I want to route my design in SoC Encounter and I use the follow script for Nanoroute:

    setNanoRouteMode -quiet routeFixPrewire true
    setNanoRouteMode -quiet route_selected_net_only false
    setNanoRouteMode -quiet routeWithTimingDriven false
    setNanoRouteMode -quiet routeTdrEffort 1
    setNanoRouteMode -quiet drouteFixAntenna true
    setNanoRouteMode -quiet routeWithSiDriven true
    setNanoRouteMode -quiet routeSiLengthLimit 200
    setNanoRouteMode -quiet routeSiEffort normal

    globalDetailRoute

    This work without problem.
    But as I want to avoid routing on the first layer, I also add the follow option:

    setNanoRouteMode -quiet routeBottomRoutingLayer 2

    But with this option the program report an segmentation fault.

    What's I'm doing wrong?

    Christian


    Originally posted in cdnusers.org by lets
    • Post Points: 0
  • Sun, Jul 23 2006 6:46 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    Dear Christian,
    Its not a bad idea to block M2 ( metal 2 layer ) on your design ,
    But one thing is it really possible to block whole M2 in the design think practically . NO
    how ever you can do the same by blocking M1 in your design , as STD cell pins can reach M2.

    Suggestion .
    1. Add M2 routing blockage over a region to restrict so .
    2. check placement ( and see unplaced count is = 0 )

    If you are blocking M2 for only clock nets then its OK then use
    setAttribute -net @CLOCK -bottom_preferred_routing_layer 2 -top_preferred_routing_layer 4
    setNanoRouteMode routeTopRoutingLayer 4
    setNanoRouteMode routeBottomRoutingLayer 2





    Originally posted in cdnusers.org by mohanch007
    • Post Points: 0
  • Mon, Jul 24 2006 11:28 PM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    Thank you for your answer, but I think there is a misunderstood.

    What I want is to route on layer 2-7 compared to the "normal" 1-7, so it is the first layer that I don't want to route on.

    The real problem is that the command routeBottomRoutingLayer give me a segmentation fault.
    Is there an incompatibility of this command with others Nanoroute options?

    Thanks again

    Christian


    Originally posted in cdnusers.org by lets
    • Post Points: 0
  • Tue, Jul 25 2006 2:37 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    Hi Christian,

    As Mohanch mentioned, it is impossible to route layer 1-7 if you have pin on metal1 (note: layer1 is metal1 and layer 7 is metal7).

    Most std cell pins are on metal1.

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Post Points: 0
  • Tue, Jul 25 2006 2:38 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    Hi Christian,

    As Mohanch mentioned, it is impossible to route layer 1-7 if you have pin on metal1 (note: layer1 is metal1 and layer 7 is metal7).

    Most std cell pins are on metal1.

    If you ready want to route 2-7, then you must also tell the software which net you want to route. You have to make sure those net does not need to connect to metal1 pin.

    Regards,
    Eng Han


    Originally posted in cdnusers.org by EngHan
    • Post Points: 0
  • Thu, Jul 27 2006 6:45 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    HI ,
     Since 3 years we are using Soce and i have not fased such problems ,
    Its duffecult to justify the right reason for such issues spacific to your design .
    check how are the WARNINGS and ERROR msg.  at the time of loading and running nano route.
    In practical I have even limited using some layers on all subversion of 4.1 . -NO PROBLEM .

    If possible can you please let me know on which technology and your encounter.log & cmd file ... not all only the Nano route attrebuts and reported log.

    advice  before sending more details
    1. before globaldetail  route just check  Global Route .
    and check each layer conjesion map .
    during Global route check :

    #Start data preparation...

    # #Using automatically generated gcell grid.

    # Layer Direction #Track Blocked #Gcell Blocked

    # --------------------------------------------------------------

    # Metal 1 V 10249 37.73% 466489 26.39%

    # Metal 2 H 10250 15.61% 466489 28.03%

    # Metal 3 V 10249 12.81% 466489 30.53%

    # Metal 4 H 10250 30.34% 466489 26.46%

    # Metal 5 V 8200 29.28% 466489 25.71%

    # Metal 6 H 3416 27.51% 466489 26.03%

    # Metal 7 V 1282 8.27% 466489 18.09%

    # ---------------------------------------------------------------

    # Total 53896 27.36% 3265423 24.46%

    #

    #cpu time = 00:00:09, elapsed time = 00:00:19, memory = 200.00 (Mb)

    #

    #start global routing iteration 1...

    #cpu time = 00:00:03, elapsed time = 00:00:07, memory = 202.00 (Mb)

    #

    #start global routing iteration 2...

    . . .

    #start global routing iteration 6...

    #cpu time = 00:00:14, elapsed time = 00:00:25, memory = 202.00 (Mb)

    #

    # Layer #OverCon %OverCon

    # --------------------------------------------

    # Metal 1 2 0.00%

    # Metal 2 0 0.00%

    # Metal 3 2 0.00%

    # Metal 4 0 0.00%

    # Metal 5 0 0.00%

    # Metal 6 0 0.00%

    # Metal 7 0 0.00%

    # --------------------------------------------

    # Total 4 0.00%

    #

    #Complete Global Routing.

    #Total wire length = 580805 um.

    #Total half perimeter of net bounding box = 227492 um.

    #Total wire length on LAYER M1 = 88617 um.

    #Total wire length on LAYER M2 = 294704 um.

    #Total wire length on LAYER M3 = 221670 um.

    #Total wire length on LAYER M4 = 5812 um.

    #Total wire length on LAYER M5 = 5344 um.


    2. use Routing Control ( area Route ) and try .
    [command ]
    globalRoute
    detailRoute
    globalDetailRoute

    ################## # Routing Control ##############
    #### [option]
    setNanoRouteMode -routeSelectedNetOnly false (bool)
    setNanoRouteMode -routeBottomRoutingLayer default (integer/dynamic)
     setNanoRouteMode -routeTopRoutingLayer default (integer/dynamic)
    setNanoRouteMode -routeWithEco false (bool)
    [command]
     globalDetailRoute
    detailRoute

    Best Regards,
    Mohan


    Originally posted in cdnusers.org by mohanch007
    • Post Points: 0
  • Thu, Jul 27 2006 6:46 AM

    • archive
    • Top 75 Contributor
    • Joined on Fri, Jul 4 2008
    • Posts 88
    • Points 4,930
    RE: Segmentation fault in SoC Encounter 4.1 with Nanoroute Reply

    HI ,
     Since 3 years we are using Soce and i have not faced such problems ,
    Its difficult to justify the right reason for such issues specific to your design .
    check how are the WARNINGS and ERROR msg.  at the time of loading and running nanoroute.
    In practical I have even limited using some layers on all subversion of 4.1 . -NO PROBLEM .

    If possible can you please let me know on which technology and your encounter.log & cmd file ... not all only the Nanoroute attributes and reported log.

    advice  before sending more details
    1. before globaldetail  route just check  Global Route .
    and check each layer congestion map .
    during Global route check :

    #Start data preparation...

    # #Using automatically generated gcell grid.

    # Layer Direction #Track Blocked #Gcell Blocked

    # --------------------------------------------------------------

    # Metal 1 V 10249 37.73% 466489 26.39%

    # Metal 2 H 10250 15.61% 466489 28.03%

    # Metal 3 V 10249 12.81% 466489 30.53%

    # Metal 4 H 10250 30.34% 466489 26.46%

    # Metal 5 V 8200 29.28% 466489 25.71%

    # Metal 6 H 3416 27.51% 466489 26.03%

    # Metal 7 V 1282 8.27% 466489 18.09%

    # ---------------------------------------------------------------

    # Total 53896 27.36% 3265423 24.46%

    #

    #cpu time = 00:00:09, elapsed time = 00:00:19, memory = 200.00 (Mb)

    #

    #start global routing iteration 1...

    #cpu time = 00:00:03, elapsed time = 00:00:07, memory = 202.00 (Mb)

    #

    #start global routing iteration 2...

    . . .

    #start global routing iteration 6...

    #cpu time = 00:00:14, elapsed time = 00:00:25, memory = 202.00 (Mb)

    #

    # Layer #OverCon %OverCon

    # --------------------------------------------

    # Metal 1 2 0.00%

    # Metal 2 0 0.00%

    # Metal 3 2 0.00%

    # Metal 4 0 0.00%

    # Metal 5 0 0.00%

    # Metal 6 0 0.00%

    # Metal 7 0 0.00%

    # --------------------------------------------

    # Total 4 0.00%

    #

    #Complete Global Routing.

    #Total wire length = 580805 um.

    #Total half perimeter of net bounding box = 227492 um.

    #Total wire length on LAYER M1 = 88617 um.

    #Total wire length on LAYER M2 = 294704 um.

    #Total wire length on LAYER M3 = 221670 um.

    #Total wire length on LAYER M4 = 5812 um.

    #Total wire length on LAYER M5 = 5344 um.


    2. use Routing Control ( area Route ) and try .
    [command ]
    globalRoute
    detailRoute
    globalDetailRoute

    ################## # Routing Control ##############
    #### [option]
    setNanoRouteMode -routeSelectedNetOnly false (bool)
    setNanoRouteMode -routeBottomRoutingLayer default (integer/dynamic)
     setNanoRouteMode -routeTopRoutingLayer default (integer/dynamic)
    setNanoRouteMode -routeWithEco false (bool)
    [command]
     globalDetailRoute
    detailRoute

    Best Regards,
    Mohan


    Originally posted in cdnusers.org by mohanch007
    • Post Points: 0
Page 1 of 1 (7 items)
Sort Posts:
Started by archive at 22 Jul 2006 06:18 AM. Topic has 4 replies.