connectivity check after p&R

I am running First Encounter v06.10-p005_1 (7/2006) for Linux. I am using ARM 90nm wirebond for the I/O and want to do the power planning.

I create the global power nets with:
globalNetConnect VDD -type pgpin -pin VDD -inst * -override -verbose
globalNetConnect VSS -type pgpin -pin VSS -inst * -override -verbose
globalNetConnect VDD -type tiehi -inst * -override -verbose
globalNetConnect VSS -type tielo -inst * -override -verbose

Then I route the special nets and followpins with:
sroute -noCorePins -noPadRings -noBlockPins -noStripes -jogControl { preferWithChanges differentLayer } -nets {VSS VDD}

After this is complete, I run verify connectivity and get:
Net VDD: unconnected terminal, special open, antenna.
Net VSS: unconnected terminal, special open, antenna.

I think it is because of this that I have problems routing the tie high/low pins because the entire VDD/VSS nets are open/unconnected. Am I missing something obvious?

not sure what you are trying to connect if you used "-noCorePins -noPadRings -noBlockPins -noStrips". If you just want to have only M1 follow pin then it is ok. With that, all the M1 follow pins are not connected since you told "sroute" not to connect them thru either padRing or Strips and you will have open VSS/VDD nets.

li siang

Sorry, the sroute command was one of a series from the script. Later it was called with:
sroute -noPadRings -jogControl { preferWithChanges differentLayer } -nets { VSS VDD }

I solved the problem, actually. I had several blocks with block rings and there were stripes that were routed very close to the block rings. The followpins were routing to the stripes and not the block rings causing the open net. By increasing the value of the -merge_stripes_value option for addStripe, stripes that are too close to the block rings will merge and the problem was solved.

Thank you for your help.

Hi everyone,

I have the same problem of conectivity too:

Design Name: cordic
Database Units: 1000
Design Boundary: (0.0000, 0.0000) (1267.7200, 1267.7200)
Error Limit = 1000; Warning Limit = 50
Check all nets
Net vdd: special open.
Net gnd: special open.

Begin Summary
    4 Problem(s) [200]: Special Wires: Pieces of the net are not connected together.
    4 total info(s) created.
End Summary

End Time: Sat Mar 27 12:24:01 2010
******** End: VERIFY CONNECTIVITY ********
  Verification Complete : 4 Viols.  0 Wrngs.

Then I've used the following command:

 sroute -noPadRings -jogControl { preferWithChanges differentLayer } -nets { gnd vdd}

but the terminal said that:

Begin power routing ...
**WARN: (SOCSR-1254):    Net vdd does not have block pins to be routed. Please check net list.
**WARN: (SOCSR-1256):    Net vdd does not have CORE class pad pins to be routed.
    Please check net list or port class.
Net vdd does not have AREAIO class pad pins to be routed.
    Please check net list or port class.
**WARN: (SOCSR-1254):    Net gnd does not have block pins to be routed. Please check net list.
**WARN: (SOCSR-1256):    Net gnd does not have CORE class pad pins to be routed.
    Please check net list or port class.
Net gnd does not have AREAIO class pad pins to be routed.
    Please check net list or port class.
 

 Would you please tell me where is the source of this error? 

Thank you very much.