Cannot update 'partName' property on copied cells

[lagos.jl]

cadence error hicreatecyclicfield

Hello all!

I am having a serious problem with Virtuoso not updating a cell's
"partName" property when making copies of it. I was advised to try
using the instance update options in the dialog window that appears
when making the copies, but they don't seem to work. So far what I
tried is as follows.

I first attempted to use the "(Update Instances) Of New Copies Only"
option on the copy cell dialog box, but for some reason it doesn't
work. The copies still bear the partName of the original cell and the
wrong names when instantiated. The Library Manager message window
doesn't report any error when I make the copies using this option:
...
Copy is doneProcessing files to be copied...
Beginning simple copy to library "Turbo_Decodificador_UMTS40".
Transfer of 8 files phase complete in 0:00:00
Performing instance update.
Start running ccpCdbaUpdtr ...
ccpCdbaUpdtr ran successfully ...
Loading all available p-cell functions
ROD pcell code loaded
Copy is done
...

I therefore tried to use the "(Update Instances) Of Entire Library"
option, but not only doesn't it also fail to solve the partName
updating problem on the copies, but I also get the following errors in
the Library Manager messages window:
...
Processing files to be copied...
Beginning simple copy to library "Turbo_Decodificador_UMTS40".
Transfer of 8 files phase complete in 0:00:00
Performing instance update.
Start running ccpCdbaUpdtr ...
Loading all available p-cell functions
*Error* eval: undefined function - hiCreateCyclicField
*Error* eval: undefined function - hiCreateCyclicField
*Error* eval: undefined function - hiCreateStringField
*Error* eval: undefined function - hiCreateStringField
...(about 8 more of these hiCreateStringField errors)..
*Error* eval: undefined function - hiCreateStringField
*Error* eval: undefined function - hiCreateSeparatorField
*Error* eval: undefined function - hiCreateAppForm
*Error* eval: undefined function - addToAMSMenu
ccpCdbaUpdtr ran successfully ...
ROD pcell code loaded
...

Finally -all the previous not working-, I reviewed the documentation
and according to the Library Manager User Manual it should be possible
to update a cell view by selecting it and using the "Design Manager ->
Update" command, but this command is grayed-out for all the views/
cells/libraries in my Library Manager! (I am the only one working in
this project so it's impossible that the cells could be checked out by
somebody else). Since I have never used this option before, I don't
know how to interpret this: is it because according to Cadence all the
cells are up to date and therefore no further updating is possible
(i.e., it's expected behavior), or is it really that somehow this
option is disabled in my installation? (in fact, the only non-greyed-
out options on the 'Design Manager' menu of my installation are
'Properties' and 'Update Workarea').

What could be wrong here? Could it be that I am missing some
definitions on my environment configuration scripts? Or is it maybe a
design kit bug? (BTW I'm using IC5.10.41.500.3.49 with
AustriaMicrosystems Hit-Kit v3.70 on RHEL3)

As usual, thanks so much in advance for any ideas!!!

Best regards,

 

[tsinghua]

cadence part name error

You can update the partName property manually in the symbol editor.
In the opened symbol editor, click Edit->Properties->CellView... or press the bindkey Q (Capital Q). You can see the partName property field. It bears the old property value. You can update it here. Then the displayed symbols in your schematic will update accordingly.

 

[lagos.jl]

partname cadence

Thanks for your response, tsinghua. Your solution works, but unfortunately I really need to do it in a way that can be automated, since I literally have hundreds of cells to update, and I am trying to avoid editing them manually.

I was also advised that if change the "@partName" label to "@cellName" in the symbol view, further copies of the cell will display their correct names when instantiated. This surely works, but once again it involves changing the label in every cell... Well I guess I'll just have to content with this... :|

Thanks anyway for your help!

Regards,

Jorge.