Schematic Probe highlight thickness

You can change the definition of a packet using the SKILL function drSetPacket.

For example:

existing=drGetPacket("display" "y0")
rplaca(cdddr(existing) "thickLine")
apply('drSetPacket existing)

Or if the list manipulation is a bit unobvious there, you could do:

drSetPacket("display" "y0" "blank" "thickLine" "yellow" "yellow" "outline")

The colors, fill styles and line styles have to be names that are already in your display.drf.

Note that there is no need to ever change the display.drf in the Cadence installation; you could always create a local one (say in the working directory, or somewhere else in the "setup.loc" search path). Or you could load one using drLoadDrf().

Regards,

Andrew.

Thank you Andrew, that does the trick.

I did stumble into Solution 11010566 which illustrates as you suggest.

I am curious about one thing:

Lets say I have a display.drf that I want to share between multiple users and it lives in some shared path /common/mygroup/display.drf

Manually copying or linking in the display is somewhat clunky and it may overried someone's customizations. Is there a way to source this display.drf using SKILL only? It has been awhile since I read about setup.loc but if I remember that is part of the install area (for me this is read only).

Hi,

Yes, you can load a display.drf with the following command:

drLoadDrf

drLoadDrf(
  t_filename
  [ g_askToSave ]
) => t | nil

Description

Loads the display resource file (usually called display.drf) from any location.


Arguments

t_filename - The path and name of the display resource file (usually called display.drf).

g_askToSave - Indicates whether you want a dialog box displayed asking whether you want to save your changes when you quit the Display Resource Editor.
Valid Values: t, nil (Default: t)

Hope it helps!

Lawrence.

Hi Ange,

Which "highlite" are you talking about (i.e. which operation are you doing) - different layers are used for different things, so it's important to understand precisely what you're trying to do.

Kind Regards,

Andrew.

deleted

Virtuoso Schematic: Design->Probe->Add Net

Regards

What do you get if you type these commands in the CIW:

envGetVal("schematic" "probeHiliteLppList")
envGetVal("schematic" "probeHiliteLppString")

Note that the default graphic editor sets the equivalent variables to the "hilite" layers (hilite/drawing, hilite/drawing1, hilite/drawing2 etc), but the default for schematic is to set these to y0 to y9.

The other thing is that the layers maybe y0 to y9, but your technology file may have assigned a different packet name to them. You can find the packet name used with this SKILL code (make sure your schematic window is the current window before entering this in the CIW):

techGetLPPacketName(techGetLP(techGetTechFile(geGetEditCellView()) list("y0" "drawing")))

For one TSMC technology I'm using, this returns "winColor5dashed_LB" whereas for a GPDK-based example it returns "y0". If the packet name is different, you'd have to set that packet rather than the y0 packet.

Thanks,

Andrew.

envGetVal("schematic" "probeHiliteLppList")
envGetVal("schematic" "probeHiliteLppString")

gives error:

*WARNING* envGetVal: Could not find variable 'probeHiliteLppList'

techGetLPPacketName(techGetLP(techGetTechFile(geGetEditCellView()) list("y0" "drawing"))) gives

"winColor5dashed_L"

So

drSetPacket("display" " winColor5dashed_L " "blank" "thickLine" "yellow" "yellow" "outline")

does the trick

Thanks a lot

Ange

Ange,

Not sure why the envGetVal() doesn't work - I checked in a number of releases - it appeared in IC614, so it ought to work.

Anyway, it wasn't necessary in this case as it was the packet name which was the issue.

Kind Regards,

Andrew.