Stats

  • Locked Locked
  • Replies 10
  • Subscribers 91
  • Views 17248
  • 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

Filler cells placed outside EndCap

stevemc

 My design has an area of placement blockage in one corner. In the core rows along this blockage, I get endcaps which are spaced away from the blockage, causing filler cells to eventually be placed at the end of the row, outside the endcap. Is this a problem with my addEndCap, addFiller, or possible addStripe?

 

Parents

  •  yeah, it sure seems that way. That's what I've been primarily messing with. Unfortunately for me, someone else wrote the tcl, and I'm not too familiar with the subtleties of the commands. What I have now is an addStripe followed by an sroute, so I'm not sure what it's doing.

     

               addHorzStripe GND M2 M2 M2 M2 M3 0.36 5.76 $YMIN
              addHorzStripe Vdd M2 M2 M2 M2 M3 0.36 5.76 [expr $YMIN + 2.88]
              # extend M2 strip to close to macro boundray
              sroute \
                -corePinLayer 2 \
                -layerChangeBotLayer 2 \
            -connect { corePin floatingStripe } \
                -straightConnections { straightWithDrcClean } \
            -stopStripeSCPin { boundaryWithPin }

     

     

      # Draw a horizontal power stripe
    proc addHorzStripe {NET LAYER BLOCK_BOT BLOCK_TOP VIA_BOT VIA_TOP \
                        WIDTH PITCH YOFFSET} {
        global YMAX
        addStripe \
            -nets $NET \
            -layer $LAYER \
            -direction horizontal \
            -width $WIDTH \
            -spacing 0.24 \
            -set_to_set_distance $PITCH \
            -start_y [expr $YOFFSET-$WIDTH/2] \
            -stop_y  [expr $YMAX+$WIDTH/2] \
            -allow_jog_block_ring 0 \
            -allow_jog_padcore_ring 0 \
            -max_same_layer_jog_length 0.0 \
            -merge_stripes_value 0.0 \
            -block_ring_bottom_layer_limit $BLOCK_BOT \
            -block_ring_top_layer_limit $BLOCK_TOP \
            -stacked_via_bottom_layer $VIA_BOT \
            -stacked_via_top_layer $VIA_TOP \
            -create_pins 0 \
            -extend_to design_boundary
    }

     

     

     

Reply

  •  yeah, it sure seems that way. That's what I've been primarily messing with. Unfortunately for me, someone else wrote the tcl, and I'm not too familiar with the subtleties of the commands. What I have now is an addStripe followed by an sroute, so I'm not sure what it's doing.

     

               addHorzStripe GND M2 M2 M2 M2 M3 0.36 5.76 $YMIN
              addHorzStripe Vdd M2 M2 M2 M2 M3 0.36 5.76 [expr $YMIN + 2.88]
              # extend M2 strip to close to macro boundray
              sroute \
                -corePinLayer 2 \
                -layerChangeBotLayer 2 \
            -connect { corePin floatingStripe } \
                -straightConnections { straightWithDrcClean } \
            -stopStripeSCPin { boundaryWithPin }

     

     

      # Draw a horizontal power stripe
    proc addHorzStripe {NET LAYER BLOCK_BOT BLOCK_TOP VIA_BOT VIA_TOP \
                        WIDTH PITCH YOFFSET} {
        global YMAX
        addStripe \
            -nets $NET \
            -layer $LAYER \
            -direction horizontal \
            -width $WIDTH \
            -spacing 0.24 \
            -set_to_set_distance $PITCH \
            -start_y [expr $YOFFSET-$WIDTH/2] \
            -stop_y  [expr $YMAX+$WIDTH/2] \
            -allow_jog_block_ring 0 \
            -allow_jog_padcore_ring 0 \
            -max_same_layer_jog_length 0.0 \
            -merge_stripes_value 0.0 \
            -block_ring_bottom_layer_limit $BLOCK_BOT \
            -block_ring_top_layer_limit $BLOCK_TOP \
            -stacked_via_bottom_layer $VIA_BOT \
            -stacked_via_top_layer $VIA_TOP \
            -create_pins 0 \
            -extend_to design_boundary
    }

     

     

     

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.