How to Convert Global pins( Vdd! and Gnd!) to local inputOutput pins in Schematic?

First of all, you might find it useful to look at SKILL for converting global supplies to inherited connections after VerilogIn, CDLIN, SpiceIn . Note that this doesn't quite do what you want, because this handles converting global labels on wires (e.g. vdd!, gnd!) into inherited connections, either as net expressions on the wires or as explicit pins (with net expressions too on the wires).

To answer your questions in your "suggestions" section above:

1. I assume you don't really mean "global pins" but you're using the tap cells such as the vdd and gnd components in analogLib which name the net to which they are connected?
2. The centre of the pin of the global tap components is the origin of the instance. So for a specific instance, you'd use instId~>xy (it wouldn't be terribly helpful to use cv~>instances~>xy as that will find all the other instances too)
3. dbDeleteObject(instId) will delete it.
4. Before deleting the instance, use xy=instId~>xy and then pass xy as the 6th argument to schCreatePin. I'm not sure why your pin is called "I11" in your example (that's the terminal name) - presumably something more meaningful would be useful.
5. Call schCheck(cv) afterwards to re-extract connectivity and run the schematic checks too.

"Is there any function replace an cell by a pin directly?" - No (it wouldn't be very helpful; you want to ensure the terminal and pin objects are created and replacing an instance with another wouldn't do that).

Andrew

First of all, you might find it useful to look at SKILL for converting global supplies to inherited connections after VerilogIn, CDLIN, SpiceIn . Note that this doesn't quite do what you want, because this handles converting global labels on wires (e.g. vdd!, gnd!) into inherited connections, either as net expressions on the wires or as explicit pins (with net expressions too on the wires).

To answer your questions in your "suggestions" section above:

1. I assume you don't really mean "global pins" but you're using the tap cells such as the vdd and gnd components in analogLib which name the net to which they are connected?
2. The centre of the pin of the global tap components is the origin of the instance. So for a specific instance, you'd use instId~>xy (it wouldn't be terribly helpful to use cv~>instances~>xy as that will find all the other instances too)
3. dbDeleteObject(instId) will delete it.
4. Before deleting the instance, use xy=instId~>xy and then pass xy as the 6th argument to schCreatePin. I'm not sure why your pin is called "I11" in your example (that's the terminal name) - presumably something more meaningful would be useful.
5. Call schCheck(cv) afterwards to re-extract connectivity and run the schematic checks too.

"Is there any function replace an cell by a pin directly?" - No (it wouldn't be very helpful; you want to ensure the terminal and pin objects are created and replacing an instance with another wouldn't do that).

Andrew

Thanks Andrew,

I have done the same approach.

After I execute the code , I am able to save the changes in schematic, but I am not saving its symbol view . So I am getting error over their.  schCheck(cv) is saving only schematic view. How can I save its symbolic view?

Thanks,

Sandeep

Sandeep,

schCheck() does not save anything. To save the cellView (either schematic or symbol) you would need to use dbSave(). You do not need to check a symbol for things to work - saving is enough.

Regards,

Andrew

Andrew,

I am saving the changes to Schematic. But I am having issues to the old symbol view (the symbol that is before making changes to the present schematic). For the present Schematic I have modified some pins ,It is getting changed in Schematic but getting this error.

Nand2 is the schematic I need to do changes but I am unable to save to its existing symbolic view.

Error: Terminal "ground_pin" in view schematic not found in "nand2 symbol". 

Thanks!

Presumably you should add the pins to the symbol before doing the schCheck(cv), especially if you've increased the severity of cross-view checks to "error" (the default is "warning").

Andrew