• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. delete existing wire from a terminal and redraw a new one...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 143
  • Views 16885
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

delete existing wire from a terminal and redraw a new one.

AdeshNamekumar
AdeshNamekumar over 9 years ago

I'm trying to redraw all nets on the bulk terminal of all instances by deleting exisiting nets after extracting information about the net label name from them. I have the working SKILL to redraw the nets at the bulk terminal but I'm having trouble deleting the existing nets. 

if cvSch stores the cellView id. 
This is what my snippet looks like:

BulkSignals = "x y z"
BulkSignals = parseString(BulkSignals)

foreach(biasinst cvSch~>instances

; loop through all the terminals of each instance
foreach(myTerm biasinst~>instTerms
if( ( myTerm~>name == "B" ) then
biasnet = myTerm~>net~>name

if((setof(x BulkSignals (x == myTerm~>net~>name)) != nil) then
foreach(fig myTerm~>net~>figs
if(((setof(x BulkSignals (x == fig~>net~>name) ) != nil) && fig~>children != nil) then

schDelete(fig)

function call to draw the new net
)));all loops end here

The problem in using and deleting "figs" is that it has all instances of the same net name rather than just the one specific to the instance I'm presently looking at. As a result, I'm deleting 'n' number of wires at once instead of just one,

I did find a work around by including the fig~>children condition to but now I see warnings as follows:
dbGetq: object is a purged/freed object - db:0x158bb9c4

Is there an easier way I can do this? I've seen a couple of related posts but can you be more specific?


Thank you,
Adesh

  • Cancel
  • skillUser
    skillUser over 9 years ago

    Hi Adesh,

    I have not investigated this but you could try setting the "net" attribute of the instTerm - however if I recall correctly, if you set just the net in a schematic and don't update any associated label, then Check & Save will re-assign connectivity based on the label, not the net db object.  You could find the physical wire that is overlapped by the instTerm and then find the one associated label and update that - use dbGetOverlaps() to find the 'line' db object that represents the wire and then you should be able to find the attached/associated label (or textDisplay?).

    Hope this helps!

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AdeshNamekumar
    AdeshNamekumar over 9 years ago

    Hi Lawrence,

    The end goal is to redraw the wires on the bulk terminal in a different manner, hence setting the net wont help I think. I will have to extract information, delete and then redraw. 

    I tried using the dbGetOverlaps() , thanks for letting me know about it. But since the instTerm's are not always in the same order, its a pain having to find out the terminal order and then access the bulk terminal. Having done that, I'm still having to access the figs attribute since line is not a layer/property it says.

    I'm trying to modify the algorithm with what I have from the dbGetOverlaps() but still looking for a easier way to access and modify the wires instance by instance. 

    Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    I'd suggest you contact customer support, providing the code you have so far, and an example schematic and details on precisely what you're trying to do. It's quite difficult to infer that from what you've said so far - because there's rather strange terminology that you're using (I'm not sure what the order has to do with it). Also I don't know what a line layer/property means.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • AdeshNamekumar
    AdeshNamekumar over 9 years ago

    Hi Andrew,  

    Let me to try to be precise as to what I'm trying to do.

    I want to edit a schematic by redrawing nets on all bulk terminals but since the net names need to be same after redrawing, I extract information from the original schematic before deleting the original nets on these instances.

    My algorithm would be:

    foreach instance
    (
    find the bulk terminal from the instTerms
    (
    save net name from wire connected to the bulk
    delete the net on the bulk terminal
    function call to draw new net with the same net name
    ))

    To delete the bulk net, I use schDelete() and I delete the figs attribute of the net which gives me a warning saying,
    dbGetq: object is a purged/freed object - db:0x158bb9c4

    and I want to avoid this or do the task in some other way. 

    Thanks.


     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    This still isn't very precise which is why I suggested you contact customer support (you ignored that part). For a start. it's hard to understand why you want to delete and recreate it with the same net - what's the point? Also, you're talking about deleting the net - do you mean delete the all the wires on that net, or just the segments connecting to the bulk pins? Or should it delete further than that? When you are recreating the "net" (the wiring) how are you determining the geometries for that wiring?

    Note I'm not expecting you to answer these here, as without some examples of what you're trying to do, it's very hard to give specific advice. That's why I suggested contact customer support, so you can share some actual examples rather than just incomplete descriptions.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information