Stats

  • Replies 2
  • Subscribers 132
  • Views 609
  • Members are here 0

Update NLPlabel with Skill

DH202603191437

Hi all,

I have an issue with updating NLPlabel on given pcell from pdk. Symbol of the pcell has [@info] label, type NLPLabel. Default value for the pcell is [@libName]:[@cellName]:[@instanceName]. When I place it into schematic, it is working well and "info" label is in schematic shown like this: realLibrary:realCellName:I1. The problem is, that I would like to change it with Skill script. When I try to change it by car(selectedSet())~>info = "[@cellName][@instanceName]", it is renamed to text  "[@cellName][@instanceName]", but in schematic I see exact plain text instead of realCellName:I1 (@cellName and @instanceName are shown as text, not executed or updated to real names of instance and cell). This happens, when I try to update it directly after placing pcell to schematic. When I place pcell to schematic, change "info" label manually and then update it using skill script, it is working as expected - @instanceName and @cellName are shwon as real values.

Is there an function, how to force labels to update values? Or other way, how to udpate "info" label with executed @values. 

Thank you very much

Denis

Parents
  • Andrew Beckett

    Denis,

    Rather than setting the value of the property using inst~>info="..." you should use dbReplaceProp with something like:

    dbReplaceProp(car(selectedSet()) "info" "NLPExpr" "[@cellName]:[@instanceName]")

    By setting it directly, you're converting into a string property (it infers the property type from the type of the value). I assume the default info is an NLPExpr.

    Andrew

  • DH202603191437
    in reply to Andrew Beckett

    Hi Andrew,

    it is working well, thank you very much.

    Denis 

Reply
  • DH202603191437
    in reply to Andrew Beckett

    Hi Andrew,

    it is working well, thank you very much.

    Denis 

Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.