modifying pin names of a symbol

Zakir,

procedure( buildmysymbol()
  let((pinlist pat)
    pinlist = schSymbolToPinList("zakir_ams" "spi_top" "symbol")
    pat=pcreCompile("dig_")
    foreach(port pinlist->ports
        port->name=pcreReplace(pat port->name "dig1" 0)
        foreach(pin port->pins
            pin->name=pcreReplace(pat pin->name "dig1" 0)
        )
    )
    schPinListToSymbol("zakir" "spi_top" "symbol" pinlist)
  )
)

Regards,

Andrew.

 Thank You Sir!

  Andrew,

What I really wanted to do was a little more complex substituition. But when it did not work, I played with a  simpler substitution which was the example I posted.

if the pin name has "dig_", I need to remove it.

if the pin name has "_1v1", I need to remove it.

so  dig_tx_vcm_1v1_ch1<4:0> will become tx_vcm_ch1<4:0>

In perl I would do:

  if (/^dig_(.*)_1v1(.*)/)
 {
 $newname = $1.$2;
 print "$newname \n";
 }

I do not quite understand the pcreCompile & pcreReplace functions. Are there examples of this within the cadence documentations? If you can help with modifying the code you sent, I would appreciate it.

Or if there is a way for me to use skill to read the pin information into a file ... then I can use perl to modify the file as necessary and then use another skill script to read the modified file and regenerate the symbol. I would be comore comfortable with this but if the skill can do this just as well, I would rather learn with skill. When I just type in the icfb window, the pin list is spewed out. 

pinlist = schSymbolToPinList("zakir_ams" "spi_top" "symbol")

How do I pipe this out to a file. My attempts below did not work

 schSymbolToPinList("zakir_ams" "spi_top" "symbol") > ~/spi_pins

thanks

zakir

Zakir,

See below. You can do the same kind of things here too (pcre is "Perl Compatible Regular Expression"). Note that I also included fixing the portOrder property too - I hadn't done this before (this is the bit at the end). Probably not too critical, but thought I might as well fix that at the same time.

procedure( buildmysymbol()
  let((pinlist pat)
    pinlist = schSymbolToPinList("zakir_ams" "spi_top" "symbol")
    pat=pcreCompile("^dig_(.*)_1v1(.*)")
    foreach(port pinlist->ports
        when(pcreExecute(pat port->name)
            port->name=pcreSubstitute(pat "\\1\\2")
        )
        foreach(pin port->pins
            when(pcreExecute(pat pin->name)
                pin->name=pcreSubstitute(pat "\\1\\2")
            ) 
        )
    )
    pinlist->prop->portOrder=foreach(mapcar portName pinlist->prop->portOrder
        if(pcreExecute(pat portName)  then
            pcreSubstitute(pat "\\1\\2")
        else
            portName
        )
    ) 
    schPinListToSymbol("zakir" "spi_top" "symbol" pinlist)
  )
)

Regards,

Andrew.

 Thank You very much!!

zakir

 Andrew, On another note ... it is a different issue , I can start a new thread if you think so ..

I will take an empty schematic and instantiate a block that has a few hundred pins on it.

But I now want to automatically wire each pin  of that block to another pin that has the same identical name.

The only reason I am doing this is to have  a different symbol view.  The script is essential as it will grab each pin of the instance and wire it to an identical pin. It will eliminate human error if I try to hook it up myself.

Thanks

zakir

I'm on vacation for the next couple of weeks and won't have email or web access, and so won't be able to answer this or any other question, so I'll leave it to other folks on the forum to answer this for now. 

Kind Regards,

Andrew 

Hi Zakir,

A quick no-coding approach to this would be to use Create -> Cellview -> From Cellview to create the new schematic from the existing symbol - this will get you all of the pins and their appropriate directions in an otherwise blank cellview.  Then you can place the original symbol in this new schematic and use the option to create wire stubs for all of the pins; this option creates a wire stub on each pin with the name of the pin as a label on the wire - these wires will be logically connected to the schematic pins of the same name, so no additional wiring should be needed.[I'm assuming that you are using at least IC615]

It sounds like you aren't too concerned about the appearance of this schematic, so hopefully this suggestion will meet your needs?

Best regards,

Lawrence.

 Yes , That does do what I want in an easy way. I have it going that way now.

Thank You!

zakir