Stats

  • Locked Locked
  • Replies 6
  • Subscribers 90
  • Views 15109
  • 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

Segmentation fault in SoC Encounter 4.1 with Nanoroute

archive

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
Parents

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