Stats

  • Replies 3
  • Subscribers 143
  • Views 488
  • Members are here 0

Skill code to automatically add cdsTerm("") in schematicSymbol view

hongjr

Hello,

I’m working on a Skill code that automatically appends cdsTerm("pin_name") in the schematicSymbol view.

I added the path to my code file in the .cdsinit, and the cdsTerm generation works correctly.

However, in all schematics, the terminals of instances are now labeled as nil, and the DC annotate voltage also shows nil.

When I comment out the code file in .cdsinit, the issue disappears.

What could be causing this problem? I’d appreciate any help or guidance.


procedure(cdsTerm()

let(()

cv = geGetEditCellView(hiCurrentWindow())

pin_name = cv~>terminals~>name

pin_xy = cv~>terminals~>pins~>figs~>children~>xy

pin_orient = cv~>terminals~>pins~>figs~>children~>orient

foreach((label_name label_xy label_orient) pin_name pin_xy pin_orient

label_x = car(car(car(car(label_xy))))

label_y = cadr(car(car(car(label_xy))))

label_or = car(car(car(label_orient)))

label = strcat("cdsTerm(\""  label_name "\")")

label_id = schCreateSymbolLabel(cv label_x:label_y+0.05 "analog pin annotate" label "centerCenter" label_or "stick" 0.0625 "ILLabel")
);foreach
);let
);procedure

Parents

  • Your function is called cdsTerm - so what's happening is that you've redefined the function (it's normally a macro). That means that when the label is displayed, it calls your function but will silently catch the errors in it so you wouldn't see that.

    Why did you call it cdsTerm? Seems an odd choice... (just call the function HongjrAddCdsTerm or something like that).

    Andrew

Reply

  • Your function is called cdsTerm - so what's happening is that you've redefined the function (it's normally a macro). That means that when the label is displayed, it calls your function but will silently catch the errors in it so you wouldn't see that.

    Why did you call it cdsTerm? Seems an odd choice... (just call the function HongjrAddCdsTerm or something like that).

    Andrew

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.