error using soc encounter

Hi Suresh,

It's really hard to say for sure what the issue is without knowing which command within your script is issuing the error message. Perhaps you could add "Puts" statements to your run script in order to determine which command is generating the message? Like this:

Puts "a"
loadConfig
Puts "b"
globalNetConnect gnd -type pgpin -pin gnd -all
Puts "c"

If I had to guess at the cause, it's probably that you're requesting the tool globally connect all instance pins named "gnd" to to the global net "gnd" and the tool isn't finding any instance pins named "gnd". Perhaps you could check the LEF definition for one of the cells in your design to see what the name of the ground power pins is called? Maybe it is "GND" or "VSS"?

It's also possible that you're not intentionally trying to make this connection. The .conf file can retain these connections and sometimes when you migrate a .conf file to a new library these connections are inadvertently brought along. If you suspect that to be the case, examine you .conf file for a section that looks like this:

set rda_Input(ui_pg_connections) [list \
{PIN:*.VDD:} \
{PIN:*.VSS:} \
{PIN:*.vdd!:} \
{PIN:*.gnd!:} \
{TIEHI::} \
{TIELO::} \
]
set {rda_Input(PIN:*.VDD:)} {VDD}
set {rda_Input(PIN:*.VSS:)} {VSS}
set {rda_Input(PIN:*.vdd!:)} {VDD}
set {rda_Input(PIN:*.gnd!:)} {VSS}

If that's the case, it would be good to resolve the issue by editing the .conf file (or by deleting these statements from the .conf file and redoing the global net connections within a new Encounter section).

Hope this helps,
Bob