• 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 Design
  3. Cadence schematic showing up all as yellow

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 126
  • Views 22494
  • 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

Cadence schematic showing up all as yellow

Rebekah Zhao
Rebekah Zhao over 6 years ago

While using Cadence version 5.1.0, everything in the schematic window shows up yellow (as shown in picture below). I am using x2goclient to remotely log in to the server. I tried replacing the "display.drf" file and it is still the same. Does anyone have a clue why?

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    Paste this code into the CIW (or put in a file and do load("abDebugPacket.il") to load it):

    /**************************************************************************
    *                                                                         *
    *          abDebugPacket(layer purpose @key (display "display")           *
    *                                                                         *
    * Code for debugging what packet is associated with a given layer purpose *
    *                                                                         *
    **************************************************************************/
    
    procedure(abDebugPacket(layer purpose @key (display "display")
            (cv geGetEditCellView()) "tttd")
        let((tf lp packetName packet)
            tf=techGetTechFile(cv)
            lp=tf && techGetLP(tf list(layer purpose))
            packetName=lp && techGetLPPacketName(lp)
            packet=packetName && drGetPacket(display packetName)
            printf("%s %s : %L %L\n" layer purpose packetName packet)
        )
    )
    

    Then type these three lines and post what you are getting (make sure the schematic window is the current window when you do this):

    abDebugPacket("wire" "drawing")
    abDebugPacket("device" "drawing")
    abDebugPacket("pin" "drawing")

    Thanks. This may help me to understand what's wrong.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Fariborzlp
    Fariborzlp over 6 years ago in reply to Andrew Beckett

    Hello dear Andrew,

    I have the same problem with Cadence 6.1.6. I have done your instruction but nothing is changed. Disappointed Do you know what he problem is?

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Fariborzlp
    Fariborzlp said:
    Do you know what he problem is?

    No, because you didn't post what the output was. In my response in the thread I said:

    Andrew Beckett said:
    Then type these three lines and post what you are getting (make sure the schematic window is the current window when you do this):

    So can you do that? Then I might be able to understand what is going wrong.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Fariborzlp
    Fariborzlp over 6 years ago in reply to Andrew Beckett

    Thank you for your reply, a snap shot is attached.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Fariborzlp

    OK, based on the packet names, that looks as if you must be using a schematic in a library attached to a TSMC PDK technology library. They renamed the packets used to be similar to those you're showing.

    So, what I would suggest is checking the name of the attached technology library:

    techGetTechFile(geGetEditCellView())->libName

    and then in the library manager, go to that library name and use Right Mouse->Properties. Look for the readPath and then in UNIX take a look in that directory (and most likely the one above it) to see if there's a display.drf. That's almost certainly got the packet definitions you need.

    What is odd is that this would normally get automatically loaded by the libInit.il file within the technology library - but maybe something has been changed in your environment. You probably could just copy the display.drf you find into your working directory and restart Virtuoso and see if that helps?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Fariborzlp
    Fariborzlp over 6 years ago in reply to Andrew Beckett

    Thank you for the solution, I don`t know what the problem exactly was but I could fix it by Tools->Display Resources Manager->Merge... from the icfb menu.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Fariborzlp
    Fariborzlp over 6 years ago in reply to Andrew Beckett

    Thank you for the solution, I don`t know what the problem exactly was but I could fix it by Tools->Display Resources Manager->Merge... from the icfb menu.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Children
  • Aida
    Aida over 4 years ago in reply to Fariborzlp

    Hi Fariborzlp,

    Could you please explain what files you merged. I am having the same issue that you had. I tried the Merge option but, I am not sure what to select in the options attached below

    https://www.linkpicture.com/view.php?img=LPic612f6b47a3d6b1595449656 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 4 years ago in reply to Aida

    It rather depends on what technology you're using - can you give a bit more info? The picture you posted (better to load the image in the post directly rather than elsewhere, but never mind) only showed a couple of Cadence-provided libraries - most likely you're going to have to locate the display.drf on your system somewhere. Usually most PDKs come with a display.drf and usually that would be auto-loaded when that library is used so you might need to look for a file somewhere wherever the PDK is installed.

    You may not need to merge it - you may just need to load it with Tools->Display Resource Manager, then Edit, the File->Load and navigate to the location of the display.drf.

    If you know the PDK you're using, we might be able to give you some insight as to where it is likely to be.

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • Aida
    Aida over 4 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thank you for your response! I am using TSMC 180nm. I still couldn't find the display.drf on the system.  I would appreciate it, if you give me some insight to where I will likely find the display.drf if that's possible.
    Regards,

    • 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